Construction
Public tenders: preparing the documentation
What repeats in every bid and what has to be redone each time.
Bidding for public contracts consumes days of work, and a large part of that work is redoing what was already done for the last one. The difference between a team bidding ten times a year and one bidding thirty is rarely size: it is how much they have prepared in advance.
What repeats almost every time
| Block | How often it changes | What to have |
|---|---|---|
| Company details and capacity | Rarely | Up to date and ready |
| Financial standing | Annually | With the last update date visible |
| Similar works completed | When you finish one | With its completion certificate, collected at the end |
| Certifications and insurance | Annually | With warnings before they expire |
| Assigned technical team | Per bid | With qualifications and experience already digitised |
Important
The third row is the most valuable and the worst preserved. The completion certificate is requested when the works finish, while the client relationship is live; requesting it three years later for a specific tender is slow and sometimes impossible.
How to shorten preparation
- 1
A permanent "company documentation" file
What repeats, always current, not a folder per tender full of copies.
- 2
Due dates with warnings
An expired insurance discovered the evening before submission is the classic cause of exclusion.
- 3
One file per tender that links rather than copies
What is specific to that bid; the common part is referenced.
- 4
And collect the certificate as each job ends
The highest-yield investment and the most forgotten.
Watch out
Beware exclusion on a formality. Many bids fall not on price or technical merit, but because a document had expired, was wrongly signed, or a declaration was missing. It is the most avoidable part and gets the least attention.
After submitting
That last point reduces future exclusions: the same three mistakes nearly always repeat, and they only become visible once someone has been noting them.
Worth knowing
It applies equally to large private tenders, supplier approvals and supply competitions: the specification changes, not the fact that 70% of what is asked for is always the same.
›Can a previous bid be reused?
The common part yes; the technical content and price, no.
›What about joint ventures?
Each company contributes to the shared file; agree beforehand who keeps the whole.
›How long must submissions be kept?
Years: appeals and reviews can come much later.
A real case
The situation
A contractor spends four days per tender redoing the same documentation.
What you do
- Builds the permanent company file with due dates
- Collects the completion certificate as each job ends
What you get
Prepares bids in a day and stops losing tenders to expired documents.
The situation
The documentation is gathered in the final week.
What you do
- Keeps a permanent file current
What you get
Each tender costs a fraction of the previous one.
The situation
A certificate expires right on the deadline.
What you do
- Records expiries with a warning
What you get
Renewal happens beforehand.
The situation
A document is missing on submission day.
What you do
- Checks what is missing in advance
What you get
The gap closes with time to spare.
The situation
Each tender asks for the same in another format.
What you do
- Keeps the original and adapts on submission
What you get
The underlying work happens once.
The situation
What was submitted must be evidenced after the award.
What you do
- Keeps what was submitted, with its date
What you get
You answer with what was handed in.
This article answers
- documentation for public tendering
- preparing a public bid
- technical capability documentation
- what repeats in every tender