Capital-project portfolio controls: run a recurring payment review

Choose a repeatable contract family first

Start with a group of projects that share enough contract structure and source systems for the review to repeat. Identify the portfolio sponsor, project reviewers and financial owner. Define which periods, suppliers, applications and change types are included.

Create a contract-specific rule sheet for each agreement. Record the effective rates, eligible cost bases, authority limits and billing definitions. Standard fields make comparison possible, but a common markup percentage across all projects would be a dangerous shortcut. Keep rule changes versioned and require the responsible owner to approve their interpretation.

Set the review around the actual payment cycle

Reconcile the source population before the billing or certification cutoff, run the agreed tests, collect missing evidence and present exceptions to the authorized reviewer. Preserve the submitted version and resulting decision. Then trace corrections into the affected financial records.

GAO's Green Book supplies a federal internal-control framework emphasizing preventive controls and documented risk responses. A private owner's process should be designed for its own agreements and organization; citing the framework does not make every federal requirement applicable. The operating model here is an original practical design.

Sources: GAO: Standards for Internal Control in the Federal Government (2025)

Worked example: a common test uses different rules

A fictional owner reviews three projects with markup rates of 5%, 8% and a negotiated fixed fee. A common test can ask whether each applied treatment matches its approved rule. It cannot correctly multiply every project's eligible base by the same percentage.

Suppose all three projects have an apparent $10,000 difference. One is a calculation error, one is a pending contract interpretation and one is an intentional fixed-fee arrangement supported by an amendment. The dashboard should show one confirmed issue, one unresolved decision and one cleared item. A portfolio total of $30,000 “savings” would obscure the actual result.

Measure coverage, decision quality and effort

Report how much of the relevant population was available, reviewed and independently resolved. Show counts and values with denominators. Track unresolved evidence gaps, false positives and time per reviewed item. Distinguish the period's new exceptions from its carried backlog.

Keep confirmed financial outcomes in separate categories and avoid summing currencies without a documented conversion policy. Do not compare raw exception counts across projects with different scopes or transaction volumes. A project can appear cleaner because fewer records were delivered. Coverage gives the sponsor the context needed to interpret the result.

Turn a diagnostic into an annual scope only after it works

Define the recurring deliverable as a review queue, coverage statement, resolved exceptions and outcome record. Specify which work remains with the owner's auditors, cost consultants, certifiers and accounting team. A control can operate alongside Procore or Oracle without replacing either system.

Discuss a fixed-fee historical diagnostic with Buildalytic, then independently validate the proposed work on clean and problematic records. Any annual contract, integration and service boundary needs a separate written agreement. Recurrence should come from actual repeat-project review needs, with pricing tested against that scope and delivery effort.

Sources: Buildalytic: current custom-workflow scope