What is a PCSR?

How it\'s structured

A PCSR is typically organised one row per construction package or discipline. Each row carries four numerical columns — committed, anticipated, forecast, out-turn — plus narrative columns explaining variance and exceptions. Most PCSRs include a portfolio total at the foot of the report and a summary stat strip at the head, showing total project value vs target.

Committed is the value of issued purchase orders and signed sub-contracts to date. Anticipated is committed plus the value of approved or pending variations. Forecast is anticipated plus the QS\'s judgment on remaining variations and contingency drawdown. Out-turn is the eventual final cost, locked at project closeout.

Most UK consultancies update the PCSR monthly in time for the project monthly report cycle. Some run a weekly internal cost picture in addition; the formal PCSR remains monthly because that\'s the cadence the client expects.

Common pitfalls

• Stale forecast. The QS updates committed and anticipated as POs and variations land but forgets to revise forecast. Forecast then reads stale until the next monthly cycle catches it.
• Inconsistent variation treatment. A variation that has been instructed but not yet priced should sit in anticipated. Many PCSRs leave it out entirely until pricing is agreed, understating the real picture.
• No reconciliation with cashflow. The PCSR\'s forecast cost should match the cashflow\'s forecast spend. If they\'re maintained as separate workbooks, they drift; the client gets two different numbers from the same project.

Where to learn more

For a deeper treatment of how a PCSR fits into the consultancy\'s monthly cost cycle, see The complete guide to cost reporting for UK consultancies. For how Projavio represents the PCSR as a live data surface rather than a workbook, see the cost reports module.