← Bookings, calendars and scheduling
Can my app stop two people from booking the same time?
Short answer
Yes, if your AI writes that check: GilbPlatform has no booking rule, but it can refuse a change to a record someone changed meanwhile.
Before you start
Words used here (2)
- GilbPlatform
- GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
- record
- A record is one piece of data with its own address, such as a person, a place, a thing or a note.
Deeper
GilbPlatform today. GilbPlatform and GilbApp have no booking or calendar part of their own today, and no help answer shows one. So no rule of its own stops a double booking; the check is code your AI writes.
What the check does. Before a booking is saved, your app checks that nothing else is booked for that time, including longer bookings that overlap it, and, where people book staff or rooms, for that one staff member or room.
Two people at the same second. Both may see the time as free. The check must still let only one of them through. One way your AI could do it: keep each bookable time as a record, one piece of data with its own address, and mark it booked only if no one has changed it since your app read it. GilbPlatform can do that part: a change sent with the version your app read is refused if the record changed meanwhile, and your app then reads it again and shows the time as taken. The developer answer How do I write only if nothing changed (If-Match)? shows how. It works only for a change made with PUT, PATCH or DELETE at one existing record's own address, and only if that change carries the version: a PUT must, a PATCH or DELETE may leave it out and then lands anyway. Some other ways of writing ignore it, and some edits you make in GilbApp are sent without it, so your own edit there can land between your app's read and write. It does not stop two new booking records for the same time, so your AI must plan where the check sits.
Who may write. A person can mark a time booked only in a vault, the place where a person or a group keeps their records, where they, or your app's server, a computer on the internet that runs your app's own code, may write; the answer Can my app have its own users who sign in? says more.
Ask your AI to test it: two bookings for the same time, sent at once, must end with one booking. A booking service run by someone else has its own rules for this; read its pages.
Tell Kai-Zen, the planning agent, what you want; it changes the plan, and Agent.Coder, the agent that writes your app's code, builds the change. Whether you want it is your choice.
This answer is written for a computer screen.
Source: GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): no booking, calendar, e-mail-sending or timed-job route for apps in src/routes (e-mail is sent only for sign-in codes, src/auth/send-otc-email.ts, and the owner's monitor alerts). GilbApp 49b1ae53 (https://gilb.com/app/version.json, read 13 November 2026): no booking or calendar control in src. Standards: Proc_v_i_c_PublishPagesDev (a built static folder is published at https://<name>.pages.dev); Agent.Coder (GilbStack 14a: a browser-only app cannot keep a key secret). Live help page, sentences shared: Where do I keep the passwords and keys for the services my app uses? Live help pages, sentences shared: How do I write only if nothing changed (If-Match)? (read the record and keep its ETag; PUT, PATCH or DELETE with If-Match; on 412 read it again; only PUT, PATCH and DELETE at a record's own address read If-Match); Can my app have its own users who sign in?; Can my app let people book a time with me, and show my free times?
Checked against GilbApp d529620.