Overview
FF&E quotation review · exception-based
—
Designer specifications, vendor quotations, POs, goods-received notes and invoices are read into one structure. Deterministic checks then cross-reference them item by item: spec against quote, quote against PO, PO against goods received and invoice, revision against revision, vendor against vendor. You only review the issues, and each one links back to its document and page. Nothing is approved automatically.
Budget and schedule
Committed and forecast against the approved budget, and where every item stands on the way to site. Follows the project selected above; with "All projects", the project you last picked is shown.What needs your attention
Highest-severity issues first. Click any row to see the evidence.Rule issues by check
colour = severityIssues by vendor, by severity
current quotations onlyEvery item, from design to payment
One row per item code. Coloured cells carry an issue (click for the evidence). A PO issued while the spec still has open deviations, goods billed before they are received, a price that drifts from quote to PO to invoice: each one is caught where the stages meet.End-to-end funnel
items · valueStage done, nothing foundProduct or scope differs from spec / POMoney: price, quantity billed, duplicateQuotation column carries the ordered vendor's deviations from the spec (all bidders while tendering)
Specification vs quotation
One table per specification sheet. Each row is a requirement from the designer's spec, each column a current vendor quotation. Click a coloured cell to see the evidence.Like-for-like by specification item
Prices are shown as quoted. Where a vendor prices one suite, the total is multiplied by the room count on the spec. Components one vendor includes and another leaves out are flagged, so a lower number is never mistaken for a cheaper offer.Commercial terms
A quoted price is only comparable once the terms are priced in. Bars show what each offer becomes delivered and installed at site; the matrix compares the terms themselves, with the best offer on each row ticked.Schedule and commercial attention
Beyond the document checks: quotations expiring, comparisons overdue, POs placed late, items at risk of missing their site date, budget overruns and pending change orders. Click a row for the item.Project documents
Loaded: HPL's sample set for Four Seasons Resort Mahé (3 specs · 3 quotations from 2 vendors), extracted with the same pipeline.
How the review works
What goes in, what the system does, and where a person decides.1 · You drop
Documents
Designer spec sheets, vendor quotations and their revisions, later quantity matrices and POs. PDFs as received.
2 · AI reads
Read into one structure
Every line: code, dimensions in mm, material and finish codes, fabric, fill, qty, price, and the page it came from. Transcribes only. Never decides.
3 · Rules run
Deterministic checks
Spec vs quote (F1–F8), quote hygiene (Q1–Q6), revision diff, vendor comparison. Same inputs, same result, every time.
4 · You see
Issues only
Each one says expected vs found, carries a severity, and links to the source page. Clean lines are not shown.
5 · You decide
Accept · Reject · Query
Design and commercial decisions stay with your team. The decision is logged; nothing is approved by the system.
6 · Goes out
Vendor query · PO
Export the issue list, send it to the vendor or designer, raise the PO once the quote is clean.
The four steps in detail
- Read. Claude reads each PDF into a fixed schema: codes, dimensions in mm, material and finish codes, fabrics, fill, quantities, prices, exclusions, and the page every value came from. It only transcribes. When it spots something odd on the page (a wrong code reference, a spec vs drawing conflict), it records that as an AI observation and leaves the value as printed. Observations are labelled as such in the issue list.
- Normalise. Codes are canonicalised (
LF-305→LF-0305), units converted, and per-suite pricing multiplied by the room count. - Check. Deterministic rules compare documents. There is no AI in this step, so the same inputs always give the same issues (see the rule list below).
- Review. Every issue shows expected vs found and links to the source page. Your team accepts, rejects or queries the vendor. The system never approves anything itself.
What this demo does not do yet
- Quantity matrix and layout plans: the specs say “Qty: refer to list” and no list was in the sample set. With the matrix loaded, rule F4 checks every quantity against it rather than only against the spec's per-item counts.
- Material / finish schedule: codes such as
ST-02andFB-01are checked for being referenced. With the schedule loaded, they are checked for meaning as well (e.g. that ST-02 is the stone the vendor offers). - POs and cost reports — done. Your PO and cost-report formats map onto the same item structure (Project → Area → Room type → Item → Vendor → PO → Change order → Final cost). Project control exports the cost report as an .xlsx in HPL's layout and prints purchase orders in HPL's PO format, straight from the item records.

FF&E project control · one current view
—
Procurement progress
Share of active item lines that have completed each stage of the pipeline. Click a stage to see what is stuck there.Cost by room type
budget / key vs forecast / keyCost by category
forecast · share of projectWhat needs your attention
Every open issue, grouped the way you want to work it. Click a row for the item.Accountability scoreboard
Open issues routed to the person who owns the category. Click a person to filter the tracker.Budget · Committed · Forecast · Variance
Project → Room type / area → Category → Item. Click a row to expand. Committed = PO + approved change orders. Forecast = committed + pending change orders, or the best comparable quote where no PO exists yet.Why the forecast moved
Largest drivers of variance, explained from the data: change orders, POs above budget, quotations above budget, VE savings.Like-for-like by specification item
Prices are shown as quoted. Where a vendor prices one suite, the total is multiplied by the room count on the spec. Components one vendor includes and another leaves out are flagged, so a lower number is never mistaken for a cheaper offer.Commercial terms
A quoted price is only comparable once the terms are priced in. Bars show what each offer becomes delivered and installed at site; the matrix compares the terms themselves, with the best offer on each row ticked.Vendor scorecards
On-time record from prior HPL projects, deviation rate from the spec-vs-quote review, share of this project's committed value.Savings proposals (value engineering)
A cheaper way to achieve the same design: original specification vs the proposed alternative, the saving, and whether the designer confirms the design intent is preserved. The system explains; the designer and Catherine approve.Changes to POs after issue (change orders)
Every change to a purchase order after it was placed: quantity, price or scope, with its reason and approval. Approved changes count as committed cost; pending ones sit in the forecast until approved.Delivery risk
PO date + production lead time + shipping vs the date the item is needed on site for the opening. Days late are computed, not reported by the vendor.Currency exposure
uncommitted forecast by quote currencyVendor concentration
share of committed valueQuotations expiring within 30 days
Prices lapse before the PO is placed more often than anyone notices. These need a reconfirmation email this week.Cost per key
This project's forecast FF&E cost per key and per m² by room type, next to HPL's prior projects. Same basis: FF&E only, excluding freight, duties and tax.Reference projects
Who owns what
Issues route by category to a named buyer; change orders to the procurement lead. Click a person to see their items in the tracker.Vendor directory
Who we buy from, who to write to, their standard terms, and their record with HPL. Every clarification email is addressed from here. Names and contacts are illustrative.How project control works
The workflow engine owns status, dates, responsibility and history. AI reads documents; rules decide what to show.1 · Inputs
Documents & data
Designer specs, quantity matrix, quotations and revisions, approved budget, POs, change orders, VE proposals, shop-drawing and sample approvals.
2 · AI reads
One item structure
Every document lands on the same item record: Project → Area → Room type → Category → Item → Vendor → PO. Transcription only.
3 · Rules run
Status, cost, risk
Milestone status, budget / committed / forecast / variance, normalised quotes, delivery projection, FX exposure. Deterministic.
4 · One view
Dashboard + issues
Drill from any number to the items and documents behind it. Only issues ask for attention.
5 · People decide
Approve · VE · PO
Commercial and design approvals stay with the team. Every decision is logged against the item and the person.
Extras beyond the brief, and why they pay
- Delivery risk from arithmetic. PO date + lead time + shipping vs required-on-site. Catches the late PO months before the vendor admits it.
- Quotation expiry watch. Lapsed prices are the most common cause of a re-quote at a higher number.
- Currency exposure. Uncommitted EUR and SGD forecast is shown so the CFO can hedge or accelerate POs.
- Vendor scorecards. On-time and deviation history feed the next tender, not just this one.
- Cost per key benchmarks. Every project adds to the library; the next budget starts from evidence.
- Accountability. Issues carry a name. The scoreboard is who has what open, in dollars.