84Construction and Contracting: Estimates, Progress, Subcontractors, Claims, and Retention

Varza promise: clear enough for a first-time learner, exact enough for a professional conversation, and practical enough to support a real decision.

Why this chapter matters

This track applies the common financial core to different industries. The accounting equation does not change, but the operational evidence, risk, unit economics, timing, and control points change sharply from retail to farming or software.

Central question: How can a contractor control long-duration, site-based work where scope evolves, suppliers and subcontractors perform before billing, and cash follows certification?

Construction finance integrates quantity-based estimate, WBS, schedule, subcontract commitments, site records, progress measurement, change, claim, retention, cash, and forecast. The project can be physically advanced yet commercially unprotected or financially overrun.

Varza approaches the subject from life to ledger and from ledger to decision. We begin with what actually happened, identify the rights, obligations, resources, timing, and uncertainty, and only then choose the correct term, calculation, document, or account. This order protects the learner from a common error: learning a label without understanding the economic reality that the label is supposed to describe.

Learning outcomes

• Define and distinguish estimate in plain and professional language.
• Define and distinguish contract costing in plain and professional language.
• Define and distinguish work breakdown structure in plain and professional language.
• Define and distinguish subcontractor in plain and professional language.
• Apply the concepts to a numerical case and explain the result rather than only calculate it.
• Identify evidence, workflow, controls, and Varza entities required for reliable use.
• Recognize when jurisdiction-specific or licensed professional advice is required.

The Varza mental model

A financial concept becomes decision-ready when six questions have answers: what, who, when, how much, based on what evidence, and under which assumption or rule. A seventh question—what should happen next—turns knowledge into management.

This chapter uses internationally recognized terminology, but it remains jurisdiction-neutral unless explicitly stated. Accounting standards, tax rules, contract law, consumer protection, labor requirements, and investment regulation can produce different legal outcomes in different countries. The global foundation gives the learner a stable map; local collections must add the binding rules.

Core concepts

1. Estimate

Working definition. Estimate is a reasoned approximation of future quantity, time, cost, revenue, or result based on scope, method, data, assumptions, and uncertainty.

A professional estimate is traceable and updateable. It records basis and uncertainty rather than presenting false precision. In Varza language, the concept becomes useful when it changes a decision.

Simple example. A project estimate links quantities, rates, productivity, schedule, escalation, and contingency.

Decision test. What is being measured, and what has been left outside the boundary? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

2. Contract costing

Working definition. Contract costing is the accumulation and control of cost for a substantial, often long-duration customer contract or site-based undertaking.

Contract cost joins scope, estimate, commitments, progress, changes, billing, risk, and forecast. The professional term matters because it prevents two different realities from being recorded as though they were the same.

Simple example. A two-year construction contract tracks labor, materials, equipment, subcontractors, and site overhead.

Decision test. When did the underlying right, obligation, benefit, or sacrifice arise? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

3. Work breakdown structure

Working definition. Work breakdown structure is a hierarchical decomposition of the total project scope into manageable deliverables and work packages.

The WBS should cover one hundred percent of project scope without overlap and provide stable links to schedule, responsibility, estimate, cost, and progress. A non-specialist can understand this by separating the object, the timing, and the consequence.

Simple example. A building project decomposes into design, foundation, structure, envelope, systems, and handover.

Decision test. Which document or observation would allow another person to verify it? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

4. Subcontractor

Working definition. Subcontractor is a party engaged by a principal contractor to perform a defined part of contracted work.

Subcontract control covers scope, qualification, insurance, schedule, progress measurement, variations, retention, claims, safety, and payment. The concept should be measured at the smallest level that still supports a real action.

Simple example. An electrical subcontractor completes and certifies a building work package.

Decision test. How would a different assumption change the result? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

5. Progress invoice

Working definition. Progress invoice is a billing document issued for work completed, milestones achieved, quantities certified, or time elapsed under a project contract.

Progress billing follows contract evidence and may differ from revenue recognition. Preserve certification, deductions, tax, retention, and prior billing. The number alone is not enough; its definition determines whether comparisons are valid.

Simple example. The monthly certificate approves CU 400,000 gross work less retention and advance recovery.

Decision test. Who can influence the result, and who only reports it? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

6. Project claim

Working definition. Project claim is a formal assertion of entitlement to additional time, money, relief, or other remedy under a contract.

A claim requires notice, contractual basis, cause, evidence, quantum, schedule effect, status, and probability. Submitted value is not automatically recognized revenue. This is where operational activity and financial reporting meet.

Simple example. A contractor claims cost and time caused by late customer access.

Decision test. Does the item affect cash now, later, or not at all? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

7. Retention

Working definition. Retention is a portion of payment withheld under a contract until specified completion, defect, or warranty conditions are met.

Retention is not a discount. Track receivable or payable, release conditions, aging, security alternatives, and collectability. In Varza language, the concept becomes useful when it changes a decision.

Simple example. Five percent of each certified amount is withheld until final completion.

Decision test. What is being measured, and what has been left outside the boundary? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

8. Project cash flow

Working definition. Project cash flow is the timing and amount of cash inflows and outflows attributable to a project.

Project profit can coexist with negative cash when mobilization, procurement, billing, certification, retention, and collection are misaligned. The professional term matters because it prevents two different realities from being recorded as though they were the same.

Simple example. A project pays deposits and labor months before the first certified customer payment.

Decision test. When did the underlying right, obligation, benefit, or sacrifice arise? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

How the concepts connect

The concepts in this chapter are a system, not a vocabulary list. Estimate, Contract costing, Work breakdown structure, Subcontractor, Progress invoice, Project claim, Retention, and Project cash flow describe different parts of the same decision. Confusing them usually creates one of three failures: the wrong amount is measured, the right amount is assigned to the wrong period or person, or a correct report is used for a decision it was never designed to support.

A useful analysis therefore preserves both classification and relationship. Classification tells us what an item is. Relationship tells us what caused it, what it affects, and what could change it. Varza should store both. A report that shows only totals may be suitable for orientation; a controlled decision requires traceability to the underlying relationships.

Formulas and quantitative relationships

Quantity-based earned progress

Earned quantity value = Verified installed quantity × Approved budget or contract rate

The calculation links physical progress to a defined rate.

Boundary: Rate may serve budget, billing, or earned value; do not assume the same rate serves all purposes.

Worked case — Physical progress is ahead of commercial protection

A contractor installs extra work instructed verbally by the customer representative.

Item	Amount or observation
Verified extra direct cost	CU 90,000
Requested price	CU 125,000
Formal change approval	none
Contract notice period	seven days
Notice age	five days
Schedule effect	estimated ten days

Calculation and reasoning

1. Issue the contractually required notice immediately with scope, cause, instruction, cost, schedule, and reservation of rights.
2. Record the CU 90,000 expected cost in project forecast and commitments or accruals as appropriate.
3. Keep the CU 125,000 requested price in an at-risk change or claim state, not approved contract value.
4. Obtain written direction on continuing work and consider authority and risk before further exposure.
5. Preserve daily records and critical-path evidence.

What the result means

Construction control must show both realities: work and cost may be real, while entitlement and collection remain uncertain. Hiding either creates a false project picture.

The case is deliberately compact. In practice, Varza would preserve the supporting documents, currency, dates, counterparty, project or cost center, approvals, and links to the resulting records. The lesson is not merely to reach a number; it is to make the path to that number reviewable.

Practical workflow

1. Define the decision, responsible person, economic unit, period, and acceptable uncertainty. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
2. Build quantity and productivity estimate linked to scope and WBS. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
3. Procure subcontract and material packages with clear measurement and change rules. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
4. Capture daily site evidence, installed quantity, labor, plant, delay, and instruction. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
5. Certify, bill, claim, forecast, collect, and close with all retention and final-account items reconciled. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
6. Reconcile the result to source evidence and investigate exceptions rather than forcing agreement. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
7. Approve the decision or record at the authority level required by value, risk, and legal consequence. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
8. Monitor the outcome, compare it with the original assumption, and retain the learning for the next cycle. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.

How this concept should appear in Varza

The minimum Varza data model for this chapter includes project, quantity_takeoff, estimate, wbs, site_record, subcontract, progress_measurement, change, claim, retention, forecast, final_account. These names are not merely interface labels. Each entity should have a stable identifier, status history, responsible owner, applicable currency or unit, effective dates, evidence links, and access controls.

A useful Varza screen should answer four questions without forcing the user to reconstruct the story manually:

1. What happened or is expected to happen? Show the operational event, obligation, or decision in plain language.
2. What changed financially? Show cash, asset, liability, equity, income, expense, commitment, or risk effects.
3. Why should the user trust it? Show source documents, calculations, approvals, and revision history.
4. What requires attention now? Show exceptions, due dates, thresholds, and the next responsible action.

The Varza design principles most relevant here are:

• Begin with the real event, not the accounting label.
• Keep value, cash, profit, and ownership distinct until their relationship is proven.
• Attach every important number to a source, period, currency, entity, and responsible person.

Varza AI may explain, classify, compare, simulate, and prepare a proposed action. It should not silently change a legal record, post a material transaction, close a period, release a payment, or make an investment decision on the user’s behalf. Material actions require visible evidence, permissions, validation rules, and an accountable human approval path.

Controls and professional boundaries

1. No site instruction without a commercial notice path. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
2. Subcontract progress independently measured. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
3. Quantity, cost, and schedule forecast updated together. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
4. Retention and claim registers reviewed through closeout. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
5. Stable definitions, versioned assumptions, and consistent units across plans, records, and reports. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
6. Traceability from every material total to evidence, calculation, owner, and change history. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
7. Access and approval rights aligned with responsibility and the possible consequence of error or misuse. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.

A control is effective only when it operates in practice. A policy that everyone can bypass is a statement of hope, not a control. Likewise, a control that blocks ordinary work without distinguishing low-risk and high-risk cases encourages hidden workarounds.

Common mistakes and better responses

Mistake 1: Measuring progress from money spent

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 2: Allowing verbal scope change without contemporaneous notice and evidence

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 3: Paying subcontractor percentage from its invoice without site verification

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 4: Reporting profit before forecast includes defects, delay, demobilization, and final settlement

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 5: Using a technically correct number outside the period, entity, currency, or decision boundary for which it was calculated

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 6: Accepting an automated result without reviewing the evidence, assumptions, exceptions, and required professional judgment

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Decision checklist

• Can I explain estimate in plain language and in professional terms?
• Can I explain contract costing in plain language and in professional terms?
• Can I explain work breakdown structure in plain language and in professional terms?
• Can I explain subcontractor in plain language and in professional terms?
• Have I stated the entity, currency or unit, date or period, and decision boundary?
• Can another person reproduce the number from retained evidence?
• Have I separated actuals, estimates, commitments, and scenarios?
• Have I tested timing, liquidity, risk, and at least one adverse outcome?
• Is the required approval proportional to the possible loss or legal consequence?
• Does the final output lead to a specific action, owner, and review date?

Practice lab

1. Explain it. Describe Estimate to a person who has never studied finance. Then add the professional definition and identify one boundary your simple explanation omitted.
2. Classify it. Create five examples from your household or a small business and classify each using Contract costing. State any assumptions.
3. Calculate it. Rebuild the worked case with amounts 20% higher. Identify which conclusions change and which remain structurally true.
4. Challenge it. Describe a situation in which Work breakdown structure could be measured correctly but still lead to a poor decision because timing, risk, or incentives were ignored.
5. Design it. Sketch a Varza screen or report for this chapter. Include fields, evidence links, status, owner, exceptions, and one AI-assisted action.

Answer guidance

A strong answer uses consistent definitions, reveals assumptions, distinguishes fact from estimate, and connects the result to an action. More than one conclusion may be reasonable when the learner clearly states the decision objective and uncertainty. The worked-case recalculation should preserve the method even when the numbers change.

Varza AI knowledge capsule

This capsule is intentionally explicit so that a retrieval system can distinguish canonical teaching points from examples and commentary.

{
  "chapter_id": "VARZA-F100-084",
  "canonical_topics": [
    "Estimate",
    "Contract costing",
    "Work breakdown structure",
    "Subcontractor",
    "Progress invoice",
    "Project claim",
    "Retention",
    "Project cash flow"
  ],
  "facts": [
    "Estimate: a reasoned approximation of future quantity, time, cost, revenue, or result based on scope, method, data, assumptions, and uncertainty.",
    "Contract costing: the accumulation and control of cost for a substantial, often long-duration customer contract or site-based undertaking.",
    "Work breakdown structure: a hierarchical decomposition of the total project scope into manageable deliverables and work packages.",
    "Subcontractor: a party engaged by a principal contractor to perform a defined part of contracted work.",
    "Progress invoice: a billing document issued for work completed, milestones achieved, quantities certified, or time elapsed under a project contract.",
    "Project claim: a formal assertion of entitlement to additional time, money, relief, or other remedy under a contract.",
    "Retention: a portion of payment withheld under a contract until specified completion, defect, or warranty conditions are met.",
    "Project cash flow: the timing and amount of cash inflows and outflows attributable to a project."
  ],
  "formula_names": [
    "Quantity-based earned progress"
  ],
  "jurisdiction_scope": "global-foundation",
  "required_answer_qualifiers": [
    "entity",
    "date_or_period",
    "currency_or_unit",
    "source_or_assumption",
    "jurisdiction_when_relevant"
  ],
  "human_approval_required_for": [
    "posting_material_transactions",
    "closing_periods",
    "changing_master_data",
    "releasing_payments",
    "submitting_filings",
    "individual_investment_execution"
  ],
  "source_ids": [
    "S208",
    "S209",
    "S210",
    "S211",
    "S114"
  ],
  "edition": "2026.1",
  "review_date": "2026-08-31"
}

Suggested questions for Varza AI

• Explain this chapter using an example from a household, a shop, and a service business.
• Ask me five diagnostic questions before applying this concept to my situation.
• Show the difference between cash effect, accounting effect, and decision effect.
• Recalculate the worked case using my currency and assumptions, but preserve the original definitions.
• Identify which parts require local accounting, tax, legal, labor, or investment rules.

Sources and standards horizon

This chapter is original Varza educational content. It paraphrases and synthesizes concepts; it does not reproduce a standard or third-party article. The following sources were used to establish terminology, scope, and current professional context:

• S208 — U.S. Government Accountability Office, Cost Estimating and Assessment Guide. 2020-03-12. Reliable estimating, work breakdown structures, assumptions, risk and estimate updates. Source: https://www.gao.gov/products/gao-20-195g
• S209 — U.S. Department of Energy, Earned Value Management. accessed 2026-08-31. Integrated measurement of scope, schedule and cost. Source: https://www.energy.gov/projectmanagement/earned-value-management
• S210 — U.S. Department of Energy, EVMS Implementation Guidance. accessed 2026-08-31. Implementation of earned value management systems. Source: https://www.energy.gov/projectmanagement/evms-implementation-guidance
• S211 — Project Management Institute, Work Breakdown Structure—Basic Principles. accessed 2026-08-31. Product-oriented decomposition of total project scope. Source: https://www.pmi.org/learning/library/work-breakdown-structure-basic-principles-4883
• S114 — IFRS Foundation, IFRS 15 Revenue from Contracts with Customers. 2026 standards set. Principles for recognizing revenue from customer contracts. Source: https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/

Standards horizon. Reviewed through 2026-08-31. IFRS 18 and the third edition of the IFRS for SMEs Accounting Standard are included as transition knowledge where relevant; both have mandatory effective dates beginning in 2027, with early application permitted under their respective requirements.

Jurisdiction note. Global educational foundation; local law, tax, reporting, consumer-protection, licensing, and professional requirements must be checked separately.

Professional-use note. This learning material does not replace advice from a qualified accountant, lawyer, tax adviser, licensed investment professional, or other regulated specialist who has reviewed the user’s facts and jurisdiction.