Cost Cue
Task-specific guidance for ordinary budget entry and cost-code assignment.
Project 15
Create and maintain one residential job-cost control system that reconciles original budget, approved changes, commitments, actual cost, pending exposure, forecast-to-complete, billing, and variance by cost code, using the approved Book 24 estimate, contract value, cost-code structure, and current project documents as the controlling information.
These cues appear at the point of work. They identify budget, commitment, forecast, and reporting issues before they become uncontrolled overruns, missed billing, or unreliable cost history.
Task-specific guidance for ordinary budget entry and cost-code assignment.
An uncontrolled overrun, hidden exposure, or unauthorized commitment is possible.
Practical coordination with field supervision, accounting, and procurement on cost data.
Accounting cutoff, accrual, or billing timing conditions vary. Verify before assuming.
Follow the company's specific rules for pending-cost recognition and commitment authority.
Recordkeeping and period-history guidance for cost reports.
This project qualifies you to build and operate a residential job-cost control system — the controlling record that reconciles what the project was budgeted to cost, what has been committed, what has actually been spent, what exposure remains unrecorded, and what the project is forecast to cost at completion. The finished work product is one current, cost-code-aligned job-cost report supported by a locked original budget, commitment records, actual-cost entries, a pending-cost log, and a preserved history of every issued report.
You will import the approved estimate and contract value, align cost codes with the WBS and accounting system, lock the original budget, create current-budget, commitment, actual-cost, pending-cost, forecast, and revenue fields, enter purchase orders, subcontracts, labor, material, and equipment costs against the correct codes, reconcile invoices against the accounting cutoff, identify and investigate variance, prepare a job-cost report with a written narrative, and preserve each issued report as a period record.
This project depends directly on the estimate produced under Book 24, the WBS and cost codes established in Project 03, the procurement records built in Project 07, and the change and allowance log operated in Project 11. It supplies the current cost picture used in every Project 09 coordination meeting from this point forward, and its final reconciliation becomes part of the Project 18 closeout package.
The job-cost system built here is the financial mirror of the WBS from Project 03, the procurement log from Project 07, and the change and allowance log from Project 11: the same cost codes, the same work packages, and the same approved changes drive schedule, procurement, and cost together. A job-cost report that cannot be traced back to the WBS and the approved change log is not a controlled report — it is a disconnected spreadsheet.
The discipline established here — locking the original budget, distinguishing commitment from actual cost, and never treating unapproved exposure as zero cost — is the same discipline the Chapter 20 capstone requires when it reconciles final job cost, contract value, allowances, changes, credits, retainage, and closeout costs before the project can be archived.
This project covers:
This project does not authorize the learner to:
Any conflict between the estimate, the contract value, and the current approved changes must be identified and resolved in writing before the original budget is locked.
Establish these references before entering any cost data, and do not change them mid-project without a recorded revision.
| Term | Definition |
|---|---|
| Original budget | The locked budget derived from the approved estimate and contract value at the start of cost tracking |
| Current budget | The original budget adjusted for approved transfers and change orders |
| Commitment | Cost obligated through an issued purchase order, subcontract, rental, or approved change, whether or not invoiced yet |
| Actual cost | Cost recorded from a verified labor record, material invoice, equipment cost, or subcontractor invoice |
| Pending cost | Known but unapproved or unbilled exposure, including unapproved changes, expected invoices, damaged material, rework, and claims |
| Forecast-to-complete | The estimated cost still required to finish the remaining scope of a cost code |
| Forecast-final-cost | Actual cost plus commitments plus pending cost plus forecast-to-complete for a cost code |
| Variance | The difference between current budget and forecast-final-cost, with an identified cause |
Before issuing the first job-cost report, record the system identification directly on the cost-code register:
Project name: ______ Project number: ______ Original budget locked date: ______ Contract value: ______
Accounting cutoff day: ____________ Update frequency: ____________ Responsible person: ____________ Review cycle: ____________
Every job-cost report in this book, from this chapter's residential cost control system to the Chapter 20 capstone reconciliation, follows the same sequence: align, lock, commit, record, forecast, investigate, report, preserve. Learning that sequence here, on one residential project, means every later cost update starts from a method you already trust.
Every job-cost report must separate what has been formally committed, what has actually been paid or invoiced, and what remains a known but unapproved exposure. Write pending-cost entries immediately when a condition is identified so a reader cannot mistake unrecorded exposure for a project that is under budget. An item left out of the pending-cost field becomes a forecast surprise once the exposure is finally invoiced.
Every job-cost report must carry a report date, the responsible preparer, and the accounting cutoff it reflects. Do not overwrite a previously issued report with the current update. Preserving only the current version, without the period history, removes the ability to see how the forecast changed and prevents accurate lessons-learned analysis later in the project.
Do not exclude an unapproved change, an expected invoice, damaged material, rework, or a claim from the forecast merely because it has not been formally approved or billed. Treating known exposure as zero cost is a leading cause of a forecast that looks accurate until the exposure is finally recorded, at which point the overrun appears all at once.
Confirm installed quantity and remaining scope directly with field supervision before finalizing forecast-to-complete for a cost code. A forecast built only from office records, without field confirmation, misses productivity, waste, and rework conditions that only field supervision can observe directly.
Where company policy specifies a particular method for recognizing pending cost, accruing late invoices, or setting commitment authority limits, follow that method exactly. Do not substitute a personal judgment call for the accrual or authority rule the company requires, even when it would be faster to report a rounder number.
PM-085 – PM-090
Cost Control / Reporting Qualification
Deliverable: one operating residential job-cost control system, containing aligned cost codes, a locked original budget, current budget, commitment, actual-cost, pending-cost, forecast, and revenue fields, entered purchase orders, labor, material, equipment, and subcontractor costs, updated allowance and change status, investigated variance, and one issued job-cost report with narrative, reviewed with the appropriate parties and preserved as a period record.
| Field | Content | Source | Purpose |
|---|---|---|---|
| Original budget | Labor, material, equipment, subcontract, general conditions, allowances, contingency, overhead, and other approved categories | Book 24 estimate, contract value | Establishes the locked starting point for every later comparison |
| Current budget | Original budget plus approved transfers and change orders | Change log | Reflects the budget as formally revised by approval |
| Commitments | Purchase orders, subcontracts, rentals, and approved changes | Procurement register, subcontracts | Records obligated cost before invoices arrive |
| Actual cost | Labor, material invoices, equipment, subcontract invoices, fees, other costs | Time records, invoices | Records verified cost actually incurred |
| Pending cost | Unapproved changes, expected invoices, damaged material, rework, claims, known exposure | Change log, field reports | Prevents known exposure from being reported as zero cost |
| Forecast-to-complete / forecast-final-cost | Remaining cost to finish each cost code; total forecast cost at completion | Field review, productivity data | Projects the final cost outcome for each cost code |
| Revenue | Original contract, approved changes, allowances, alternates, billings, retainage, collections, remaining value | Contract, billing records | Tracks the revenue side alongside the cost side |
| Variance and narrative | Variance by cost code and cause; corrective action and management decision | Comparison of current budget and forecast | Explains why cost differs from budget and what will be done about it |
| Check | Standard |
|---|---|
| Cost codes | Aligned across estimate, WBS, accounting, procurement, labor, and changes; no orphan codes on either side |
| Original budget | Locked and unchanged; revisions tracked only through the current-budget field |
| Commitments and actuals | Every purchase order, subcontract, invoice, and labor entry recorded against the correct cost code |
| Pending cost | Every known unapproved or unbilled exposure recorded, not treated as zero cost |
| Forecast | Based on field-reviewed installed quantity and remaining scope, not budget minus actual alone |
| Variance | Identified by cause for every cost code with significant variance; investigated before reporting |
| Report and history | Reviewed with the appropriate parties, distributed under confidentiality rules, and preserved as a dated period record |
Inspect every job-cost report using the same checks regardless of project size or complexity.
Complete the Job-Cost Report Inspection Checklist in the Inspection Checklist section below before issuing the report to the review parties identified in Step 32.
Probable cause: the forecast was calculated as budget minus actual cost without a field review of installed quantity and remaining scope, in violation of Step 23.
Confirmation: check whether the forecast-to-complete field was populated from a field review or from a simple subtraction, and compare against actual field progress.
Correction: conduct a field review with supervision for the affected cost codes and recalculate forecast-to-complete from installed quantity and remaining scope.
Reinspection: repeat the forecast check across all active cost codes, not only the one identified.
Probable cause: the pending-cost field was left blank for an unapproved change, expected invoice, damaged material, rework, or claim, in violation of Step 8.
Confirmation: check the change log, field reports, and correspondence for known exposure items and compare against the pending-cost field for the affected cost code.
Correction: enter the exposure in the pending-cost field with its estimated amount and update the forecast-final-cost accordingly.
Reinspection: repeat the pending-cost check across the full cost-code register.
Probable cause: the cost-code alignment in Step 2 was not completed, or a cost code was created in one system without a matching code in another.
Confirmation: check the cost-code register for the item in question and confirm whether it exists in the WBS, procurement register, labor records, and change log.
Correction: create or correct the missing code across all systems, reassign the misfiled entry, and document the correction.
Reinspection: repeat the cost-code check across the full register, not only the disputed item.
Probable cause: the variance investigation in Step 25 was not completed, or the actual cause among productivity, waste, damage, rework, or a reporting error was never identified.
Confirmation: compare the cost code's actual cost, committed cost, and reported percent complete, and check field records for productivity, waste, damage, or rework conditions.
Correction: identify the specific cause, record it in the variance narrative, and assign corrective action with a responsible party and due date.
Reinspection: repeat the variance check for the cost code after the next reporting period.
Probable cause: the period-history convention from Step 34 was not followed, and the current update was saved over the previous report instead of preserved as a new period record.
Confirmation: check the period-report archive for a complete, dated sequence of issued reports and confirm whether any period is missing.
Correction: reissue the current report as a new dated period record, and correct the archive procedure so future updates are preserved rather than overwritten.
Reinspection: confirm the archive shows an unbroken sequence of period reports going forward.
Probable cause: the authority limit from Step 13 was not confirmed before the purchase order or subcontract was released.
Confirmation: check the commitment amount against the responsible person's documented authority limit and confirm whether the required approval was obtained.
Correction: obtain retroactive approval from the correct authority level, document the exception, and correct the commitment authority process for future purchase orders and subcontracts.
Reinspection: repeat the authority check on the next commitment issued against the affected cost code.
This project ends with the current job-cost report reviewed and archived, not left as an open working file.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-085 | Sets up cost codes aligned across the estimate, WBS, accounting, procurement, labor, and change systems with no orphan codes | |||
| PM-086 | Compares locked original budget, current budget, commitments, and actual cost by cost code and identifies discrepancies | |||
| PM-087 | Tracks labor hours, wage, burden, crew, phase, and cost code from verified time records and compares production against the estimate basis | |||
| PM-088 | Tracks material and equipment costs from invoices against the correct cost code, purchase order, and delivery record | |||
| PM-089 | Identifies overruns and variance by specific cause and investigates cost codes with mismatched cost and reported progress | |||
| PM-090 | Prepares a complete job-cost report with narrative, reviews it with the appropriate parties, and preserves it as a period record |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Cost codes | Aligned across estimate, WBS, accounting, procurement, labor, and changes | ||
| Original budget | Locked and unchanged; revisions tracked only in current budget | ||
| Commitments | Recorded against the correct cost code before invoices arrive | ||
| Actual cost | Recorded from verified labor, material, equipment, and subcontractor records | ||
| Pending cost | Every known exposure recorded, not treated as zero cost | ||
| Forecast | Based on field-reviewed data, not budget minus actual alone | ||
| Variance | Identified by cause with corrective action assigned where needed | ||
| Confidentiality | Report distributed only to authorized parties | ||
| Review | Reviewed with project management, field supervision, accounting, procurement, and management | ||
| Period history | Issued report preserved as a dated record without overwriting prior reports |
Variance narrative status: ____________ Open corrective actions carried forward: ____________
Job-cost report declared issued: ______ (Pass/Fail) Date: ____________ Project manager name: ____________
With the job-cost report prepared and reconciled, review it against the Acceptance Standards table and confirm every cost code is aligned across the estimate, WBS, accounting, procurement, labor, and change systems, the original budget remains locked, every commitment and actual cost is recorded against the correct code, every known pending exposure is recorded rather than treated as zero cost, the forecast reflects a field review rather than budget minus actual alone, every significant variance has an identified cause and, where needed, an assigned corrective action, the report has been reviewed with the appropriate parties under confidentiality rules, and the report is preserved as a dated period record. Complete the Job-Cost Report Inspection Checklist and correct any failed item before issuing the report. If an item fails, identify whether the error occurred in cost-code alignment, budget locking, commitment entry, actual-cost entry, pending-cost recognition, forecast calculation, variance investigation, or reporting and archiving before revising.
You have completed the fifteenth project in the construction project management sequence: tracking budget, cost codes, and job cost reports. This project required you to set up cost codes (PM-085), compare budget to actuals (PM-086), track labor costs (PM-087), track material costs (PM-088), identify overruns (PM-089), and prepare a job cost report (PM-090).
You now have an operating job-cost control system with a locked original budget, aligned cost codes, recorded commitments and actual costs, a pending-cost log, a field-reviewed forecast, investigated variance, and one issued, reviewed, and archived job-cost report. This system carries directly into the next project: coordinating required authority, trade, utility, special, manufacturer, lender, and owner inspections, whose scheduling and correction records will in turn affect the cost and schedule picture this report establishes.
File your issued job-cost report, cost-code register, and variance narrative where later coordination meetings, change events, and the Chapter 20 capstone reconciliation can rely on this exact cost baseline.