CRM Check List and Approval Process is an Odoo app, which provides a checklist for each pipeline stage to control the requirements' fulfillment and to make sure that each action is fully approved by responsible users. Choose stages to assign various checklists and prepare any number of checkpoints for each stage. Check the fulfillment progress on opportunities kanban and form views. 

To move a CRM lead forward in your funnel, its checklist should be fully confirmed. Configure specific stages to be mandatory, so users would not be able to skip those. Then, the stages with the 'Forbid skipping this stage' option will be always visited and their checklists will be fulfilled.

Configure the CRM pipeline to forbid moving opportunities back. To that goal, turn on the option 'Forbid regression to this stage' for particular stages. For example, to make sure that no opportunities that were moved forward become 'New' again.

Mark some stages as 'No need for checklist', to avoid moving restrictions (e.g. 'Canceled').

Checklist actions are saved in history. If an opportunity is moved between stages, already-done check items would be recovered. Turn on the setting 'not saved' to avoid that behavior for specific approval points. 

The app lets assign security groups for each checklist point and only users from those groups would be able to confirm a related item. You can also assign a person to be a 'CRM Checklists Super User'.

Checklists are assigned per each opportunity stage and sales team, if necessary. For instance, actions for the 'new' and 'proposition' stages might be different. You can prepare any number of checkpoints for each CRM stage.

You can manage checklists in two interfaces: in the stage wizard and from the checklist menu. 

To open a stage wizard click on the gear on the right side of a stage's name. There you will see all available checkpoints for the stage. Each Lead will require the completion of all the checkpoints in order to move on to the next stage. From here you can add checklist points for the current stage, change their order, delete them, and assign responsible people.

To add a checkpoint from the stage wizard:

1. Start creating or editing a pipeline stage

2. Click 'Add a line'

3. Write the checkpoint title

4. Set the order

5. Choose one or several teams, so the checkpoint would be assigned only to the related to them leads/opportunities

6. Choose user groups, that will be able to mark the checkpoint as done

7. Click 'Not saved', if it is required to mark the checklist point done every time it gets to the stage

8. Optionally, click 'No need for checklist,' if the stage doesn't require completing a checklist (see Approving Process)

9. Optionally, click 'Forbid skipping this stage', to make sure that the stage will be always visited and it's checklists will be fulfilled  (see Approving Process)

10. Optionally, click 'Forbid regression to this stage' to forbid moving the opportunit back to the stage (see Approving Process).

In the checklist menu, you can see and edit the checklist points for all available stages.

How to add a checklist point from the separate menu:

1. Go to Configuration > Checklist

2. Click 'New'

3. Write the checkpoint title

4. Select a CRM stage to which this checklist point relates to

5. Choose one or several teams, so the checkpoint would be assigned only to the related to them leads/opportunities

6. Choose user groups, that will be able to mark the checkpoint as done

7. Click 'Not saved', if it is required to mark the checklist point done every time it gets to the stage

8. Add some notes to the checkpoint. The note will be shown as a user hovers over the checklist point.

A checklist represents a set of checkpoints that defines what should be done at this particular stage to move the lead forward. A checklist is formed automatically as the lead is created or put to the next stage according to the stage's checklist settings. 

Each checkpoint is a certain statement that is assumed to be confirmed/completed at a certain CRM stage, e.g. 'Contract is signed' or 'Approved by financial department'. The responsible for the checkpoint completion may be all employees or particular user groups.

In case, one or several sales team is defined for certain checklist points, they will be added only to the related to those sales teams leads/opportunities. This way, different sales teams may have a different set of checklist points.

Moving a lead forward implies putting a lead to the stage with a greater sequence. The stage sequence is its order on the pipeline. Thus, the transition from 'New' to 'Considered' is considered progress ('moving forward'), while from 'Qualified' to 'New' - is not ('moving back').

As you move the lead forward, the app would consider whether the stage's checklist is fully complete. If not - a user would be shown a warning. Otherwise, this lead would get to the target stage, and the checklist would be updated to checkpoints linked with this new stage. 

A lead/opportunity with a completed checklist can be moved to any further stage. For example, you can move an opportunity from the stage 'New' to the stage 'Done', skipping the stage 'Proposition'. Optionally, configure specific stages to be required, so users would not be able to skip those. For that, as you edit a stage, tick the option 'Forbid skipping this stage'. This way, you can make sure that the stages will be always visited and their checklists will be fulfilled prior to moving forward to one of the next stages.

The setting does not influence the option 'No need for checklist'. This way, you will still be able to move the lead/opportunity to the stage, that doesn't require completing a checklist, even if it is placed after the stage that is forbidden to skip, for example, it might be useful, when you move an opportunity to the 'Lost' stage as it should be possible to do it anytime, regardless of the current stage.

The app assumes that users can move a lead to one of the previous stages without the need to complete the checklist for that. For example, a customer asks for other products or services, so this lead is returned from the stage 'Proposition' to the stage 'New'. In such a case, a user would not have to approve 'Advance payment has arrived', since it is senseless.

However, it is possible, to forbid moving a lead/opportunity back to the previous stage. It might be especially useful, when it is forbidden to introduce the changes. For example, when all the details are confirmed with the client and the contract is signed. So, no further changes can be made, and a new opportunity must be created instead. For that, as you edit a stage to which it should be forbidden to return, tick the option 'Forbid regression to this stage'. This way, you can make sure, that no opportunity will return to this stage, after leaving it.

Certain stages might be also marked as 'No need for checklist'. This setting indicates that even if a user moves a lead to this stage, no checkpoints should be approved. For example, you can let employees move leads to the 'Cancelled' stage without confirming that the 'contract is signed'.

If a user tries to move any opportunity further without completing all the checklist points, such a transition would be blocked and the warning would appear. Thus, to move a CRM lead forward in your funnel, its checklist should be fully confirmed. The exception to the rule is the CRM Checklist Super User, which can apply any changes (see User Roles).

If a person tries to mark a checkpoint to which he or she has no access, then the warning 'Access Error' would appear and such changes cannot be saved (see User Roles). The warning also states which checklist point cannot be marked.

You can see the history of approval on the lead form. There you can find out who and when marked a particular checklist point, did or reset any of such approvals. In such a way it is always possible to control user actions and, if needed, ask for an explanation. 

The app lets define statements that should be checked regularly and statements that might be approved only once.

By default, if an opportunity is moved, previously done check items are recovered from the history. For instance, entering a client's details should be done only once disregarding how many times a lead is on the stage 'New'.

Simultaneously, a client's solvency has to be checked regularly, since it might be changed in the meanwhile. To make a checkpoint regularly approved, turn on the setting 'Not saved' by particular checklist points, while editing a pipeline stage.

For example, two checkpoints were marked as done on the stage 'Won'. One of those was configured not to be saved. The lead was moved back for one of the previous stages, and then returned back to 'Won'. Out of two completed checkpoints, only one would be restored and the shown progress would be 50%. The other, that was 'Not saved' should be marked as done again.

Access to mark the checkpoints can be given to various user groups.

To choose the responsible-for-a-checkpoint groups of users:

1. Start editing a stage or a checkpoint

2. In the field 'User groups' choose all user groups that will have a right to mark the point done

Each point can be available for different user groups. If the field is left empty, then any user with access to the lead can approve that checkpoint.

Here are some examples of the assigned-per-checkpoint user groups:

1. 'Confirm the stock availability'  User groups: Inventory/Administrator

2. 'Check the details'  User groups: Sales/User: all documents and Sales/User: Own Documents only

3. 'Confirm the payment'  User groups: Accountant

4. 'Sign the contract'  User groups: Sales/Administrator

5. 'Feedback is requested'  User groups: empty

If the checklist is not done, a user can't move the lead forward: the warning would appear. Simultaneously, to approve a certain checkpoint, a user should have the right to that item. In such a way, you may configure the multi-role approval CRM process, when different groups are responsible for different actions.

Simultaneously, there is the special role 'CRM Checklists Super User' which allows overcoming the restrictions. In particular, such users would be able:

1. To confirm any checkpoints disregarding defined security groups

2. To move any opportunity further without fulfilling checklists

To assign a user the 'CRM Checklists Super User':

1. Go to General Settings > Manage users

2. Choose a user

3. Scroll down to the section 'Sales' and find the field 'CRM Checklist'

4. Choose the option 'CRM Checklists Super User'.