Project teams running Odoo constantly re-encode the same "definition of done" into free-text task descriptions, chatter notes, and spreadsheets that live outside the record. Odoo's native project.task gives you stages, deadlines, and a description field, but it has no first-class concept of a repeatable checklist: a discrete list of items that must each be ticked, attributed to a person, and rolled up into a completion signal. The moment a QA gate, an onboarding runbook, a compliance sign-off, or a multi-step handover needs to be enforced consistently across dozens of tasks, native Odoo runs out of road — reviewers eyeball the description, items get silently skipped, and there is no reportable data on what was actually completed versus merely marked done.

This is a build-to-order module that ECOSIRE designs, builds, and installs for your environment. We add a proper project.task.checklist.item model (One2many from project.task, and cascading to subtasks via the task's parent_id/child_ids relationship) with fields for sequence, name, responsible user, done boolean, done date, and optional notes. A stored computed field on the task — driven by @api.depends('checklist_item_ids.is_done') — aggregates progress into a checklist_progress percentage and an item count, so you get a live "7 / 10 done" indicator and a progress bar directly on the task form and kanban card. Checklist templates (an ir.model-backed template + line model) let you define reusable lists once and apply them to any task, or auto-apply them per project or task type via an base.automation automated action on task creation. Security is enforced through ir.model.access.csv for the new models plus record rules that keep checklist visibility aligned with each user's existing project access, so nothing widens your data exposure.

Technically, the build ships as a clean, versioned addon with its own __manifest__.py declaring dependencies on project (and hr only where responsible-user assignment needs it). Views are delivered as XML inheriting the standard task form, list, and kanban views — no core overrides — with an OWL-based checklist widget where interactive tick-and-progress behavior warrants it, degrading gracefully to standard editable list rows otherwise. A QWeb report renders a printable checklist sign-off sheet per task for audit trails, and every checklist field is exposed over the XML-RPC/JSON-RPC API so external systems (field apps, portals, CI pipelines) can read progress or tick items programmatically. We target Odoo 17.0, 18.0, and 19.0, and we build cleanly against Community — calling out explicitly if any requested capability (for example, tying checklist gates to Enterprise-only approvals or field-service flows) depends on Enterprise so you decide before we build.

Delivery is build-to-order: after a short scoping call we confirm the exact models, template rules, and reporting you need, then build on a staging copy of your database, run UAT with you, and deploy with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope, depending on queue and complexity. Pricing starts from $249 (indicative, single-company base scope); multi-company checklist isolation, deep localization, external-system integrations over the API, or migrating large volumes of existing checklist data from spreadsheets or a prior system increases the quoted scope. You receive a firm fixed quote after the scoping call — the from-price is a starting indication, never a final figure.