Tender packages and the register
What is extracted from each document type, how narrative requirements are surfaced, de-duplication, classification, addenda.
Package documents
| Document | Extracted |
|---|---|
| General / mechanical / electrical specifications | Numbered clauses; normative statements in prose |
| Data sheets | Each line item: parameter, value, unit, tag |
| Standards and codes list | Standard, part, edition |
| Inspection and test requirements | Tests, witness/hold points, certification levels |
| Documentation requirements | Deliverables, formats, numbering (Annex references) |
| Drawings | Title-block requirements, notes |
| Instructions to tenderers | Submission format, deviation-table layout, Q&A window |
| Addenda, Q&A | Changes diffed against the register |
Normative language
shall · must · minimum / maximum · not less / more than · in accordance with · to be provided. Narrative statements containing these are extracted as candidate requirements marked 'from narrative, confirm'. Over-inclusion is intended; the bid manager strikes, the agent does not guess.
De-duplication
Requirements repeated across documents (spec and data sheet) are linked; the decision is made once. Conflicts between documents (different values for the same parameter) are flagged for a clarification question.
Classification
performance · material · standard · inspection/test · documentation · commercial-technical. Class determines where evidence is searched.
Addenda
Diffed against the register: changed, added, withdrawn requirements with a change log. Affected matrix lines are re-run and status changes flagged.
Limits
Package up to 300 pages per Tender (+0.3 per additional 150). Scanned PDFs are OCR'd; drawings are indexed for text only. Password-protected files must be unlocked.