There is no single list of what is happening
Works live in departmental spreadsheets, paper files, and the memory of the officer handling them. Assembling a picture across sectors takes days, and it is out of date by the time it is presented.
Public Works & Contract Monitoring Systems
Leadership needs to answer which works are active, which are stuck in procurement, which are awarded but never started, and which are ready for a payment decision. Firelinkx scopes systems that hold that in one register, with the site photograph and the inspection attached to the project instead of sitting in a WhatsApp group.
Who this serves
Regional and municipal bodies accountable for works they do not perform themselves
Executive officers, engineers, department heads, project and procurement officers, site inspectors, and the Council, Ministry, and audit users who receive what the office reports.
Projects disappear after approval
Between approval and a contractor arriving on site there is a procurement stage that nobody outside procurement can see. Works sit there for months and the delay is only noticed when someone asks why nothing has started.
Evidence is inconsistent and unfindable
Before, during, and after photographs, inspection notes, and contractor submissions arrive by message and are stored wherever the recipient stored them. When the file is needed for a payment or an audit, finding it is a search, not a lookup.
Reporting is rebuilt from scratch every time
Weekly, monthly, Council, Ministry, and audit reports each get assembled by hand from the same underlying facts, which is both expensive and the reason two reports on the same works can disagree.
Operational workflow
From an approved work to a completed one somebody can audit
Every work is one record that accumulates its own history. Procurement stage, contractor, milestones, evidence, inspections, and payment readiness attach to it, so the register is the report itself.
1
Register the work
Sector, department, community, estimated value, and the officer responsible. A work that exists in the programme exists in the register from the day it is approved, well ahead of the day it starts.
2
Track it through procurement
The stage it has reached and how long it has been there. Works that have not moved raise themselves before anyone asks.
3
Record the award
Contractor, contract value, duration, and the start conditions. Awarded and not started is its own visible state, because it is the state where time is most often lost.
4
Track implementation against milestones
Progress recorded against the milestones the contract defines, so percentage complete is a claim with something behind it.
5
Capture evidence on site
Before, during, and after photographs with the date and the work they belong to, captured by the officer standing in front of it.
6
Inspect and record the outcome
The inspection, who carried it out, what it found, and whether it passed. A failed inspection creates the remedial action instead of ending in a note.
7
Assemble payment readiness
The system states what is present and what is missing against the requirements for a payment decision. It supports the decision and does not make it.
8
Complete, then follow up
Completion, the defects period, and the maintenance follow-up that is normally where the record stops and the problems start.
Records and controls
The register, the evidence, and who may change either
What the register holds
One record per work, carrying everything attached to it, so continuity survives a change of officer.
- Works and projects by sector, department, and community
- Procurement stage, and how long it has been at that stage
- Contractors, contracts, values, and durations
- Milestones, progress, and revised dates with reasons
- Evidence, inspections, and remedial actions
- Payment readiness, completion, and defects follow-up
Who may see and who may change
Public bodies need read access to be wide and write access to be narrow, and the two questions are answered separately.
- Enter and update works in your own department
- Record an inspection outcome
- Confirm a milestone as reached
- Move a work to awarded, suspended, or terminated
- Sign off payment readiness
- Read-only access for Council, Ministry, and audit users
What escalates on its own
The value of a register is that overdue things announce themselves before a report is due.
- Sitting at the same procurement stage past its threshold
- Awarded, with no start recorded
- Past its completion date with progress outstanding
- Required evidence missing for the current stage
- Inspection due, or a failed inspection with no remedial action
- Defects period ending with an item unresolved
Reporting that does not need assembling
Each audience gets its own view of the same underlying register, which is why two reports cannot disagree.
- Executive dashboard across every sector
- Status by department, community, or contractor
- Procurement movement and where works are held up
- Works overdue, blocked, or awaiting inspection
- Payment-readiness position for a period
- Council, Ministry, and audit packs with their evidence
Project scope
Start with the register, because everything else reports off it
The first release should make one live list of works exist and be trusted. Evidence capture, inspections, and payment readiness are worth far more once the register is complete, and close to nothing before it.
- The works register, procurement stage tracking, and contractor records form the foundation, and the reporting that leadership wants is downstream of them.
- Field evidence capture, inspections, and remedial actions are the second release, and they are what turn the register from a list into a control.
- Evidence files stay private by default, with access through short-lived signed links and only the metadata and object keys held in the database.
- Migration covers the existing programme, contractor records, and any historical works still under a defects period, with reconciliation before cutover.
Investment
What a system like this costs
Public bodies procure against a specification, so the specification is the first deliverable and the build is priced from it and not from an estimate.
Specification
Fixed-scope engagement
A written suite covering requirements, functional behaviour, roles and permissions, the data model, architecture, reporting, security and retention, and acceptance criteria. Procurement-ready, and yours whether or not Firelinkx builds from it.
Build
Quoted from the specification
Priced against the agreed document, delivered in stages with acceptance at each, so the body is never asked to accept an entire platform on a single day.
Operations
Scoped to the system
Hosting, monitoring, backups with tested recovery, patching, user administration, and support responsibilities defined for a system holding evidence that audits depend on.
Every proposal separates the one-time build from the monthly operations that follow it. See full pricing for how both are structured.
Implementation
How this goes in without stopping the works programme
Map the operation
Review representative records, current tools, staff responsibilities, handoffs, delays, and exceptions.
Define the system
Specify records, states, permissions, approvals, integrations, reports, and acceptance checks.
Build and review
Deliver working stages that staff can test against representative scenarios before the scope expands.
Prepare the change
Plan data migration, training, deployment, support responsibilities, and the operational cutover.
Questions
Questions public bodies ask
Does this replace the national procurement process?
No. It records where a work has reached within the process your body already follows, so leadership can see movement and delay. The tender, the evaluation, and the award remain where they are and under the rules that govern them.
Our officers use WhatsApp for site updates. Will they use this?
Only if it is faster than what they do now, which means capture on a phone, at the site, in a few taps. A system that asks an inspector to return to an office and retype what they photographed will be worked around, and the working-around is what you are trying to remove.
Who can see the evidence files?
Only people with permission to that work. Files are private by default, served through short-lived signed links, with the database holding only metadata and object keys. Every access is recorded, which matters when the evidence supports a payment.
Can Ministry and audit users be given access?
Yes, as read-only accounts scoped to what they are entitled to see. That is usually cheaper for everyone than compiling a report each time a question is asked, and it removes the argument about whether the figures were prepared for the audience.
What happens when an officer or a contractor changes?
The work keeps its history. That is the main argument for a register over a set of departmental spreadsheets: continuity currently depends on the person, and the cost of losing them is measured in works nobody can account for.
Does it decide whether a payment should be made?
No. It states what is present and what is missing against the requirements, and the decision stays with the officers who hold that authority. Software that appears to authorise public payments creates a problem rather than solving one.
How would a body start?
With the specification, which gives procurement something to evaluate and gives the build a fixed reference. Bring the current works programme, a project that went badly, and the last Council report, and the requirements largely write themselves.
Related guides
Industry workflow planning guides
Discuss the workflow your team manages
Bring a representative job, record, exception, or report. Firelinkx will help define the users, controls, integrations, and first useful release.