How does the AI respect accessibility and mobility needs?
Accessibility rules are evaluated at the top of the constraint hierarchy: mobility and wheelchair access, front-row placement for visual impairment, and adjacency to exits are treated as non-negotiable constraints. Seats that meet accessibility requirements are flagged in exports and visible on the floorplan.
How can I handle day-of changes, swaps, and cancellations without redoing the entire chart?
Use the visual editor to perform seat-level overrides, merges or removals. Changes are appended to a changelog so you can apply swaps incrementally; locked sections remain unchanged unless explicitly unlocked by a permitted editor.
What input formats are supported and what fields should I include?
Common inputs include CSV/Excel and Google Sheets exports, ticketing lists and simple floorplan images (SVG/PNG) or grid schemas. Recommended fields: guest_name, email or id, party_id, accessibility_notes, dietary_tags, vip_flag, and any grouping tags (family, company, industry).
How do manual overrides work and can I lock parts of the plan?
Manual overrides are applied directly on the seat map or in the CSV. You can lock tables or seat ranges to prevent automated changes and restrict who can edit locked areas during review and publishing.
How are dietary restrictions and catering groupings surfaced on outputs?
Dietary tags are included as columns in operational CSVs and shown in the plan legend. Printable table cards and vendor exports can be grouped by catering requirements to simplify production and service sequencing.
Can I generate printable table cards, seat labels, and labeled floorplans for vendors?
Yes. The system exports printable PDFs for table cards and seat labels and produces labeled PNG/SVG floorplans with seat markers and an exportable legend for dietary and accessibility notes.
What privacy and data-handling options are available?
The generator accepts CSVs, Google Sheet exports and ticket lists without requiring a full database migration. Workflows can be configured to minimize persistent storage of attendee data; consult your account plan for specifics on encryption and retention policies.
How does the system balance competing goals like VIP placement versus networking optimization?
Constraints are prioritized: accessibility and conflict avoidance are applied first, then VIP and reserved placements, and finally networking or diversity optimizations. You can adjust the rule order and rerun seatings to tune trade-offs before finalizing.
Is there an audit trail of changes and approvals?
Yes. Each edit—whether automated or manual—can be recorded in an audit log with timestamps, editor identity and optional notes to document why a change was made and who approved it.
What are typical implementation steps for integrating this into venue workflows?
Typical steps: prepare and clean guest CSVs, import a floorplan and set accessibility zones, run a seeded plan with conservative constraints, review and lock sections, export production files, and train a small operations team on day-of edits and changelog review.