A wedding house takes three events a day at most, sends a crew to each one, and runs the majlis to a written order. This is what the studio side looks like once the booking calendar has a production layer under it.
The cap is enforced in the database, not in the browser, so two families can never both take the last slot on a Saturday. Blocked dates — Raya, crew leave, a week off — are struck out rather than silently unavailable.
Assigning a crew member to an event checks every other event on that date first. The warning appears while you are still assigning, which is the only moment it is cheap to fix.
This is the artefact the business actually sells. It prints, it goes in a folder, and the times are written the way a majlis is really run — after Maghrib as often as 19:30.
Quoted against what it cost to deliver — crew and suppliers — so the margin on a package is a number rather than a feeling. This is the part that changes what the next quote looks like.
The shape is real: the three-a-day cap, the crew clash check, the run-sheet builder and the job costing are all things this system does. The content is not — every name, date, package and figure on this page was made up for the demo, because a real booking holds a family's name and phone number and those never leave the client's own system.
Built by IAstudio · iastudiobn.com