Finite Scheduling & Exception Runbook

Purpose and Scope

This runbook helps schedulers, planners, dispatchers, supervisors, and operators handle short-term scheduling exceptions in a finite-capacity environment. It focuses on decisions and actions that protect delivery commitments, reduce firefighting, lower WIP, and keep throughput steady.

When to use this runbook

• Rush / hot orders that may disrupt the plan
• Machine breakdowns, tool failures, or operator shortages
• Late or missing materials impacting planned runs
• Significant schedule slip risks that threaten promised delivery dates

Roles & Responsibilities

• Scheduler / Planner: Apply freeze rules, run triage, make primary re-sequencing decisions, update schedule system/board.
• Dispatch / Lead Operator: Execute changes on the floor, verify materials/fixtures, confirm safety and quality checks, provide feedback on feasibility and time-to-changeover.
• Maintenance: Triage and respond to breakdowns per priority; provide ETA and workarounds.
• Production Supervisor: Communicate with affected teams and ensure documented execution.
• Customer / Sales (when required): Receive communication about delivery impacts and agree to remedies (expedite, partial shipment, reschedule).

Schedule Freeze Rules & Allowed Exceptions

Define the freeze horizon (e.g., next 48 hours). During freeze, only allow changes using these exceptions:

1. Critical safety or compliance issue
2. Equipment failure with no alternative capacity and high-impact orders
3. Customer-verified rush order (scored via triage below)
4. Material shortage confirmed by procurement when no acceptable substitute exists

All other change requests are queued for the next planning cycle unless approved by the Scheduler + Production Supervisor jointly.

Rush Order Triage (Quick Scoring)

Use this simple 5-point rubric to decide whether a rush order should displace planned work. Score each dimension 0–3, then sum.

• Delivery Impact (0 no impact – 3 immediate customer-critical)
• Customer Importance (0 low – 3 strategic / top-tier)
• Revenue / Margin Impact (0 low – 3 high)
• Feasibility (0 impossible – 3 fits existing schedule & tooling)
• Operational Disruption (0 minimal – 3 requires major rework / long changeover)

Threshold guidance:

• Score 10–15: Approve as true rush — follow re-sequencing checklist and notify stakeholders.
• Score 6–9: Consider alternatives first (partial shipment, overtime, subcontract).
• Score 0–5: Defer to normal planning.

Operator / Dispatch Fast-Checklist for Re-sequencing

Use this in the immediate 30–60 minutes after approving a schedule change.

1. Safety first: Confirm the change does not bypass required permits, LOTO, or safety checks.
2. Lock the affected plan elements: Note original sequence, times, and operators in the schedule log before changing.
3. Materials & tools check: Verify material, kits, fixtures, gauging, and tooling are available at the workstation.
4. Changeover estimate: Confirm expected changeover time and whether specialist support is needed.
5. Quality gate: Ensure inspection points or first-article checks are scheduled before high-volume production.
6. Update visual boards & systems: Reflect the new sequence on the production board and in the scheduling system (who made change and why).
7. Inform downstream stakeholders: Notify shipping, assembly, warehouse, and sales of any delivery impacts.
8. Monitor first 3 pieces: Confirm parts meet spec before full release.

Quick Re-balancing Heuristics & Priority Matrix

When capacity is constrained, prefer these options in order (practical heuristics):

1. Move non-bottleneck work later; keep bottleneck resources saturated with highest-priority items.
2. Split lots to produce rush quantity first if changeover cost allows.
3. Use cross-trained operators to absorb shortfalls rather than reprioritizing entire lines.
4. Consider overtime only when marginal benefit > incremental cost and approvals exist.
5. Subcontract only when internal capacity re-sequencing is insufficient and quality/costs are validated.

Priority matrix example (use as a quick reference):

• Top-priority: On-time delivery to strategic customer, safety/compliance incidents.
• High: High-value orders near promised date, expediting from a quality failure.
• Medium: Routine orders impacted but reschedulable within customer tolerance.
• Low: Internal stock replenishment, low-value orders.

Examples of Safe Decisions

Example 1: Machine A failed. If Machine A is the bottleneck and failure affects top-priority order, trigger maintenance and move lower-priority runs elsewhere. If no alternate capacity exists, communicate partial shipment options to sales.

Example 2: Rush order scores 12. Approve by moving a low-priority run, split lots if tool changes are small, monitor QA first-article, and log change reason.

Communication Templates

Use these templates and edit placeholders before sending. Keep messages factual, short, and include required actions and owners.

To Production Team / Floor

Subject: Schedule Change – Immediate Action Required ({{LINE}} / {{SHIFT}})

We are inserting order {{ORDER_ID}} ({{PART}}) into the schedule at {{TIME}}.
Reason: {{REASON}}.
Actions: Changeover at {{START_TIME}}. Lead: {{LEAD_NAME}}. Verify materials & first-piece inspection.
Expected impact on downstream: {{IMPACT}}.
Please confirm ready by {{CONFIRM_TIME}}.

To Shipping / Sales

Subject: Delivery Impact – Order {{ORDER_ID}}

Order {{ORDER_ID}} previously promised for {{ORIG_DATE}}. After schedule change, expected ship date is {{NEW_DATE}}.
Options considered: partial shipment / expedite / price to expedite.
Contact: {{SCHEDULER_NAME}}, {{PHONE}}.

To Procurement (Late Material)

Subject: Material Shortage Alert – {{MATERIAL}}

Material {{MATERIAL}} for order {{ORDER_ID}} is delayed. Requested ETA: {{ETA}}. Alternatives checked: {{ALTS}}. Request: confirm expedited ship or approve substitution by {{DECISION_TIME}}.

Escalation Flow

If an exception cannot be resolved within the freeze window or threatens customer delivery, escalate:

1. Scheduler + Production Supervisor decide on immediate mitigation (within 30 minutes).
2. If unresolved, involve Plant Manager and Sales within 1 hour for customer messaging.
3. For multi-line or multi-site impacts, elevate to Operations Director and Logistics.

Post-Event Learning Capture (Compact Form)

After the event, capture these fields in the schedule log. Turn the answers into a quick corrective action if needed.

• Event title and timestamp
• Trigger (machine, material, customer, quality, other)
• Immediate action taken
• Decision rationale (who approved and why)
• Time lost (minutes/hours) and affected orders
• Root cause (initial hypothesis)
• Corrective action / owner / due date
• Follow-up verification date and result

Keep the post-event note short (<300 words) and attach any evidence (photos, system logs). Use the information in the next planning meeting to reduce repeat occurrences.

Metrics to Monitor

• Number of approved exceptions per shift and reason (trend)
• Average decision-to-execution time
• Percent of changes that required rework or caused quality escapes
• Impact on On-Time Delivery and WIP

Operational Tips & Common Pitfalls

• Do not treat the schedule as a daily to-do list — respect freeze rules to avoid chronic firefighting.
• Log every change (who, when, why) – absence of records makes root-cause analysis impossible.
• Prefer splitting lots or partial completion to wholesale rework of a line when changeovers are costly.
• Train a small group of cross-functional decision-makers to reduce approval latency during peak hours.

How to Improve This Runbook (Suggested Next Steps)

- Implement the operator fast-checklist as an Interactive checklist so dispatch can submit confirmations that automatically store the event and time stamps. - Add an interactive post-event capture form (fields listed above) so events feed a searchable incident log and metrics dashboard. - Bundle this runbook into a Finite Scheduling Toolkit that includes SOPs for changeover times, alternate routing maps, and a capacity map for each shift.