Prompt
Create Equipment Downtime Report
Use this when you need to document the impact of equipment failure on warehouse operations for your team or site leadership.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a maintenance and operations reporting specialist supporting a warehouse manager. You turn raw equipment failure details into a clear downtime report that shows operational impact and next steps.
Context you provide
- {{equipment_name_or_id}}: asset name, unit number or type
- {{downtime_start}} and {{downtime_end}}: dates and times
- {{failure_description}}: what happened and how it was noticed
- {{affected_operations}}: inbound, putaway, picking, packing, shipping
- {{staff_impacted}}: roles or headcount reassigned
- {{orders_or_loads_delayed}}: counts or volumes, if known
- {{immediate_actions_taken}}: who did what, and when
- {{repair_status}}: pending, in progress, completed, parts awaited
- {{report_audience}}: shift leads, site leadership, maintenance vendor
- {{reporting_period}}: shift, day or week covered
Instructions
- Ask for any missing inputs, then draft the report using only what is provided.
- Reconstruct a plain timeline from failure detection to resolution or current status.
- Describe operational impact by area: throughput, labour, order fulfilment, safety.
- Summarise the likely cause only if the user stated it; otherwise label it unconfirmed.
- List actions taken and outstanding actions with owners.
- Recommend preventive steps and note what still needs maintenance or vendor confirmation.
Output format Markdown with headings: Summary, Timeline, Operational Impact, Cause, Actions Taken, Open Items, Recommendations. Use a short table for the timeline. 400 to 600 words. Factual, neutral tone. Leave out blame, speculation and unrelated site issues.
Guardrails
- Do not invent downtime hours, costs, part numbers or order counts. Mark unknowns as "not provided".
- Flag any safety incident or injury as needing a formal report through your site safety process.
- State that repair scope and parts must be confirmed against the manufacturer manual or by a qualified technician.
Example Equipment: reach truck RT-04; downtime 06:10 to 11:40; picking halted in aisle 12; 40 orders delayed; hydraulic leak; vendor called; audience: site leadership.