See the installed product first
Shown with fictional English demonstration data. These are working product views, not design mockups.
Project, Manufacturing and Field Service timesheets under one roof
Bring project and task timesheets, manufacturing order and work order time, and Field Service job timesheets into one governed operational view. Managers can compare employees, departments, customers, projects, production operations and service work without replacing the native Odoo records that remain the source of truth.
Unified Timesheet Field Service
Carry technician, customer-site and service-task context into weekly, live and executive performance reporting.
Built for decisions, not decorative totals
Customer-site work becomes visible alongside project and manufacturing activity without fragmenting reporting.
Technician work context
Show the real task, project, customer and service description behind every field-service duration.
Live job visibility
Display active field jobs, elapsed duration and the responsible employee in the workforce snapshot.
Weekly service grid
Review technician time by employee, work context and day with direct record drill-down.
Enterprise-aware integration
Uses official Field Service capabilities when installed while keeping dependencies explicit and safe.
Commercial continuity
Preserve project, task and customer relationships for downstream cost and billability analysis.
Suite-native UX
The connector appears inside the same multilingual premium dashboard and reporting experience.
Observe
Read authoritative Odoo business records.
Reconcile
Synchronize reporting context idempotently.
Explain
Expose traceable KPIs, anomalies and drill-down.
Act
Approve, correct and improve with confidence.
Real operational screens
Premium, multilingual and designed to preserve the context behind every number.
Designed for production Odoo
| Context | Technician, project, task, customer and site work |
| Views | Weekly grid, dashboard and live workforce |
| Compatibility | Odoo 18 Field Service capability detection |
| Dependencies | Project connector and Dashboard |
Your Odoo data remains yours
The suite is an analytical and workflow layer. Project, task, manufacturing, attendance and leave records remain authoritative in their native Odoo applications. Addon-owned reporting records can be rebuilt, and removing the addon does not require destructive changes to native business data.
Multilingual foundation: translatable interface strings follow the active Odoo language; English is the source language and Turkish translations are included where supplied.
Clear dependencies, governed capabilities
Install only the capabilities you need. Core is the governed foundation; connectors preserve their native domain context; Dashboard turns the combined dataset into the premium management experience.
| Module | Relationship |
|---|---|
| Unified Timesheet Core | Required foundation |
| Unified Timesheet Dashboard | Requires Core + Project + MRP |
| Unified Timesheet Project Connector | Requires Core |
| Unified Timesheet MRP Connector | Requires Core |
| Unified Timesheet Attendance Bridge | Requires Project + MRP |
| Unified Timesheet Field Service | Requires Project + Dashboard |
See technician time, customer context and active service work in one operational view.
Move beyond totals. Every score is paired with a formula, a valid denominator, a reporting period and a path back to the Odoo records that produced it.
Know who is active and what comes next.
Compare schedule, duration and repeat visits.
Keep project, task and customer context visible.
Know what each number means before acting on it
The sample values below illustrate the product experience. Your results are calculated from your own authorized Odoo records and selected reporting period.
| Score | Example | Calculation basis |
|---|---|---|
| SERVICE UTILIZATION | 79.5% | Field-service hours / expected capacity |
| SCHEDULE ADHERENCE | 91.8% | On-plan service hours / planned service hours |
| TECHNICIAN PRODUCTIVITY | 87.2% | Productive service time / attended capacity |
| AVERAGE JOB DURATION | 2.7 h | Completed service hours / completed jobs |
| CUSTOMER SITE COVERAGE | 94.6% | Jobs with customer and site context |
| FIRST-TIME COMPLETION | 88.3% | Jobs without linked repeat follow-up / completed jobs |
| TIMER INTEGRITY | 99.2% | Valid timer sessions / inspected sessions |
| TRAVEL/SERVICE BALANCE | 18/82 | Travel share / productive service share |
See the signal. Understand the formula. Open the evidence. Take action.
Premium presentation is matched by operational depth: multilingual UI, company-aware security, source traceability, period controls and drill-down are part of the product story.
From installation to management action
This guide explains the complete operating model: what must be configured, which native Odoo record remains authoritative, how the reporting layer is refreshed, how managers should interpret metrics and how common data-quality issues are resolved.
Installation and first configuration
Prepare a controlled, auditable rollout before exposing metrics to management.
- Install the Project Connector and Dashboard, then install Field Service support for the matching Odoo 18 environment.
- Confirm that field-service tasks carry project, assignee, customer, planned date and service description.
- Validate the official Enterprise Field Service capability when installed; the connector keeps optional capability checks explicit.
- Test one technician timer from start to stop and verify task, project, customer and employee context in Weekly Grid.
Daily operating workflow
Understand where data originates and how it becomes visible in the suite.
- Dispatchers plan and assign service tasks using native Field Service and Planning workflows.
- Technicians start work from the supported task/timer action; open evidence appears in Live Workforce.
- Basic mode shows the active job, related project/customer and record ID in a compact all-personnel view.
- Advanced mode adds attendance, elapsed duration, previous three jobs and next three planned assignments.
Manager review procedure
Use drill-down and comparable periods to turn indicators into defensible decisions.
- Compare technician time by customer, service task, project and period.
- Open a duration to inspect contributing analytic lines and the authoritative task.
- Use planned-versus-performed comparisons to identify dispatch, travel, access or execution variance.
- Treat customer-site time, attendance presence and productive task time as related but distinct measures.
How the principal indicators are calculated
Percentages are meaningful only when their denominator is valid. Always confirm calendar, leave, planning, cost and source completeness before comparing employees or departments.
| Metric | Formula | Interpretation |
|---|---|---|
| Service Utilization | Field Service Hours / Expected Capacity x 100 | Capacity directed to customer-site service. |
| Schedule Adherence | On-plan Service Hours / Planned Service Hours x 100 | Execution matched to dispatched service work. |
| Average Job Duration | Completed Service Hours / Completed Jobs | Typical captured duration per completed job. |
| First-time Completion Context | Jobs completed without repeated follow-up / Completed Jobs x 100 | Useful only when follow-up relationships are maintained. |
Resolve the cause at the authoritative source
Recommended production acceptance checklist
1. Reconcile a sample period against native Odoo totals.
2. Test multi-company access with real non-admin roles.
3. Confirm timezone and calendar behavior around day boundaries.
4. Verify every KPI drill-down reaches its contributing records.
5. Test approved leave, holiday and no-schedule scenarios.
6. Start and stop each supported timer path.
7. Upgrade in a staging database before production.
8. Document who owns data correction and period approval.
Make time, capacity and performance explainable
Purpose-built for organizations that need operational clarity across project delivery, manufacturing and workforce capacity inside Odoo.
Unified Timesheet Field Service - Odoo 18| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) • Manufacturing (mrp) • Inventory (stock) • Project (project) |
| Community Apps Dependencies | Show |
| Lines of code | 7562 |
| Technical Name |
unified_timesheet_fsm |
| License | LGPL-3 |
Please log in to comment on this module