Customizing Pipeline Stages

Policy Stack includes five default pipeline stages, but your process may not map exactly to them. You can rename stages, add new ones, reorder them, assign colors, and set checklist blueprints so each stage carries the right default work.

Opening Stage Settings

Go to Settings → Pipeline → Edit Stages.

Renaming a Stage

Click any stage name in the list and type the new name. Renaming takes effect immediately across the entire pipeline — existing deals in that stage reflect the new name as soon as you save.

Adding a Stage

1. Scroll to the bottom of the stage list.
2. Click "Add Stage."
3. Type a name for the new stage.
4. Drag it to the desired position in the order (or use the up/down arrows).
5. Optionally assign a color.
6. Click "Save."

The new stage appears as an empty column on your pipeline board immediately.

Common custom stages advisors add:

• Nurture — Prospects interested but not ready yet; parked for future follow-up
• Underwriting Hold — Separate from the standard Application stage when underwriting delays are common
• Policy Delivered — Between Application and Active, for policies issued but not yet in-force
• Re-Engagement — Reopened lost deals or cold prospects coming back

Reordering Stages

Drag any stage row up or down in the Settings → Pipeline list. The pipeline board updates to reflect the new order immediately.

Assigning Colors

Each stage has a color swatch you can customize. Colors appear as a left border on deal cards in that stage and as the column header accent on the Kanban board. Use colors to create quick visual categories — for example, all pre-application stages in one color family, post-application in another.

Setting Checklist Blueprints

Open a stage in Settings → Pipeline and expand its checklist section. Add the default checklist items that every deal in that stage should start with, then save.

Blueprints affect inheritance:

• New deals created in that stage start with the stage checklist.
• Deals moved into that stage inherit the current checklist blueprint for the new stage.
• Edits on an individual deal stay local to that deal.

Use short, concrete items. For example, "Confirm insured", "Collect illustration", "Review owner/payor", or "Send onboarding invite". The checklist is operational context, not a client-facing recommendation.

Deleting a Stage

You cannot delete a stage that has deals in it. To delete:

1. Move all deals out of the stage (move them to another stage or mark them Won/Lost).
2. Return to Settings → Pipeline → Edit Stages.
3. Click the delete icon next to the now-empty stage.
4. Confirm.

The stage is removed from the board. Its name continues to appear in historical deal activity logs.

Impact on Existing Deals

| Change | Effect on Existing Deals | |--------|--------------------------| | Rename stage | Deals in that stage immediately show the new name | | Add stage | No effect — no deals are in the new stage yet | | Reorder stages | No effect — deals stay in their current stage | | Delete stage | Requires emptying the stage first; historical references preserved | | Change color | Cosmetic only — no data impact | | Change checklist blueprint | Future inherited checklist state updates when deals enter that stage; existing deal-level edits stay on their deal |