CAPINTELLIGENCE
Data-driven. Field-proven.

CAP·EXE · Execution & Field Quality  ·  A module of CAP·PATH, the Capital Project Management Platform

Issue the shift. Finish by system. Know where you stand by morning.

CAP·EXE carries the plan to site: a shift look-ahead cut from the current schedule and issued by crew, commissioning and startup planned by system with the packages tied to the systems they finish, and progress claimed on a phone or a printed sheet and verified by the owner. What the field found is on the record the same hour, and the same claims feed earned value overnight.

The plan goes to site, and the site answers back.

Systems and startup on a project: each system, its startup order, and the packages that complete it.
Systems and startup on a project: each system, its startup order, and the packages that complete it.Illustrative demo data

The problem

Construction runs on paper the plan never sees.

The schedule is updated weekly from what the contractor reports. The look-ahead is a spreadsheet. The systems list lives with commissioning. Each works until the month they disagree, and that is the month the in-service date moves.

A look-ahead by email
Issued as a spreadsheet, progressed by rumor

Nobody can say which work was actually issued to which crew, so nobody can say whether the crew that is behind was ever sent.

Bulk construction to the end
Areas finished, systems not

The job is ninety percent complete by area and no system can be handed to commissioning, because nothing tied the packages to the systems they finish.

Progress by opinion
Percent complete nobody verified

The contractor claims it, the schedule takes it, and the gap between claimed and true surfaces at mechanical completion.

Findings at shift end
Radioed in, written up from memory, decided a day late

A quality issue or a field change waits for the paperwork, and the decision it needed arrives after the crew has moved on.


What it does

From the issued shift to the signed handover, on one record.

The look-ahead knows a constraint is open, the system knows a package is still open, and the handover gate knows a punch item is still counted. Each of those is usually a different spreadsheet.

01

Issue the work

The planner cuts the next shifts from the schedule and issues them by contractor and crew.

The shift look-ahead

Cut the next two to six shifts from the schedule you keep here. Every line carries its crew, a named owner coordinator, and the holds the platform knows: an isolation not in, a permit not reviewed, a hold point, materials not arrived, an open change, an inspection plan not issued, a system not released. Issuing freezes it and renders the sheets.

Only issued work is progressed

Once an issue stands, a claim on work that was not issued is refused, with the way to ask. The request goes to the coordinator for that work, who hears at once; approving it adds the line. The gap between what was sent and what was worked closes at the source.

Paper is first-class

Each crew gets a printed sheet with a box per shift for percent, hours left, crew, delay, and a note, a line for the foreman’s signature, and a code. A foreman with no account scans the code and reports from a phone, or the sheet is keyed in. The coordinator’s initials are recorded as validated on paper.

Your current schedule lives here

An administrator or the planning lead uploads the current schedule export, or the scheduler’s script pushes it. The team confirms its coding once and later copies carry it forward. The copy’s age reads on every page that uses it, amber past a day in execution. It is kept current, never scored: a score takes a review.

02

Finish and start up by system

Commissioning and startup planned by system, with the packages tied to the systems they complete.

A project is many systems

Process systems and their utilities, each with its commissioning and startup steps and targets that move when the start moves. Commissioning’s own spreadsheet or project file imports, and nothing is written until you apply it.

Packages tied to the systems they finish

Each package names the systems its work completes, proposed from the schedule’s codes and the equipment tags and confirmed by a person. The gates view lists the packages planned to finish after their system’s turnover target, while there is still time to re-sequence.

Mechanical completion and handover, held

A system cannot be turned over while a package on it is open, an A punch item is open, or a completion form is unsigned. The board says which, and the last signature turns it over.

03

Make the tie-in safe, in sequence

Where the project meets the running plant, the order of locks and blinds is held by the record.

The isolation on the package

A package states the isolation it needs, or that none is required and why. A confined space entry needs a positive isolation at the equipment, or a recorded deviation.

Locks before blinds, and back again

A blind goes in only once the valves are locked and the make-safe steps are reported done. Those locks release only once every blind is verified. A blind comes out only under the valves locked again. Each refusal names what blocks it, and operations can pass one with a reason that is kept.

Permits proposed, reviewed by operations

Each step proposes the permit kinds it needs, and operations reviews them by package. The review is stamped against the steps as they stood, so any later change to a step reads proposed again.

04

Capture it where it happens

A phone, a tag, or a poster at the gate: the finding is on the record before the crew leaves it.

Raise it where you stand

A quality issue, a field observation, an RFI, a punch item, or a field change, raised on a phone with a photo and a line, from the job or from the tag on the equipment. With no signal it waits on the phone and sends itself.

A poster, and no account

A contractor’s worker scans the poster at the gate and reports a safety observation, a near miss, a quality issue, or a lesson with no sign-in. Sending without a name is the default for safety. Every entry is held until your site team accepts it into the register, and a severe near miss reaches them at once.

Hold points with a clock

The crew calls the hold point when it is ready and the notice clock starts: yellow past notice, red past the hours you set. Who may release it is a rule, never the caller.

05

Know where you stand

Progress claimed at the work, verified by the owner, and read as earned value by morning.

Report this shift

Two minutes at shift end: the steps by quarter, hours by craft, and one delay code. It works offline and sends when the signal is back.

Claimed, then verified

The named coordinator validates the crew’s claim. A contractor never verifies its own, and you can choose to count verified claims only. Validated progress goes back to your scheduling tool as a file.

The shift handover

Issued, claimed, validated, done, slipped, and disputed, with hours remaining and delays by code, read from the same lines the crews worked. The daily meeting walks it rather than rebuilding it.


Systems · startup

Construction finishes by area. Plants start by system.

The systems view holds commissioning and startup by system, with the packages that feed each one and the gates they have to meet.

Systems and startup on a project: each system’s steps, and the packages that complete it.
Systems and startup on a project: each system’s steps, and the packages that complete it.Illustrative demo data

Statuses here are reported by a named person · your permit-to-work system stays the authority


Where the line sits

We hold the plan and the count. Never the lock.

This is safety-adjacent work, so the line is drawn where it belongs. The platform plans, sequences, and tracks what named people report. It authorizes nothing. A status here reads ‘reported by’, never ‘proven safe’.

  • Your permit to work stays the authority. The platform proposes permit kinds and records operations’ review. It issues no permit and no certificate.
  • No personal locks, no names on a box. It tracks the site’s numbered isolation locks and crews by package. Gas test values stay in the permit-to-work system.
  • Not your timekeeping. Hours from a shift report are estimates until your timesheet or gate record lands.
  • No model in the loop. Nothing in the look-ahead, the isolation sequence, or the systems plan is decided or drafted by AI.

What changes

The difference between six spreadsheets and one record.

Executed the usual way

  • ×A look-ahead emailed weekly, progressed by rumor
  • ×Ninety percent complete by area, no system ready
  • ×Percent complete claimed by the party being paid for it
  • ×Handover argued system by system in a meeting

Executed in CAP·EXE

  • ✓Issued work by crew, and only issued work progressed
  • ✓Packages tied to the systems they finish
  • ✓Claims validated by a named owner coordinator
  • ✓Handover held by the record until the last signature

How it fits

The packages come from planning. The progress goes to cost control.

How it is packaged

One add-on, three modules.

CAP·SCP (Scope Management), CAP·PLN (Planning, Estimating & Materials) and CAP·EXE (Execution & Field Quality) are one add-on to the CAP·PATH subscription, per site, and one add-on covers both the capital and the turnaround door a site holds. The gated work process, the portfolio, governance, risk, cash forecasting, lessons, the readiness indicator, and the role guides are in the base platform.

CAP·PLN releases the packages this module issues, and the cost control one-pager covers how the claims made here become earned value. Completion forms and the punch list, already part of the platform, close the work by system.

Bring your current schedule and your systems list.

We load the schedule, bring your systems in, and cut the first look-ahead with your construction lead.