Author: AILesson6 min setupTested with:ChatGPTReviewed: 2026-08-28
Quick answer
Organize symptoms, conditions, history, impact, and safe observations without inventing a diagnosis. Provide: Equipment and observed problem, Evidence and safe steps already taken, Impact, safety, and service logistics. Expected result: A technician-ready fault brief with reproduction clues, evidence, access details, and safety flags.
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Turn the supplied repair information into a concise service brief for a technician or provider.
Item, location, model, symptoms, onset, frequency, conditions, expected behavior, and current state:
[problem]
Photos, recordings, readings, codes, changes, prior repairs, safe checks, results, and untried steps:
[history]
Impact, warning signs, shutdown status, risk, access, contact, warranty, and desired next step:
[service]
Describe observable behavior and sequence before suggesting categories of possible investigation. Never claim a root cause or tell the user to open, reset, energize, move, smell, touch, or test equipment when that action is not explicitly known to be safe. Preserve exact codes, units, intermittent conditions, negative observations, and the difference between not observed and checked absent. If supplied facts indicate possible immediate danger, lead with the stated shutdown or emergency action and recommend following the applicable provider or emergency instructions without fabricating a procedure. Return: one-line issue summary; equipment and location; expected versus observed; timeline and trigger pattern; impact and safety status; steps and results; evidence inventory; access and warranty details; technician questions; missing information; and a copy-ready service request.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Equipment and observed problem
Built-in dishwasher in apartment kitchen, brand Lumen, model unknown. Since 24 August, three of four cycles stopped about 12–18 minutes after starting and displayed E07. A short rinse completed once. Expected: full cycle finishes and drains. Observed after stop: standing water below the filter level; door remained locked for about five minutes, then opened. Current state: switched off at the wall and not being used.
Evidence and safe steps already taken
Photo of E07 and 15-second video of sound before stop. No visible water outside the machine. Sink drains normally. Filter was cleaned on 20 August before the problem; no parts removed since. Power cycling was not attempted because the appliance is under landlord warranty. No prior repair known.
Impact, safety, and service logistics
Dishes cannot be washed by machine; hand washing available. No smoke, burning smell, sparks, heat, or external leak observed. Two adults, no children. Ask landlord's appliance contractor to inspect. Access Wednesday 13:00–17:00 or Friday 09:00–12:00 with confirmation. Warranty details held by landlord. Email preferred.
Example output
Issue summary: Lumen built-in dishwasher intermittently stops 12–18 minutes into a cycle with E07 and leaves water below filter level.
Expected versus observed: a full cycle should finish and drain; three of four cycles since August 24 stopped with E07. One short rinse completed. After a stop, the door unlocked after about five minutes. Current status: wall power is off and the machine is not in use. Impact is loss of machine washing with hand washing available. No smoke, burning smell, sparks, heat, or external leak was observed; this records observations, not a safety diagnosis.
Completed checks/evidence: sink drains normally; no visible external water; filter was cleaned August 20 before onset. E07 photo and pre-stop sound video are available. No power cycle or disassembly was attempted. Model, warranty terms, and repair history are missing. Technician questions: what does E07 mean for this exact model, should standing water be removed by the technician, and what identifying label can be checked safely during the visit?
Service request: Please arrange an appliance-contractor inspection for the built-in Lumen dishwasher. It has stopped with E07 on three of four cycles since August 24. It is switched off and unused. Photos and video are available. Access is possible Wednesday 13:00–17:00 or Friday 09:00–12:00 after confirmation; please advise the appointment and any provider-approved precautions before the visit.
Why this works
1
Observable symptoms and trigger patterns give technicians diagnostic value without a premature cause claim.
2
Separating safe completed checks from untried actions prevents a generated brief from overstating troubleshooting.
Check the result
Are symptom, timing, trigger, code, and current state recorded exactly?
Are diagnosis, safety conclusions, and unperformed steps clearly absent or qualified?
Can the provider tell what evidence exists, what access is possible, and what response is requested?
Use it with confidence
Frequently asked questions
Practical answers about when to use this recipe, what to provide, and where human review still matters
What should I prepare before using “Turn a repair problem into a service brief”?
For “Turn a repair problem into a service brief,” prepare Equipment and observed problem, Evidence and safe steps already taken, and Impact, safety, and service logistics. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Turn a repair problem into a service brief” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A technician-ready fault brief with reproduction clues, evidence, access details, and safety flags—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Turn a repair problem into a service brief”?
The published test record for “Turn a repair problem into a service brief” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT