The weekly job-cost loop
Each week the same loop runs: set the baseline, record, measure output, compare, verify the data, explain, act, and feed back.
OpenStax says management should investigate an unfavorable variance to find its cause before responding.
The last step feeds actual yield and hours back into the next estimate as a new dated version, as AFS does with prices, never as an overwrite.
Eight steps in a loop: baseline, record, measure, compare, verify the data, explain, act, feed back, then back to the baseline. A panel lists what AFS records about a job and what it does not.
- A
- Baseline: the estimate and the standards, in hours, sheets and feet
- B
- Record: time tickets and material issued, each against one job and one operation
- C
- Measure output by a physical count: pieces, feet or bends formed
- D
- Compare actual with baseline: variances, CPI and SPI
- E
- Verify the data: reconcile sheets and hours before trusting an index
- F
- Explain: find the cause before acting
- G
- Act: correct, re-plan, or change the next quote
- H
- Feed back as a new dated version of the estimate, never an overwrite
Sources
- 8.2 Compute and Evaluate Materials Variances - OpenStax, Principles of Accounting, Volume 2: Managerial Accounting
- AFS price book and quote history rules: prices are versioned and dated, an edit adds a new version and never overwrites, an issued quote keeps the prices it was built on, and a finished job raises its invoice from the approved quote - Architectural Flashing Supply
