Condition and objective
Inspection or assessment information, project purpose, urgency, asset impact, risks of delay, and the standard the work must meet.
Capital planning resource
Property Capital Project Oversight Checklist
Capital projects become risky when scope, authority, funding, schedule, and proof of completion fall out of alignment. Good oversight makes those connections visible from the first question to closeout.
Project discipline
Do not approve a price before defining the decision.
The strongest early question is not “Which proposal is cheapest?” It is “What condition, risk, or outcome must the project address—and what evidence tells us that the proposed scope is sufficient?”
Boards and owners should distinguish professional determinations from governance decisions. Appropriate specialists provide the technical or regulated expertise; leadership organizes options, authority, funding, stakeholder communication, and accountable implementation.
- Define the asset condition, objective, constraints, and decision required
- Identify the records and qualified professional input needed
- Compare scope, assumptions, exclusions, schedule, and risk—not price alone
- Document authority, budget source, approvals, and change-control process
- Require progress evidence and a structured closeout record
Capital project file01 02 03 04 05 06
What leadership should be able to find quickly.
Scope and alternatives
Defined scope, assumptions, exclusions, options considered, professional recommendations, expected disruption, and dependencies.
Procurement record
Proposals, comparison matrix, qualifications, insurance, references, clarification questions, selection rationale, and contract review process.
Budget and authority
Funding source, estimate, contingency, approval limits, cash-flow timing, change-order authority, and reporting expectations.
Delivery controls
Schedule, milestones, site access, communication plan, quality verification, payment conditions, risk log, and decision register.
Closeout evidence
Completion verification, warranties, permits, final documents, unresolved items, final cost, lessons learned, and future maintenance requirements.
Project checkpoints
Seven gates before the work disappears into execution.
- FrameWrite the problem, objective, critical constraints, risk of deferral, and decision leadership needs to make.
- InvestigateCollect relevant records and identify the qualified professional input required for the property-specific question.
- ScopeDefine deliverables, exclusions, quality standard, site conditions, stakeholder impacts, and assumptions.
- CompareNormalize proposals so differences in scope, schedule, staffing, warranty, supervision, and exclusions are visible.
- AuthorizeRecord selection rationale, funding, authority, risk acceptance, contract review, and change-control rules.
- MonitorReview milestone evidence, costs, quality, schedule, resident impacts, changes, and decisions on a fixed cadence.
- CloseVerify completion, retain records, resolve punch-list items, transfer warranties, and document lessons for future work.
Board questions
Questions to ask before approving a major project.
Are we comparing the same scope across proposals?
Confirm that each proposal uses the same assumptions, quantities, exclusions, access constraints, materials or performance standard, schedule, supervision, warranty, and change-order approach. A lower price may reflect a different scope rather than a better value.
What makes a project status report useful?
It should show completed milestones, next milestones, approved and pending changes, forecast cost, schedule changes, quality or safety issues, stakeholder impact, decisions needed, accountable owner, and evidence supporting the report.
When is the project actually complete?
Not simply when a vendor says work is finished. Closeout should follow the agreed acceptance process and include applicable verification, punch-list resolution, records, warranties, permits, final costs, and future maintenance information.
Working checklist
Capital project oversight checklist
Use this evidence set from project definition through closeout. It separates board approval, field verification, financial control, and operational handover.
These rows define suggested controls, not completed property findings. Interpret each check against your actual property records, responsible role and acceptance evidence. See the review instructions and reuse terms.
18 checks shown
No check matches those filters. Try a different term or area.
| Review area | Check | Evidence to request | Decision question |
|---|---|---|---|
| Definition | Problem statement | Observed condition affected assets and consequence of inaction | Is the project solving a defined problem? |
| Definition | Scope boundaries | Included work exclusions assumptions and interfaces | What is outside the approved scope? |
| Definition | Baseline condition | Photographs assessments and specialist recommendations | What condition will be compared after work? |
| Definition | Owner requirements | Performance durability access and resident constraints | How will success be judged? |
| Procurement | Comparable proposals | Same quantities specifications schedule and exclusions | Are bids truly comparable? |
| Procurement | Qualifications | References insurance license as applicable and project team | Can the team perform the proposed work? |
| Procurement | Contract terms | Deliverables payment triggers changes warranties and remedies | Do terms protect the owner decision? |
| Finance | Approved budget | Base cost contingency soft costs and funding source | Does approval cover the full expected cost? |
| Finance | Cash schedule | Expected draws reserve timing and other commitments | Can payments be met when due? |
| Finance | Change exposure | Open requests potential cost and schedule effect | What remains unapproved? |
| Delivery | Milestone plan | Start dates dependencies inspections and substantial completion | Which delay requires board direction? |
| Delivery | Site observations | Dated photos field reports and deficiency list | Does reported progress match visible work? |
| Delivery | Payment evidence | Application backup lien documents as advised and approval record | Does the requested payment reflect verified progress? |
| Delivery | Resident impact | Access outages notices and complaint escalation | Who owns the resident communication? |
| Control | Decision log | Approved changes authority dates and revised baseline | Can the board reconstruct scope changes? |
| Control | Risk register | Safety permit material lead time and weather risks | Which risk has no mitigation owner? |
| Closeout | Acceptance record | Punch list tests inspections and final approvals | What evidence supports acceptance? |
| Closeout | Operations handover | As built records warranties training and maintenance plan | Can operations maintain the completed asset? |
Working method
Define acceptance before work begins
Completion is a testable outcome, not merely a paid invoice.
Before procurement, specify the owner requirements: performance, finishes, access, permits, testing, documentation, training, warranties, and the conditions for final acceptance. Identify which decisions belong to the board, manager, design professional, and contractor. A responsibility map prevents a field question from becoming an unauthorized change.
Track dependencies that could affect the critical path, such as design decisions, permits, long-lead materials, resident access, inspections, and funding releases. Review these alongside budget and physical progress. At closeout, use the dedicated capital project closeout guide to verify punch items, commissioning, asset information, and turnover records before final acceptance.
Need independent structure for a major property decision?
Discuss the project
Hypothetical worked example
A design change breaks the funding sequence
A fictional project scope changes after estimates and funding timing were prepared. The original plan no longer represents the proposed commitment.
Original fictional example · no completed client assignment or property inspection is represented.
| Record to obtain | Review question or calculation |
|---|---|
| Current professional scope | Reconcile scope maturity before procurement |
| Revised estimate and dependencies | Review cumulative commitment and cash dates |
| Funding and payment schedule | Retain the new acceptance requirements |
Useful working output: An updated decision package linking scope, funding, procurement and operational acceptance.
Adapt the record request to authorized access, governing documents and the actual property. The example does not verify any unknown input or replace a professional conclusion.
Capital Project Payment Evidence and Milestone Review · More capital projects and building safety examples
Before acting on this guide
Set the review boundary and the acceptance test.
When to use it
A project moves from concept to funding or procurement.
What the evidence does not prove
Do not treat a preliminary estimate as a fixed complete commitment.
What to verify before acceptance
Identify estimate stage, design basis, exclusions, temporary service and approval dependencies before release.
Original proposed coordination checks · adapt to authorized access, the actual obligation and the appropriate professional review. These are not findings about your property.
Follow the related handoff workflow · Read the review definitions
A number, its evidence and the decision
Show commitments and remaining work in the same forecast
A paid-to-date figure is not the expected final cost. Distinguish paid invoices, unpaid commitments and uncommitted remaining work so each amount appears once in the forecast.
Baseline
Record the authorized scope and budget.
Commitment
Include paid and unpaid committed cost once.
Forecast
Estimate uncommitted remaining work separately.
Control
Review headroom and changes before commitment.
A worked example with visible assumptions
A fictional project has a $300,000 authorized budget, $220,000 in commitments including invoices already paid, and $65,000 of uncommitted remaining forecast cost. Expected final cost is $285,000 and headroom is $15,000. Do not add paid invoices again. Headroom excludes any risk allowance not entered in the remaining forecast.
Original hypothetical arithmetic example. The amounts describe a fictional scenario, not observed property performance or a recommended target.
Continue with Capital Project Change Order RegisterExplore the calculation
Enter non-negative values using the same scope and period. This calculation stays in your browser tab.
A change needs a baseline
Identify what changed against the executed scope, including price, time, dependencies and acceptance effects.
Avoid double counting
If a commitment includes a paid invoice, adding both inflates the forecast. Track payment status within the commitment.
Closeout starts before the last invoice
Commissioning, permits, punch-list work and warranty records belong in the plan while the delivery team can still resolve them.
Put the guidance to work
Control the handoff between design and procurement
Do not ask bidders to solve different versions of the same problem. Use the professional scope, revision date, access assumptions, and accepted alternates as a common pricing baseline.
Maintain a decision log for scope changes and a dependency map for approvals, permits, resident access, temporary service, and materials. A contractor schedule may omit tasks owned by the association.
Report forecast final cost as committed cost plus remaining forecast work and pending exposure. Show contingency separately, with an explanation of what it is intended to cover.
Apply the next operating control
- Capital Project Warranty Tracking and Defect Follow-Up
- Capital Project Resident Access and Disruption Planning
Find checklists and data definitions · Explore capital projects and building safety