Record effort against recognizable client requests and review it against the actual retainer arrangement. Distinguish extra scope, internal rework and ordinary delivery variation before changing charges or forecasts. A timesheet total alone should not determine an overage invoice; preserve the request, commercial decision and any agreed change in priorities.
Understand the decision
One client may request urgent revisions while another delays the inputs needed for planned work. The agency needs to understand capacity and profitability without inventing a universal rollover rule. The configured process should reflect the accepted agreement and expose decisions about additional work or deferred deliverables.
Work through the requirements
- Classify extra requests and internal rework.
- Review effort against the accepted agreement.
- Approve revised priorities or additional charges.
| Record or decision | Why it matters |
|---|---|
| Request log | Connects client instructions and actual effort. |
| Retainer review | Explains included and additional work. |
| Priority decision | Records agreed deferral or scope change. |
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
Treating every hour above a target as a customer overage confuses internal planning with contract terms. Keep the actual request and approved treatment visible, and have the responsible commercial owner review the billing consequence.
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 Marketing agencies 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: timesheet configuration and recording ↗Odoo 19: sales quotations and invoicing methods ↗