A day in the life of EventLock

Riley is planning an autumn dinner for sixty-four people at the Orchid House on Friday, October 23. She finds your form on your website or from a link in your bio. She fills in the date, the venue, how many guests, and what she is hoping for. She hits send from her couch.

On your end it lands in your request inbox already structured: contact, date, place, and the details you would normally have to ask for on the phone. You are alerted. You read it in thirty seconds and go back to your evening.

Open the request, tap Create Proposal, and her name, the date, the venue, and her notes are already in it. If you have set up your services and products, they are already on the proposal. Set the deposit, set what each role pays the person doing it. The math is done for you.

If you are adding a service you have never written up, type its name. EventLock drafts the description your client reads, the contract notes for the proposal, and the notes your contractor will need. You review it, change what you want, and save it. Nothing goes out until you say so.

She gets a private link. On her phone she sees the services, the amounts, the date and time, and the venue. She has a question about parking at the Orchid House, so she asks it right there in the message thread, and you answer from wherever you are.

Before she signs, she reads and acknowledges your cancellation and reschedule terms. Then she signs. The signed proposal becomes the booking record, with a contract number, and the deposit is now due. She can pay it by card through your connected Stripe account, or you can record a Zelle, Venmo, or check payment when it arrives. Either way, the job shows deposit paid.

The dinner needs someone on site to run the evening and a caricature artist for the cocktail hour. You send a direct offer to your first-choice coordinator. For the caricature role you post an open call to the people on your roster who do that work. Open calls only go to contractors who work in the area of the event. The first one to accept gets it, and anyone after that lands on the waitlist.

Each contractor sees the date, the time, the city, the pay for their role, and your instructions. They do not see the client's name or street address until the job is confirmed. They accept or pass in one tap. You see who answered and who you are still waiting on, without a single phone call.

Most days you open EventLock, look at the Action Center, and close it. It shows only what needs a decision: a signature still waiting, a deposit due, a role not yet filled, a balance coming up.

The Thursday before the dinner, Riley asks to start an hour later. She sends the request from her own booking page. You see the new time, your contractors are flagged to reconfirm, and your reschedule terms are applied the way you set them. Nobody has to dig through a thread to remember what was agreed.

EventLock syncs with Google Calendar, warns you when a new booking conflicts with something already on it, and puts every confirmed job on your phone's calendar. Apple Calendar is coming soon.

Your coordinator taps On my way. Twenty minutes later, Arrived. You are across town at a different job, and you know both of your people are where they should be without texting either of them.

The balance was due after the event. It came in by card through Stripe, so the job reads paid in full. You mark each contractor's pay as paid when you send it, so you and they both know where it stands. Every message, the signed agreement, the payments, and the people are still attached to that one job if you ever need them again.

Total time you spent running the paperwork on this booking, start to finish: about as long as it took to read this page.