For institutions
Conservatories, universities, opera houses, museums, and festival networks run programming, residencies, masterclasses, and commissions on Kalinklo — with multi-department access, audited approvals, managed onboarding, and a procurement record that closes.
Built for Conservatories & universities · Opera houses · Museums · Festival networks
Institution sample
An institutional engagement crosses artistic, finance, venue, and committee review. The workspace keeps every step — and the reason behind each decision — on a record any reviewer can open.
Workflow sample
IllustrativeOpen
The slot names the venue, season, budget line, owner, and the artistic brief before any hold is requested.
Review
Terms are reviewed in place — no reconstruction from forwarded email attachments.
Close
The engagement reaches settlement with a procurement record the board can read end to end.
What Kalinklo replaces
Today
Engagement history trapped across departmental inboxes
On Kalinklo
One audited record per engagement, readable by any reviewer you authorise
Today
A separate tool and login for every team
On Kalinklo
Multi-department access with SSO (roadmap) and committee-based routing
Today
Approvals chased by email and remembered by hand
On Kalinklo
Approval chains recorded with actor and timestamp on every step
Today
A platform you are left to operate alone
On Kalinklo
Managed onboarding and a named contact who runs the setup with you
What this lets you do
Every engagement carries one clean chain — request, hold, quote, contract, invoice, settlement — each step logged with actor and timestamp.
Soloist engagements, masterclass series, residencies, and new-work commissions run on the same workflow with different fee models.
Add halls, studios, and auditoria; each engagement points at a venue and a budget line, and the season planner reconciles across them.
Programming reviews, finance signs, the registrar handles teaching engagements. Permissions follow committee membership, not individual logins.
Setup, season import, and migration are scoped and run with you. Custom annual agreements are available for larger institutions.
How it flows
01
Verification, then a scoped setup: departments, venues, budget lines, and the people who sign. Managed onboarding runs this with you.
02
Each venue carries capacity and an owner. Committees define who reviews, who approves, and who signs each kind of engagement.
03
Plan the season, place holds, route approvals, and reconcile invoices — producing the procurement record your board expects.
Privacy, access & compliance
Kalinklo is a private operating system, not a public marketplace. Institutional data stays inside the institution, with the controls a procurement review expects.
Institutions are admitted on documentation and onboarded by hand — never by open sign-up.
Departments and committees get scoped access. People see what their role requires, and no more.
Programming, budgets, contracts, and settlement records are never public and never indexed.
Every state change is logged with actor and timestamp. SSO (roadmap) and procurement integration are available on enterprise terms.
Get started
Access is approval-gated and reviewed by hand. For a closer reading of this workspace, see the help centre article.