Templates

Delivery

Spot stalled work before it slips

Use Template

By Nalvin

Use Template

Description

Nalvin helps you prevent delivery drift by detecting work that has stopped moving and summarizing why it’s at risk. It scans current in-progress items, flags tickets with low activity or unclear next steps, and turns the findings into a short list you can act on immediately—without requiring you to manually inspect every board.

Supported Integrations

Templates are flexible by default. Nalvin automatically picks the right integrations based on what you’ve connected.

Asana

ClickUp

Monday

Trello

Shortcut

Linear

Microsoft Teams

Jira

Slack

How to best use this template

Below are a few tips & tricks from the Nalvin team to get the most out of this template.

Pick a clear “stuck” threshold

Stuck could mean “no updates in 7 days” or “in progress for 14 days”. Setting the threshold helps Nalvin focus on the items most likely to slip.

Separate blocked vs unclear

Some work is blocked by dependencies; other work is unclear or missing acceptance criteria. Ask Nalvin to categorize these differently so you know what kind of intervention is needed.

Look for scope creep signals

You can level this up by asking Nalvin to flag tickets where comments add new requirements. This helps you catch creep early and keep scope intentional.

Use a lightweight escalation path

If an item is stuck, decide what happens next (ping owner, escalate to lead, split scope). Nalvin can suggest the next step, but you keep the final call.

Turn findings into a short agenda

Use the output as the agenda for a quick unblock sync. Keeping the list short makes it more likely the team actually resolves the issues.

Pick a clear “stuck” threshold

Stuck could mean “no updates in 7 days” or “in progress for 14 days”. Setting the threshold helps Nalvin focus on the items most likely to slip.

Separate blocked vs unclear

Some work is blocked by dependencies; other work is unclear or missing acceptance criteria. Ask Nalvin to categorize these differently so you know what kind of intervention is needed.

Look for scope creep signals

You can level this up by asking Nalvin to flag tickets where comments add new requirements. This helps you catch creep early and keep scope intentional.

Use a lightweight escalation path

If an item is stuck, decide what happens next (ping owner, escalate to lead, split scope). Nalvin can suggest the next step, but you keep the final call.

Turn findings into a short agenda

Use the output as the agenda for a quick unblock sync. Keeping the list short makes it more likely the team actually resolves the issues.