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 Project Connector
Connect project and task timesheets to the governed suite with customer, commercial and delivery context intact.
Built for decisions, not decorative totals
Project hours become explainable delivery and commercial insight-not just a total in a spreadsheet.
Native timesheet authority
Reads Odoo analytic lines as the authoritative project-time record and synchronizes reporting data idempotently.
Rich work context
Expose employee, project, task, customer, description and date instead of generic time-source labels.
Commercial performance
Analyze cost, revenue, margin, billability and utilization with company-aware currency handling.
Weekly drill-down
Open the exact underlying work records directly from duration cells and employee work rows.
Approval integration
Route project time through shared validation and locking without altering the original accounting truth.
Field-service ready
Provides the project/task foundation used by the optional Field Service connector.
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
| Source model | account.analytic.line |
| Context | Project, task, customer, employee and company |
| Financials | Cost, revenue, margin and billability |
| Dependency | Unified Timesheet Core |
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 |
Transform native project timesheets into delivery, utilization and margin intelligence.
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.
Spot allocation overruns before deadlines slip.
Compare project time cost, revenue and margin.
See the exact task behind every duration.
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 |
|---|---|---|
| PROJECT UTILIZATION | 76.8% | Project hours / expected capacity |
| TASK EFFICIENCY | 93.4% | Allocated hours / actual task hours |
| DELIVERY CONSISTENCY | 91.2% | Stability of normalized weekly delivery |
| BILLABILITY | 82.5% | Billable project hours / project hours |
| REVENUE PER HOUR | Native financial context | Timesheet revenue / project hours |
| TIME MARGIN | Native financial context | Timesheet revenue - employee time cost |
| ALLOCATION VARIANCE | +18.5 h | Actual task hours - allocated hours |
| CONTEXT COMPLETENESS | 98.1% | Lines with project, task and employee context |
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 Core, then install the Project Connector. Keep Odoo Project and Timesheets configured as the employee entry point.
- Confirm that employees are linked to users and companies, and that projects and tasks carry the required customer and billability context.
- Configure employee hourly cost and sales/billable information when cost, revenue and margin reporting is required.
- Run synchronization for a controlled date range and reconcile sample totals against native analytic lines before extending the range.
Daily operating workflow
Understand where data originates and how it becomes visible in the suite.
- Employees record time from the task, weekly timesheet or supported timer extension.
- Each analytic line remains the authoritative project-time record and is projected with project, task, customer and description context.
- Managers use Weekly Grid to see employee and work context by day, then click a duration to open its detailed records.
- Corrections are made on the native timesheet line. The next synchronization updates the same unified projection.
Manager review procedure
Use drill-down and comparable periods to turn indicators into defensible decisions.
- Group by project, task, customer, employee, company or billability to answer delivery and commercial questions.
- Compare recorded hours with task allocation and planned dates rather than interpreting a raw total in isolation.
- Use margin and billability only after employee cost and commercial pricing have been validated.
- Lock reviewed periods through shared governance while retaining a direct link to the source analytic line.
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 |
|---|---|---|
| Project Utilization | Project Hours / Expected Capacity x 100 | Capacity directed to project delivery. |
| Billability | Billable Project Hours / Project Hours x 100 | Commercial share of project work. |
| Time Margin | Timesheet Revenue - Employee Time Cost | Time-based commercial contribution. |
| Task Variance | Actual Task Hours - Allocated Task Hours | Overrun or underrun against allocation. |
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.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) • Project (project) |
| Community Apps Dependencies | Show |
| Lines of code | 1773 |
| Technical Name |
unified_timesheet_project |
| License | LGPL-3 |
Please log in to comment on this module