Owner's representatives: one ledger per owner, one portfolio view for you
An owner's representative firm with eight clients and twelve active GMP contracts faces a problem that neither the contractor's tools nor the client's accounting system was built for. Each client is a separate owner with a separate contract, separate audit rights and a separate board to report to. The rep is the only party who sees all twelve.
The usual answer is twelve spreadsheets, one per project, each built by whichever project manager set it up. They drift. This post is about the two views a rep needs, the client's and the firm's, and why they should come from the same record rather than from two sets of files.
The record belongs to the client
The GMP ledger for a given project is the client's record. It documents the client's contract, the client's contingency approvals and the client's classification of each change. If the client changes representatives, or audits the contractor, or ends up in a dispute at closeout, the ledger goes with the client. The rep is its custodian, not its owner.
That shapes how the books should be kept. Each client's projects should live in a separate ledger that the client can be given access to, in full, without seeing anything about another client. The rep's internal notes, staffing and fees have no place in it. When the engagement ends, the client keeps a clean record from the GMP amendment to the final reconciliation of shared savings.
The view the rep needs
The rep's firm needs the opposite: one page with every active GMP on it, showing where each one stands. Which projects have contingency exhaustion dates before substantial completion. Which have PCOs older than thirty days without a cause. Which have allowance decision deadlines in the next sixty days. Which have a pay application due this week that nobody has reviewed.
That page is a working list, not a report. It tells the principal which project manager needs help this week and which client is about to get a surprise. It only works if every project's ledger uses the same structure, so the same flag means the same thing on a fictional $30 million charter school and a fictional $110 million office tower.
Same rules, different thresholds
The structure should be identical across clients. The thresholds can differ. One client may want to be told when contingency drops below 30 percent remaining. Another may want to hear only when the exhaustion date moves ahead of substantial completion. The ledger should hold the rule per project and apply it, so the rep's portfolio page shows each client's flags by each client's standard.
Consistency is the rep's product
Clients hire an owner's rep because they do not have a construction department. What they are buying, in practice, is a consistent reading of the contractor's numbers every month by someone who has read a hundred pay applications. That consistency is hard to deliver if each project manager in the firm computes anticipated final cost differently, or records change order causes with different words, or keeps contingency in a different tab.
A firm wide ledger structure fixes the definitions once. Anticipated final cost means the same thing on every project. Cause classification uses the same four categories. The contingency log carries the same fields. A new project manager learns one way of keeping the record, and a client who has two projects with the firm sees two reports that read the same.
What the software does and does not do
Costwitness is built for this arrangement. Each client is a separate owner with a separate ledger and separate access. The rep's firm sees a portfolio page across all of them. The rules are applied per project and the flags roll up. The software does not classify causes, approve draws or decide whether a change is recoverable. The project manager does that, on the client's behalf, and the record shows who did it and when.
It is also not a replacement for the contractor's Procore or the client's accounting. It sits between them, holding the owner's version of the GMP position so the rep is never reconstructing it from the contractor's files the night before the client's board meeting.
What to standardize this month
- Write a one page definition of anticipated final cost and the four change order causes, and have every project manager use it.
- List every active GMP with its contingency exhaustion date and its oldest unclassified PCO, on one page.
- Separate each client's record so it could be handed over in full tomorrow without editing.
- Agree a flag threshold with each client in writing, and record it with the project.
Questions on this
Should the client see the same ledger the rep uses?
Yes, for their own projects. The client owns the record and should be able to read every entry. The rep's portfolio view across clients is internal to the firm and should not be visible to any one client.
What happens to the ledger when the engagement ends?
It stays with the client. A clean handover is part of the service. Under most AIA A133 based agreements the owner's audit rights and shared savings reconciliation run through closeout, and the next representative or the client's own staff will need the full record to exercise them.
Can a rep use the contractor's reporting instead of keeping a separate ledger?
The contractor's reporting is an input, not the record. It is organized around the contractor's cost codes and obligations. The owner's ledger ties to the GMP amendment line by line and records the owner's decisions. A rep who relies only on the contractor's files has nothing independent to show the client.
In the product
Monthly owner report, GMP baseline, Change order register. Free tool: Pre-GMP Readiness Score, Contingency Runway.
Keep reading
Earlier: Public agencies: transparency requirements and the contingency log. Later: Developers: how a GMP overrun reaches the equity waterfall. All articles on by owner type.
See it on a project shaped like yours.
Thirty minutes on a call. A fictional project at your GMP size and your contract form, walked module by module.