Odoo app guide
Odoo Project: Delivery Tasks, Time & Milestones
Odoo Project organizes delivery work into projects and tasks, with related time and commercial workflows where configured. The useful design connects a customer commitment to accountable execution and the evidence needed for billing. Ever Digital helps establish that structure. Complex construction contracts, engineering design, specialist scheduling and advanced project accounting require their own fit assessment.
Official Odoo Partner · Ever Digital
Translate the sold scope into work that can be assigned.
A project needs a clear purpose, responsible manager and meaningful completion criteria. Tasks should represent work someone can own and report on. Copying every line of a lengthy proposal into an equally lengthy task list can obscure the handoffs that actually control delivery.
Start by identifying deliverables, dependencies and the evidence needed to accept them. Decide how a change to the customer’s scope becomes authorized project work. Without that rule, the team may complete substantial additional activity that never reaches the commercial record.
Choose the relationship between work and billing.
The contract and finance policy determine what should become billable. Demonstrate the chosen configuration with a realistic project.
| Arrangement | Record that matters | Question to resolve |
|---|---|---|
| Fixed scope | Agreed deliverables and commercial order. | How is completion reviewed when actual effort differs from the estimate? |
| Time and materials | Approved time and chargeable costs or products. | Who reviews entries before they are used for billing? |
| Milestones | The milestone and its accepted completion. | What evidence authorizes invoicing and how are disputes handled? |
| Mixed delivery | Separate commercial components with explicit rules. | Can the team distinguish covered work from additional charges? |
Odoo documentation · CC BY-SA 4.0 · CC BY-SA 4.0
Original documentation image, shown without altering the interface. The screenshot illustrates standard Odoo, not a customer implementation.
Time records need a purpose and a review routine.
If time informs billing, costs or capacity decisions, staff must know which task to use and what description is required. Define how corrections are reviewed and when a period is ready for reporting. Inconsistent time entry can make an otherwise well-structured project appear misleadingly profitable or unproductive.
Avoid treating every recorded hour as automatically chargeable. Internal coordination, rework, travel and contracted allowances may have different commercial treatment. The implementation should preserve those distinctions in a way the team can maintain.
Connect procurement and site execution deliberately.
An installation project may require equipment purchasing, warehouse delivery and field visits. Identify which app owns each event rather than expecting a project task to replace a purchase order or stock movement. The manager needs visibility of the dependencies and an owner for each exception.
For IT and technical projects, distinguish deliverable acceptance from ongoing support. A completed implementation may hand over to Helpdesk or Field Service, but support entitlement and contact channels should be agreed rather than inferred from the project’s existence.
Clarify specialist project requirements before selecting the design.
These needs can materially change scope and should be demonstrated with actual documents.
- Construction BOQs, retention, variations, performance guarantees and complex progress certification.
- Advanced resource optimization, specialist engineering schedules or external design-tool integration.
- Detailed cost allocation, revenue recognition and statutory financial treatment.
- Customer approval portals, secure document exchange and contractual audit trails.
Use a project with a change and an unfinished deliverable.
Create the initial work, record time or milestones as appropriate, then introduce an additional request and a delayed task. The project manager should be able to explain what remains, what is authorized and what can be billed. Finance should reconcile the invoice basis to the agreed commercial arrangement.
Bring a project plan, sample contract and one completed billing example to Ever Digital. These provide a better assessment basis than a list of desired dashboard widgets. The rollout should establish a reliable delivery routine before adding elaborate reporting.
Questions businesses ask
Can a sales order create project work?
Relevant service product settings can connect Sales and Project. Verify the project or task created and how it retains the customer and billing context.
Can projects be billed by time or milestones?
Odoo documents time-and-materials and milestone workflows. The contract, product setup and review responsibilities determine the appropriate configuration.
Does Project replace a construction specialist system?
That should not be assumed. BOQs, retention, contract variations and other construction controls require an exact fit assessment.
Should we import every historic task?
Only where the history has an operational or reporting purpose and can be reconciled. Prioritize active projects, remaining obligations and a clear archive boundary.
Sources and factual scope
Capabilities checked against official Odoo documentation. These are planning examples, not promises that every feature is included in a Starter package.
Reviewed:
Ever Digital
Bring your real workflow to the conversation.
Tell us how you sell, stock, deliver or service. We will identify the standard apps, decisions and any extensions your implementation needs.
View Starter packages Current implementation fees and included scope are maintained on the Starter package pages. Odoo licences, hosting and custom work are separate.