Update Quality

Tickr evaluates update quality and gives playful feedback on vague progress notes. Max plan only.

ℹ️ Max plan feature

Update quality evaluation requires the Max plan. On other plans, all updates are accepted without evaluation.

When you provide a task update (via slash command, modal, @mention, or nudge response), Tickr evaluates whether the update is meaningful. Vague updates get playful pushback — not to punish, but to help your team communicate better.

What makes a good update

A quality update includes at least one of:

What was specifically accomplished since last update
Current progress (percentage, milestone, phase)
What you're doing next
Any blockers or risks
Estimated remaining time

Good example:

Finished the auth module and unit tests. Starting integration tests tomorrow. On track for Wednesday delivery.

What triggers pushback

Vague or low-effort updates like:

"Working on it"
"Making progress"
"Same as before"
"Still going"

What happens

If your update is evaluated as low quality, Tickr posts a playful follow-up:

🤔 I recorded your update, but it's a bit vague.
Could you share what specifically changed since last time?

💡 Nudge, not a blocker

If you insist that's all you have, Tickr accepts it gracefully and moves on. Quality feedback is a nudge, not a gate — your update is always recorded regardless.

Quality scores

Every update gets a quality score stored on the record:

Score	Meaning
Good (1)	Specific, actionable update
Poor (0)	Vague, no concrete details

These scores feed into the AI Reports:

Lowlights report includes tasks where updates were flagged as vague ([vague] tag)
This helps identify patterns — e.g., a task that only gets vague updates may need attention

Where quality is evaluated

Updates are evaluated regardless of how they're submitted:

/tickr update command with a note
Update modal from task card button
@mention with progress update
Reply to a nudge message (see Auto-Close)
Thread monitoring (see Thread Monitoring)