71The Financial Life of a Project: Opportunity, Estimate, Contract, Delivery, and Close

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 treats projects, services, labor, and contracts as time-based financial systems. Scope, schedule, cost, billing, cash, obligations, and performance must be integrated; otherwise a project can appear successful in one view while failing in another.

Central question: How can a project be financially controlled from the first commercial idea through final settlement and lessons learned?

Project finance begins before award. Opportunity assumptions shape estimate and price; contract allocates risk and cash; baseline integrates scope, schedule, and cost; execution generates progress, commitment, billing, and forecast; close resolves obligations and preserves learning.

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 project lifecycle in plain and professional language.
• Define and distinguish estimate in plain and professional language.
• Define and distinguish contract value in plain and professional language.
• Define and distinguish contract 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. Project lifecycle

Working definition. Project lifecycle is the sequence through which a temporary undertaking is identified, evaluated, authorized, planned, executed, controlled, delivered, and closed.

Financial control begins before contract signature and continues after physical completion through claims, settlement, warranty, and lessons. This is where operational activity and financial reporting meet.

Simple example. A project moves from opportunity and estimate to baseline, execution, acceptance, final account, and archive.

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.

2. 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. 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.

3. Contract value

Working definition. Contract value is the consideration stated or expected under a contract, adjusted for approved variations and governed by contract terms.

Contract value is not automatically revenue, billing, cash, or profit. Variable consideration, claims, taxes, financing, and scope changes may require separate analysis. The professional term matters because it prevents two different realities from being recorded as though they were the same.

Simple example. An original CU 5 million contract plus CU 300,000 approved variation produces CU 5.3 million current contract value.

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.

4. Contract

Working definition. Contract is an enforceable agreement that creates rights and obligations between parties, subject to applicable law.

Operational and accounting systems should preserve the signed terms, amendments, performance evidence, consideration, dates, and responsible parties. A non-specialist can understand this by separating the object, the timing, and the consequence.

Simple example. A service contract defines scope, milestones, acceptance, price, payment terms, liability, and termination.

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.

5. Baseline

Working definition. Baseline is the formally approved scope, schedule, cost, or performance plan used as the reference for control.

A baseline is protected history. Forecasts may change as reality changes; baseline changes require governed change control. The concept should be measured at the smallest level that still supports a real action.

Simple example. The approved project budget and schedule become the basis for variance and earned-value measurement.

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.

6. 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 number alone is not enough; its definition determines whether comparisons are valid.

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

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.

7. Final settlement

Working definition. Final settlement is the controlled resolution of remaining contract amounts, claims, variations, retention, defects, obligations, and releases at project close.

Physical completion is not financial close. Reconcile contract value, billing, cash, cost, assets, warranties, and open risks. This is where operational activity and financial reporting meet.

Simple example. The final account resolves pending variations and releases remaining retention.

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.

8. Accountability

Working definition. Accountability is the obligation to explain and accept responsibility for decisions, actions, controls, and results.

Responsibility without information is unfair; authority without accountability is dangerous. Varza should connect each material state change to an identifiable actor. In Varza language, the concept becomes useful when it changes a decision.

Simple example. The project manager owns the latest cost forecast and must explain material changes.

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.

How the concepts connect

The concepts in this chapter are a system, not a vocabulary list. Project lifecycle, Estimate, Contract value, Contract, Baseline, Project cash flow, Final settlement, and Accountability 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

Project forecast margin

Forecast margin = Current contract revenue forecast − Estimate at completion cost

The relation compares expected contract economics with latest total cost.

Boundary: Revenue forecast must reflect approved and supportable consideration; cost forecast must include committed, accrued, remaining, risk, and closeout cost.

Worked case — A winning bid that needs a second decision

A company wins a CU 2 million fixed-price project originally estimated at CU 1.55 million.

Item	Amount or observation
Contract value	CU 2,000,000
Original estimated cost	CU 1,550,000
Tender margin	CU 450,000
Post-award scope clarification	CU 180,000 additional expected cost
Payment terms	first customer cash after four months
Mobilization need	CU 300,000

Calculation and reasoning

1. Update the estimate before baseline: expected cost becomes at least CU 1.73 million before further risk.
2. Forecast margin falls to CU 270,000, or 13.5% of contract value.
3. Assess whether scope clarification is included, negotiable, claimable, or a bid error.
4. Model the CU 300,000 mobilization and four-month cash gap.
5. Authorize the project only after commercial, capacity, and funding responses are explicit.

What the result means

Contract award is not the end of estimation. It is the point at which the organization must convert a sales promise into a financially executable baseline.

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. Qualify customer, scope, capability, risk, cash, and strategic fit before bid. 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. Build a traceable estimate and negotiate contract terms consistent with assumptions. 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. Authorize project and establish integrated baseline and governance. 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. Control performance, change, billing, collection, forecast, and final settlement through close. 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 opportunity, estimate, bid, contract, project, baseline, work_package, commitment, progress, billing, forecast, closeout. 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:

• Turn information into a decision, a control, or a question; otherwise it is only decoration.
• Begin with the real event, not the accounting label.
• Keep value, cash, profit, and ownership distinct until their relationship is proven.

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. Independent bid review for high-risk projects. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
2. Estimate-to-baseline reconciliation. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
3. No project close with unresolved assets, claims, retention, warranties, or supplier obligations. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
4. Lessons captured against original assumptions. 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: Treating award value as profit

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: Starting work before scope, authority, and commercial responsibility are clear

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: Measuring project success only by physical completion

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: Closing the project operationally while receivables, claims, and commitments remain open

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 project lifecycle in plain language and in professional terms?
• Can I explain estimate in plain language and in professional terms?
• Can I explain contract value in plain language and in professional terms?
• Can I explain contract 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 Project lifecycle 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 Estimate. 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 Contract value 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-071",
  "canonical_topics": [
    "Project lifecycle",
    "Estimate",
    "Contract value",
    "Contract",
    "Baseline",
    "Project cash flow",
    "Final settlement",
    "Accountability"
  ],
  "facts": [
    "Project lifecycle: the sequence through which a temporary undertaking is identified, evaluated, authorized, planned, executed, controlled, delivered, and closed.",
    "Estimate: a reasoned approximation of future quantity, time, cost, revenue, or result based on scope, method, data, assumptions, and uncertainty.",
    "Contract value: the consideration stated or expected under a contract, adjusted for approved variations and governed by contract terms.",
    "Contract: an enforceable agreement that creates rights and obligations between parties, subject to applicable law.",
    "Baseline: the formally approved scope, schedule, cost, or performance plan used as the reference for control.",
    "Project cash flow: the timing and amount of cash inflows and outflows attributable to a project.",
    "Final settlement: the controlled resolution of remaining contract amounts, claims, variations, retention, defects, obligations, and releases at project close.",
    "Accountability: the obligation to explain and accept responsibility for decisions, actions, controls, and results."
  ],
  "formula_names": [
    "Project forecast margin"
  ],
  "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.