---
id: KB-CN-001
url: https://app.codecontract.io/help/construction/document-control-in-construction
idioma: en
categoria: sector-construccion
subcategoria: facility
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-006, KB-CS-016]
citadoPor: [KB-CN-003, KB-CN-004]
---

# Document control in construction

_People coming and going daily, and a liability that cannot be subcontracted._

**Responde a:** construction document control · subcontractor documentation construction · contractor safety coordination · where to start with site documentation

Construction has the hardest combination: many different people, coming and going weekly, working somewhere mistakes genuinely hurt. And the duty to check who enters is not subcontracted along with the work.

## The three levels to cross-check

| Level | Documentation | How often it changes |
| --- | --- | --- |
| The subcontracted firm | Insurance, tax clearance, certificates | Annual, and it expires |
| Each worker | Training, medicals, authorisations | Changes with every new person |
| Each machine | Conformity, inspections, authorisation to use | It travels between sites |

> [!IMPORTANT]
> The cross-check between the three is what decides whether someone can enter today. A firm with everything in order and a worker with expired training is exactly the case examined after an accident, and the one no folder solves.

## Why spreadsheets break here sooner than anywhere

Because status changes daily. The list someone updated on Monday no longer tells the truth on Wednesday, and the supervisor opening the gate is not in the office where that list lives.

**En corto**

- Status recalculates itself when something expires.
- It is checked from a phone, at the gate.
- Each branch — civil works, building, installations — adds its own on top.

> [!WARNING]
> Expiry warnings have to come with a long margin. Renewing training means arranging a course, and fifteen days does not do it: sixty does.

> [!NOTE]
> If you are audited on contractor safety coordination, this cross-check is exactly the file requested. Building it properly serves both purposes.

**What about self-employed contractors?**

Same as a firm: their own case with their documents.

**Can I give the safety coordinator access?**

Yes, read-only and scoped to that site.

**Does it work across several sites?**

One case per site, and machines travel with their own.

## Ejemplos

**A contractor tracks nine subcontractors in a spreadsheet updated by one person.**

- One case per subcontractor, with workers and machines inside
- 60-day warnings

→ The supervisor checks at the gate from a phone, and the spreadsheet stops being the only place the truth lives.

**Each project keeps its papers its own way.**

- Uses the same file structure for all

→ The answer does not depend on which project is asked about.

**The site manager carries the documentation on their phone.**

- Stores captures in the project's file

→ The record survives a change of personnel.

**At close-out, documentation from months back is missing.**

- Requests as the event happens, not at close-out

→ Close-out becomes a formality.

**A subcontractor comes in without being current.**

- Checks the status before authorising

→ The gap shows before the gate.

**A client asks you to evidence something from a finished project.**

- Keeps the file beyond the end of works

→ The warranty period is faced with the record.