What to Include in Your Standup

Strova's AI captures five areas from your daily update. You don't need to follow a rigid format — write naturally and the AI will extract and structure the information — but understanding what each area covers helps you write better updates.

The Five Areas

1. Yesterday's Work

What did you complete or make meaningful progress on since your last update?

Good examples:

• "Finished the auth middleware refactor and merged PR #142"
• "Reviewed 3 PRs, fixed the pagination bug in the reports page"
• "Completed the API design doc for the notifications service"

What the AI looks for: Concrete outputs — merged PRs, completed tasks, finished reviews, shipped features.

2. Today's Plan

What are you working on today?

Good examples:

• "Writing unit tests for the auth module, then starting on the email queue"
• "Syncing with design on the onboarding flow at 2pm, then implementing feedback"

What the AI looks for: Specific tasks with enough detail to assess planning quality. Vague entries like "continuing work" score lower on the Planning Quality KPI.

3. Blockers

Is anything slowing you down or preventing you from completing your work?

Good examples:

• "Waiting on DB access credentials from ops — blocked on the migration task"
• "The third-party API keeps rate-limiting us in staging, need to investigate"
• "No blockers today"

What the AI looks for: Clear description of the impediment and ideally what's needed to unblock. If you have no blockers, say so — it still contributes positively to your Blocker Communication score.

4. Discussions & Meetings

Any sync calls, decisions made, or discussions worth noting?

Good examples:

• "Team planning call at 10am — agreed to push the v2 release to next sprint"
• "Quick sync with PM about scope changes to the onboarding feature"

This field is optional. If you had no meetings, you can skip it or say "none."

5. PR Reviews

Pull requests you reviewed, or PRs of yours that need reviewing?

Good examples:

• "Reviewed: PR #138 (approved), PR #141 (requested changes)"
• "My PR #143 needs a review — link in Slack"

This field is also optional. Skip it if it doesn't apply to your role or your day.

Tips for Better Updates

• Be specific. "Fixed bug in checkout flow" scores better than "fixed a bug."
• Name your PRs and tickets. The AI can reference them in your weekly report.
• Always address blockers. Even "no blockers" is valuable data.
• Don't worry about formatting. Write in plain sentences, bullet points, or shorthand — the AI handles structuring.

What Happens to Your Update

Once you post, Strova's AI analyzes the content and assigns KPI scores across five dimensions. Your update also appears on your team's DSM Board for teammates and leads to review.