TG Navigator
Live-project intelligence for industrial capital · 2026

Check if the project is on track.

The TG Project Health Index (TG PHI) scores how a live capital project is actually performing — 1 to 100, in plain numbers. One score that guides the people who run the project and evaluates it for the people who fund it.

1–100A single health score
Two usesGuide the build · evaluate the risk
LiveRead off the monthly reports
Project Health Index (PHI) — while we build: an owner team, engineer and contractor reviewing a project's health on a live construction site

One score. Two ways to use it.

It guides the people who run the project — and evaluates it for the people who fund it.

To run the project — a guiding tool for the six seats that control it
To evaluate the project — an outside read for those who fund it, off the reports they already receive
Investor The read behind the report

You receive a monthly report and a green dashboard. PHI scores the same report for drift — telling you whether the number you are being shown will hold, and how far your returns are likely to move before anyone says so.

Lender Cover, before the covenant

The reports that reach you are written to reassure. PHI reads them for the early signs of slippage — so you see pressure on completion, contingency and covenant cycles before it shows up in a formal variance.

No site access required. PHI works from the monthly and progress reports a stakeholder already receives — turning a document written to reassure into an independent read on whether the project is actually on course.

The TG PHI, in motion

The same score, read six ways.

Below is a single live project's health read — the guiding view. Switch the seat: the score never changes, but what you should do about it does.

Illustrative read
Specialty-chemicals project · in construction · month 14 of 26
58 / 100
Band · Strained
Cost
48
Schedule
55
Quality & Safety
74
Risk & Change
56
<40
Critical
40–60
Strained
60–75
Stable
75–90
Healthy
90+
Excellent
Illustrative dimensions & bands. How the score is built — and why it measures drift, not percent-complete — is set out below.

How the check works

Documents in, a defensible score out — every answer shown, sourced, and editable.

01

Set up

Define the project: baseline cost, baseline schedule, and the assumptions both rest on. Build the organisation: skill matrix, RACI, and a clear Delegation of Authority.

02

Ingest

Monthly, weekly, and daily reports flow in — plus minutes from every stakeholder meeting: engineering company, contractors, vendors, and inside-department reviews. One place. Chaos contained.

03

Analyse

Two lenses run together. Nadler–Tushman congruence tests whether governance, skill, workflow, and culture are pulling the same way. Project controlsCPI, SPI, and Monte Carlo — model the uncertainty and predict the real finish date.

04

Act

Drift is named — the kind, the cause, and the layer of the organisation that must act. Corrective actions, advisory, and a forecast you can defend. Every step logged and auditable.

How we measure

How we calculate drift.

Every capital project drifts. The only question is whether you see it while it is still cheap to fix — or after it has cost you a quarter and a year.

Most reporting tells you what already happened. Your dashboard says cost is on track and schedule is five percent behind. By the time it says twenty-five percent behind, the money is already spent.

Most teams

The S-curve

Percent progress against a planned curve. It tells you the project is behind. It never tells you why — or what happens next.

Better teams

Daily productivity

Output per day, crew by crew. Sharper, and closer to the work. But it still only measures what was done yesterday.

TG PHI

Drift

Not how far behind you are — how fast the project is coming loose, and where. The first measure of what is about to happen, not what already did.

PHI reads two things at once.

What your team already tracks

The structure

  • Schedules and milestones
  • Approvals and change orders
  • Procurement cycles
  • Cost actuals against budget

This tells you what has happened.

What nobody tracks

The live signals

  • How long decisions take to close
  • Who is escalating what, to whom
  • How often the design basis is being “clarified”
  • Whether the language in monthly reports is getting more careful, month over month

This tells you what is about to.

Most reporting is rear-view.
PHI is windshield.

Together, the two streams answer seven plain questions about your project
01

Are your functions still aligned with each other?

02

Where are decisions getting stuck?

03

Is the design basis holding, or quietly moving?

04

Can your owner team actually carry this load?

05

Are engineering, procurement and construction telling the same story?

06

How far will a small problem spread if left alone?

07

How much hidden friction is the project absorbing?

The signal that matters most

False-convergence — when your dashboard is green and your project is in trouble.

Cost looks fine — because money is sitting Money is sitting — because milestones are slipping Milestones are slipping — because something underneath has come loose

Most reporting takes six months to surface this. PHI surfaces it in two cycles.

1–100 higher is healthier

A single number, refreshed every cycle. The score also names which kind of drift is dominant — and which layer of your organisation must act on it — backed by the CPI, SPI, and Monte Carlo forecast.

Why projects fail

The same list. The other half.

These are the very same causes PMI found — but now read from the delivery side. A project can start with good maturity and still fail if it is allowed to drift: priorities move, scope changes, communication slips, change goes unmanaged. TG PHI exists for this: it tracks a live project so it is delivered without drift.

Change in organization priorities41% Inaccurate requirements gathering39% Change in project objectives36% Inadequate vision or goal30% Poor communication30% Inaccurate cost estimates28% Poor change management28% Poorly defined opportunities and risks27% Inadequate sponsor support27% Inaccurate time estimate26% Resource dependency23% Inadequate resource forecasting23% Limited or taxed resources22% Inexperienced project manager20% Task dependency11% Team member procrastination11% Other11%
Poor execution / driftPriorities, scope, communication and change problems that form while the project runs. This is what TG PHI catches.
Poor starting maturityDefinition and readiness gaps present before commitment. That is the job of TG PMI.

Highlighted bars are the causes a live health check keeps in check.

Harshit Kapoor
Built by

Harshit Kapoor

Twenty-five years on industrial capital projects — across the owner, consultant, and contractor seats. Deep, hands-on work in India and the United States, with project exposure across Europe, China, Japan and Southeast Asia, in specialty chemicals and petrochemicals.

TG PHI is the live-project companion to that method. Today it is delivered as a hands-on advisory engagement — Harshit works alongside your team to keep a project's health honestly read while it is being built.

Cornell — New YorkMBA · AI Pathway specialization
MIT — BostonExecutive education
IIM — AhmedabadExecutive education
L&T · Deepak · ThirumalaiIndustry
CII / UT AustinMethodology base
Work with Harshit

While the project is being built, keep its health honest.

TG PHI is offered as a direct advisory engagement. Tell Harshit about the project in delivery, and he will walk you through how a live health read would work for it.

Education, industry & method
Cornell University
Martin Trust Center for MIT Entrepreneurship
IIM Ahmedabad
Larsen & Toubro
UT UT Austin CII RESEARCH BASE
CII CONSTRUCTION INDUSTRY INSTITUTE