Templates

Delivery

Answer “where are we at?” in seconds

Use Template

By Nalvin

Use Template

Description

Nalvin helps you answer status questions about a project or initiative by summarizing what’s shipped, what’s in progress, what’s at risk, and what decisions are needed next. It pulls the minimum set of work items in scope, clusters them into a stakeholder-friendly story, and keeps details traceable to real ticket activity.

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.

Start with the right container

Give Nalvin a project, epic, sprint, or initiative link/key. A tighter scope produces a clearer status story and avoids noisy results.

Ask for risks and asks, not just progress

You can level this up by having Nalvin always include a “Risks” and “Asks” section. This turns updates into decision-making, not reporting.

Prefer themes over ticket IDs

Ticket IDs are useful for follow-up, but stakeholders care about outcomes. Have Nalvin group work by theme (onboarding, performance, billing) instead of listing tickets.

Call out uncertainty explicitly

If data is missing (e.g., no recent activity), Nalvin should say so and propose what to check next. This avoids false confidence in the status.

Reuse the same format every time

Consistency makes updates skimmable. Use a stable structure (Shipped / In progress / Risks / Asks) so teams build trust in the output.

Start with the right container

Give Nalvin a project, epic, sprint, or initiative link/key. A tighter scope produces a clearer status story and avoids noisy results.

Ask for risks and asks, not just progress

You can level this up by having Nalvin always include a “Risks” and “Asks” section. This turns updates into decision-making, not reporting.

Prefer themes over ticket IDs

Ticket IDs are useful for follow-up, but stakeholders care about outcomes. Have Nalvin group work by theme (onboarding, performance, billing) instead of listing tickets.

Call out uncertainty explicitly

If data is missing (e.g., no recent activity), Nalvin should say so and propose what to check next. This avoids false confidence in the status.

Reuse the same format every time

Consistency makes updates skimmable. Use a stable structure (Shipped / In progress / Risks / Asks) so teams build trust in the output.