The prompt
Score 10 of 10, Excellent
Use it when You need inspectors to check a product or service the same way every time, with limits taken from the spec and a clear next step when something fails.
- {{item}}
- {{inspectors}}
- {{inspection_point}}
- {{specification}}
- {{sampling}}
- {{tools}}
- {{nonconformance_process}}
- {{known_issues}}
Full prompt and why it works
Prompt
Build a quality inspection checklist for {{item}}, for {{inspectors}} to use at {{inspection_point}}, so that two inspectors checking the same unit reach the same result and every reject has a clear next step. The specification, drawing or service standard, with its revision: """ {{specification}} """ Our sampling plan, or how many we check: {{sampling}} Tools and gauges available: {{tools}} What happens to a failed unit or lot today: {{nonconformance_process}} Known problem areas or customer complaints to watch for: {{known_issues}} Produce: 1. A header block with fields for item, specification revision, lot or order, quantity, inspector, date and time. 2. The checklist as a table with the columns #, Characteristic, Requirement, Method or tool, Sample size and frequency, Class (critical, major or minor), Result. Put critical checks first, up to 30 rows. 3. On fail: numbered steps from our process (stop, tag and separate, record, who to notify, what can be released and by whom). 4. A sign-off line for the inspector and for whoever approves a release. Each requirement must be a measurable limit taken from the specification, for example "Length 120 mm, plus or minus 0.5 mm, measured with calipers at both ends", or for a service, "Every wastebasket emptied and relined; any left full is a fail". That example shows the form only. A good checklist leaves nothing to taste: an appearance check names the reference sample, photo or defect limit it is judged against. Use only limits, tolerances and sampling from the material. Do not invent a tolerance, a sample size or an acceptance level, and do not add checks the specification does not support, except those from the known problem areas, which should be marked "(from complaints)". If the specification gives a target without a tolerance, or a requirement is vague (such as "good finish"), write [CHECK: limit needed] in the Requirement column and list each one after the table for the quality lead. If no sampling plan is given, write "Sample size to be set by the quality lead" instead of choosing one.
Variables
- {{item}}
- The product, part or service being inspected, for example "the 2-liter bottle label" or "hotel room turnover".
- {{inspectors}}
- Who will use the checklist, for example "line inspectors on each shift".
- {{inspection_point}}
- Where in the process the check happens, for example "incoming goods", "end of line" or "before the guest checks in".
- {{specification}}
- The specification, drawing notes or service standard, with limits and tolerances, and its revision.
- {{sampling}}
- How many you check and how often, for example "5 per lot of 500", or "no plan yet".
- {{tools}}
- The gauges, test equipment or reference samples inspectors have.
- {{nonconformance_process}}
- What happens now when something fails: who is told, how it is tagged, who can release it.
- {{known_issues}}
- Problems seen before or raised by customers, or "none".
Why it works
- What good looks like. Every requirement has to be a measurable limit from the specification, and appearance checks need a reference to judge against, which is what makes two inspectors agree.
- What to avoid. No invented tolerances or sample sizes, because a made-up limit on an inspection sheet quietly becomes the specification.
- If unsure. A target without a tolerance gets a [CHECK: limit needed] note for the quality lead instead of a guessed range.