Run the whole booking, from first lead to final invoice.
Catch the lead, quote it, get it signed and paid, then run the day on a live run of show. Every step of the booking, in one place.
Grouped by the part of the job each feature does, Sales CRM, Operations, Onboarding & compliance, Billing & payments, Admin and Reports, so you can read only the half you own.
Everything below is on the Professional plan. Hospitality adds the catering and back-of-house stack on top. See plans and pricing.
Professional
Hospitality
The complete event booking CRM
Everything you need to win bookings and run the events behind them. This is the core plan, and every feature below is on it.
Everything up to the signature.
The lead-driven half of the event booking CRM: capture leads from your own website, work them through a pipeline from new to won, and keep one searchable contact database behind it. Every email, phone note, appointment, quote, proposal and signed confirmation stays on the client's record, with follow-ups that send themselves and pipeline reports that show what is actually closing.
Everyone you work with, in one searchable list.
Contacts is the address book that lives across every event you ever run: caterers, AV crews, photographers, stylists, florists, drivers, account managers, clients. Bulk-import the whole lot on day one, tag people the way you actually think about them, and search the full history in one place.
- Contact records carry contact details, role, business affiliation, and an optional photo.
- Bulk-import the whole address book from a CSV in two minutes.
- Tag contacts the way you actually think about them (AV, kitchen, photographers, regulars) and filter the list down to one tag, or stack tags to narrow further.
- Define your own contact fields (text, choice lists, or file uploads), reorder them, and they appear on every contact. A field only shows on a contact once it has a value, so records stay clean.
- A per-contact Requests tab keeps every request that person has had across all your events, with their answers and uploaded files, in one read-only history.
- A per-contact Emails tab tracks every send to that person, with delivered, opened, or bounced status, so you can see whether your message actually landed.
- Search across name, business, email, and phone, with results updating as you type.
One corporate client, not five unrelated bookers.
A corporate client rarely sends you one person: the office manager books the Christmas party, someone in marketing books the product launch, and a third name is on the invoice. Each of them stays their own contact, and a company record sits above them so their leads, their bookings and their money read as one organisation.
- Companies sits under Contacts: every organisation with how many people you deal with there, how many bookings, what those bookings are worth, and the date of the most recent one. Search matches the name or the email address.
- Build it from the names you have already typed. 1pm reads the company names sitting on your contacts and offers them back as a review list. Names shared by two or more people come pre-ticked, because a name on several contacts is almost always a real organisation; names on a single contact start unticked, because those are usually a couple or a sole trader. Tick, confirm, and each becomes a company with its contacts linked.
- Link from the Company box on a contact. Start typing and matching companies appear, each showing how many people you already have there. New client? Type the name and pick 'Add as a new company' without leaving the form.
- Typing a name that matches nothing still works exactly as it always did. That is the wedding couple and the sole trader, and they carry no company record behind them.
- The company record has four tabs. Contacts: everyone you deal with there, unlinkable one by one without touching the person. Leads: every lead from the organisation, won and lost, because the ones that got away only answer "why did we stop hearing from them" if they sit beside the ones that landed. Events: every booking, with who booked it.
- Money totals the whole organisation: bookings, booked value, paid, outstanding, total invoiced, guest numbers, and the dates of their first and most recent booking. It counts tentative, confirmed and completed bookings, and leaves out leads and cancellations.
- Top clients can group by company. Three people booking three parties from the same office read as one customer worth the lot, and the "booked more than once" figure finally tells the truth about your repeat business. A client with no company keeps a row of its own, so the period total is the same either way.
- The Conversion funnel carries a By company table: how many leads each organisation sent, how many were quoted, won, lost and still open, the win rate, and what the wins were worth. Leads that all reach Quoted and stop are a pricing problem; leads that never reach Quoted are a speed one.
- Rename once and it lands everywhere. The company name is the name printed on a BEO, an invoice bill-to block, a merge field and a crew email, so a rebrand is one edit that rewrites every linked contact and lead.
- Deleting a company deletes the record and nothing else. Its contacts, leads and bookings stay exactly where they are, and each contact keeps the name it was showing. They simply stop being grouped.
- Beyond the name, a company holds the switchboard phone, the accounts inbox, a website, an address and to details block for invoicing, and internal notes that never reach a client, a crew member or a portal.
Catch every lead, and reply without leaving 1pm.
Embed your lead form on your own website and new leads land in a triage inbox, not a shared mailbox everyone half-watches. Qualify them, reply in a thread, and turn a hot lead into an event in a couple of clicks. It can even answer for you, but only on a date you could genuinely take.
- Embeddable lead form: paste one snippet onto your site. Run several named forms (weddings, corporate, functions), each with its own fields, copy, and submit button.
- Or run one form that fronts all of them. The combined form is a single link and a single snippet: the visitor picks what they are enquiring about from a dropdown, and that lead type loads its own fields and wording underneath. Nothing is chosen for them when the page loads, which is what stops a lead arriving on the wrong lead type. You choose which types appear and what each is called in the list.
- Bring your backlog with you. Import a CSV out of a spreadsheet, another CRM, or the inbox somebody has been tracking leads in. Download the template, paste your rows under it, upload. Nothing is emailed and no automation fires, because an imported file is history rather than fresh leads, and re-importing the same file is safe: a row matching an existing lead on email, event date and lead type is skipped.
- Build the form from your own contact fields (text, choice lists, dates, numbers), mark what's required, and reorder by dragging, with a live preview as you edit.
- Spam never reaches you. A hidden honeypot and optional Cloudflare Turnstile filter the bots, and the Spam tab clears itself after 30 days.
- The inbox is a pipeline: New, Qualified, Converted, and Lost tabs with live counts, plus a red badge in the sidebar the moment a lead arrives.
- Put a date on a lead and 1pm brings it back. Say when you'll chase it and what the chase is for, and it lands on your Follow-ups queue on the day. Until then it stays out of the way, which is the point of planning it rather than carrying it around in your head.
- It also names the leads nobody has planned to touch. The same queue lists qualified leads that have gone quiet for three days with nothing scheduled, counted from the last real step the lead took (the quote you sent, the quote they opened, the deposit) rather than the last email that happened to land in the thread. That is the half of a pipeline that usually disappears without anyone deciding to lose it.
- Reply in a two-way email thread without opening your mail client. The lead's reply lands straight back in the thread, live.
- Or just hit Reply in your own email client. 1pm emails you when a lead replies; answer that notification from your phone or Outlook and your message is relayed onward to the client as your venue, and logged in the thread. No app, no laptop, no copy and paste.
- Auto Reply answers a new lead for you, a set number of minutes after it lands (60 by default), with the reply template that lead type already uses. The lead that gets answered first usually wins, and leads never arrive when you are at a keyboard.
- It only replies on a date you could actually take. Before anything sends, 1pm runs the same availability check that stops a double booking: tentative, confirmed and completed bookings occupy the date, times narrow it, and a lead carrying a Space only clashes with that Space. If you are already working that day nothing goes out and the bell tells you instead, so the held reply hands you a lead that needs a human answer.
- The automatic reply can carry a real quote. Put a package on the reply template and the lead gets your words, your brochure and a live quote they can open, adjust and accept, inside the hour. A quote does not have to be exact to be useful: the client picking six hours rather than eight is a number they choose on the quote itself, so there is nothing for you to work out first. You get a notification saying who was quoted and for how much.
- You choose which lead types take part, so weddings can answer themselves while corporate leads wait for the quote only you can write. Get there first with your own reply, or mark it spam, and the automatic one quietly stands down. Every pending reply shows its due time in the inbox with a Cancel button next to it.
- Jot an internal note in the same thread (a phone call, a reminder, who to chase) that's logged against the lead and clearly marked, but never emailed to them.
- Every client-facing email lands in the same thread, badged so you can tell them apart: the auto-acknowledgement, the quote, the confirmation, the invoice, and anything an automation sent. One scroll tells you everything this client has ever been sent.
- Attach files to a reply: upload on the spot or pull a brochure, menu, or floor plan from your file library, no email client needed.
- Save reply templates with merge fields ([first name], [event date], [guests]) and drop one in with a click. Pin files to a template (that brochure or menu) and they ride along every time you use it.
- Send from your own domain. Verify it once with the DNS records 1pm hands you, and every reply and auto-acknowledgement goes out as your venue, not a noreply@. Until it's verified, mail safely falls back to a 1pm address so nothing bounces.
- Pin the files from the thread onto the event when the lead converts, so the floor plan and the running order they sent at lead are on the booking, not buried in an email.
- Capture the start and end time, the company name, and a link to an existing contact right on the lead, so a returning client is recognised before you convert rather than after.
- Convert to an event in two steps: match the lead to an existing contact (or create one), and 1pm seeds a tentative event ready to finish, with the times and contact already carried over.
- Each lead type can name a request pack, so the booking arrives already asking the client for the things that kind of job needs: a run sheet and a family photo list for a wedding, a purchase order and an AV brief for a corporate function. You wrote the list once; the lead type decides which one applies.
- Raise a quote straight off a lead and send it through the same thread. Invoices show under the quotes on the same lead, so the money story reads in one place.
Build the proposal once. Send it as a live web page.
A block builder for the pitch you send before a booking is won. Drop in your logo, write the sales copy, then add smart blocks that pull the event's own details straight off its BEO. Save it as a reusable template, link it to a lead reply, and it goes out as a branded web page instead of a PDF nobody can open on their phone.
- Build a proposal as a stack of blocks and drag them into any order. Save it as a reusable template, so the wedding pitch and the corporate pitch each live once and get reused on every lead.
- Static blocks carry your own words: a Logo, a rich Text block (headings, bold, bullet lists), and an Image pulled from your Files library.
- Smart blocks pull live event data, so the proposal is never out of date: the event details, the Venue, the BEO header (access and vacate, service and setup), the Menu, food and beverage, AV notes, and Pricing. Change the event and every proposal for it follows.
- A Schedule block shows a curated client timeline: star the run of show items you want the client to see and only those appear, time and title, never the full back-of-house run of show.
- Drop merge fields like [event name] and [event date] into your copy and they fill in per event. Pick the heading and body fonts from the same webfont library the menus use.
- Preview as a real event while you build, so what you see on screen is exactly what the client will open.
- The proposal is a branded web page at a private link, not an emailed attachment. It reads on a phone, stays off search engines, and never lands as a heavy PDF in a spam folder.
- Link a template to a lead reply and the proposal goes out with your reply from the leads inbox, live against that lead's event, flipping from draft to sent the moment you hit send.
Let clients book a viewing without the back-and-forth.
Put a booking page online and clients pick a slot themselves: a venue viewing, a tasting, a consultation, in person, by phone, or over video. You choose which Spaces are bookable and when; 1pm handles the confirmation, the reminders, and any change of plan.
- A public instant-book page branded with your logo and accent colour: the client picks a day from a month calendar, sees your open slots, and books in one step, no login.
- Opt-in availability per Space: choose which Spaces take appointments and the hours they're open, with buffer time held either side so a viewing that overruns doesn't collide with the next one, and a notice period so nobody books the slot you're already walking into.
- Phone, video, or in person. Video appointments hold their confirmation until you drop in the meeting link (Meet, Zoom, or Teams, with a create-a-link shortcut); in-person bookings carry the Space address.
- Automatic confirmation and reminders: the client gets a confirmation on booking and a reminder a set time before, and the Space's contact can be reminded too.
- Clients manage their own changes: a manage link lets them cancel or reschedule without emailing you.
- And you're told in your own diary. A booking, a move, or a cancellation emails you with the appointment attached as a calendar file, so it lands in your calendar straight away rather than whenever the subscribed feed next polls. The wording is yours to edit, like every other automation.
- Every appointment lands on your calendar alongside your events, in its own availability band, and never double-books a Space that's already holding an event.
One private link where the client accepts, agrees, and pays.
The Booking Portal is the money side of a job, in the client's hands: the quote, the confirmation and its terms, the deposit, and the invoices, all at one private link. Turn a priced event into a client-facing confirmation, with the BEO details and the costing on one page, frozen the moment you send. The client reviews it, approves it with their name, and the event becomes confirmed. Attach a deposit and they secure the booking on the spot. The link keeps working afterwards, so it stays the one place they go for what they agreed to and what they have paid.
- Raise a confirmation straight off the event's pricing. It captures a snapshot of the BEO (access and vacate, service and setup, menu, bar, AV) and the priced lines, frozen at send, with an optional cover note and your terms.
- Choose exactly what the client sees. Untick any block (AV, setup, bar, menu, the access and vacate window) to keep it off their copy while it stays on your internal record. The pricing always shows.
- The quote can be theirs to configure, not just to accept. Where you have opened lines up, they move a stepper, tick an extra on or off, set their guest count and pick a start time inside your window, and the document re-prices as they go. Accepting builds the booking from what they chose.
- The client opens it at a private link, no login, reads every detail, then approves by typing their name and ticking to agree, or asks for changes. Approving moves the event to Confirmed.
- Attach a deposit as a percentage of the total or a fixed amount, with its own due date. The confirmation breaks out the deposit and the balance still to come.
- The client pays the deposit online at sign-off and the balance later, by card through Stripe, or you record a bank transfer or cash by hand. The balance due tracks live.
- Bank transfer is a first-class option, not a footnote. A client who would rather transfer says so on the page, and 1pm raises their invoice and emails it to them as a PDF on the spot, so they have something to give their finance team without waiting on you.
- The client's page walks them through three clear steps, Accept, Agree to terms, Pay deposit, auto-advancing so they always know what's left to do, and you can offer pay in full alongside the deposit for a client who'd rather settle it all now.
- Every page carries the same strip at the top: a home icon, the portal's name, your business name, and the rooms that client is entitled to, the one they're reading in bold and the rest as links. Home goes back to the link you actually sent them, so a client you invoice in March lands on the invoice, not on January's quote. It never prints and never appears on the PDF.
- Show the shape of the day, not just the price. Put a You're up! run of show on the lead and both the quote and the booking carry a run of show button: the timeline slides out in a panel beside the document, so the client reads what the day costs on the left and how it runs on the right. It is live, not a copy taken at send, so moving the ceremony in You're up! moves it on their page with nothing to resend. You're up! is free to start and 1pm only ever asks for the read-only share link.
- And the client can adopt that run of show. An Adopt this run of show button hands them their own copy in You're up!, with the rows they took still pointed at yours, so a time you move moves on their sheet too. Around it they add their own private items, the hair and makeup call, the family photo list, the ride home, and send their version to the suppliers you were never going to email. Their copy never changes yours.
- The Booking Portal and the Event Portal join up, both ways. Give the client their own link to the event and the Booking Portal carries a button through to the Event Portal: the live run of show, with the briefing (Space, access and vacate, pax) above it. The Event Portal carries a Your booking card back to the confirmation they signed, with any invoices billed to them beside it. Whichever link they kept, they can reach the rest of the booking without asking you to resend anything.
- Call it something else if you'd rather. Booking Portal is the shipped name; rename it to Client Portal, Quote Portal, Payment Portal, or your own word at Account, Profile, Wording, and it changes on the pages and in the emails.
- Attach your terms from a versioned terms library. The exact wording they agreed to is snapshotted onto the confirmation, so you always keep the version they actually signed, even after you update your standard terms.
- Running a multi-day occasion? Group the events into a Program (a wedding weekend, a multi-day conference) and confirm the whole thing as one agreement: one sign-off and one deposit across the lot.
- Every sign-off is logged with the signer's name, email, and a timestamp, so the approval is on the record. You get a bell and an email the moment they sign or decline.
- Send it as a real PDF alongside the live link, or print the whole thing clean on A4 for the file.
Set the follow-ups once, then let them run.
Automations send the right email, create the right tasks, or move somebody along, at the right moment without you remembering: a set number of days around the event date, the instant a lead crosses a step in your sales funnel, the moment a new lead lands, or any of a dozen moments in your crew's onboarding. Build a nurture sequence, chase the crew who haven't finished their requests, chase yourself over the files you haven't reviewed, scope it all to one lead form, and review anything client-facing before it sends.
- A trigger for every moment: X days before or after the event date, funnel edges (quote sent, opened, accepted, agreement signed, booking confirmed), the moment a new lead comes in, a set time before an appointment, or a point in your crew's onboarding.
- Triggers that fire off your own actions too: the moment you email a quote, an invoice, a confirmation, or a crew invite, and the moment a client picks bank transfer and generates their own invoice to pay. The routine follow-up rides along with the thing you just sent.
- Twelve onboarding triggers, so the whole compliance loop runs itself: someone is added, they self-register through a link or QR code, they finish their requests, everyone on the event finishes, you approve a document, a certificate is about to expire, one already has, a rejected upload still hasn't come again, or an invite has gone unanswered.
- Even the documents with no expiry date get asked for again. A police check, a site induction, a WHS refresher and a policy sign-off print no lapse date, so the expiry chases can never see them and they sit approved forever. Set 'Time to ask again' a number of days after approval and they come round on their own.
- Two of them chase you, not them. A link that was never opened is a dead address rather than a slow supplier, and wants a resend from you instead of a nudge to them, so that one comes to you. The other watches your own approval queue, so the file somebody sent a fortnight ago stops sitting there unread.
- Actions that do the work, not just email about it. Send somebody their invite the moment you add them, put them into a named section so the driver gets the driver pack and nobody else does, or move their status to Inducted or Cleared to work, so 'who is not cleared' answers itself on the Crew report instead of waiting on someone to change a dropdown.
- Pick who hears about it: the client, the event's organizer, the crew member (with their own private link), yourself, or any address you type, so a compliance inbox or a site manager who has no login here gets the alert directly. Or skip the email entirely and drop a whole workflow of tasks onto the event. Merge in fields like [first name], [event date], and [their link] so each one reads personally.
- Nurture and chase drips with a Wait step: chain "send, wait 3 days, send again" into a sequence, dragging the steps into order, whether you're warming a lead or nudging crew who haven't finished onboarding. A lead sequence stops itself once they've accepted or booked, so a chase never lands after they've said yes.
- Scope to one lead form: give a wedding lead an entirely different workflow than a general event lead, on both the arrival trigger and the scheduled ones. The form the lead came in on drives the sequence.
- A 24-hour review queue: client emails wait in a "Sending soon" list you can read and cancel before they go out, with a 15-second undo on lead replies too. Nothing surprises you.
- Seeded, editable defaults: the transactional emails (quote sent, booking confirmed, crew invite, requests complete) come pre-written and ready to use; tweak the wording or reset to the original any time.
- Attach files from your library to any automated email, so the welcome sequence carries the brochure, the crew chase carries the site map, and the pre-event reminder carries the parking pass, every time, without you remembering.
- See a date-based rule fire before it fires. Show upcoming forecasts it against your real bookings for the next 30 days: the date each email goes out, the booking it lands on, and beside anything that won't run, the reason why. Preview the wording against a sample event and send a test to yourself too, so a rule that matches nothing never looks the same as one that's working.
Everything after the signature.
Turning a won booking into a delivered event: the diary, the rooms, the tasks in the run-up, the run of show, the BEO your departments work from, and the crew who run the day, live on their phones.
See the whole book at a glance.
A visual scheduler for everything on the books: month, week, and day views, colour-coded by status, with the times on every chip the way an operator reads a diary. Feeds run both ways: a one-way feed pushes your bookings out to Google, Outlook, or Apple Calendar, and an external calendar read in shows a Space's outside bookings as busy times.
- Month, week, and day views. Every event chip leads with its start and end time, Google-calendar style, so the diary reads at a glance.
- Colour-coded by status: lead, tentative (pencilled-in orange), confirmed, and completed. Filter the calendar by status, or by Space.
- Hover any event for a preview card with the access and vacate window, Space and zone, pax, client, value, and a jump straight into its run of show.
- Drag to reschedule: move an event to another day, or onto another Space row to change the room. Click an empty day to start a new event on that date.
- Subscribe Google, Outlook, or Apple Calendar to a private one-way feed, so confirmed and tentative bookings sit alongside the rest of your week. Reset the link any time to revoke access.
- Read a calendar in, too. Attach an existing Google, Apple, or Outlook feed (or anything fed by Acuity or Calendly) to a Space, and its outside bookings show up as busy times, so you can see a room's real availability at a glance. Read-only: 1pm never changes your calendar.
- Import existing bookings from a calendar (.ics) file, so moving to 1pm doesn't mean re-typing your diary. Choose the status they land as.
Change the run of show once. Everyone already knows.
The run of show your crew see is live. When you move an item, swap a vendor, or push a time, every open crew view of the run of show updates within a second or two. No refresh, no republish, no group text. The connection indicator on each crew view shows whether they're live, syncing, or working offline.
- Server-sent events stream changes to every open crew view in real time.
- A clear Live / Syncing / Offline indicator on each crew view so you know what state they're in.
- Offline reads still work from the cached copy. Updates catch up the moment the connection comes back.
Speaks BEO, pax, access, vacate.
The fields a venue's department briefs already carry, in the same language your kitchen and AV teams already use. Service style, setup style, pax guaranteed, dietary summary, menu summary, bar package, AV notes, access from, vacate by. Called a BEO in hotels and banqueting, a function sheet almost everywhere else, and it works the same whether you cook the food yourself or the client brings a caterer.
- BEO fields live on the event itself, so the brief travels with the run of show instead of as a separate PDF.
- Per-owner autocomplete on Service style, Setup style, and Zone, so "Rounds of 10" or "Stage left" only need to be typed once.
- Access from and Vacate by mark the load-in window. Multi-day events handle them cleanly because each item carries its own date.
- The client writes their own brief, in their own words, in their event portal: what the day should feel like, who is coming, what must not be interrupted. It arrives as a request, so it is chased like every other ask, and it prints at the top of the BEO above your own fields, because reading their version first is how the two get checked against each other at the morning huddle. Only the booking's client can write it, and you read it rather than edit it.
- On Professional you describe the food and drink in free text, which is all a dry-hire room or a contract-catered venue ever needs. On Hospitality you build and price the menu properly, and it flows onto the brief as real courses and dishes instead of a paragraph.
Save the room once. Every booking knows how to get in.
A Space is anywhere you actually run an event: a hotel ballroom, a restaurant's private dining room, a park, a rooftop, a warehouse. Save it once with its address and its access notes, attach it to any event, and the loading dock instructions stop living in someone's head. Rooms are flat, not nested, so the Ballroom and the Rooftop Bar are two Spaces with their own addresses rather than children of one venue record.
- Spaces are reusable: save your venue's rooms (or a park, a rooftop, a warehouse) with addresses and access instructions, then attach to any event.
- Access and parking notes travel with the room, onto the BEO and the crew's share link, so nobody has to ask which door the dock is behind.
- A room can't be double-booked by accident. Two events overlapping in the same Space are blocked, with the clashing booking named, unless you deliberately allow concurrent use of that room.
- Buffers before and after hold the room for turnaround, so a 6pm pack-down does not let a 6pm load-in book on top of it.
- Renaming or re-cutting a room? Move events to another Space in bulk, with a preview of exactly what will shift and a stop on anything that would clash.
- Attach floor plans, seating charts and manuals to the Space itself and they appear on every event held there.
- Read an external calendar into a Space to show its outside bookings as busy time, so a room you don't solely control still reads honestly.
When the day starts moving, the run of show keeps up.
Print a clean back-of-house copy for the kitchen folder. Filter the run of show down to one crew member when something's on fire. Crew tick off items as they go. Close out at end of shift with actual durations and a debrief that lands back on you.
- Print the run of show as a black-and-white document with your logo, the event metadata, a crew contact sheet, and every item laid out for paper.
- Filter the run of show by who's responsible, useful when one supplier needs a clean view to plan around.
- Crew mark items complete as they happen. Each tick is visible to everyone on the link.
- Know who is actually in the building. Turn check-in on for the events that need it and crew tap once on the link they already have. You get a live On site now count that updates without a refresh, and a named roster split into who is here (most recent arrival first) and who is not, which is the list you want in your hand if the building has to be cleared. Check anyone in or out yourself for the phone that died in the loading dock.
- A tap works with no signal. A loading dock with no bars is exactly where this gets used, so an offline tap updates the crew member's card straight away and sends when the connection returns. Every check-in and check-out is logged with the time, who did it, and the person's name as it was, and it all comes out in your account export.
- Close out at end of shift: capture actual durations against the planned ones, plus crew feedback for the venue.
Who's doing what, item by item.
Crew is what your contacts become once they're working a specific event. Assign people to the items they're responsible for, give each one a private brief, and they get a filtered view of just their part of the day, without ever creating an account.
- Assign a Responsible person to each run of show item. The crew member sees the item on their view and a clear "Mine" filter.
- Per-crew briefing notes ride alongside the public run of show, private to that one person.
- Crew add a photo of themselves from their own Event Portal (or you add it for them), so the day-of view shows a face, not just initials.
- Assign a table and seat to each crew member or guest, with autocomplete that shows a running "N seated" count as you fill each table.
- Rename "Crew" per event to whatever your world calls them (Team, Staff, Volunteers, Artists), and the label updates across the app, the share link, the print-out, and emails.
- Crew tick items off as they happen, and every tick is visible to everyone on the link in real time.
Share the run of show with one link. They open it on their phone.
The Event Portal is the job side of a booking on one page: the run of show, the briefing, the requests still owed, and the event files. No app to install, no login, no seat to license. Each crew member gets a scoped link that shows only the rows they're involved in, and the client can be given one too. Mobile-first, cached locally, and designed to keep working when the venue Wi-Fi gives up halfway through service.
- No download, no account. Crew tap the link and they're in.
- One page for the whole day. The run of show, the briefing (Space, access and vacate, pax), the requests they still owe you, and the event files all sit in the Event Portal, under a strip that names the portal and lists the rooms that person is allowed into.
- Filtered per person. AV sees AV rows. Kitchen sees kitchen. Less noise, fewer misreads.
- Mobile-first. The crew view is built for a phone in a back hallway, not a desktop browser.
- Cached locally. Once a crew member has loaded their link, the run of show stays available even if their signal drops.
- Resend a crew member's link in one click if the first email never arrived or they lost it.
- A QR-code-friendly public version exists for events that want a single big-room link instead of per-person.
- Running your run of show in You're up! instead? The sheet on the lead opens in a panel here as well, from the same button the quote and the booking carry, so the one page about the day is never the one page without the day on it.
- Open the Event Portal for the client too, from the portals panel on the booking, and close it when the job is done: that one link stops working immediately, while their quote and invoice links keep working.
Build the run of show without fighting the document.
Inline edits, smart time math, drag-to-reorder when you need it, auto-sort when you don't. Multi-day events group by date. Long agendas paste straight in.
- Add items at the bottom of the list, persistent form means you can rapid-fire entries.
- Auto-fills the next Start time from the previous item's end, so a 30-min item at 4:00pm leaves the next at 4:30pm.
- Click any cell to edit. Drag the handle to override sort. Multi-day events get a Date column automatically.
- When an item runs over, a Push control starts the next item exactly when this one ends, or Push all slides the rest of the day by the same amount and keeps the gaps, with one-click undo.
- Items that share a start time are grouped so two things happening at once read as parallel, not as a mistake.
- Save a polished event as a template and reuse it forever, the supported way to duplicate an event.
- Paste an existing run of show from Word, Google Docs, or a spreadsheet, and 1pm parses it into rows.
- Select several items and act on the lot: shift them all by an hour when the ceremony moves, or delete them together when a whole segment is cut.
- Copy the whole run of show out as clean text or a spreadsheet-ready block, for the one supplier who insists on having it in their own document.
- Give an item's details real formatting (headings, bold, bullet lists) when a line needs to carry a shot list or a set of cues rather than a sentence.
The to-do list for the run-up, and the manual behind it.
Every event carries a task list for the work before the doors open: chase the deposit, confirm the caterer, order the flowers. Save a job as a reusable workflow, write down how each step is actually done, and print the lot as a procedures manual you can hand to somebody on their first day.
- A task list on every event for the planning work, kept separate from the run of show (which is the day itself).
- Break a task into steps when one line is not enough. "Confirm the caterer" becomes send the numbers, chase the dietaries, sign off the menu, each ticked off in its own right.
- Reusable workflows: save a standard set of steps (a wedding prep list, a corporate setup list) once and apply it to any event in a click.
- Write the procedure into each step, so a workflow stops being a memory aid for whoever wrote it. "Check the cool room" becomes how to check it, what it should read, and where to log it. Written once and read by every task made from it, so correcting it corrects everything.
- Sort workflows into your own categories and put those categories in a deliberate order. Safety first, pack down last, because a manual has a running order and alphabetical is not it.
- Print the whole library as a procedures manual: a branded PDF with every workflow under its section, each step numbered with its written procedure. It reads live off your workflows, so there is no stale copy to remember to regenerate.
- Assign tasks to your team and see who completed each one, so nothing falls between people.
- Automations can create the tasks for you: wire a workflow to a trigger (a booking confirms, an event is a week out) and the list appears on its own.
Paperwork collected, not chased.
Certificates, licences, answers and signatures gathered from crew, suppliers and clients through their own link, with a dashboard of who is still outstanding and expiry dates tracked before they lapse.
Collect certificates, documents, and answers from every person.
Stop chasing fifteen suppliers by email for a public liability certificate, a parking pass count, or an updated dietary list. Send each crew member their own compliance request, or ask everyone the same question at once. Certificates, documents, and answers land on the event, tracked against what's still outstanding.
- Request packs: save the set you always ask for (a wedding's run sheet, photo list and signed agreement; a supplier's insurance certificate and induction) and add the whole pack to a booking or a portal in one click. Build as many as you have kinds of job.
- Or let the pack land on its own. Point a lead type at a pack and the asks are created the moment a lead of that kind becomes a booking, so a wedding client opens their portal to the run sheet and the agreement already waiting, and a corporate client opens theirs to the purchase order and the AV brief. Once, at conversion, so accepting a quote twice never doubles them up.
- Per-crew requests: ask one supplier for a specific certificate, document, or detail (a public liability certificate, an updated headcount).
- Event-wide requests: ask every crew member the same question at once. Responses are grouped by supplier under each request.
- Get your terms accepted and signed. Add a Terms / Agreement request, pick a document from your versioned terms library, and choose what they have to do: tick to agree, type their name, or draw a signature on their phone. The exact version they accepted is frozen with a timestamp, so you keep what they actually signed.
- Let people register themselves through a shared link or a QR code, instead of you adding every name by hand. They land on their own checklist the moment they sign up.
- Attach a reference file or link to any request (a site map, a uniform photo, a sample certificate) so crew see exactly what you mean before they answer.
- Map a request to one of your custom contact fields, so a supplier's answer (a licence number, a public liability certificate) writes straight onto their contact record and is there next time.
- Track expiry dates on documents. Mark an upload field as needing an expiry and 1pm holds the date alongside the certificate, so a lapsed public liability policy surfaces before the event, not on the day.
- Upload files directly to an event without going through a crew member, or attach a file to somebody's upload field on their behalf when they send it to you the slow way.
- Review every uploaded file on a single page, with a reporting dashboard and printable report showing what's in and what's still outstanding.
- A history behind every request and every answer. Admin History on each request shows every change ever made to its wording and settings, who made it and when. And where somebody has re-answered, what the answer used to say is kept and shown underneath the current one, so 'this number was different last week' has a dated answer rather than a shrug.
Collect documents from a group with no event attached.
Sometimes you need paperwork from people, not a booking: the contractor register, the casual staff pool, the stallholder applications, the volunteer waivers. An Onboarding Portal is a stripped-back record with no date, no venue, and no run of show, carrying only the part you actually want: a list of people, a checklist of things to collect, and a no-login link each person opens on their phone.
- No date, no Space, no run of show. An Onboarding Portal drops everything an event needs and keeps the people and the paperwork, so nobody is typing a fake date to make a form work.
- Build the same requests checklist you would on an event: document uploads with expiry dates, text answers, choice lists, contact-field write-back, and a Terms / Agreement block to be signed. Or add a saved request pack and get the whole intake checklist in one click, the same packs your bookings use.
- People add themselves through a shared link or QR code, or you add them by hand. Either way they get their own no-login link to their own checklist.
- Close an Onboarding Portal when the intake is done and both the sign-up link and the existing links stop working, without touching anything already submitted. Reopen it next season.
- Onboarding Portals sit in their own Onboarding section and stay out of your events list, your calendar feed, and your reports, so an intake register never pollutes the event book.
Quoted, invoiced, paid, reconciled.
Deposits and balances, card and bank payments taken on the document itself, and a one-way push into Xero so the ledger matches without anyone re-keying an invoice.
Quote, invoice, and get paid where you run the event.
One document editor builds your pricing sheet, your quotes, and your invoices off a shared catalog of priced items. Send a quote from a lead, turn it into a confirmed event, raise the invoice, and take card payment online.
Card payments are powered by Stripe. Connect your own account, keep your own payouts, and pay no platform fee on top.
- One editor for pricing, quotes, and invoices. Group lines into packages, drop loose lines between them, and drag to reorder. Each line carries a name, an optional description, quantity, and tax.
- Build a reusable catalog of priced items in categories, then add a whole package to an event in one click. Per-head lines pull the event's pax automatically.
- Every event keeps a living pricing sheet that feeds the pipeline value in your Sales pace and Conversion funnel reports. Copy it to a draft invoice when you're ready to bill.
- Raise a quote on a lead and send it through the lead thread. The client opens it at a private link, and accepting it creates a confirmed event with the pricing already seeded. Copy any quote to a draft invoice when it is time to bill.
- Let the client build the quote instead of sending three. Open a line up and they get a stepper inside your range ("coverage, 6 to 10 hours"), a tick beside any optional extra, one guest count above the lines that rescales every per-head line at once, and a start-time picker inside your window. The whole document re-prices as they move, with no calculate button, and the limits are checked on our side rather than trusted from the browser.
- What they accepted is what gets built. Their quantities seed the event's pricing sheet, the guest count they agreed lands as the guaranteed pax, the agreed start and finish land on the booking, and an extra they declined is never billed. A declined line stays visible on their page marked "Not included", so switching something off is not a one-way door.
- You are told exactly what moved. An adjusted acceptance writes a plain account into the lead thread (guest count 67 to 73, coverage 6 to 10, added Second shooter, total before and after), and says in as many words when the booking's own times changed, so you know to re-check crew call times and what the kitchen is counting on.
- Save the same offer on the catalog item and every quote built from it arrives already offering it, then change it for one client without touching the item.
- Invoices follow the Xero model: the figures freeze when you send, while your business number, terms, and branding render live from your settings so the boilerplate stays current.
- Every document is a real PDF, generated on our side rather than through a browser print dialog. Emailing an invoice, quote, or confirmation, you choose whether the client gets the live link, the PDF attached, or both, so an accounts department that wants a file to file gets one.
- Bill a deposit and a balance as separate invoices, each numbered and each payable on its own, with the schedule shown on the document so the client can see what is due now and what is due later.
- Take payment online: connect your own Stripe account (no platform fee) and a Pay now button appears on the public invoice. Card payments mark it paid automatically.
- Save a card on file with the client's consent and charge the balance later without chasing them for details again.
- Record manual payments (bank transfer, cash, cheque) too, with the balance due tracked live. Publish your bank details once and every invoice carries a Pay by transfer panel with the account and the reference already filled in.
- Set your tax rates, due days, number prefix, and default terms once in account settings.
- Set your account currency once and every figure, on your own screens and on the documents your clients see, shows in it, formatted correctly with a matching tax label.
Raise the invoice once. Xero gets it, itemised and tax-mapped.
Keep your books in Xero and let the two talk. Connect your Xero organisation and 1pm pushes your invoices and their payments straight across, so nobody is rekeying figures at month end. The sync runs one way, 1pm to Xero, so 1pm stays the source of truth for the invoice and Xero gets a faithful copy for the books.
- Connect your Xero organisation once, then map it once: pick the sales account invoices post to, the bank account payments land in, and match your tax rates to Xero's. Set it and it sticks.
- Every invoice goes across itemised, line by line, with the right tax on each. A service charge crosses as its own line at your default rate, a gratuity crosses untaxed.
- Choose how invoices land: Draft (the safe default) drops each one into Xero for you to review and approve there, or Authorised sends them straight through as approved.
- Payments follow the invoice. Record a payment in 1pm, whether by hand or through an online card payment, and it syncs to the bank account you mapped, with the amount, date, and balance matching what you see here.
- Push invoices by hand from the sync console, one at a time or all at once, or turn on auto-push and let 1pm send each invoice the moment you issue it or get paid on it, in the background.
- The console flags anything that didn't go across cleanly, with a count on the button, so a hiccup is something you notice, not something your accountant finds. Push the same invoice twice and it updates the one in Xero rather than creating a duplicate.
The account, and who else gets into it.
Alerts the moment something needs a human, and per-seat access for colleagues, with the wording and the navigation each of them sees.
The moment something needs you, you know.
A bell in the top bar lights up the instant a client signs or declines a confirmation, a lead replies, or a payment lands, so the things that move a booking forward never sit unseen in a mailbox.
- A bell in the top bar with an unread count for confirmations signed or declined, lead replies, and payments received.
- Each alert links straight to what needs you: the confirmation, the lead thread, or the invoice. One click and you are there.
- The same events email you too, so a signed booking, a declined one, or a payment reaches you even when you are not in the app.
- A weekly summary email on the day and hour you choose, in your own time zone, listing what is waiting on you: files to review, documents about to expire, ones that already have, and anything you sent back that hasn't come again. Off by default, it can go to a shared inbox instead of you, and it only arrives when there is something in it.
- Clear the lot with Mark all read once you have caught up.
Bring a colleague into the account.
Need a second pair of hands in the same account? Invite a colleague by email, add a seat, and they work inside your account as you: build events, edit the run of show, manage contacts, send share links. They never need a subscription of their own. Your money, your identity, and who else gets in stay yours alone.
- Pay per seat, on your bill. Add a colleague and their seat is added to your subscription, so nobody on your team is buying their own 1pm. Add and remove seats as the team changes and the cost follows.
- Invite a colleague by email. Once they sign up and accept, they get admin access to your events, contacts, spaces, requests, branding, custom fields, and the operational settings that run the venue.
- They switch into your account and act as you, so crew links, branding, and history all stay under the one account. A clear indicator in the top bar shows when someone is working in your account.
- The owner-only things stay owner-only: your subscription and payment details, your Stripe and Xero connections, two-factor, the account export, sender domain, deletion, and managing who has access.
- Revoke access, or let them leave, at any time. Access is checked on every request, so removing someone takes effect immediately, and the seat comes off your bill.
- Call things what your world calls them. Rename "Event" to Booking, Job, Project, or Function, and the word changes everywhere: the nav, the buttons, the emails, and the share links.
- A setup guide in the sidebar lists the next few things worth doing, each linking to the screen you do it on with a help article beside it. It ticks itself off as you go, and anything you are never going to do is marked Not needed so it stops asking, one step or a whole section at a time. It disappears once the list is done, and a switch brings it back.
- Hide the parts of the sidebar you never touch, per person, so a duty manager and a sales lead in the same account each get the nav they actually use.
Where the pipeline and the book really stand.
Sales pace, conversion, revenue, utilization, crew, and the compliance paper trail, every one filtered by date, exported to CSV, or printed for the management pack.
The numbers behind the book.
27 reports across money, sales, events, crew, and requests, grouped by the question each one answers. Every report filters by date and exports to CSV (Excel-safe) or prints clean in full black for the management pack. The kitchen reports are on Hospitality.
Money & invoicing
- Revenue
- Invoiced, paid, and outstanding across any period, with overdue invoices flagged so nothing slips.
- Invoices
- Every invoice in a date range, or just what is still owed bucketed by how overdue it is as a chase list.
- Payments received
- Every payment that landed in the period by date, broken down by method (card, cash, bank transfer).
- Deposits & balances
- Every confirmation with its deposit, what has been collected, and the balance still outstanding, with overdue balances flagged so nothing slips.
- Tax summary
- Tax collected by rate for your sales-tax or BAS filing, with per-invoice detail that ties back to revenue.
- Revenue by item
- What actually sells, by category and individual line, so you can see which packages and menu items earn their place.
Sales & leads
- Sales pace
- Bookings and pipeline value by event date, compared against the same point last year, so you can see how the book is filling.
- Leads
- The lead pipeline (new, qualified, converted, lost) with a conversion rate that never counts spam.
- Lead sources
- Which capture form pulls the most leads, which converts best, and how fast you reply to each.
- Conversion funnel
- Where the pipeline leaks: leads received, quoted, and converted, with the drop-off at each step, plus the same figures broken out per company.
- Quotes
- Quote win rate and value over a period: raised, accepted, declined, and still out.
- Event type performance
- Which event types you draw, which of them convert, and what each one is worth.
- Revenue by salesperson
- Booked revenue grouped by whoever owns the sale, with won events, average per event, and share of the total.
Events & spaces
- Events
- Every booking in a date range with Space, pax, status, and value, totalled.
- Space utilization
- How hard each room works: bookings, days in use, fill rate against capacity, and revenue, including the rooms sitting idle.
- Average spend
- Yield per event and per cover, split out by Space and service style.
Clients & crew
- Top clients
- Your best customers by booked value, with how often they book and what they have paid. Group by client contact, or by company so everyone who books from the same organisation adds up on one row.
- Contacts
- Your whole address book, filterable by tag, rating, and search, with a crew portal link for each.
- Crew
- The crew on a chosen event, listed alphabetically or grouped by tag or compliance status.
- Crew utilization
- Who is booked across events and who is idle, by tag, with each supplier's next booking.
Requests & onboarding
- Outstanding requests
- Everyone across every event and portal who still owes you something, in one list, with the requests holding the most people up ranked above it. Switch to the engagement view to separate who never opened their link from who opened it and stopped, so a resend and a nudge stop being the same follow-up.
- Response speed
- How long people actually take: link issued to first opened, opened to finished, and start to finish, as medians with the completion rate beside them.
- Request answers
- A grid of every person against every request for a chosen event or portal, showing their actual answers, with a problems-only view for chasing.
- Expiring documents
- Documents about to expire across one, several, or all events, with how far ahead you look up to you and anyone you've already chased hidden.
- Portals
- Your onboarding portals listed: who is invited, what they have to complete, how many are done, and whether the intake is open or closed.
Procedures & terms
- Procedures
- Your workflow library as a manual: every workflow under its category, each step numbered with its written procedure, as a PDF for a new starter.
- Terms history
- Who agreed to a terms document, which version they agreed to, and when.
Everything in Professional, plus the kitchen
The catering and back-of-house stack for caterers and F&B-led venues. Hospitality includes every Professional feature above and adds these. Compare plans.
Build the menu, price the plate.
A reusable menu library that flows onto the BEO, the confirmation and the bill, recipes costed to the gram, and the kitchen reports behind both.
Know what a plate costs before you price it.
Cost your menus from the ground up. Enter what you pay for ingredients, build recipes that roll up to a cost per serving, and see plate cost, food cost percentage, and margin on every dish and menu. Internal only, so your clients never see the numbers behind the price.
- Costed ingredients: enter the pack price and 1pm works out the cost per usable unit after waste, in whatever unit you buy in (metric, US, or AU volumes), with count bridges so you can cost eggs by weight and lemons each.
- Multi-supplier price lists: keep more than one quote per ingredient, and 1pm flags where a cheaper supplier would save you money and by how much.
- Recipes that scale: set a recipe's yield and get batch cost and cost per serving, with sub-recipes (a sauce inside a dish) and cycle detection so nothing loops on itself.
- Plate cost, food cost %, and margin on each menu, drawn straight from the recipes behind your dishes, flagging any dish or menu running above a target food-cost percentage.
- Printable cost cards for the kitchen: a line-by-line breakdown of each recipe with every ingredient's share of the plate.
- Feeds the kitchen reports, recipe cost cards, menu food cost and margin, and an ingredient price list, so the numbers are always a click away.
Covers, plate cost, and margin.
5 kitchen reports for the catering side: covers and dietaries, printable menus, menu food cost and margin, recipe cost cards, and an ingredient price list. Same date filters, CSV export, and clean print as every other report.
Kitchen & costing
- Catering & covers
- Covers served over a period, the service-style mix (plated, cocktail, buffet), and dietary totals across events.
- Menus
- Print or export one or more of your menus, each grouped Menu, Course, Dish, as a kitchen and front-of-house sheet.
- Menu food cost & margin
- Plate cost, food cost percentage, and margin for each menu, flagging anything above your target. Internal only.
- Recipe cost cards
- Batch cost and cost per serving for each recipe, line by line, with each ingredient's share of the plate.
- Ingredient price list
- Cost per usable unit for every ingredient after waste, with the current supplier and a cheaper-quote flag.
Start your next event at 1pm.
30-day free trial. No credit card.