How PHC Works
PHC works by keeping a project’s reality visible and reviewable through structured records and a regular review cadence. It turns “we think we’re on track” into concerns owned, actions closing properly, and claims backed by evidence.
Core loop: Capture → Review → Validate → Report
The PHC Cycle
Capture
Record concerns, actions, time + narrative, and deliverables as work happens — with links to evidence where available.
Review
Run a regular cadence (lightweight but consistent) to surface drift early: what changed, what’s blocked, and what decisions are needed.
Validate + Report
Validate key claims (so reporting isn’t wishful thinking), then produce a clear snapshot: what’s true, what’s next, and what needs escalation.
How it’s structured
SCALPED live snapshot
PHC maintains a live snapshot across:
Schedule, Concerns, Actions, Locations, People, Events, Deliverables (SCALPED).
This keeps the “story” and the “proof” in the same place.
The records PHC maintains
- Concerns (risks, blockers, unknowns — with owners)
- Actions (owners, dates, closure evidence)
- Time + narrative (what was done and why)
- Deliverables + validation (outputs and checks)
What “validation” means (in practice)
Validation is simply: claim → evidence → check.
Not everything needs heavy verification — but anything used for decisions, reporting, funding confidence, or public statements needs reviewable support.
What you get each cycle
- A current project snapshot (what’s real, what’s changed)
- A clean list of next actions and who owns them
- A maintained concerns register (with escalation where needed)
- Evidence-backed reporting outputs suitable for owners, funders, auditors, and future teams