TQ-07

Invalid AC Format

Text Quality

Default severity: high
ProcessMetrics

What it detects

AC present but not structured (bullets, GWT, numbered, checkbox); tests; catalogue.

Detection formula

No published identification formula is available yet for this rule.

Examples in practice

  • A team shows ac present but not structured (bullets, gwt, numbered, checkbox); tests; catalogue during analysis.
  • Example signal: AC present but not structured (bullets, GWT, numbered, checkbox); tests; catalogue.

Suggested response

Review the observation details with the team and agree one concrete next step to reduce recurrence.

Coaching playbook

Symptom

The "Invalid AC Format" signal shows a repeatable delivery anti-pattern on the cited issues.

Why it matters

When "Invalid AC Format" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.

What you can achieve

Review the observation details with the team and agree one concrete next step to reduce recurrence.

Facilitation questions

  • What system change would stop "Invalid AC Format" from firing again?
  • What do the cited issues have in common — same root cause or same workaround?
  • Who owns the two-week experiment and how will we verify on the next import?

Run this rule against your own tracker data with Flow Analyzer.

Product tourSign in
TQ-07: Invalid AC Format — FlowAnalyzer