Custom construction software

Bring the site and office into one system.

We build software to manage drawings, contractors and budget changes. We help organise your workflow, connect the tools you already use and launch the first release.

Equipment classification and asset details
Related project · LENS Data Explorer

Engineering assets, connected records and revision history.

  • The approved drawing version
  • An owner for every action
  • Changes with a decision history
Industry workflows

Follow project decisions from request to approval

A drawing revision, site issue or change order can affect schedule and budget. We map who submits, checks, approves and acts on each item, then connect the existing tools that carry the source information.

Where the work gets stuck

  • Site teams and office teams use different drawing revisions.
  • Change requests move through email without a clear approval state.
  • Progress reports arrive after a decision has already been made.
  • Contractor records, documents and payments are difficult to connect.

How we would approach it

  • We agree drawing identifiers, version rules and the people authorised to approve changes.
  • We link project records to BIM elements where the current tools expose the required data.
  • We record site evidence with its location, time and reviewer, including delayed synchronisation.
  • We keep proposed cost or schedule changes separate from approved revisions.
Functional modules

Keep site work tied to drawings, owners and approvals

Give site teams the approved information and give the office a record of changes, evidence and outstanding decisions.

BIM and project data

We link model elements to documents and tasks through available interfaces, keeping the project and version identifiers visible.

Schedule review

We compare the approved plan with reported progress and flag missing or conflicting updates for the project manager.

Site inspections

We capture observations, photos and follow-up tasks, with an assigned reviewer and a recorded closure decision.

Cost and change control

We track proposed changes, estimates and approvals, showing which revisions have been included in the current budget.

Contractor coordination

We give contractors access to their assigned work, required documents and open decisions, with permissions tied to the project.

Document control

We distinguish drafts, approved drawings and superseded versions, preserving the review history and links from site records.

Systems and data to assess

Connect the drawing, the site update and the project record

Project plans

Identify the approved schedule, task codes and how revised plans reach site teams.

Document stores

Link to the source drawing and its version rather than maintaining uncontrolled file copies.

Contractor tools

Match company, project and assignment identifiers so each update reaches the responsible contractor.

Cost systems

Agree cost codes and the approval point at which a variation updates commitments or budget.

Field data

Define required evidence, device access and what happens when an update arrives after an offline period.

Reporting

Separate submitted progress, checked work and unresolved issues, with dates and source references.

Controls and compliance

Keep project evidence ready for review and handover

We agree document, inspection and handover requirements with your project and site owners. The software records evidence and routes decisions to the authorised people.

Document status and versions

Agree naming, approval states and version references so site records identify the drawing used for the work.

Handover documentation

Define required certificates, material records and completion evidence, with missing items assigned to an owner.

Inspection and correction

Link each observation to evidence, corrective work and a reviewer’s acceptance or reason for return.

Site access and responsibility

Define who may record, assign and close an issue, and which site events require immediate escalation.

Workflow examples

Pilot a site issue from observation to acceptance

One possible first workflow

A site employee records an issue against a drawing version and assigns it to a contractor. The contractor submits completion evidence; the reviewer accepts the work or returns it with a reason.

Start with one site and one inspection workflow, retaining the document repository and accounting system. BIM authoring and quantity take-off are separate from this issue-management release.

Bring a sample issue, drawing-version rules, contractor roles and field connectivity constraints. The site owner confirms what evidence is needed to accept the work.

Checks for this example release

  • The issue retains its original drawing reference when a new revision is published.
  • Only the authorised reviewer can accept the work; returns retain the reason and previous evidence.
  • A delayed field update preserves its capture time and does not create a duplicate issue.
Review the assessment brief
Your next step

Where Does Project Coordination Break Down?

Bring one document or approval flow. We will map the people, tools and records needed for a first release.

Discuss construction software