Four roles, one job record
An ERP earns its keep in four different days: the project manager’s, the foreman’s, the site superintendent’s, and the subcontractor’s. This guide walks each day on the Northgate Yard Expansion — the same job the rest of the guides use — and shows exactly where each role works. Everything below happened on real records in this system.
The project manager: money and status
The PM’s thread runs estimate → contract → changes → claim, and it never leaves the job record. The estimate was won and became the job; the contract total moved only when change order CO-1 was approved, so the job’s progress panel reads contract + approved changes = current total without anyone re-typing a figure.
The claim position assembles itself on the same panel. The first progress claim was raised in the shared CCJV Accounting module from the job record; its invoice number sits on the job record as the claim reference, and the panel’s claim-backup line carries what a claim is certified from: the schedule’s average completion, the value of accepted materials, and the approved changes. Certification stops being a Friday-afternoon reconstruction.
What is due and what changed surface on the dashboard every morning: approvals waiting, exceptions open, and anything past its date — RFI answer dates and submittal review dates included — with the per-wallet agent reading the same live work and directing the next step. Escalation in Constructum means the overdue item is in front of you and your agent, named, until it closes.
The foreman: the field day
The foreman’s day is a Daily Log. On 7 November the Northgate log reads: foreman D. Whitecourt, crew of 9, trades on site — electrical (Prairie Grid), concrete, formwork; weather clear, −2 °C at start; work completed — electrical rough-in continued in grid C, footings poured on the grid D line; delays — none. Filed logs accumulate into the job’s history and stand behind the progress claim: the claim says what was earned; the logs say what happened. The foreman answers to the site superintendent: the log is filed to the trailer, and it waits in the superintendent’s approvals until he reviews it — the review is what closes the foreman’s day.
When the day produces a problem, it becomes a tracked flow, not a note. That afternoon the City of Edmonton electrical inspection found two junction boxes in grid C missing cover plates, with conduit stub-ups uncapped. The inspection record carries the finding; a Deficiency was raised from it — assigned to Prairie Grid Electrical Ltd, due 12 November — and walked to Rectified, then Verified by the site superintendent, then Closed. Open deficiencies count on the job’s progress panel until they reach zero, and the client sees the same count on their view.
The drawings the foreman works from are the register’s current set: the panel lists each job’s current drawings by number and revision — A-101 at revision 2 on Northgate — and a superseded revision leaves the current set the moment its replacement is marked Current, staying on the record as history. Nobody builds from a stale sheet because the set itself says which sheet is current.
The site superintendent: the trailer
The superintendent runs the site as a whole from the trailer, and his day is four jobs at once. The foremen on the job answer to him — their filed Daily Logs land in his approvals, and his review closes their day. Ordering: materials and equipment are raised against the job from the same screen he works in — on Northgate, the formwork release oil (PO-2214, four drums, due 10 November) was ordered, confirmed and tracked to In transit on the Materials record, and a delivery that slips past its date surfaces as overdue rather than being discovered at the pour. Managing staff: the Daily Log is his site diary as much as the foreman’s — crew count, trades present by company, the day’s work — so who was actually on site, against who the schedule expected, is read off two records that name the same job.
Pushing progress: his morning starts from the position, not from assembling it — the dashboard’s approvals, exceptions and overdue items across every module, and the job’s progress panel: schedule completion (Northgate reads 100 / 60 / 25 percent across its three tasks), open deficiencies, the current drawing set, each sub’s position. Keeping the project on schedule: the Schedule register is his instrument — tasks, predecessors, percent complete and due dates, with delay and weather states recorded when they happen — and the Inspections register carries the hold points in the same view of the job, so a gate that will stop next week’s work is visible this week. When the north-gate hoarding signage deficiency was raised from an earlier inspection, it sat on his list as an assigned, due-dated, open record — due 9 November — until the fix is verified, not in a notebook he has to remember to open.
The subcontractor: their thread
A subcontractor works inside the system as a collaborator: invited to the workspace, bound to their own wallet, personally holding CST for every module they use — the same gate law as the contractor’s own staff, enforced continuously. Prairie Grid’s submittals and change orders are records they work, not emails they chase.
Their money position is kept on their Subs record, visible to both sides of the contract: contract value, claimed to date, paid to date, and the difference. On Northgate, Prairie Grid’s position reads claimed to date, paid to date, and the difference outstanding — the outstanding balance being the job’s holdback percentage applied to what has been claimed, matching the job’s holdback terms. A holdback dispute starts from a shared number instead of two spreadsheets.
And when the deficiency above landed on Prairie Grid, it arrived as an assigned record with a due date in the same workspace — not a phone call, not a photo in a group chat. The rectification, the verification, and the close are on the same record the PM and the client read.
Why one record matters
Four roles, four different days, one job file. The PM certifies from the logs the foreman filed; the foreman works from the drawings the office issued; the sub’s position is the position the PM sees. That is what the token gate buys: not software rental, but a single record of the job that every party can stand behind — held, never spent, at 1 CST per module per month.