Project management has run near double an installer rate. One flat rate hides that.
2 · Units
The unit-series codes are derived from the unit count using the rate card.
Garden style is the average of Sample Job (278 units) and Sample Job A (330 units), which
agree within a few percent. Podium comes from Sample Job alone and is a single sample.
3 · Accubid report
Export the Accubid report as text if you can; a PDF is read in the browser and the text
layer is less reliable. The report's own totals are used as control figures, so if the
mapping does not add up you will see it rather than inherit it.
4 · Budget
Enter a unit count, then read a report or build by hand.
5 · Margin
Margin is the contract less every cost class in the
budget above. It is only as honest as what is entered there.
Enter a contract value and build a budget.
6 · Comparison
Target follows the margin % in section 5.
Read an Accubid report or build a budget first.
6 · Schedule of values
Load what exists before touching the model below. The model is for a job
that has no schedule yet; it does not replace one already agreed with the GC.
Percentages come from the G703 continuation sheets on jobs already billed, so the
starting point is what Ops has actually billed rather than a guess. Every value is
editable and the total is forced to the contract amount — a schedule of values
that does not tie to the contract gets rejected by the GC.
Enter a contract value, then build.
7 · Save
Draft saves the budget so you can come back to it. Create writes job_budgets,
job_financials and the schedule of values. On a job already running it
rebuilds the budget instead, archiving the old rows first. Export writes
nothing — it just downloads the workbook.