Planning and projects

Work, time and delivery, on one board

A plan that lives apart from the work stops being true within a week. Tasks, the hours booked against them and the date they are promised for belong on the same record, or the schedule is a picture of an intention.

An Odoo project board with task counts and dates per project.

Tasks

Stages that mean something, not colours on a wall

Each column is a state the work is genuinely in, with the hours booked and the person responsible on the card rather than in a separate sheet.

An Odoo task board by stage with assignees and hours.

Time

Hours against the work, not against the week

Time booked to the task it was spent on, which is what makes billable hours invoiceable and unbillable hours visible.

One task

Everything about it in one place

The customer, the sales order line it belongs to, the milestone, the allocated time and the whole conversation, on the record rather than around it.

An Odoo task record with milestone, customer and time allocation.

Where it went

What the work actually cost to deliver

Tasks by project and by state, so the difference between what was scoped and what was delivered is a figure rather than a feeling at the end.

An Odoo task analysis chart by project and state.

Screenshots show the Odoo interface, captured from Odoo's public demo database or published by Odoo S.A. at odoo.com — not Rkieh Productions client systems. Odoo is a trademark of Odoo S.A. Rkieh Productions is an Odoo partner and implements and configures Odoo for its clients; what any given system does depends on edition, enabled modules, hardware and the agreed solution design.

In scope

What the module covers

This describes the scope Rkieh Productions can implement or configure using Odoo and related integrations. Final availability depends on edition, enabled modules, hardware and the agreed solution design.

Tasks

The unit of work, with an owner, a state, a deadline and the conversation attached to it.

Schedules

Who is doing what and when, across people and across weeks, on a plan that reflects the work.

Resource allocation

Capacity per person and per role, so a commitment is checked against the hours that exist.

Timesheets

Hours booked to the task, feeding billing and cost rather than being retyped into both.

Delivery tracking

Milestones and dates measured against what was promised, not against what is left.

Reporting

Progress, effort and profitability per project, off the tasks and hours themselves.

The plan

Who is on what, and when

ERP and business operations

A schedule by person and by week, with the work laid against the hours that actually exist. It is the difference between agreeing a date and knowing whether anybody is free to meet it — and it is the same data the timesheets later book against.

An Odoo resource schedule by person across a week.

Connected

What delivery is wired to

Project work is where a business finds out whether the price it quoted survived contact with the job.

Sales

A sold service becomes the project and the tasks that deliver it, without a second entry.

Invoicing

Billable hours reach the invoice as hours, at the rate the order agreed.

Employees

Capacity, roles and time off come from the same people records HR keeps.

Accounting

Cost and revenue land on the analytic account for the project, so profitability is per job.

Field service

Interventions scheduled, worked and reported against the same task.

Customers

The client sees progress on the work they bought, on the record it is being done on.

What changes

Four things delivery stops doing

Planning in a spreadsheet

The schedule is the work, not a picture of it.

Retyping hours

Time booked once reaches billing and cost together.

Finding out at the end

Effort against scope is visible while it still matters.

Guessing profitability

Cost and revenue meet on the project, per job.