Guides — running a job end to end on Constructum
Constructum is one system, not a shelf of separate tools. A job enters as an estimate, is won, opens, gets scheduled and resourced, is inspected and changed under control, is claimed against in Accounting, and closes out with its file in the vault — every record naming the same job, no figure re-keyed anywhere along the way. These guides take each module in turn: what it runs, how work moves through it, and the Alberta rules that govern the money and the safety duties.
The worked example
The demonstration job below was run through this live system, start to finish — one full run of the canonical workflow, Bid Won to Project Complete. It is the fastest way to see what the suite does:
- Estimate #41 — Northgate Yard Expansion for Northgate Developments Ltd: Draft → Costing → Internal review → Sent → Won.
- The workflow fires — Bid Won to Project Complete runs on the job’s CRM deal: the mobilise task in Projects, the approval of the safety and inspection gates (assigned by the template to a second wallet, the Project lead, wherever the tenancy has one), the execute-and-claim task, and the closeout inspection on the Calendar. The full-span run is receipted on the CCJV hub, hash-verified; an earlier run of the template’s first version receipted the mobilisation leg only.
- Job #42 opened at the won figure — carried, not re-typed — and moved to On site.
- Schedule — three tasks with crews and due dates: mobilisation (completed), earthworks (in progress), foundations (issued).
- Committed to the job — Prairie Grid Electrical (subcontractor, mobilised and working); 40 t of 15M rebar (ordered through to accepted); a CAT 320 excavator (allocated, on site).
- Drawings under revision control — A-101, the foundation plan: revision 1 issued and marked Current; when CO-1 changed the footings, revision 2 issued and took Current, and revision 1 moved to Superseded on the register — the site set is revision 2.
- Safety #49 — a near miss investigated and closed. Inspection #50 — foundations passed; one deficiency (hoarding signage) rectified; record closed.
- RFI-001 answered; SUB-001 approved — the superintendent’s footing question answered on the record by the design lead (bear at 2.1 m) and closed; the rebar mill certificates submitted, reviewed and approved before the steel was worked.
- Change order CO-1 — deeper footings on grid C: priced, submitted, approved, instructed, completed. The contract total moved by the approved amount only.
- Progress claim #1 — raised in CCJV core Accounting from the job record, GST applied. Marked Sent, then Paid — the payment posted to the journal, debits equal credits.
- Closeout — the job walked Practical completion → Defects period → Closed, and its closeout certificate was filed to the vault: SHA-256 recorded, queued for Avalanche anchoring, +1 credit earned on upload.
The module guides
- Jobs & Projects — the job file everything hangs on; completion, defects and the Alberta holdback.
- Estimates & Bids — bid discipline and the prompt payment clock that starts when you win.
- Schedules — tasks, crews, due dates, and delay recorded as evidence.
- Safety Records — Alberta OHS duties, stop-work, investigation and honest records.
- Equipment & Fleet — allocation, service dates and failed-inspection discipline.
- Materials & Deliveries — order to accepted, with short and damaged deliveries handled on the record.
- Subcontractors — engagement on the record and the seven-day payment cascade.
- Inspections — safety codes hold points, deficiencies and the closeout sign-off.
- Change Orders — nothing built on a verbal: priced, approved, instructed, then built.
- Drawings — the drawing register: revisions, the current set, and superseded revisions kept as evidence.
- RFIs — questions raised, assigned, answered and closed on the job record, with due dates that surface when they slip.
- Submittals — shop drawings and certificates through review: approved, approved as noted, or sent back to revise and resubmit.
- Orientation — the worker door: the firm’s video and two questions, per worker wallet, open to workers, registered and signed in.
- Daily Logs — the foreman’s day on the record: crew, trades, weather, work completed and delays, filed per job per day.
- Deficiencies — punch items raised from inspections, assigned to the responsible company, due-dated, rectified and verified closed.
Working the job — the four roles
Working the Job — one job walked through four working days: the project manager’s money-and-status thread, the foreman’s field day, the site superintendent’s trailer, and the subcontractor’s own view of their scope, claims and holdback position.
Beyond the sector suite
Two parts of the chain live outside the eighteen modules, by design. Progress claims and invoicing run in the CCJV core Accounting module — the shared ledger every sector ERP connects to — and the canonical workflow runs on the Workflows module, receipted on the hub. The vault sits inside the ERP portal: every upload is SHA-256 hashed on arrival and queued for Avalanche anchoring; uploads earn 1 CST credit, and viewing a file costs 0.1 CST per MB from credits — including your own files. And from any job record, the contractor can issue a client view link: the client opens it with no wallet and sees the job’s progress and its document list — names and hashes, never the files themselves, which stay in the vault.