Record the observed condition, its affected work and the decision needed before treating extra effort as approved revenue. Separate immediate operational action from the commercial agreement, preserving costs and instructions as they occur. Update the forecast only through the agreed review process so project reporting distinguishes proposed, authorized and completed changes.
Understand the decision
A concealed condition may interrupt one trade while others continue. The supervisor needs to identify the blocked sequence, additional material requirement and temporary plan. Finance needs evidence of the commercial treatment, not an assumption that every site instruction automatically creates an invoiceable variation for the customer.
Work through the requirements
- Describe affected work and dependencies.
- Preserve cost and instruction evidence.
- Review proposed and approved change values.
| Record or decision | Why it matters |
|---|---|
| Condition notice | Explains the operational issue and evidence. |
| Change register | Separates proposed and accepted commercial scope. |
| Forecast revision | Shows the agreed effect on remaining cost. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Combining proposed and approved variations makes the project appear better funded than it is. Keep their status distinct and require finance to reconcile accepted value with the evidence supporting each intended customer charge.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for General contractors in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: project management ↗Odoo 19: project milestones ↗Odoo 19: sales quotations and invoicing methods ↗