When a checklist policy is set to Workflow Gate on the Sales Order Confirm event, Odoo refuses to confirm the order until all required checklist items are completed. This enforcement runs at the server level - no UI tricks, no workarounds.

• Gate fires on every action_confirm call, including API calls
• Error message names the blocking checklist and remaining required item count
• Gate event key sale.order.confirm registered automatically on install

Create reusable checklist templates targeting any Odoo model - Sales Orders, Contacts, Manufacturing Orders, or any custom model. Each template holds an ordered list of items and one or more policies that control when and how the checklist is applied.

• Target any non-transient Odoo model from a single template manager
• Progress policy: Required Items only or All Items
• Starter "Sales Order Readiness" template included out of the box

A compact launcher box appears in the bottom-right dock of every supported form view — even when the drawer is closed, the current checklist state is instantly visible without opening anything. The button shows a live completion badge (e.g. "1/3"), status pills for blocking and overdue items, and a Manual indicator if manual templates are available to start.

• Stat-button style: shows required done/total count at a glance
• Danger pill when a gate checklist is blocking confirmation
• Warning pill for overdue items — no need to open the drawer to spot problems

An OWL-powered side drawer appears on every supported form view - users never navigate away from the record to complete a checklist. The launcher button shows a live badge with completion %, blocking count, and overdue count so the signoff state is always visible at a glance.

• Live badge: completion %, blocking, and overdue pills updated in real time
• Grouped item sections: Pending, Done, Skipped - collapsible
• Start new manual checklists from the drawer without leaving the order

Each template can have multiple policies - each policy independently controls creation mode (Manual or Automatic) and enforcement mode (Advisory or Workflow Gate). A domain filter scopes which records the policy matches, so you can gate only high-value orders or specific customer segments.

• Auto creation: checklist starts when a matching order is opened or created
• Domain builder filters by any field on the sale order model
• Multiple gate events per policy - assign exactly which Odoo actions to block

Each template item can be pre-configured with an assignee type - the current user, the record's responsible user, or a specific user field on the target model. Deadlines can be set as a fixed offset from checklist start or derived from a date field on the record.

• Assignee types: None, Current User, Record Responsible, Specific Field User
• Deadline modes: None, Days After Checklist Start, From Record Date Field
• "Assign to me" button for unassigned items directly inside the drawer

Template items can require an execution note - a free-text explanation the assignee must write before marking the item done. Items can also require one or more evidence attachments (proposals, approval emails, screenshots) that remain permanently linked to the checklist item.

• Note required: item cannot be completed without a non-empty note
• Evidence required: at least one attached file must exist before completion
• File uploads done directly inside the drawer - no page navigation needed

Every checklist instance maintains a live completion percentage, required done/total counts, overdue item count, and a blocking flag. The drawer's summary card surfaces next-due item, next assignee, and available manual starts so managers always see the team's signoff state.

• Completion % computed on required-only or all items - configurable per template
• Overdue count highlights items past their deadline in real time
• Blocking badge turns red on the launcher when a gate checklist is incomplete

Every meaningful action - checklist creation, item completion, reassignment, note update, evidence upload, gate block - writes an immutable event record with actor, timestamp, old value, and new value. These events cannot be edited or deleted, making the trail a trustworthy compliance artifact.

• 11 event types covering every state change including gate-blocked
• Actor recorded on every event, even server-triggered ones
• Auditor role can read all trails without any management rights

Three access levels ship out of the box: User (complete items), Manager (configure templates and policies), and Auditor (read-only trail access). Assigned checklist items automatically create Odoo activities, and company-scoped record rules ensure strict data isolation in multi-company setups.

• Activities sync after every item state change - completed items clear their activity
• Company-scoped rules on templates, policies, instances, items, and events
• Only the assigned user or a Manager can update a checklist item