Platform

Available now

Plan the portfolio.
Run every project.
Keep what you learn.

CAP·PATH is the software your capital program runs on, from the five-year plan down to the person who owns one deliverable this week. The gated work process is its spine. Around that spine it carries the portfolio and its cash by year, the scoping requests that bring projects in, the governance forums and their gate decisions, the risk register, every open action, and the lessons that make the next project better.

Book a walkthrough See how it fits the reviews→

The standard, made live

CAP·CORE is the standard. CAP·PATH runs it.

The Capital Project Management System (CAP·CORE) is the documented best-practice work process, built on public frameworks. CAP·PATH is where it comes alive: the standard is visible and editable inside the tool, deployed to each project at its tier as a dated, gated plan your team actually works. Own the standard, not a black box, made literal.

Run it on your process, whichever it is

The CAP·CORE master. Copy the CAP Intelligence work process into your library and tailor it to your sites, your approval ladder, and your funding sources.
Your own existing gate process. Import the stage-gate process you already run as a workbook and keep your house standard, now live and enforced.
Three kinds of project. Physical asset is the baseline. Control and systems projects carry the commissioning and validation steps and drop civil; business-system projects keep the gates and the governance and drop the field. The delivery profile decides which steps a project ever gets.

The forty-seven governing standards, procedures, and deliverable templates ride along as the document library, deployed with every project and one click away on the step that needs them, with each document’s version and change log read out of the file itself.

Plan the portfolio

Before any of this

The capital plan, built as a model rather than a spreadsheet.

Every project at every site on one timeline, gate to gate, with the turnaround windows they ride. Cost by year with the grant and internal split, cash by month from your own finance export, the standing obligations of the portfolio on a calendar, and a candidate list fed by scoping requests rather than hallway asks.

Explore the capital portfolio→

Your existing capital forecast imported as it stands
Project cost, funding split, and turnaround cost stacked by year
Monthly cash forecasting with the finance-system round trip
Terms of Reference lead times by tier, on a calendar

What it does

One system, from the scoping request to the post-investment review.

It governs what happens, when, who owns it, and what gets approved, then carries the decisions, risks, actions, cash, and lessons that grow around it. The detailed engineering and the construction schedule stay with your engineers and planners.

Bring projects in the front door

A project enters through a scoping request that the disciplines review before anyone sees a row on the plan.

One-page scoping request

Anyone can raise one: what you saw and where, why it matters, whether it needs a turnaround window. It is routed through the sections your template names, each with a named discipline owner, a lead time, and the option to say not applicable. A register item, an action or a risk, can start one directly.

A portfolio decision, recorded

When every section is decided, the site's deciders record one outcome: accept onto the portfolio with a stage, an investment class, a budget year, a sponsor, and a project manager; defer to a revisit date; or decline with a reason. Accepting creates the project on the plan. The request keeps the template version it was raised on.

Tiered before it is deployed

The complexity calculator scores the seven factors and recommends the tier. Nothing is saved until the deploy dialog runs it for real, so the calculator is safe to play with on a hypothetical project.

Run the project

The work process, deployed to a real project with a real team on it, and held to.

Own the standard

Your work process is a versioned template your company controls, not a vendor's black box. Start from the CAP·CORE master, import the gate process you already run, or build one, then edit every activity, role, gate, and offset. No change requests to alter your own standard.

Deploy by tier, anchored to the gates

The tier decides which activities deploy. The front end back-calculates from the sanction gate and, on a turnaround-coupled project, from the earlier of the window start and the scope freeze; execution runs forward from the start of field work. A conditional track, grant funding or a window, switches on only when it is true of the project.

Coached on the step, accountable at the close

The governing standard, what good looks like, and the date the gate needs it by sit on the step itself, so a person learns the standard by doing the work. Every activity has a named responsible person and a named accountable one. A key deliverable keeps the record behind it, closes only on the accountable person's acceptance against its acceptance test, and a gate closes only through a recorded decision: proceed, recycle with a dated re-review, hold, or cancel. It all lands in an append-only audit trail.

Two lamps on every project

Cost and schedule each carry an Andon lamp. Yellow is an open rated risk that threatens a milestone or the budget. Red is a recorded impact: a forecast breach, a slipped gate, a risk realized. A lamp can be raised, never switched off; it clears when the record behind it closes. The weekly and monthly reports open on the lamps and the stage's open steps, lit ones first.

Improve the standard

The Drift report shows exactly how a running project diverged from its template, including every re-lay of the plan and who decided it. When a change is worth keeping, promote it into a new version of the company standard in one step. One project's lessons become the starting point for the next.

Report and notify

Weekly and monthly reports computed live from the data date, frozen as numbered PDFs on a schedule the company sets. Roll up compliance by role, person, and phase, export the board to Excel for the steering meeting, and let event-driven email keep owners and approvers moving without anyone chasing them.

Govern it

The forums that actually steer a capital program, run as a system rather than a calendar invite.

Portfolio body, steering, gate meetings

The portfolio governance body is a monthly series seeded from your own work process, with the portfolio report on its agenda. Each project's steering forum and gate meetings are recurring series with a question-form agenda and a context dashboard built from live data: what moved, what is escalated, what is owed.

Minutes people trust

Record the room if you want to, disclosed and started by the facilitator, and the transcript drafts the minutes. Decisions, actions, and risks are proposed, never assumed: the facilitator accepts, edits, or dismisses each one. Approval freezes the minutes and sends them out.

The gate decision is the record

A gate meeting records its decision as one object, bound to the gate row on the plan: the outcome, the conditions, the re-review date on a recycle, who chaired it. Every decision carries who agreed it and when it should be looked at again, and superseding one requires naming its replacement, so the register can never quietly contradict itself.

Manage what threatens it

An evergreen register with the heartbeat enforced, contingency by estimate class, and cash forecast monthly.

Your matrix, your language

Scoring runs on your own risk matrix, uploaded in whatever form it exists today and read into the tool. Risks are written as cause, uncertain event, and effect, filed under the phase they belong to, and the coach helps shape a vague one rather than refusing to save it.

The heartbeat is the product

Every risk has one named owner and a review-by date keyed to its severity. Mitigations are real actions in the same spine, not prose in a cell. A risk that reaches its date untreated forces an explicit, recorded acceptance rather than quietly aging out. Gates hold for a register pass, and a rated risk against a milestone lights the lamp.

Cash forecast, every month

Each project owes a monthly estimate at completion and a note on what moved. Cash by month is entered on the project or imported for every active project from your finance system's export, matched row by row in a preview before anything commits. Late forecasts escalate to the portfolio manager after the days you set.

Learn from it

The half of lessons learned that everybody skips: capture during, not after. Most lessons change nothing; here each one becomes an owned, dated action, and the ones worth keeping change the standard itself.

Thirty seconds, from anywhere

One box, on the activity you are standing on, typed or spoken. The project, phase, and category fill themselves in. Attributed by default, anonymous when it needs to be. A register opened at closeout is reconstruction; this one is a record.

It comes back where it was learned

A lesson resurfaces on the next project's copy of the same work-process activity, in front of the person about to do that job. When a lesson echoes one from a previous project that was never actioned, the platform says so, which is the finding that actually changes behavior.

Actions that land in the plan

One action spine for the whole organization: gate conditions, meeting commitments, lessons actions, readiness tasks. One named owner, never a committee. Re-dating after the first due date requires a recorded reason. Verified is its own state, and the owner cannot verify their own action.

Ride the turnaround window

Most capital at a running plant either rides a window or has to stay out of one. The link is a first-class object, not a note.

Linked from either side

A project links to the turnaround or outage it executes in, ties into, depends on, or shares scope with. The turnaround manager sees the capital projects riding their window from the STO door; the project manager sees the window from this one. One record, two views, one sign-in.

Pinned, so a moved window moves the project

A project that executes in a window pins its field start to the window's start. When the turnaround moves, the project re-lays, and the plan revision records that it did and why. The front end is back-calculated from the earlier of the window start and the turnaround scope freeze, because the tie-ins have to be defined before the freeze, not before the outage.

On the same portfolio

Turnaround cost and project cost stack on one year-by-year view, with linked projects drawn attached to their window. Overlapping preparation windows and the people they share are named on the planning tab before they collide.

Ask the platform

The standard, answering questions.

A standard nobody reads is a binder with a login. Every person on the project can ask the platform what a deliverable has to contain, why a gate exists, what an estimate class commits them to, or what their own role owns this month, and get an answer grounded in two things only: your governing standard and your deployed plan.

It cites the standard. Every substantive answer names the governing document it came from, so the person can go and read it.
It reads your plan, not the template. Dates, owners, and sequence come from your deployed project, drift included. The master describes practice; your plan answers what is due here.
It coaches, it never decides. It will not approve, score, gate, or judge readiness. Asked whether a package is good enough for sanction, it explains what the standard expects and points at the accountable approver by name.
It says when it does not know. If the standard and the plan do not cover the question, it says so and points at who can answer, rather than inventing a requirement.

How it is built

One standard, an editable copy per project, a named owner per activity.

Work process

Corporate admin

The company standard, versioned and published. The single source of truth every project starts from, with each step's governing standard, deliverable template, and acceptance test attached.

Project process

Site admin

An editable copy running one project at its tier. Adjust it to the project without ever changing the company standard; the drift is recorded.

Activity

The assigned person

One row of the process on one project: start it, attach the deliverable, submit it for the accountable person's acceptance.

Why it is different

A tool you run, not a subscription you cannot see into.

You edit it, not the vendor

Copy the standard into your library and change any activity, role, gate, or offset yourself. The process the tool runs is the process you can read and edit, not a subscription you cannot see into.

Tailoring is honest, not silent

Every requirement is classed. An interlock is never tailored, at any tier, and a request to tailor one is refused and recorded. Core is present at every tier with its depth a recorded variance. Stretch is adopt-or-not. So a conformance reading means something.

One record, end to end

The scoping request that started the project, the gate decision, the risk it was about, the action it created, the activity that action landed on, the cash it moved, and the lesson that came out the other side are one chain of records, not seven tools that agree by convention.

The standard learns

The drift-to-standard loop turns each project's real experience into the next project's starting point, so the process gets better with use instead of drifting apart across sites and tiers.

Keeping it alive

One brief a week, not a notification habit.

A process only survives if people are reminded of it at the right frequency, and gets abandoned if they are reminded too often. Everyone gets one brief a week: what moved across their projects, and what is theirs in the week ahead. Only the genuinely time-critical items, approvals waiting, a forecast owed, anything overdue, interrupt the day.

How you start

Stood up with you, then run by your team.

We do not hand you a login and walk away. CAP Intelligence sets the platform up alongside your team, and your people run it from there. Secure Microsoft sign-in, so we never hold a password.

Already set up? Sign in to CAP·PATH→

01Stand up your company and sites, and load the standard, ours tailored to you or your own imported.
02Import your capital forecast as it stands, so the portfolio opens on your list, not a blank page.
03Deploy the first projects together: score the tier, anchor the gates, staff the roles, link the ones that ride a window.
04Walk the team through their tasks, seed the portfolio forum, then hand them the wheel.

The bigger picture

One project record

CAP·PATH is the operational front door of the CAP Intelligence platform. The work process, the assurance reviews, and the analytics all meet on the same project record, so process conformance and an independent read on definition, schedule, and performance sit together. It shares its spine with the sister platform for turnarounds, which is why a project and the window it rides are one record rather than two systems. It is the live foundation the forward-looking capabilities are being built on.

See where it is going→

Deploy the standard. Run the project.

See CAP·PATH on your gate process.

Tell us how you run capital projects today. We will show you the platform on your own process, or on the CAP Intelligence standard.

Book a walkthrough

Plan the portfolio.Run every project.Keep what you learn.