Job Cost Review for General Contracting
Job Cost Review is the recurring process of comparing actual project costs and commitments against the original budget, current forecast, and revenue billed to date. It uses structured reports, variance analysis, and joint reviews with the project team to catch coding errors, overruns, and savings early. The process also updates forecasts, reallocates budgets when needed, and feeds accurate information into work-in-progress and cash flow reporting. When done properly, Job Cost Review gives a clear picture of project health and supports timely decisions before cost problems become unfixable.
Define job cost review cadence, scope, and responsibilities
Step 1: Identify which projects require regular job cost reviews
Work with operations and finance leadership to decide which jobs will be included based on size, risk, and duration. For example, include all active projects over a certain dollar amount and any smaller jobs flagged as higher risk.
Step 2: Set review frequency and timing
Decide how often reviews will occur (for example, monthly for active jobs, more often near critical milestones). Align timing with other financial processes such as progress billing and work-in-progress updates.
Step 3: Define roles and responsibilities
List the roles involved in the review (finance staff, project manager, project engineer, superintendent, operations leader) and specify what each is responsible for preparing or reviewing.
Step 4: Create a standard agenda and checklist
Draft a simple agenda and checklist for each review that includes reports to run, topics to cover (budget vs actual, commitments, change orders, forecast), and decisions to make. Keep it consistent across projects.
Step 5: Document the process in a short procedure
Write a one- to two-page procedure summarizing cadence, scope, roles, and agenda. Store it in the company’s finance and project management procedures library.
Step 6: Communicate expectations to all stakeholders
Share the procedure and schedule with project managers and operations leaders. Explain that job cost reviews are a standard requirement and how they support both project and company performance.
Prepare job cost review report package
Step 1: Define standard reports needed for each review
Agree on which reports will be used, such as budget vs actual by cost code, committed cost report, change order log, labor cost detail, and revenue/billing summary. List these in the job cost review checklist.
Step 2: Set reporting period and cut-off date
Choose the cut-off date for data (for example, end of the prior month). Make sure all costs, time entries, and invoices through that date are entered in the system before running reports.
Step 3: Run core job cost reports from the accounting system
For each job being reviewed, run the standard job cost reports for the chosen period. Check that the correct job and date range are selected and that reports show both current period and cumulative amounts where possible.
Step 4: Export reports into a common format
Export reports to PDF or spreadsheet format so they can be easily shared and annotated. Name files clearly using job number, job name, and date (for example, “1234_MainSt_JobCost_2024-01-31”).
Step 5: Compile a single review packet per job
Combine all relevant reports and supporting documents (such as change order logs) into a single digital or printed packet for each project. Place reports in a logical order (summary first, then detailed breakdowns).
Step 6: Store packets in a shared review folder
Save the packets in a shared folder accessible to finance and project teams. Confirm that project managers know where to find the documents before the review meeting.
Reconcile costs, commitments, and change orders before review
Step 1: Confirm all current-period costs are posted
Check that all vendor invoices, timesheets, equipment charges, and other costs for the review period have been entered and posted to the correct job. Follow up with accounts payable or payroll if something is missing.
Step 2: Review open purchase orders and subcontracts
Run a report of open commitments (purchase orders and subcontracts) for each job. Verify that all known contracts and POs are in the system with correct values and that canceled or completed commitments are closed.
Step 3: Check change order status and values
Compare the change order log to the accounting system to ensure all approved change orders are reflected with the correct values and that pending change orders are clearly marked as not yet part of the budget or contract value.
Step 4: Identify and correct obvious coding errors
Scan cost detail for items coded to clearly wrong jobs or cost codes (for example, large costs coded to general conditions that belong in a specific trade code). Reclassify these entries to the correct codes with clear notes.
Step 5: Ensure revenue and billing are current
Verify that progress billings to the client through the review date have been entered and posted, and that the contract value in the system matches the latest approved amount.
Step 6: Document unresolved data issues for discussion
Make a short list of any data issues that could not be resolved before the review (for example, disputed invoices or pending change order approvals). Include these on the review agenda so they can be addressed with the project team.
Review cost coding accuracy and reclassify mis-coded costs
Step 1: Scan job cost detail for unusual patterns
Look at detailed cost reports for each job and identify unusual patterns, such as large amounts in “miscellaneous,” costs in codes that should be inactive, or negative balances that do not make sense.
Step 2: Compare coding to scope definitions
For a sample of larger transactions, compare the cost code used to the actual scope of work or item description. Use the job’s cost code guide to confirm whether the chosen code is appropriate.
Step 3: Identify mis-coded entries
List any transactions that appear to be in the wrong cost code, cost type, or even wrong job. Group them by type (labor, materials, subcontract, equipment) and by the correct destination code.
Step 4: Reclass costs in the accounting system
Create reclass journal entries or corrections in the accounting system to move mis-coded costs to the appropriate cost codes. Provide clear descriptions explaining the reason for each reclass.
Step 5: Confirm that reclasses resolve report issues
Re-run affected job cost reports to ensure that corrections now present a more accurate picture. Check that negative balances or odd spikes have been removed or reduced.
Step 6: Record coding issues for training and prevention
Note recurring coding mistakes by team or cost type. Share this information with project managers and field staff to improve future coding accuracy and update any coding guidance documents.
Analyze budget vs actual variances by cost code
Step 1: Calculate variances by cost code
Using your job cost reports, calculate for each cost code the difference between budget and actual costs to date, and express it both in dollars and as a percentage of budget.
Step 2: Flag significant positive and negative variances
Decide on thresholds that make a variance “significant” (for example, more than 10 percent of budget or above a set dollar amount). Highlight these codes in your report or spreadsheet.
Step 3: Determine if variances are timing or permanent
For each significant variance, consider whether it is due to timing (for example, large material delivery earlier than planned) or likely to be a permanent overrun or saving. Use knowledge of upcoming work and commitments to make this assessment.
Step 4: Review underlying detail for large variances
Drill into the cost detail for the largest variances to see what drove them: unexpected change order work, productivity issues, price increases, or coding anomalies.
Step 5: Prepare variance commentary
Write short notes explaining each significant variance in plain language, indicating cause and whether it is expected to correct over time or remain. These notes will guide discussion with the project team.
Step 6: Share preliminary variance summary with project manager
Send the variance summary and your initial commentary to the project manager before the review meeting so they can think about causes and potential corrective actions in advance.
Update cost-to-complete and forecast final cost with project team
Step 1: Provide current cost and commitment data to project team
Share updated reports showing actual costs to date, open commitments, and remaining budget by cost code with the project manager and project engineer before the meeting.
Step 2: Discuss remaining scope and risk for major cost codes
During the review, ask the project team to describe what work is left in each major cost code and any known risks such as difficult site conditions, schedule pressure, or subcontractor issues.
Step 3: Estimate cost-to-complete for each major code
For each key cost code, have the project team estimate the additional cost required to finish that scope, considering both remaining commitments and expected new costs (labor, equipment, or uncommitted subcontract work).
Step 4: Calculate forecast final cost
Add actual cost-to-date and estimated cost-to-complete for each code to calculate a forecast final cost. Compare this forecast to the original budget and note overruns or savings.
Step 5: Discuss and document reasons for forecast changes
For codes where the forecast final cost is higher or lower than budget, document the reasons (for example, scope increase, buyout savings, productivity gains or losses).
Step 6: Update forecast summary for use in WIP and management reports
Compile the updated cost-to-complete and forecast final cost into a summary for the job. Save this summary in the project file and use it as the basis for work-in-progress and margin reporting.
Conduct formal job cost review meeting with project team
Step 1: Schedule job cost review meeting in advance
Set a date and time for the review with the project manager, project engineer, superintendent (if needed), and finance representative. Send calendar invites with enough lead time for people to prepare.
Step 2: Distribute review packet and agenda beforehand
Share the job cost review report package and a simple agenda at least one business day before the meeting. Ask participants to review key variances and come prepared with explanations and ideas.
Step 3: Walk through summary results first
Start the meeting by reviewing the high-level picture: total budget, cost-to-date, committed costs, forecast final cost, billed-to-date, and projected margin. Make sure everyone understands the overall status.
Step 4: Discuss significant variances and forecast changes
Go through the list of significant variances and forecast adjustments cost code by cost code. Ask the project team to explain causes and whether corrective actions are possible.
Step 5: Identify agreed corrective actions and owners
For each issue that requires action (for example, re-bidding a trade, adjusting crew size, changing sequencing), agree on specific actions, assign an owner, and set due dates.
Step 6: Summarize decisions and next steps at the end
Before ending the meeting, recap key conclusions about job health, forecast margin, and the list of actions. Confirm that everyone agrees and understands their responsibilities.
Record job cost review findings, actions, and forecast updates
Step 1: Create a job cost review summary sheet
Use a simple template to record job name, date of review, participants, and headline results (forecast final cost, projected margin, and key variances).
Step 2: List key findings by cost category
Write bullet points summarizing important findings for major cost categories (for example, “sitework over budget due to unforeseen rock,” “structural steel under budget due to favorable buyout”).
Step 3: Document updated forecast metrics
Record the updated cost-to-complete, forecast final cost, and projected margin for the job. Note how these numbers have changed since the last review.
Step 4: Capture agreed corrective actions
List all actions agreed during the meeting, including what will be done, who is responsible, and target completion dates. Be specific so there is no confusion later.
Step 5: Save summary and share with stakeholders
Save the summary sheet in the project’s financial folder and email a copy to the project manager, operations leader, and finance leadership as appropriate.
Step 6: Schedule follow-up on open actions
Make a note of when to check back on the status of action items (for example, at the next job cost review or in a separate follow-up call). Add reminders to your calendar or task list.
Update budgets, forecasts, and WIP in accounting system
Step 1: Determine which changes require budget revisions
From the review summary, identify any agreed changes that involve reallocating budget between cost codes or increasing total budget within approved contract limits. Check company policy on when formal budget revisions are allowed.
Step 2: Enter approved budget changes
In the accounting system, input budget changes at the cost code level with clear descriptions (for example, “Budget moved from 03-Concrete to 31-Earthwork due to revised design”). Ensure that total job budget remains consistent with contract value unless a change order has increased it.
Step 3: Update forecast final cost fields
Enter updated forecast final cost for the job and, if your system allows, for key cost codes. Confirm that these match the values agreed in the review summary.
Step 4: Refresh work-in-progress calculations
Run updated work-in-progress reports that use the new forecast and cost data to calculate percentage complete, under/over billings, and projected margin. Check that these reports make sense relative to the review.
Step 5: Verify reports with project manager or operations
Share summary WIP and forecast results with the project manager or operations leader and confirm that they align with expectations from the review meeting.
Step 6: Save updated reports in job cost review folder
Store updated budget, forecast, and WIP reports with the review documents so there is a clear record of what changed and why at each review cycle.
Monitor follow-up actions and recurring problem areas
Step 1: Create an action item tracking list
Consolidate all action items from job cost review summaries into a single tracking list, including job, action description, owner, due date, and status.
Step 2: Check status of actions before the next review
Prior to each new job cost review, review the action list for that job and contact owners for updates. Note whether actions are complete, in progress, or stalled.
Step 3: Escalate overdue critical actions
If important actions (such as renegotiating a subcontract or changing crew structure) are past due, notify the project manager and operations leader. Ask whether due dates need adjustment or additional support is required.
Step 4: Identify recurring issues across projects
Look for patterns in action items and review findings across multiple jobs, such as repeated buyout overruns in certain trades or chronic under-budgeting of general conditions.
Step 5: Share trends with estimating and leadership
Prepare a short summary of recurring problem areas and discuss it with estimating and company leadership. Suggest where estimating assumptions, standard details, or processes might need to change.
Step 6: Adjust future job cost review focus areas
Based on patterns and trends, update your job cost review checklist to pay extra attention to frequent problem areas on future projects, improving the effectiveness of each review cycle.
👈 Use this SOP template inside Subtrak
Edit with AI. Customize in seconds. Store and share all your SOPs and checklists in one place.