| Ref | Text | Source | Page |
|---|---|---|---|
| 3.1 | HVAC for all occupied floors… | marina-tower-rfp.pdf | 3 |
| 4.2 | LV distribution with N+1… | marina-tower-rfp.pdf | 4 |
| 5.4 | Structured cabling Cat6A… | marina-tower-rfp.pdf | 5 |
Capture the tender
Every line traces to a page
Each requirement keeps its source filename and page number, so a reviewer can jump straight back to the clause.
A hand-built mock in the site theme, modelled on the real screen and populated with our demo tenant's data — not a screenshot. Hover to pause.
More in Capture the tender
Keep going
marina-tower-rfp.pdf10 pages · rfp · Marina Tower — MEP Fit-out
1Upload2Analyse3RFI4Compliance5Export
Drop the tender in
Upload the RFP and EstiWright pins the tender number, page count and source file before anything else happens.
| Ref | Discipline | Text | Page |
|---|---|---|---|
| 3.1 | mechanical | HVAC for all occupied floors per ASHRAE 62.1. | 3 |
| 4.2 | electrical | LV distribution with N+1 redundancy on risers. | 4 |
| 5.4 | elv | Structured cabling Cat6A to every workstation. | 5 |
1Upload2Analyse3RFI4Compliance5Export
Extract the requirement register
One pass over the tender produces a structured register — reference, discipline, mandatory flag and source page.
3.1 · HVAC per ASHRAE 62.1
—Mandatory
4.2 · LV N+1 redundancy
—Mandatory
5.4 · Cat6A to workstations
—Optional
Mandatory versus optional
Every requirement carries an explicit mandatory flag, so nothing binding is left to memory.
See this on your own tender.
We'll run your RFP through the same pipeline and show you the output.