$ event-builder --documents-in --board-out
A content manager, on a Spec Sync call
Hand Event Builder the venue contract, the BEO packet or the menus. It reads them into a draft board you review line by line, with every value quoting the page it came from. Nothing is written to the event until you say so.
It reads. It never decides.
Documents in
Event Builder reads what the venue sent and what you already have. A revised BEO changes only the functions it names; a prior conference becomes a ranked source, not a copy.
Every value quotes its page
Each imported fact points at the page and the line it was read from, and a value that cannot be verified against the document is rejected with a reason, never kept quietly.
Planner outranks document
The authority order is yours. A conflict between a signed contract and what you told it is a question on screen, not a silent default.
One commit, or none
Rooms, functions, menus and budget lines land together. A step that fails leaves no half-built event behind. Build more later and it adds to what you have rather than starting over.
A Spec Sync builds your first board from one real BEO or function sheet.
“It’s faster. It’s more accurate. And I don’t have to chase the details anymore.”
Lauren Koleszar, CMP
Meetings Manager, ASIS International
Case study · URMIA
“For 25 years I was stuck translating spreadsheets and mail merges into something venues could understand. Pholeo changed that.”
A lean association team centralized its logistics in Pholeo, cut the Excel and PDF version confusion, and cleaned up the venue conversation without adding staff.
Jack Voorhees
Senior Director of Events, URMIA
FAQ
Straight answers. If yours is not here, ask it on the Spec Sync.
Venue contracts, BEO and MEO packets, catering menus, function books and the master workbook you already keep. Scanned PDFs are read too. It also reads a prior pholeo, so this year starts from last year’s board with this year’s documents on top.
No. It produces a draft you review. Every row is accept, change or reject, and nothing is written until you commit. The model reads and proposes wording and estimates; the rules build the plan and it cannot add, move or delete a row on its own.
Each value shows the page and the line it was read from, and you can open the document beside it. A value that cannot be matched to the text is flagged with a reason rather than filled in.
Build it step by step. The same wizard walks the venue, the dates, the rooms and the suppliers and builds the board when you are ready.
Yes. Build more takes a new packet against the board you have, changes only the functions the packet names, and never deletes anything. The board is re-read at apply time so a row you added meanwhile is not created twice.
It is read inside Pholeo and never leaves as a file. Hidden spans are stripped before reading and metadata is never opened. The read has ceilings on pages and cost per run, and a document that cannot be read cleanly is refused rather than guessed at.
Share one spec and we will build your first board with you.
