How should you prompt AI to summarize a quality-inspection report for management

The Prompt

Summarize this quality-inspection report for a management audience.

Raw report: [paste inspection data/notes]
Format as: overall pass/fail rate, top 2-3 recurring defect categories, and any trend versus the prior period (improving/worsening/flat).
Keep it to a half-page — management needs the pattern, not every individual data point.

Why This Prompt Works

Raw inspection data buried in individual line items obscures the pattern that actually matters for a management decision — surfacing the top recurring defect categories and the trend direction is what turns a data dump into something a manager can act on (investigate a specific line, adjust a specific supplier) rather than just file.

How to Customize It

Supply the actual prior-period numbers so the model can state a real trend direction rather than only a current snapshot — trend matters more than a single period’s absolute numbers for most management decisions. If one defect category traces to a specific line, shift, or supplier, name it directly so the summary points toward an investigation rather than just a pattern.

Common Mistakes to Avoid

Don’t let the summary bury the pass/fail headline number under defect-category detail — lead with the top-line number, then the pattern behind it. Also avoid rounding pass rates in a way that obscures a small but real decline; a shift from 98% to 96% is worth surfacing even though both sound high.

Bottom Line

A useful quality-report summary leads with the pass/fail headline, surfaces the recurring defect pattern, and states the trend — that’s what turns inspection data into a management decision, not just a record.