---
id: KB-CS-015
url: https://app.codecontract.io/help/construction/civil-works-and-public-tenders
idioma: en
categoria: sector-construccion
subcategoria: obracivil
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-006, KB-CS-016]
citadoPor: [KB-CN-009]
---

# Civil works and public tenders

_Documentation reviewed by a public authority, on deadlines that are not negotiable._

**Responde a:** documentation for a public tender · technical and financial standing tender · joint venture documentation · contractor classification civil works

In public tendering, the difference from private work is not the volume of paperwork: it is that someone else sets the deadline and it does not move. Late means absent, and the documentation comes from third parties who do not share your urgency.

## The three modules, each in its moment

| Moment | Module | For what |
| --- | --- | --- |
| Preparing the bid | Trackline | Gathering standing, certificates and documents from joint-venture partners |
| Signing the consortium agreement or the bid | Consigne | Several companies signing, in order if a signatory validates last |
| Keeping what was submitted | SmartCheck | Certifying the file exactly as submitted, with its date |

> [!IMPORTANT]
> Certifying what was submitted on the same day has a concrete purpose: if there is later an appeal or a dispute about what was handed in, you hold the exact set with a third party's date, not a folder you could have touched afterwards.

## Frameworks cited in this area

Public procurement rules, contractor classification and standing, and — once work starts — contractor safety coordination and construction health and safety regulation. What each tender document requires is stated in that document, and the specific obligations come from your adviser: this only explains how to have the paperwork ready and dated.

> [!WARNING]
> Documentation from consortium partners comes from people who do not answer to you. It is the case where asking two weeks ahead with automatic reminders shows most, because the alternative is phoning around in the final three days.

> [!NOTE]
> Saving each tender's file as a template saves most of the work on the next one: what gets asked for changes less than it seems.

**Can I give the authority access?**

Submission normally goes through their platform; this is for having it gathered and proven beforehand.

**What if a consortium partner does not deliver?**

The case shows it with a name and a date, which is what lets you chase it internally.

**Does it help justify delivery afterwards?**

The dated history is exactly what later checks ask for.

## Ejemplos

**A contractor bids on four tenders a quarter and the final 72 hours are always a scramble.**

- Builds the tender file as a template
- Requests partner documents two weeks ahead with reminders

→ Reaches the deadline with the file complete, and certifies the submission the same day.

**Tender documentation is prepared in the final week.**

- Gathers what repeats into one file

→ The second tender costs half.

**A document is missing on submission day.**

- Checks what is missing in advance

→ The gap closes with time to spare.

**A certificate expires just before the deadline.**

- Records expiries with a warning

→ Renewal happens before the tender.

**Each tender asks for the same document in another format.**

- Keeps the original and adapts on submission

→ The underlying work happens once.

**The contract is awarded and what was submitted must be evidenced.**

- Keeps what was submitted, with its date

→ You answer with what was handed in then.