Same numbers. Ten points of view.
Project cost has more customers than people think. Each one needs a different cut of the same truth — and each one QC's it their own way. That cross-checking is a feature, not a nuisance. It's how errors get caught.
The left column is who they are. The middle is what PCS hands them. The right is what they hand PCS — because a cost system that only takes and never gives back is a tax, and a cost system nobody feeds is a fiction.
| Stakeholder | What PCS gives them | What they put in |
|---|---|---|
| Finance | Integrated cash-out and revenue-earned curves for cash management — what leaves, what arrives, and when. The working-capital gap between the two, forecast forward, in every currency the project transacts in. | Payment terms, retainage, and the cash constraints the forecast has to live inside. |
| Accounting | Completely auditable historical WIP reporting — the backup that defends an accrual, for any past period, reproducible. | WIP report and AR report reconciliation against the ledger. |
| Project Manager | Budget and forecast accountability, pushed down. The PM assigns segments of the budget to a Budget Owner — say, the Engineering Manager — who assigns scope to a Budget Manager — say, the Electrical Lead. Everyone owns a number with their name on it. | Review and direction. Approval of trends and changes. |
| Project Engineering | Their discipline's budget, commitment, and forecast in one view — and every scope change traceable to the trend that caused it. | Progress against work packages; changes to the material take-off. |
| Procurement | Commitment and expediting status against every control account, so the buy is visible against the plan rather than a month behind it. | PO log with PO lines. Expediting report. |
| Contract Administration | Every contract with its commitment, goods receipts, and invoice status in one place — change orders visible against the control accounts they hit. | Contracts, change orders, and back-charges. |
| Partners & Investors | Control account metadata mapped to their cost breakdown structure, so every report they get matches their own cost structure. Plus a cash-call view: current reserves against the cash-out forecast. | Funding schedule and reserve position. |
| Client | Earned value and invoice backup they can actually check — the proforma invoice, the work it's claiming, and the cash-in forecast behind it. | Milestone acceptance and invoice approval. |
| Auditors | Append-only logs, with who changed what and when on every row. Any past period's report, reproduced exactly, on demand. | Nothing. Read-only access is the point. |
| Estimating | The feedback loop that estimating almost never gets: actual versus estimate, by cost type, by discipline, on finished work — so the next estimate is better than the last one. | Estimate basis and the original budget. |
| Accounts Receivable | Invoice aging against a real lifecycle — draft, issued, paid — and what's still left to invoice on every contract. | Payments received. |
Why this matters more than any feature.
I truly believe the number one cause of project failure is poor communication. Not bad math — bad communication. The estimate said one thing, the field knew another, procurement had a third number, and nobody found out until the accrual didn't tie.
A unified cost system where all the different stakeholders see the same picture — from their own perspective, QC'ing it in their own way — will improve project success. That's the whole thesis. Everything else in this system exists to serve it.
It is far easier to collect all the details and report, than to generalize and estimate reporting. Short cuts are not short cuts. — Rule of the house