Learn Mokapen

Checklist

The checklist breaks work down into micro-actions you can tick off inside an entity record. Each item has a title, completed/not completed status, and customizable order. At the top, badges and a progress bar show how many actions are done out of the total (e.g. 3/7) — immediate feedback for anyone opening tasks, tickets, deals, or contact records without having to read the full description.

Role in the CRM

The checklist is suited to repeatable procedures and operational steps, not to replacing tasks or projects:

• Task / project: execution steps («Brief approved», «Staging deploy», «Client email»).
• Ticket: L1 intake or resolution procedure.
• Deal: internal commercial milestones before closing.
• Contact / company: client onboarding, document collection, profile verification.

For structured work with owners, due dates, and reports use tasks; for quick sub-steps on the same record use the checklist.

Where to find it

Checklist tab or card on:

• Tasks and Projects — Tasks guide, Projects guide
• Contacts and Companies — Contacts guide
• Deals (Sales)
• Tickets — Tickets guide

The counter on the tab (modal) or card title (full page) reflects updated progress.

Adding an action

1. Open the record → Checklist tab/card.
2. Click Add action.
3. Type the title in the text field.
4. Press Enter to add another row, or save the record.

Empty rows cannot be saved: complete the text of the current row before adding a new one.

Complete, reorder, and delete

• Complete: tick the checkbox on the left. The text turns green and the progress bar advances.
• Reorder: drag the bars icon (⋮⋮) to move the action — useful when the procedure has a mandatory order.
• Delete: trash icon on the right of the row.

Checklist changes require saving the record when the Save footer appears (modal).

Progress bar

Badge (done/total) and green bar at the top of the tab. Ideal in stand-ups or reviews: «ticket #4521 is at 4/6 steps». On deals and contacts it signals onboarding progress without opening notes or comments.

Checklist and Task ↔ Project conversion

From the task Options menu: Convert to project — checklist items become tasks of the new project (structured work with owners and dates). From a project: Convert to task — project tasks become checklist items in a single container task.

Use conversion when steps stay «internal» to the record (checklist) vs when you need distinct assignees and due dates (project tasks).

Cloning

When cloning a task, project, contact, ticket, or deal you can include the checklist in the copy (dedicated checkbox in the Clone modal). Useful for templates: a «New SaaS client» deal with a pre-set sales checklist.

Recommended processes

• Contact onboarding: checklist on the company with «Contract signed», «Portal access», «Kick-off call» — progress visible to CS.
• Ticket closure: L1 checklist before escalating («Service restart», «Logs verified», «Client notified»).
• Deal in negotiation: internal steps («Legal ok», «Pricing approved») separate from the pipeline stage.
• Definition of Done: identical checklist on cloned task templates to standardize delivery.

Combine the checklist with Connections (client/deal context), Labels (classification), and Updates (change history) for complete CRM procedures.