Translate requirements into zones
Turn the working count, seating, meal service, bars, staging, AV, registration, and special requests into editable spatial objects.
Banquet event order handoff
Move from the BEO to a setup-ready floor plan
Use the BEO as the function brief, build the event’s spatial setup in Margo, reconcile counts and zones, and attach the reviewed plan or setup packet alongside the property’s controlling banquet record.
Manual BEO-to-plan workflowSetup manifest and versionNo integration implied
Current event layoutWORKING
Editable first passHuman review required
1Manual BEO-to-plan workflow2Setup manifest and version3No integration implied
The job to be done
Make the function record visible in the room
A BEO can describe attendance, timing, food and beverage, AV, and setup. The floor plan shows how those requirements occupy the actual room.
Reconcile the details that drift
Compare the BEO, guest or seat count, furniture manifest, room state, and vendor footprints before issuing the setup.
Attach a controlled layout
Print a plan or setup packet with the event identity, version, approval status, object groupings, and review notes for the BEO package.
How it works
A transparent BEO-to-layout handoff
The current workflow is deliberate and manual: read the controlling BEO, enter the spatial requirements, review the plan, and attach the output. There is no claimed direct sync.
Read the current BEO
Confirm the function name, date and times, room, working or guaranteed count, setup, service style, program, AV, and special instructions.
Create the spatial plan
Select the room template, enter attendance and seating, add every required zone, and include notes where the BEO contains a constraint the canvas cannot express.
Reconcile plan and function record
Check room, count, table mix, service areas, stage and AV, vendor needs, revision identity, and open questions with the appropriate departments.
Issue both records together
Complete the property’s normal BEO approval, record the floor-plan decision, and attach the current plan or setup packet without presenting Margo as the BEO system of record.
What the workflow supports
Spatial detail beside the banquet record
Margo focuses on the room layout and controlled setup output. It complements rather than replaces hotel sales, catering, or BEO systems.
Reusable function rooms
Save the room foundation once, then build each banquet as its own event plan with independent history and guest information.
Furniture and production manifest
The setup pack groups labeled objects by structure, furniture, production, safety markers, and annotations and displays designed seating.
Decision and revision context
Milestones, comments, approval states, timestamps, and a current-version shared view help explain which plan accompanies the BEO.
Planning checklist
BEO fields to reconcile with the floor plan
Assign an owner for each comparison and record the result under the property’s normal change-control process.
- Function name, date, event times, room, room state, and revision identifier
- Working or guaranteed count, planned seats, table mix, and reserved locations
- Meal service, buffet or stations, bars, coffee, bussing, and back-of-house route
- Stage, podium, dance floor, screens, AV control, power, décor, and entertainment
- Registration, gifts, coat check, sponsor, vendor, storage, and accessibility requests
- Setup and strike timing, department owners, open items, and distribution list
Questions to settle before the room is set
Can I upload a BEO and have Margo build the plan automatically?
No BEO parser or importer is claimed. Enter the relevant room and event requirements through the plan workflow and keep the source BEO available for manual comparison.
Does Margo replace our sales and catering platform?
No. Margo is the spatial planning and setup-record layer. Continue using the property’s system for function terms, pricing, menus, contracts, and the controlling BEO.
What can be attached to the BEO?
Use browser print to create the plan PDF or setup pack, then attach it through your existing BEO or document workflow. Confirm the printed version and status before distribution.
How should a BEO change be handled?
Update the floor plan when the changed requirement affects space, counts, or setup. The plan returns to working status, then needs reconciliation and another review under your property process.
Continue planning
Adjacent guides for the next decision
Test the BEO handoff on one current function
Use the actual function record, build the room setup, reconcile both documents, and confirm who owns the final distribution step.