Better tender packs lead to clearer builder pricing and fewer assumptions.
- What builders need
- Make allowances explicit
- Help tender comparison
- Give clear pricing instructions
- Maintain an issue record
What builders need
Builders need drawings, specifications, schedules, client selections, site constraints and pricing instructions.
Make allowances explicit
If selections are undecided, say so. Clear allowance instructions help prices be compared fairly.
Help tender comparison
A consistent tender return format makes review about scope, value and risk rather than decoding formats.
Give clear pricing instructions
State the tender deadline, return format, pricing basis, treatment of tax, required breakdown and how queries will be answered. A consistent return structure saves time for both tenderers and the reviewing team.
Maintain an issue record
When information changes, issue it to every tenderer with a revision note and confirm whether the return date changes. Do not rely on separate email threads to communicate material scope changes.
Review checklist
- Publish a complete drawing and specification register
- Identify client-supplied items and undecided selections
- Set one clarification process
- Issue revisions to every tenderer consistently
FAQs
What should an architect include in a tender pack?
Drawings, specification notes, schedules, pricing instructions, known selections and assumptions builders should use.
Why do builder tenders vary so much?
They often vary because builders make different assumptions about missing information and provisional work.
Use this thinking on a real project pack
Send drawings, specifications, notes or a current quote. Quotify will show how the project can be structured for review.
