✅ How to QC an Output

Who this is for: Anyone asked to check a new Output (document-generating template). Goal: Run the Output 10–20 times with real/sensible inputs and log any snags on the QC Monday board.

1) Before you start (2 mins)

• Open the Output in the platform.
• Gather a few real or sample files (briefs, results/metrics, visuals, T&Cs, market lists).
• Open the QC Monday board in another tab.

2) What “good” looks like

• Client-ready document: clear headings (H2/H3), bullets, UK English.
• Uses only uploaded materials; if info is missing, shows a clear placeholder (e.g., [MISSING: …]) and a one-line “What I still need.”
• On file conflicts, prefers the newest, most specific source and notes it briefly.
• Tables (e.g., markets, KPIs) are accurate and tidy; images/screenshots are referenced clearly (e.g., “Figure 1”).
• Short Sources/Provenance list if the Output includes one.

3) Run your tests (target: 10–20 uses)

Keep each run short (1–4 minutes). Mix these:

A. Complete inputs (happy path)

• Provide all expected files. Check structure, tone, tables, KPI formatting (e.g., +27% uplift).

B. Missing info

• Withhold a key input (e.g., results or markets list). Confirm [MISSING: …] appears with a helpful “What I still need.”

C. Conflicting files

• Upload two versions of the same file (dated). Confirm it uses the newest and briefly flags the choice.

D. Multi-market / multi-language (if relevant)

• Provide 2–3 markets with differences (mechanics, prizes, T&Cs). Check the comparison table reflects this; language tags where applicable.

E. Visuals & links

• Add an image/screenshot. Check it’s referenced (e.g., “Figure 1”).
• If none supplied, Output should leave a clear placeholder and (optionally) search suggestions.

F. Revision loop

• Change one input (e.g., updated results file). Ask it to refresh just that section. Confirm it updates cleanly.

4) Log snags on the QC Monday board

Use the same columns:

• Name — short title of the issue
• Link to Output/Chat — paste the Output chat URL
• What task were you trying to do? — 1–2 lines (e.g., “Generate case study with 3 markets”)
• What happened? — actual behaviour (copy error, missing table, wrong tag)
• What was the expectation? (What should have happened) — concise expected outcome
• Severity — Low / Medium / High / Critical
• Screenshots (Optional) — attach or link
• Status (For Wooshii use) — leave blank

Severity guide

• Critical: document incomplete/structurally broken; can’t deliver to client.
• High: key section wrong/missing across runs.
• Medium: formatting/logic issue with workaround.
• Low: copy polish or small layout.

Example snag (Output)

• Name: Markets table ignores prize differences
• Link to Output/Chat: https://…/assist/outputs/xyz789
• What task were you trying to do? Generate a multi-market document (UK/DE/FR) where prizes differ.
• What happened? Table shows identical prizes for all markets.
• Expectation: Table lists correct prize differences and any T&Cs notes per market.
• Severity: High
• Screenshots: (attached)

5) Finishing up

• If you hit no snags, let us know you're happy with the quality of the output and that QC is complete.
• Unsure if something is a snag? Log it anyway—we’ll triage severity.
• Need help? Reply to the rollout email with the Output name and your board link.