Capital Projects

Six gates, real evidence,
and a handover worth signing.

How stage-gate readiness is built, verified, and decided - and the reasoning behind each piece.

Prefer the full feature list?

01. The gates

Concept to handover, each one a demand for evidence rather than a date on a plan.

Six stages, one pipeline

Concept, design, procurement, installation, commissioning, handover. Every project is a row of gate nodes you can read across a room.

A checklist per gate, yours to edit

The starter set covers the reliability work that dies quietly on most projects - maintainability reviews, pipe strain, first fills, spares lead times - and every line is the organization's to change.

Requirements copied, not referenced

A project snapshots the checklist the day it is registered, so editing the standard never rewrites a project already in flight.

Carryover never dissolves

An item left open at a passed gate follows the project as red debt. Moving on is not the same as finishing.

02. Verification

The registry outranks the checkbox.

Self-verifying requirements

Criticality approved, strategy approved, lube points defined, spares listed, punch list clear - checked live against the suite's own records. Nobody can attest what the software can see.

Two kinds of claim, labeled apart

A verified item names its source; an attested item names its person and evidence. Both can be complete - the page never blurs who says so.

Readiness that cannot be gamed

Red for late or carried-over items, amber for open work or standing exceptions, green only when everything is satisfied. Zero items is "no checklist", never green.

A check that cannot see never passes

If the source module is not run here, the item falls back to human attestation and says so - it does not quietly pass.

03. Decisions

People pass gates. The software keeps them honest about it.

Gate decisions on the record

Who decided, when, the note, and a snapshot of the evidence at that moment. The pass button stays down while items stand open.

Exceptions signed, never silent

A gap that passes a gate carries a reason, an approver, and a date - and keeps the project amber until it closes.

Punch severities with meaning

A is safety, B blocks startup, C is minor. The handover check reads exactly the first two.

Cost of ownership beside the PO

Options compared on lifetime arithmetic over the project's own figures. No discount model, no recommendation - the decision stays the project's.

04. The suite connection

Why this lives here and not in a spreadsheet.

Assets registered before startup

The new machines join the shared registry while the equipment is on a truck, so every other module can start its work early.

Strategy and criticality flow in

The same assessments and strategies the rest of the plant runs, approved before first turn - not written in the first year of surprises.

Lubrication ready on day one

Points, products, and schedules live before commissioning ends, so the first service is already on a route.

The assistant answers for it

Ask which projects are red, what blocks a gate, or how much capital sits at risk - with links to the records.

The fastest way to judge it is to open it.

The demo plant has this module switched on, with records already in it.