Commercial Property Capital Project Tracking: A Landlord Workflow for Budgets, Draws, and Closeout

Commercial Property Capital Project Tracking: A Landlord Workflow for Budgets, Draws, and Closeout
Getting a roof replacement, parking-lot rebuild, exterior repair, or major building-system project approved is a meaningful milestone. It is not the point at which the work becomes easy to manage.
After approval, the project can fragment quickly: the approved bid is in one email thread, the contract is in another folder, the first invoice arrives before the schedule is updated, and a field change is discussed before anyone records its effect on the remaining budget. By closeout, the property team may know the work is finished but still have to reconstruct what was authorized, paid, changed, and handed over.
This article is an operating workflow for commercial and NNN landlords running a landlord-funded capital project after approval. It is not a CapEx budget-preparation process, a tenant-improvement allowance workflow, or a lien-waiver tracking guide. It also does not determine contract rights, payment obligations, accounting treatment, permit requirements, or lease recoverability. Those questions depend on the governing documents and local facts.
Start with one live project record
Create a single project record before issuing a notice to proceed or approving the first payment. It should point to the source documents; it should not replace the signed contract, approved proposal, or required professional records.
At minimum, include:
- Property, location, asset or system, project owner, and project status.
- The approved scope reference, approval date, approved budget, and planned contingency.
- Vendor, contract or proposal reference, key contacts, and relevant insurance or compliance records required by the agreement.
- Planned start, key milestones, expected completion, and tenant-impact or access notes.
- Baseline budget, commitments, approved draws, paid-to-date amount, forecast to complete, and remaining authorized amount.
- Links to the contract, drawings or specifications when applicable, invoices, change requests, approvals, inspection records, and closeout documents.
- The next decision, its owner, and the date it needs attention.
The purpose is straightforward: a new property manager or owner should be able to see what is approved today, what has happened since, and what must happen next without rebuilding the story from an inbox.
1. Freeze a usable scope and budget baseline
The initial budget should be a comparison point, not a number that gets silently overwritten when conditions change. Save the approved scope, vendor proposal or contract, decision record, and budget detail that supported approval. Then assign a version and date to the baseline.
Break the budget into categories that match how the work will actually be committed and reviewed. A roof project might use mobilization, demolition, roofing materials, flashings, repairs, testing, and contingency. A parking project might use demolition, base repair, paving, striping, drainage, and traffic control. Do not add more categories than the team can maintain.
For each line, show:
| Budget field | Why it matters | | --- | --- | | Baseline amount | Preserves the approved starting point. | | Approved changes | Shows decisions that formally changed the project. | | Current authorized budget | Makes the post-change limit visible. | | Committed amount | Shows signed or otherwise authorized obligations. | | Paid to date | Shows completed payment activity. | | Forecast to complete | Surfaces the expected final cost before the project ends. | | Variance and next action | Makes an overage, savings, or missing decision visible. |
Keep contingency visible as its own line or clearly identified component. If it is used, record the condition, amount, approver, and revised forecast. A contingency draw is not automatically a scope approval.
2. Separate commitments, draws, and forecast
Three numbers are often confused because they all describe project cost. They answer different questions.
- Committed amount: What has been authorized with vendors under the current project record.
- Approved or paid draws: What has been approved for payment or actually paid against that commitment.
- Forecast to complete: What the team expects the completed project to cost based on known work, pending changes, and remaining risk.
An invoice can be lower than the committed amount, and a project can look under budget on paid invoices while the forecast shows an impending overage. Keep each measure separate. The monthly review should compare the current authorized budget with commitments, paid-to-date activity, and the latest forecast—not just the last invoice.
For each commitment, retain the supporting agreement, approved proposal or scope, amount, effective date, responsible vendor, and approval record. If the vendor is performing under a revised document, link the revision rather than replacing the original record. This preserves the decision trail when the project is reviewed months later.
3. Turn every draw into a reviewable decision
A draw should be more than an invoice routed for payment. Create a draw record that lets the reviewer see what is being requested, what evidence supports it, and whether approving it would exceed an existing decision.
For every draw or payment request, capture:
- Draw number, request date, period covered, vendor, and invoice or application reference.
- Requested amount, reviewed amount, approved amount, and payment status or payment reference.
- Budget category and related commitment or contract reference.
- Work claimed or observed, plus the relevant progress documentation, inspection note, photo, schedule update, or other support used by the project team.
- Required documents under the contract, lender, insurer, or internal process, marked present, pending, or not applicable.
- Reviewer, approval date, exceptions, and the next required follow-up.
Before approval, ask four practical questions: Does the request tie to an approved commitment? Does the support match the work or deliverable being requested? Does the amount fit the current authorized budget and forecast? Is a change decision hiding inside the invoice?
The answer is sometimes “needs more information.” That is a useful status. Leave the draw pending with the exact missing item and owner instead of approving it based on an assumption. Follow the contract and your organization’s payment controls where they set a different process.
4. Log change requests before they become work in progress
Field conditions, substitutions, access constraints, design clarification, and owner requests can all change a capital project. The operational risk is not that every change is bad; it is that the change is discussed informally, performed quickly, and only later appears as a surprise on an invoice.
Use a change log with one row per request. Record the request number, date, description, reason, linked scope or budget line, requested cost, schedule effect, supporting documents, decision owner, status, and approved amount if approved.
Keep these statuses distinct:
- Requested: Submitted for review; no authorization to proceed is implied.
- Under review: The team is assessing scope, cost, schedule, or required documentation.
- Approved: Authorized through the applicable project process and reflected in the current budget.
- Rejected or withdrawn: Not part of the authorized forecast.
- Executed: Work has been completed or incorporated, with the supporting record linked.
When a change is approved, update the current authorized budget, commitment record if applicable, schedule, and forecast. When it is not approved, do not bury it in a general “variance” note. Keeping unapproved requests visible makes the next decision clear and protects the baseline from being rewritten by memory.
5. Keep invoices and contract evidence connected to the project
Good project tracking does not require every document in one PDF. It does require a clear path from a payment request back to the document and decision that support it.
Organize the file so a reviewer can move from the project record to the signed agreement or approved proposal, scope and specifications, invoice or draw request, approval, change record, progress evidence, and final closeout material. Use consistent names and references, especially where one vendor has multiple jobs at the same property.
Required documentation is project-specific. The contract, lender, insurer, applicable permits, and local requirements may call for different items or forms. Do not use a generic checklist to decide what is legally required. Instead, set up a project-specific evidence list at the start, identify the owner for each item, and review its status before each draw and at closeout.
This is also where a dependable vendor contract tracking process helps: the project record can link to the agreement, dates, contacts, and required vendor documents rather than creating a second, conflicting vendor file.
6. Review the project on a regular operating cadence
A short weekly review can work during active construction; a monthly review may be sufficient for longer or less intensive work. The cadence matters less than a repeatable agenda.
At each review, ask:
1. What work was completed since the last review, and what evidence supports that status? 2. What is committed, requested for payment, paid, and forecast to complete? 3. Which change requests need a decision before work proceeds? 4. What milestones, access needs, inspections, or tenant communications are approaching? 5. Which documents are missing, expired, or waiting for review? 6. What could prevent completion, final payment, or handoff to operations?
Record the answer and owner for each meaningful open item. A dashboard that says “on track” is less valuable than a record that says “awaiting revised proposal for drainage repair; owner: project manager; decision due Thursday.”
For the earlier, pre-approval side of this discipline, use a commercial property CapEx budget checklist. Once work is underway, the focus shifts from deciding whether to fund the project to controlling approved scope, decisions, evidence, and closeout.
7. Treat completion and closeout as separate gates
Physical completion, final payment, and closeout are related but not identical. A space or system may be ready for use while documentation, deficiencies, final invoicing, warranties, or handoff material remain open. Keep separate statuses so the project is not archived simply because the visible work has stopped.
For completion, capture the applicable completion milestone, inspection or acceptance evidence used by the project team, remaining punch items, owner, due date, and any operating restrictions. For closeout, confirm the items required by the project’s governing documents and internal process have been collected, reviewed, and stored where the operations team can find them.
Depending on the project, that may include final invoices, approved changes, record drawings, operating and maintenance information, warranties, permits or inspection records, testing or commissioning records, training material, and a final list of unresolved items. This is not a universal list. It is a practical closeout structure. Public-sector construction guidance similarly distinguishes turnover documents such as operating manuals, warranties, and record drawings from completion milestones.[^1]
Do not mark a project closed when an item is merely expected. If a warranty package, final invoice, or correction remains outstanding, leave it as an open closeout task with an owner and review date. If a contract or applicable rule requires a particular release, waiver, payment, or acceptance step, follow that requirement and obtain appropriate advice where needed.
A one-page capital-project control checklist
Before you move an approved capital project to closed, confirm that:
- The approved scope and dated baseline budget are preserved.
- Commitments, draw approvals, payments, and forecast to complete are separately visible.
- Each approved change is linked to its decision, budget effect, and supporting record.
- Each material invoice or draw can be traced to the relevant commitment and review evidence.
- Completion evidence, punch items, and operating restrictions are recorded.
- Required closeout documents are saved and accessible to the people who will operate or maintain the property.
- Open items have an owner, due date, and next review rather than being hidden in an archived folder.
- The final record identifies what was approved, what changed, what was paid, and what still needs follow-up.
The point is not to turn a small landlord team into a construction bureaucracy. It is to make the next decision easier to see while there is still time to make it well. Pair this project record with a consistent commercial property accounts payable approval workflow so the payment process and the project facts stay connected.
[^1]: U.S. General Services Administration, Project Management Guide identifies turnover documents including O&M manuals, warranties, and contractor record drawings alongside substantial and final completion milestones. It is an illustrative public-sector reference, not a substitute for a private project’s contract or requirements.
PigJet helps commercial landlords keep property documents, vendor records, approvals, tasks, and operating follow-up connected. See how PigJet supports commercial property operations.