28 August 2026 / 7 min read
What a booking and contract system actually needs to do
A practical requirements list for any business that takes bookings and issues paperwork, drawn from building one that runs daily.
- cms
- operations
- internal tools
Most booking software is a calendar with invoicing bolted on. Businesses that book people, venues or time need something closer to a small operating system.
The short answer
A booking system earns its money when one record carries an enquiry through to a paid invoice: availability, terms, contract, schedule, payment and follow-up all reading the same data, with nothing retyped.
The non-negotiables
- One record per booking. Everything else — documents, payments, messages — hangs off it.
- A real status model. Enquiry, held, confirmed, delivered, invoiced, paid. Each with rules about what can change.
- Availability that reflects reality. Provisional holds, travel time, blackout dates.
- Documents generated from data. Contracts, itineraries and invoices built from the record, not from a template someone edits by hand.
- Money. Fees, splits, commissions, deposits, VAT, currency where relevant.
- Permissions. Who can see margin, who can approve a discount, who can only read.
- History. Who changed what and when. This settles disputes.
- Follow-up. Prompts for the things that quietly lose revenue: unsigned contracts, unpaid deposits, no post-event contact.
The parts people forget
| Forgotten thing | Why it hurts later |
|---|---|
| Cancellations and reschedules | Half of all edits are these; retro-fitting them is expensive |
| Amendments to signed paperwork | Version confusion becomes a legal problem |
| Partial payments | Deposits, instalments, refunds |
| Multiple contacts per client | Agent, finance, on-the-day contact |
| Exports | Accountants want their format, not yours |
| Deleting data properly | Somebody will ask you to |
How to specify one without writing a spec
Describe a real booking out loud, from first email to final payment, and write down every document, decision and person involved. That narrative is the specification. Then do it again with the worst booking you have ever had — the one that moved twice and changed venue. The second story is where the money goes.
Build or buy
Buy if your bookings are simple and uniform. Build when your terms, splits or paperwork are part of how you compete. We built the Kruger Cowne system precisely because a talent business has none of the shapes generic booking tools assume.
Read bespoke CMS and databases for how we approach it, or try the placement CRM demo in the lab to see a pipeline and generated contract working in the browser.