On most hospitality and commercial projects, the FF&E specification exists in several versions at once. There's the master schedule in Excel, a copy someone saved locally last Tuesday, and product data pasted in from a dozen manufacturer sites. Pricing sits in supplier emails, and PO status lives in a separate sheet the procurement lead keeps. Each copy is accurate to someone, and none of them agree.
That gap is where budget overruns, wrong finishes, and missed lead times come from. It's not a design problem. It's a record-keeping problem, and it grows with every room type, area, and revision.
A specification platform exists to give the project one record that design, procurement, and accounting all work from. This guide covers what that record needs to handle, and what to ask during a demo.
Task managers track who is doing what. They don't know that one lounge chair appears in 40 guestrooms, 2 suites, and the lobby, or that changing its finish affects three quantities and a budget line.
Spreadsheets understand quantities but not versions. Once two people edit the same schedule, someone is reconciling by hand. Email carries client feedback and supplier quotes, but a comment in an inbox never updates the spec.
None of these tools were built around the unit that matters on an FF&E project: an item placed in specific areas, with a finish, a price, a supplier, and a status.
Most projects don't start from zero. A firm inherits a brand standard, a previous phase, or a consultant's spec book. A firm should be able to bring that data in and have the platform do the cleanup. That means recognizing component rows, matching items to areas, and merging a product listed across several areas into one item with separate quantities.
Fohlio's schedule imports do this:
Smart Data Extraction, currently in beta across all plans, detects where the data table starts and maps columns automatically. It also flags matches that need review. For teams with PDF extraction enabled, PDF spec books up to 10 MB go through the same import wizard as Excel files (release notes).
Designers find products on manufacturer and trade sites. The question is whether a product saved from a web page arrives structured the way the firm specifies, or as a blob someone has to reformat.
Fohlio can import products from any webpage and map details like pricing, SKU, materials, brand, and dimensions to the team's preferred columns (release notes). For firms doing bespoke work, this matters. The schedule reflects the firm's own spec format, not the vendor's.
On custom projects, the client's approval of a specific item, finish, and price is what protects design intent through value engineering and substitutions. A firm should be able to record each item's approval outcome on the item itself, not in an email thread, and find every open decision across projects.
In Fohlio, Cross Project Reporting can filter items by client approval status, such as "approved with comments" or "rejected," across all active projects. When evaluating any platform, also ask whether an approval is tied to the version of the item the client actually saw.
A spec that doesn't carry its own cost picture forces someone to rebuild it in a separate sheet. Fohlio's Budget Analysis supports:
For firms working across regions, tax handling matters as much. Supplier prices can be set as VAT-inclusive or sales-tax-exclusive, and client and purchase taxes can use different rates. Those settings flow through to cost price, client price, and margin.
Price alone doesn't decide a quote on a hotel opening schedule. Quantity quoted and delivery date matter as much. In Fohlio's quote requests, suppliers submit their quoted quantity and delivery date alongside price, all in one comparison grid. Manual quote entry checks for an RFQ number and submission deadline before it opens*.
Over time, the firm should also know who it actually buys from. Supplier analytics show spend with each supplier. Contacts can be marked Preferred or Archived without losing their history.
Once POs go out, the recurring question is how much of each line has been ordered, invoiced, and shipped. Fohlio's Fulfillment Summary shows those three figures for each purchase order, and shipments have their own dedicated page*. POs that should no longer be active can be marked Voided, so the transaction history stays intact.
Spec books and tear sheets should come from the live record, not a copy-paste into InDesign. For teams with Lio enabled, Fohlio's AI assistant opens beside the Advanced Data Sheet. You describe the columns, grouping, and filters you need, and Lio builds a starting layout or edits the one on screen.
If the spec and the books don't agree, someone re-keys the difference at month end. Fohlio connects to QuickBooks Online and can manage multiple Intuit accounts. Mappings are configured per proposal, client invoice, purchase order, or supplier invoice, and sync status and errors are shown directly*.
For other systems, webhooks send create, update, and delete events for projects, contacts, proposals, invoices, purchase orders, and shipments. Payments, PO, and supplier invoice exports include per-currency totals for month-end reconciliation*.
Hospitality groups increasingly ask vendors about data handling. As part of its SOC 2 work, Fohlio made uploaded files private by default. Files are served through time-limited links, inactive sessions sign out automatically, and single sign-on supports full logout*.
A platform that answers these with your data, not a demo file, is one your team will keep using after onboarding.
Your specification deserves one record, not six spreadsheets. Book a Fohlio demo →