The problem this app solves

Moving a card to the next stage can make a pipeline appear healthier even when a contact, close date, proposal or next activity is missing. Managers need a way to make stage expectations clear without checking every opportunity manually.

Define readiness requirements for the relevant stage transition. Salespeople see the missing items and corrective guidance, and controlled moves are checked on the server. A permitted manager override stays tied to the opportunity and policy evidence.

Features that support your daily work

• Scoped policies. Match company, team, lead type, source and target stages, priority, revenue, and user group with deterministic precedence.
• Safe evidence checks. Require customer/contact, contact channels, revenue, close date, tags, source, notes, activities, attachments, or a stored CRM field.
• Live readiness. Show percentage, green/amber/red status, missing count, and a next-step summary on CRM forms and Kanban cards.
• One server gate. Protect form, Kanban, bulk, import, RPC/API, and native Mark Won transitions through the same CRM write path.
• Controlled exceptions. Managers can approve a reasoned, expiring, single-use override that is bound to policy and lead evidence revisions.
• Audit and analysis. Immutable transition evidence, blocked/failure queues, a printable exception PDF, and UTF-8 failure-analysis CSV keep decisions reviewable.

A practical example

Illustrative workflow — the available actions depend on your configuration.

A salesperson tries to advance an opportunity before attaching the required proposal. The readiness dialog explains the blocker. After adding the document and satisfying the remaining requirements, the opportunity can move through the native CRM workflow.

How the workflow works

1. A CRM manager creates a source-to-target policy and ordered safe requirements.
2. A salesperson checks an opportunity or attempts the controlled stage move.
3. The dialog or server response groups missing blockers and shows remediation hints.
4. After the evidence is corrected, native CRM moves the opportunity and the module records the decision.
5. If needed, a different manager approves one time-limited override; material changes invalidate it.

Configuration and navigation

• CRM > My Pipeline > Blocked Opportunities
• CRM > My Pipeline > Missing Next Step
• CRM > Configuration > Stage Readiness Policies
• CRM > Reporting > Stage Readiness Analysis
• CRM > Reporting > Readiness Overrides and Frequent Readiness Failures

Reports and exports

The CRM Stage Readiness & Exception PDF shows the opportunity, transition, actor, policy, decision, override token, duration, evidence, and remediation. The manager-only Readiness Failure CSV export filters immutable blocked/override decisions by company and date range. The module does not add XLSX output.

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

Define stage-specific CRM readiness requirements. Review opportunities that need attention before advancing. See readiness status and the next corrective action. Resolve grouped blockers from a clear transition dialog. Analyse stage-readiness decisions and outcomes. Review controlled manager exceptions. Export filtered readiness failures for further analysis.

Compatibility

Version	Odoo 15.0
Editions	Community and Enterprise
Required app	crm
Optional capabilities	sale_crm quotation evidence and Documents categorisation when installed
Deployment	Odoo.sh or private/on-premise hosting
Online	Not compatible with Odoo Online; server-side lifecycle enforcement and immutable audit models require a standard module.

Clear limits

This focused app does not provide an arbitrary Python condition builder, generic BPM engine, multi-department approval suite, electronic signatures, a document management system, automatic quotation generation, message delivery, or a replacement CRM.