Link each significant revision to the client instruction, affected deliverables and reviewed commercial treatment. Separate a change of brief from normal refinement or correction of existing work. Record the actual effort even when the fee remains unchanged, and preserve the accepted prior revision so the project team can explain how the design developed.
Understand the decision
A client may change the room arrangement after approving a layout, or choose finishes later than planned. These events can affect several disciplines and the issue schedule. The practice needs a clear decision record rather than relying on email chronology to determine whether additional services were authorized.
Work through the requirements
- Record the instruction and affected revisions.
- Review scope and consultant consequences.
- Approve commercial treatment before revised billing.
| Record or decision | Why it matters |
|---|---|
| Client instruction | Explains the requested change and source. |
| Revision impact | Identifies affected documents and dependencies. |
| Fee decision | Records the reviewed additional-service treatment. |
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
A new drawing revision is not automatically an additional service, and unchanged fees do not mean the work was costless. Preserve both the reason for revision and the commercial decision while keeping actual effort visible.
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 Architecture and design practices 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: timesheet configuration and recording ↗