Tender reading service
Clarification register service
Tender questions lose value when they are detached from the clause that caused them. This service creates a register that keeps the source, question, response and bid impact together.
Illustrative example
What the reviewed deliverable contains
The rows below are synthetic. They show the structure of the output, not a client project.
| Item | Source | Review status |
|---|---|---|
| CL-01 | Scope section 4.2 | Confirm who provides cable supports |
| CL-02 | Drawing E-102 | Confirm feeder rating at boundary |
| CL-03 | Returnables R5 | Confirm required file format |
Deliverables
What you receive
- Numbered clarification register
- Source document and section for every question
- Question owner and issue date fields
- Client response and closure status
- Bid impact and assumption fields
Inputs
What we need from you
- Tender pack and addenda
- Existing questions from the bid team
- Client clarification format if supplied
- The person responsible for issue
Checked by people
How the work moves from pack to issue
01
Collect
We combine questions from the pack review and your technical and commercial reviewers.
02
De-duplicate
Related questions are grouped and each one keeps a clear source reference.
03
Prepare for issue
A person checks tone, scope and status. Your team decides what is sent.
Scope boundary
What is not included
- Sending questions to the principal
- Legal advice
- Accepting client answers on your behalf
- Changing the priced scope without approval
Project enquiry
Discuss clarification register service
Share the job type, bid stage, deliverables and closing date. A person reviews every enquiry.