Software that tracks your work will believe whatever it is told. StudioCue is built the other way round: the moments that cost money — booked, ready, delivered — cannot be reached by clicking, only by evidence. Here is what that buys you.
The points in a project's life that cost money will not move on a click. Booked, in particular, needs a signed agreement, a retainer that has cleared, a date nothing else is on, and complete client details — checked together, at the moment of booking. You can still take a job on with the retainer waived; the record then says it was waived, not that it was paid.
The gate names exactly what is missing
Overrides exist, are permissioned, and are labelled as overrides
Every check recorded with its result
It keeps working when a provider does not
No signing account? Send your own agreement and record the signature. Payments not set up? Record the transfer when it lands. The job books either way, and the record says a person vouched for it rather than pretending a provider confirmed it.
Signature recorded by the studio
Retainer recorded by the studio
Never filed as provider evidence
Nothing is quietly overwritten
The price a couple accepted, the terms they agreed, the schedule crew acknowledged: written once and kept. A change makes a new version and supersedes the old one — it does not edit history underneath the people who relied on it.
Immutable package and pricing snapshots
Versioned schedules, acknowledged per person
Superseded, never deleted
The browser is never the authority
Nothing important is decided in the page you are looking at. Bookings, invoices, permissions and the audit trail are written by the server after it checks who you are, what you are allowed to do, and whether the business rules hold.
The record collections reject browser writes outright
Every check runs again server-side
One tenant can never read another's
The same instruction twice does the same thing once
A double-tapped button, a retried request, a provider sending the same notification twice — none of it books a second job or raises a second invoice. Repeats return the original answer instead of doing the work again.
Every command carries an idempotency key
Provider notifications recorded once
Retries are free, by design
When something fails, it says so
A refused provider request is not left looking queued. The failure is shown where you are working, in words you can act on, with the way forward next to it — not discovered weeks later when a client asks.
The provider's own reason, translated
Retry, or take the manual route
Failed work never counts as done
Cue drafts. You decide.
Cue — StudioCue's assistant — will write the schedule, read the insurance certificate, and tell you what looks wrong. It will never record a payment, complete a signature, grant a permission or mark a readiness check passed — those are the four things it is structurally prevented from touching.
Extraction always leaves a human decision pending
Drafts are proposals until you send them
Charged against your plan before it runs, audited after
Twelve things happen without you
Album reminders, insurance chasing, crew offers expiring, final invoices, review requests, retries on anything a provider dropped. The work that gets forgotten in a busy season is the work nobody has to remember.
Runs on a schedule, not on your memory
Every run recorded before it acts
Nothing sent without your approval where it matters