Record why effort changed before deciding how it affects the fee. Separate a new client requirement, correction of existing work and clarification within the original scope. Preserve the associated deliverable revision and commercial decision, while retaining actual time so project managers can understand cost even when the work is not separately billable.
Understand the decision
A revised site constraint can require new analysis after a design phase was accepted. Another change may correct an internal error. Both consume engineering time but need different management and billing treatment. The workflow should let responsible reviewers distinguish those causes without hiding effort in a generic overhead code.
Work through the requirements
- Classify the cause of changed effort.
- Link time to the affected deliverable.
- Review additional-service authorization before billing.
| Record or decision | Why it matters |
|---|---|
| Change rationale | Explains why the work was required. |
| Revision reference | Identifies the deliverable affected by change. |
| Effort review | Connects actual time and commercial decision. |
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 timesheet category cannot determine whether a client owes an additional fee. Preserve the reason, scope reference and approval decision, and let the responsible commercial reviewer apply the engagement terms to the recorded effort.
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 Engineering consultancies 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 ↗