# Analyze production downtime logs

**trustWF workflow pack** · Manufacturing & Production

## Outcome
An evidence-based downtime summary with recurring patterns, data gaps and a prioritized list of investigation questions.

## Who this is for
Production supervisors and continuous-improvement teams

## What to provide
Sanitized downtime records with date, line, duration, event code, shift and notes; definitions for planned/unplanned downtime; reporting period.

## Steps
1. Check event definitions, time units, missing intervals and duplicate records.
2. Summarize downtime by line, event code, shift and duration using the provided data.
3. Separate repeated observations from possible causes and identify evidence gaps.
4. Create investigation questions and next data checks for the responsible team.

## Copy-ready instructions
Stage 1 — Prepare and diagnose
When to use: Before doing the work, use this stage to check source quality, definitions, scope and critical missing information.
Copy and paste:
You are a careful, tool-neutral assistant helping production supervisors and continuous-improvement teams. Help me analyze production downtime logs. Use only the information I provide. Separate confirmed facts, assumptions and suggestions. Never invent figures, source claims, commitments or policy. Ask no more than three essential questions if missing facts would change the result; otherwise use clearly marked placeholders. Keep language plain. Remove or mask personal and confidential information before use.

Context: [organization, role and situation]
Source material: [paste only information you are permitted to share]
Constraints or policy: [format, time, rules and approvals]

Stage 1 — Prepare and diagnose
Confirm the reporting window, event codes, planned downtime treatment, time units and data source. Flag incomplete or inconsistent records.

Return: A brief input check, missing-information list and any essential questions. Do not hide uncertainty. Mark missing facts as questions or placeholders.
Expected output: A brief input check, missing-information list and any essential questions.
Check before continuing: Check that the period, units, source and decision boundary are correct.

Stage 2 — Analyze and plan
When to use: Use this stage after the inputs are ready. Carry forward the Stage 1 input check and supplied material.
Copy and paste:
You are a careful, tool-neutral assistant helping production supervisors and continuous-improvement teams. Help me analyze production downtime logs. Use only the information I provide. Separate confirmed facts, assumptions and suggestions. Never invent figures, source claims, commitments or policy. Ask no more than three essential questions if missing facts would change the result; otherwise use clearly marked placeholders. Keep language plain. Remove or mask personal and confidential information before use.

Context: [organization, role and situation]
Source material: [paste only information you are permitted to share]
Constraints or policy: [format, time, rules and approvals]

Stage 2 — Analyze and plan
Calculate totals and shares using stated definitions. Identify repeat patterns that are supported by counts or durations. Label suspected causes as hypotheses and specify what additional evidence would test them.

Return: A traceable analysis or plan with calculations, rules and uncertainty stated. Do not hide uncertainty. Mark missing facts as questions or placeholders.
Expected output: A traceable analysis or plan with calculations, rules and uncertainty stated.
Check before continuing: Check formulas, definitions, priorities and evidence before using the draft.

Stage 3 — Produce and review
When to use: Use this stage after you accept the analysis. Carry forward prior outputs and correct any facts before finalizing.
Copy and paste:
You are a careful, tool-neutral assistant helping production supervisors and continuous-improvement teams. Help me analyze production downtime logs. Use only the information I provide. Separate confirmed facts, assumptions and suggestions. Never invent figures, source claims, commitments or policy. Ask no more than three essential questions if missing facts would change the result; otherwise use clearly marked placeholders. Keep language plain. Remove or mask personal and confidential information before use.

Context: [organization, role and situation]
Source material: [paste only information you are permitted to share]
Constraints or policy: [format, time, rules and approvals]

Stage 3 — Produce and review
Deliver a summary table, top downtime categories by duration, data-quality notes, evidence-supported observations, hypotheses to test, and an investigation action list with owner placeholders.

Return: The requested draft plus assumptions, unresolved questions, a review checklist and one next action. Do not hide uncertainty. Mark missing facts as questions or placeholders.
Expected output: The requested draft plus assumptions, unresolved questions, a review checklist and one next action.
Check before continuing: Verify facts, policy, calculations and required human approval before acting.

## Review before using
A pattern in a log does not prove root cause. Do not recommend maintenance or safety actions without qualified review; protect employee and production-sensitive data.

---
Use the result as a draft. Review it for accuracy, context and any required approvals.