Skip to main content
KalinkloOS

Production Record

One production, both sides of the house.

A guest artist is booked through an engagement and plays a production the organization runs. The Production Record holds both: rehearsals, parts, and readiness on one side; request, contract, invoice, and settlement on the other. Both engines share one truth instead of two systems reconciled by hand.

  • One production · both engines
  • Run the Week ↔ Manage the Engagement
  • One truth, scoped per party
  • Nothing reconciled by hand
Request accessSee Run the WeekSee pricing →

Built for Orchestras and opera companies · Festivals and presenters · Artist and management agencies · The guest artist

The production bridge

The week and the engagement, on one record.

The production sits in the middle. Operations and commercial work each attach to it and show only the authorized view. This is an illustrative layout, not real workspace data.

Season pipeline

Planning view · illustrative

Private workspace

Run the Week

The operations side

Production Desk
  • Services and call times
  • Personnel and chairs
  • Parts and rights-aware materials

The production

The shared record

One truth
  • Mahler 5 · concert week
  • Guest soloist engaged
  • Every stage logged

Manage the Engagement

The commercial side

Engagement Ledger
  • Request → hold → quote
  • Booking and contract
  • Invoice and settlement
The organization sees
its week and the engagement it runs
The agency sees
its engagement and commission, not internal operations
The member sees
only their own calls in My Week

Why one record

The booking and the week were never two things.

The artist you contract is the artist who walks on stage. When the engagement and production live in separate systems, someone reconciles them by hand. The Production Record removes that seam.

Operations
the production week the artist plays
Commercial
the engagement that put them there

Workflow sample

Illustrative

  1. Season → production

    A slot becomes a production

    plan

    A presenter or orchestra opens a season slot; it becomes a Production Desk record with its own services.

  2. Engagement → record

    The guest is engaged against it

    book

    The guest is requested, held, quoted, booked, and contracted in the Engagement Ledger attached to that production.

  3. One record, two views

    Both sides work from one truth

    run

    The organization runs the week, the agency tracks its engagement, and the member sees only their calls — each through their own permissions.

What the Production Record replaces

One record, not two systems reconciled by hand

Today

Booking separate from operations

On Kalinklo

Engagement attached to its production

Today

Which artist plays which week?

On Kalinklo

The engagement names the production

Today

Contract signed, week not updated

On Kalinklo

Both sides move on one record

Today

Reconciling two spreadsheets

On Kalinklo

One truth, scoped per party

Today

Leadership cannot see the whole picture

On Kalinklo

Readiness and engagement risk together

Access model

One record, each party's own view

A shared record does not mean shared visibility. Every read is scoped server-side.

Organization

The production week and the engagements it runs.

Agency

Only the engagement routed to it and its commission.

Member

Only their calls and cleared materials in My Week.

Audited

Every stage transition and access grant records actor and time.

Get started

Ready when you are.

Access is approval-gated and reviewed by hand. For a closer reading of this workspace, see the Help Center article.

Request accessSee Run the Week

The Production Record connects operational and commercial work. Each side is visible only to authorized parties, and money continues to move through your existing processes.

Production Record · Kalinklo