Skip to main content
Kalinklo · Artists

Engagement Ledger

One record, request to settlement.

Booking a guest artist is a chain — request, hold, quote, booking, contract, invoice, settlement. The Engagement Ledger holds the whole chain as one private record, tied to the production week it belongs to, visible to the organization and the agency but never to an ordinary member.

  • Request → hold → quote → booking
  • Contract · invoice · settlement
  • Tied to the production week
  • No incumbent owns the full lifecycle
Request a pilotSee Agency OSSee pricing →

The lifecycle no one owns

Incumbents stop at contracting. The ledger goes to settlement.

OPAS adds contracting in its Pro tier; #DIESE is internal-ops focused. None hold the engagement from first request to final settlement, connected to the week the artist actually plays. That full lifecycle is open territory.

Organization side
request · hold · quote · booking · contract · invoice
Agency side
the same engagement, with its commission

Workflow sample

Illustrative

  1. Request

    Open a guest need

    open

    An organization opens a need for a soloist, guest principal, or conductor — optionally tied to a production week already on the Performance Desk.

  2. Hold → quote → book

    Move it down the chain

    advance

    Place a hold with an expiry, send a quote, confirm the booking. Each stage is a tracked state with its own timer — no spreadsheet, no lost thread.

  3. Contract → settle

    Close it cleanly

    close

    Upload the signed contract, track the invoice, record the settlement. The closed engagement stays in a private, permission-scoped archive.

What the ledger replaces

Above the inbox, not another thread

Today

Booking by email and memory

On Kalinklo

A tracked chain with stage timers

Today

“Did we ever sign that contract?”

On Kalinklo

Contract status on the engagement

Today

Invoices in a separate system

On Kalinklo

Invoice + settlement on the record

Today

No link between booking and the week

On Kalinklo

Engagement tied to the production

Today

Engagement risk invisible to leadership

On Kalinklo

Red flags in the Command Center

Access model

Money and contracts stay private

An engagement's commercials — fee, commission, contract, settlement — are visible to authorized organization staff and the agency on the other side. An ordinary orchestra member never sees engagement money or contracts. Every read is scoped server-side.

Organization staff

See their side of the engagement and the production it serves.

Agency

Sees the same engagement routed to it, with its own commission.

Members

Never see engagement money, contracts, or settlement.

Audited

Every stage transition is logged with actor and timestamp.

Get started

The Engagement Ledger records obligations and settlements. Funds move through your existing processor unless a contract states otherwise; Kalinklo does not custody payment funds by default.

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

Request a pilotSee Agency OS
Request accessSign in