Fire & Safety · Project delivery

Track delivery through witnessed handover

Track technical submittals, material delivery and test evidence in one project record. Engineers, procurement teams and commissioning witnesses review the relevant decisions.

Each capability runs standalone Uploads or manual entry Raw readings and signatures never change
Harbourview Mixed Use CentreSprinkler system delivery · Pump room + retail podium
Awaiting engineer sign-off
  1. Technical submittalPackage SUB-012 issued to the consultant
    Approved
  2. Material availability1 late delivery open · 38 of 39 lines on time
    Sign-off
  3. Delivery and receiptsOrders matched · delivery notes being read
    Working
  4. Testing & commissioningWaits for installed equipment
    Queued
  5. Handover evidenceReport and evidence manifest
    Queued
pump set late for need date · awaiting PM
Exception · Schedule riskCritical

Fire pump set promised after the installation need date

Supplier update · 02 OctConfirmed delivery in week 21.
Project schedule · Rev 4Pump room installation starts in week 20.
Owner: Procurement engineerMilestone impact shown
Submittal documents verified44 / 46
Open exceptions before handover3
Who uses it
Submittal coordinators, buyers, project managers and commissioning engineers
Lifecycle stage
Delivery / Installation, through testing to handover
Works from
Your approved products, manufacturer files, orders, schedule and test plans
Sign-off
A named engineer or witness approves every issued record
What changes

Keep delivery evidence with the project today

Certificates sit in supplier emails, order dates in the ERP, test readings on paper forms and photos on phones. When the consultant or the authority asks for proof, the team rebuilds it by hand.

One job, three lanesProblems found at handover, or the week they start
Where it surfaces todayWhere the use case flags itNeed date
Submittal SUB-012Certificate for the wrong pump model
Fire pump set orderDelivery promised after the need date
Pump test and witnessWitness signature missing

Example from the Harbourview walkthrough, weeks 12 to 24 of the program.

Assembling a submittal

Today: Coordinators gather product files manually and check each revision.

Classify files, extract model and certificate details, and flag gaps before compilation.

Certificate evidence

Today: A certificate for a similar model slips into the package and the consultant returns it.

The engineer verifies model, certificate scope and revision before approval.

Tracking materials

Today: Order dates, supplier promises and site need dates live in different records.

Match demand to stock and orders, compare dates and show each shortage’s impact.

Supplier updates

Today: Revised dates arrive by email and are noticed after the installation window.

Show supplier updates with age and source; the buyer confirms revised dates.

Field testing

Today: Readings, photos and signatures are scattered across forms and phones.

Capture test readings and photos on site. Missing evidence keeps the record pending.

Defects and retests

Today: Failures are closed in conversation with no record of the retest.

Each failure gets an owner, a correction and a retest trail before the witness signs.

Proof at handover

Every link in the evidence chain, for every asset

Handover evidence is only as strong as its weakest link. Each record points to the one before it, so a gap shows the moment it opens.

Fire pump set · Serial 7741Seven records, each tied to the one before it
  1. Approved productShortlist Rev 2 · FP-750
  2. CertificateModel and scope verified
  3. Purchase orderPO-4471 · promised wk 21
  4. Delivery noteDN-882 · serial 7741
  5. Test readingsFlow and pressure logged
  6. Witness signatureSigned on their own account
  7. Handover manifestIssued with every source
What it does

Three capabilities, one delivery record

Start with the step that slows your handovers most. Each capability works on its own uploads, and each passes approved data to the next when you connect them.

SubmittalsSubmittal coordinator + engineer

Assemble submittals where every document matches the approved product

Select equipment from the approved list or a manual schedule, map the documents each item needs, close the gaps and issue an indexed package once an engineer approves the statements.

AI suggests

  • Document type, model and certificate details
  • Draft responses to specification clauses
  • Missing or inconsistent evidence

Rules automate

  • Document checklist and package order
  • Revision matching against the register
  • Approval routing and PDF compilation

Your engineers decide

  • Verify certificate scope and revision
  • Edit or reject each drafted response
  • Engineer approves the package
pump set certificate names FP-500, schedule says FP-750 mismatch
valve datasheet Rev 04 superseded by Rev 05 replace
alarm panel certificate scope matches the location verified
What you get

Indexed technical submittal with document register, specification response, certificate evidence, drawings and transmittal.

Workflow

One delivery record, from submittal to signed handover

Automated steps prepare the evidence. People make the calls. Work cannot move past a gate while a critical exception is open.

  1. Create the submittal

    Select equipment and map the documents each item needs.

    AutomatedCoordinator

  2. Approve the package

    Verify certificates, approve responses and issue the package.

    Approval gateEngineer

  3. Match demand to orders

    Link the approved BOM to orders, stock and supplier dates.

    AutomatedBuyer

  4. Resolve supply shortages

    Compare need dates, assign expediting and record the impact.

    BuyerProject manager

  5. Record tests on site

    Capture readings, photos and signatures against each procedure.

    Commissioning engineer

  6. Resolve test defects

    Assign corrections and record retests until each item passes.

    AutomatedContractor

  7. Witness and hand over

    The witness signs and the report is issued with its evidence.

    Approval gateWitness
Prepared or reviewed stepApproval gate with named sign-off
At a glance

What goes in, what comes out

Everything you bring flows through one controlled use case. Hover or tap an input to see which outputs it feeds.

You bring

Approved product listOr a manual equipment schedule with models
Manufacturer filesDatasheets, certificates and specification extracts
Orders and supplier datesPurchase orders, stock, commitments and delivery notes
Project scheduleInstallation need dates and milestones
Test plans and readingsProcedures, criteria, photos and witness schedules
The use case Technical Submittal, Procurement & Commissioning
  • Technical submittal automation
  • Procurement & project intelligence
  • Testing & commissioning
2 approval gatesFull audit trail

You get

Technical submittal packageDocument register, clause responses, certificates and transmittal
Shortage and action logMaterial status, supplier actions and schedule impact
Commissioning reportTest sheets, deficiency log, retest trail and signatures
Handover evidence manifestEvery certificate, reading and photo with its source
Who it is for

Built around the people who deliver and prove the system

Each role sees the evidence it needs and approves only what it is authorized to approve.

Compiles

Submittal coordinator

Maps documents, closes gaps and compiles the required submittal package.

Verifies

Technical engineer

Checks certificate scope and revision, and approves clause responses before issue.

Expedites

Procurement engineer

Confirms supplier dates, chases shortages and records alternate actions.

Plans

Project manager

Sees material risk against milestones and accepts or escalates the schedule impact.

Tests

Commissioning engineer

Captures readings and evidence on site and drives each failure to a retest.

Witnesses

Commissioning witness

Reviews the evidence and signs the record. Nothing is signed on their behalf.

Designed for

Specialist fire contractorsMEP contractorsDesign and build contractorsCommissioning specialistsConsultants reviewing submittalsOwners managing handover
Scope & limits

What this software will not do

Submittals, delivery dates and test results are evidence other people rely on. Every record in the use case stays with a named person, on the record.

How every output moves from AI suggestion to an issued record

  1. AI analysisAutomated
  2. Draft package or recordMarked as draft
  3. Engineer or buyer reviewAccept, correct or reject
  4. Engineer or witness sign-offWhere required
  5. Controlled recordVersioned snapshot
  6. Audit trailWho, what, when, why

A name match is not a certificate

A matching product name never proves certification. The engineer verifies model, scope and revision.

It never invents a reading

AI does not infer unmeasured values or fill in witness evidence. Raw readings and signatures stay unchanged.

Nothing is signed for the witness

A test stays pending until the required witness signs through their own account. Nobody signs on their behalf.

It does not stand in for an authority

An internal approval records your team’s decision. It never implies acceptance by the consultant or authority.

Supplier dates are shown as reported

Supplier dates retain their source and age. The buyer reviews each date and confirms or corrects it.

Your criteria, not ours

Pass and fail thresholds follow your configured test criteria. The software does not invent acceptance limits.

Standalone first

Each capability runs on its own uploads and manual entries. No other module is a prerequisite.

Connects when you are ready

Optional links to ERP, procurement, document management and consultant portals, each with mapped fields and agreed data ownership.

Your data stays yours

Separate tenants and projects, role-based access and encryption at rest and in transit. Model training requires written permission.

Example project

A ten-minute walkthrough of Harbourview

Submittal3 min Procurement2 min Testing2.5 min Defects1 min Approval1.5 min
Demo scenario · sample project

Pump room delivery and testing for a mixed-use center

The walkthrough follows the fire pump set from submittal through delivery to a witnessed test, across all three capabilities.

EquipmentFire pump set
Orders12 POs
Exceptions shown3
Sign-offs2 gates

  1. Open the pump room submittal

    The document checklist shows what each item needs and which files are already in.

    Technical submittal

  2. Catch a certificate for the wrong model

    Replace the certificate for the wrong pump model, then approve the corrected response.

    Technical submittal Approval gate

  3. See the pump set arrive late

    The confirmed supplier date falls after the installation need date, and the affected milestone is highlighted.

    Procurement

  4. Record the revised date and an action

    The buyer confirms the date, links an alternate action and the project manager accepts the impact.

    Procurement

  5. Run the pump test on site

    Record readings and a photo. A missing witness signature keeps the test pending.

    Testing & commissioning

  6. Close a defect with a retest

    A failed pressure switch gets a correction and a retest, and both stay on the trail.

    Testing & commissioning

  7. Witness signs and the report is issued

    The signature is captured and the record joins a controlled commissioning report with its evidence manifest.

    Approval gate
Pilot evaluation

Agree the measures before the pilot

We agree a baseline with you first, then compare. We do not promise a number before your own data shows it.

  1. 1
    Agree a baselineYour current process, measured the same way
  2. 2
    Run the pilotOne system type on one live project
  3. 3
    Compare on your dataSame measures, same denominator, reported openly

Submittal preparation time

Working time from an approved product list to an issue-ready package.

First-pass completeness

Packages accepted with complete, current documentation.

Material availability

Lines available by their need date, and schedule days at risk.

Supplier confirmation lag

Time from an order or change to a confirmed supplier date.

Retest cycle time

Time from a failed test to a witnessed pass, and deficiencies outstanding.

A first pilot validates one system type on one live project before wider claims.

Getting started

Define a pilot with your team

  1. Review the requirements

    We send the consolidated requirements for the use case and its three capabilities.

  2. Review the workflow example

    Review the example workflow, its records and approval points with your team.

  3. Confirm the project scope

    We map your systems, approvers and the capability to start with.

  4. Define the pilot scope

    Your checklists, templates, test procedures and sample packages define the pilot.

  5. Pilot

    Evaluate against your baseline

    One system type on one live project, measured on the agreed pilot measures.

Continue exploring

Also in Fire & Safety

Engineering & design

AI Fire Design

Review design basis, compliance, product choices and drawings in one workspace.

Explore the use case Pre-sales & tendering

Pre-Sales Estimating & Quotation

Measure quantities, build sourced estimates and prepare quotations for approval.

Explore the use case Inspection & service

Inspection & Asset History

Capture inspection evidence, review findings and keep a history for each fire asset.

Explore the use case Business operations

Fire Operations Intelligence

Connect source data, approved metrics and dashboards to reviewed management actions.

Explore the use case

FAQ

What does the submittal-to-commissioning workflow connect?

It brings together technical submittals, procurement evidence and commissioning records so teams can trace document reviews, equipment details and test evidence through the project.

Can we start with one capability?

You can scope submittals, procurement tracking or commissioning individually, or connect them end to end. Define the records and approval handoffs required for your project.

Who approves technical submittals?

A named engineer checks the document scope, equipment model, certificate details and revision before approving a response. Consultant and authority acceptance remain separate project decisions.

How are missing readings and signatures handled?

The record remains pending until a person captures the missing reading or signature. Unmeasured values and witness evidence must be supplied by the responsible team.

Do procurement records require an ERP connection?

Uploaded orders, stock lists and supplier updates provide a starting point. Any ERP or logistics connection needs its own field mapping and agreed source ownership.

What should we validate for site commissioning?

Validate the test forms, required readings, photo evidence, signatures and review process with the site team. Confirm device and connectivity requirements before relying on site capture.