Technology that makes site decisions easier to see

A site team can have drawings, messaging groups, spreadsheets and a reporting app and still lack a reliable answer to a basic question: what is the current approved position? Delay grows when evidence sits in one channel, the technical response in another and the responsible person is only known informally. The practical purpose of construction technology is to reduce that decision latency without weakening review or approval.

ISO 19650-1 describes an information-management framework that includes exchanging, recording, versioning and organising information across the asset life cycle. That principle matters even on projects that do not use a full BIM model. A controlled drawing register, inspection record or technical query can follow the same discipline: identify the information, its revision, its status, its owner and its permitted use.[1]

A useful issue record must let someone who was not present understand the problem and make the next decision. “Beam problem on level 3” is not enough. A decision-ready record connects the observation to a precise location, evidence, the governing information and a named response path.

The record should be proportionate to risk. A minor housekeeping action may need a photograph, owner and due date. A structural discrepancy may require coordinates or grid lines, marked-up drawings, measurements, temporary controls, a formal technical query and approval from the person authorised under the contract.

The minimum workflow is observe, classify, assign, respond, verify and close. Each state needs an entry rule and an owner. An item should not move to “closed” because somebody replied; it should close only when the required action has been checked against the acceptance criteria.

buildingSMART’s BIM Collaboration Format illustrates this principle in model-based coordination: an issue can identify the exact location of a clash, classify it and assign it to the relevant disciplines. The same logic works for field issues without specialised BIM software. The essential design choice is a structured issue object that travels with its context, not a screenshot detached from its history.[3]

A common data environment (CDE) should tell users which information is being developed, which is shared for coordination, which is authorised or published and which is archived. If every document appears equally valid, the platform is only shared storage. The UK BIM Framework guidance stresses that the CDE includes processes and rules so people can understand the current version and what it may be used for.[2]

For a small project, the technology may be simple: a controlled cloud repository, naming rules, a revision register and an issue log. For a complex project, the same control model may sit behind model coordination, mobile inspections, transmittals and dashboards. Complexity should follow project risk and interfaces, not software ambition.

A workflow that requires long narrative reports, perfect connectivity or repeated data entry will be bypassed. Site capture should work on a phone, tolerate weak connections, reuse project data and ask only for fields that change the decision. Office-based review can add classification, linked documents and formal response details later.

Role design is equally important. Supervisors should be able to raise and update observations; designers should answer technical questions; authorised managers should approve instructions; and reviewers should verify close-out evidence. Permissions should match contractual authority so an informal comment cannot be mistaken for a construction instruction.

Counting uploaded photographs or completed forms rewards activity rather than control. Better measures show whether important decisions are moving and whether the same failures are returning. Review trends by discipline, location, subcontract package and cause rather than using a single red-amber-green total.

Useful weekly measures include median response time, overdue high-priority items, issues reopened after closure, repeat defects, work awaiting information and upcoming activities without approved inputs. These indicators do not replace engineering judgement; they direct attention to where judgement is needed.

Start with one high-friction workflow, such as technical queries or inspection close-out. Map its current path, identify where context is lost and define the minimum record before selecting or configuring software. Pilot it with one project area and a small group of real users.

During the pilot, review overdue items twice each week and interview the people entering and answering records. Remove fields that do not influence decisions, add missing evidence requirements and publish a one-page status definition. Expand only after the team can explain how an item moves from observation to verified closure.