AI inspections for Event Temple

Overview

An Event Temple event says exactly how a room should be set; it cannot say how the room actually looked. The booking holds the client, the event holds the space, the dates, the setup style and the attendee counts, and the BEO carries all of it to banquets and the kitchen. What happens between the BEO going out and the doors opening is a person walking the room. RapidEye reads the space, the dates and the setup style from the Event Temple event, reads the photos your banquet team takes at set and at strike, and returns a finding for each thing that is wrong, tied back to the event that booked the room.

How it works with Event Temple

A function space passes through the same four moments for every piece of business, and each one leaves photos worth reading. The examples below are the common ones at a hotel or a conference venue, not the limit of what RapidEye handles.

• The set. Chairs counted, linens on, the screen where the BEO said, the head table facing the right way. RapidEye reads the setup photo against the Event Setup Style the event asked for and against what that style looks like in that room at your property, and comes back with what does not match while there is still time to move a table.
• The refresh between sessions. A general session that becomes a lunch, a boardroom that flips twice in a day. The photo after the flip shows whether water was replaced, whether the pads and pens came back, whether the last group's boxes are still in the corner.
• The strike. This is where damage arrives: a burn on a linen, a gouge in a wall from a load-out, a chair that went home with somebody, tape residue on a hardwood floor. The strike photo is read against the set photo from the same room, so the finding sits between two dated images and inside one event.
• The space nobody sold this week. A room that goes unbooked drifts. Bulbs, stained carpet, a stack of risers left against a wall. RapidEye reads whatever photos exist of that space over time and tells you what changed since anyone last looked.
• The house standard. Every venue has details that make it yours, down to how the linen falls and where the lectern sits. RapidEye learns those from your own photos rather than a generic checklist.

Each finding names the space, the spot in the room, what kind of problem it is, how serious it is, the two photos, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for banquets if you want it there. What happens next in Event Temple is yours: a task for the banquet captain, a space closure, a line in the conversation with the client. If your team documents with video walkthroughs, or with a room-by-room format of its own, tell us and we set that up with you.

How to connect Event Temple to RapidEye

1. The spaces you want watched. Your function rooms already live under Settings, Offerings, Spaces in Event Temple, each with a name and a capacity. Tell us which of them matter. Spaces you never sell stay out.
2. Photos at set and at strike. From the phone your banquet team already carries. If those photos are already going into the booking's Attachments tab, RapidEye reads them there. If not, a RapidEye capture link opens on any phone with no app to install, a fixed set of angles per room, taken as the team leaves it.
3. A read-only user for RapidEye. Added under Settings, Organization, Users. The Read-Only role can view and run reports and cannot change a booking, and the modal has the exact path.

How an event is built in Event Temple

Checked against Event Temple's help centre, September 2026.

Event Temple is sales and catering software for hotels and venues, and everything operational hangs off one ladder of records. According to Event Temple's help centre documentation (eventtemple.com), you create a Booking first and then add Events to that Booking, which is why a three-day conference is one booking with a breakfast, a general session and a gala underneath it rather than three unrelated jobs.

1. BookingThe piece of business: the client, the dates, the status and pipeline stage, the deal value, the assignees. Everything else lives under it, and its Change Log tracks who altered what, including when an attachment is added or deleted.
2. EventOne function. It carries the Space it happens in, start and end dates, an Event Type and an Event Setup Style your administrator defines, notes, custom fields, and the line items that become the menu.
3. Document, usually the BEOEvent Temple's Documents feature produces Proposals, Contracts, Group Resumes and Banquet Event Orders from templates, with merge fields that pull the event's own values in. The event's notes and counts are written to be merged here.
4. TaskWhat Event Temple's documentation notes hotels usually call a trace. Its own examples of operational tasks are a reminder to create a BEO, to set up chairs, or to create a group resume.

Under all of it are Spaces, added in Settings under Offerings with a name, a calendar colour, a capacity and an area, and taken out of play through a Space Closure whose reason comes from a list your admins maintain. Event Temple's own examples of closure reasons are maintenance, cleaning and a holiday, which is a fair description of the three reasons a function room is not sellable and of how little the record says about the state the room is in. A closure reason is a label, not a look at the space.

Four counts, and the one nobody records

Event Temple asks for the attendee number four separate times on a single event, which tells you how much of banquet operations is the gap between what was promised and what turned up.

Set is the operational one: it is the instruction to banquets, and it is the number a room is right or wrong against. Event Temple carries Set onto the BEO and into the Daily Events with Details report that banquet, catering and conference services teams pull to prepare for service. Nothing in the record says whether the room came out that way. That is the count RapidEye supplies, from the setup photo.

Can you attach photos to a booking in Event Temple?

Yes, as files, and no further than that. The help centre describes an Attachments tab on the booking for booking-specific documents such as signed contracts and certificates of insurance, and a Files area under Settings, Templates and Files that accepts jpg, png and gif images alongside PDFs and Office documents. The same article says plainly that there is no traditional photo gallery feature. The Change Log tracks that an attachment was created or deleted, and who did it, which is a record of the upload rather than of the room. So a setup photo can be stored against the right booking today. Reading it is the part that has never had an owner in anybody's day, and it is the part the integration takes.

Event Temple integration FAQ