Adaptations: the change nobody wrote down

A scaffold handed over in March is rarely the same scaffold in June. A lift goes on, a bay comes out to let a delivery through, a section is sheeted because the trade underneath got tired of the weather. Each one is a small, reasonable request. Together they are the reason nobody can say what the structure was built to.

Why the informal ones are the dangerous ones

An adaptation that goes through the office gets looked at: does it still sit inside the compliance sheet, does the tie pattern still work, does the loading class change, does the client need a new certificate. An adaptation done as a favour on a Friday gets none of that. The scaffold may well be fine. The evidence that it is fine has quietly disappeared.

What a usable adaptation record contains

• –Which structure — not which site, which structure.
• –What changed, in the terms the design uses: lifts, bays, ties, cladding, loading.
• –Who asked for it, and who carried it out.
• –Whether the original design still covers it, or whether it went back for sign-off.
• –The new tag status and whether a fresh handover was issued.

None of that is onerous when it is a form on a phone at the point the work happens. All of it is impossible to reconstruct a year later, which is exactly when somebody asks.

Why adaptations go unrecorded

Not through carelessness. An adaptation happens because something on site required it, usually under time pressure, often at the request of another trade, and the work itself takes less time than writing it up. The record is the part with no immediate consequence for getting the job done, so it is the part that gets deferred and then forgotten.

The consequences arrive later and elsewhere: an inspection against a structure that no longer matches its paperwork, a handover tag describing a different configuration, and — commercially — variations that never get paid because no contemporaneous record exists that the work happened.

Common mistakes

• –Recording adaptations at the end of a job rather than as they happen
• –No route for a gang to log a change quickly from site
• –Changes made at another trade's request with no record of who asked
• –Adaptation logged operationally but never assessed against the design
• –No photographs, so the change cannot be evidenced later
• –Treating the log as paperwork rather than as the basis for getting paid

Worth knowing: the log is a commercial document too

Adaptation logs are usually introduced for compliance reasons and end up earning their keep commercially. The same record that keeps a structure's compliance basis current is the contemporaneous evidence that work was requested, done and dated — which is precisely what a client's quantity surveyor asks for when a variation is queried at final account.

Firms that treat the log as paperwork tend to have patchy records and lose arguments about money. Firms that treat it as the basis for getting paid tend to have good records and, incidentally, a compliance position that holds up. The second framing gets far better completion from gangs, because the benefit is visible to the people doing the logging.

• –Log at the point the work happens, not at the end of the job
• –Record who requested the change, not only what was done
• –Photograph it — a picture settles arguments that a description does not
• –Make sure the log reaches whoever raises variations, automatically rather than by memory

Where this connects: make logging worth the gang's time

Adaptation logs fail for one reason: the person who has to write it gets nothing from writing it. The work is done, the client is happy, and the record is an administrative task with no visible benefit to the people being asked to do it.

Firms that get genuine completion frame it commercially rather than as compliance. An adaptation that is logged becomes a variation that gets paid; one that is not becomes work the firm did for free. Gangs generally log reliably once they have seen that connection made explicit — and the compliance benefit follows as a by-product rather than having to be argued for.

• –Frame the log commercially, not as paperwork
• –Make logging possible from site in under a minute
• –Route the log automatically to whoever raises variations
• –Show gangs what was recovered because they logged it
• –Capture who requested the change, not only what was done
• –Photograph it — a picture settles what a description does not

One practical test: count last month's variations

Count the adaptations logged last month and the variations raised from them. If the second number is meaningfully smaller than the first, work is being done and not charged — and the log is doing its compliance job while failing its commercial one.

If both numbers are near zero on a busy month, the log is not being used at all. Gangs adapt structures constantly; a month with no adaptations recorded almost never means a month with no adaptations, and that gap is the clearest measure available of whether logging is worth the gang's time as currently designed.