# Continuous Improvement Plan

Builds a structured plan to improve a specific operational process over a defined window. Use it when leadership has identified a process that is underperforming and wants a written plan with milestones, owners, and success measures.

## Prompt

## Context
You are helping an operations manager or process owner draft a continuous improvement plan. The organization is [ORGANIZATION NAME]. The process being targeted is [PROCESS NAME]. The improvement initiative is scoped to [IMPROVEMENT WINDOW, e.g., 90 days or Q3]. The reader of this plan may be a team lead, department head, or oversight committee, so it must be clear without requiring operational jargon to follow.

## Task
Produce a continuous improvement plan with the following sections:

1. Problem statement. One paragraph. What the current process does, where it falls short, and the cost of leaving it unchanged. Use only facts from the inputs below.
2. Scope. What is inside and outside this initiative. Be explicit about what this plan does not touch.
3. Current state summary. The key steps of the process as it runs today, including the handoffs and known friction points: [CURRENT STATE DESCRIPTION].
4. Improvement objectives. Two to four specific, measurable targets. Base these on: [IMPROVEMENT OBJECTIVES AND TARGETS].
5. Planned actions. A numbered list of changes to implement, each with: the action, the owner by role (not name), the target completion date, and any dependency.
6. Milestones and check-ins. A cadence for reviewing progress over [IMPROVEMENT WINDOW].
7. Success measures. How you will know the improvement held after the window closes, stated as observable conditions or measurable thresholds.
8. Risks. Two or three things that could stall the plan, and a brief mitigation for each.

Inputs for the plan:
- Current state: [CURRENT STATE DESCRIPTION]
- Objectives and targets: [IMPROVEMENT OBJECTIVES AND TARGETS]
- Known constraints: [KNOWN CONSTRAINTS]
- Stakeholders involved: [STAKEHOLDER ROLES]

## Standards
- 500 to 700 words for the full plan. Each section under a bold header.
- Tone is direct and practical. Write for a team lead who will execute this, not a consultant who will review it.
- Do not invent baseline metrics, dates, dollar figures, or target percentages. Use only the numbers the user provides. If a target is stated as a range, keep it a range.
- Do not recommend specific tools, vendors, or methodologies unless the user names them.
- Improvement objectives must be phrased in terms of observable outcomes, not activities.
- End Standards: if any named input is missing or ambiguous, ask before drafting the plan.

## Variables

- ORGANIZATION NAME
- PROCESS NAME
- IMPROVEMENT WINDOW
- CURRENT STATE DESCRIPTION
- IMPROVEMENT OBJECTIVES AND TARGETS
- KNOWN CONSTRAINTS
- STAKEHOLDER ROLES

## Input checklist

- [ ] A plain description of the current process, including the steps, handoffs, and where breakdowns typically occur
- [ ] Specific improvement targets with the numbers or thresholds you are working toward, pulled from your own data or leadership direction, not AI estimates
- [ ] The time window and any fixed deadlines (quarter end, contract renewal, audit date) that set the pace
- [ ] The stakeholder roles who will own actions, review progress, and approve changes
- [ ] Confirm all baseline metrics, target figures, and dollar amounts come from your own records, not the AI
- [ ] Keep personnel names, vendor contract details, and sensitive cost data out of the prompt; use role titles and anonymized figures

## Verification checklist

- [ ] Confirm every metric and target in the plan matches what you provided, with no figures the AI invented
- [ ] Verify improvement objectives are observable outcomes, not just activity goals like 'hold a meeting' or 'review the process'
- [ ] Check that no specific tool, software, or vendor name appears unless you supplied it
- [ ] Confirm action owners are listed by role, not personal name, and the roles exist in your org
- [ ] Review the risks section: reject any risk the AI invented that has no basis in your actual context
- [ ] Verify the success measures can actually be observed or measured in your environment with your current data sources
- [ ] Recheck any date arithmetic in the milestones against the actual improvement window you provided

## Sample output

Sample output. Generated by AI from sample inputs:

**Continuous Improvement Plan: Warehouse Inbound Receiving Process**
Organization: Northwind Distribution | Process: Inbound receiving | Window: 90 days (July 1 - September 30)

**Problem statement**
Northwind's inbound receiving process currently takes an average of 4.2 hours from dock arrival to system entry. That delay pushes fulfillment timelines past the 24-hour commitment on priority orders and has contributed to inventory discrepancies requiring manual correction. Leaving the current process unchanged risks continued fulfillment misses and inventory inaccuracy.

**Scope**
This plan covers the steps from carrier arrival at the dock through system entry and put-away confirmation. It does not cover outbound shipping, returns processing, or the purchasing workflow upstream of receiving.

**Current state summary**
Trucks arrive and wait for a dock assignment (avg. 45 min). A receiving associate unloads and counts manually (avg. 90 min). A separate associate enters counts into the inventory system (avg. 60 min). Discrepancies are flagged and held for a supervisor review that happens once per shift (avg. 60 min wait). The entire sequence runs 4+ hours when a supervisor review is triggered.

**Improvement objectives**
1. Reduce average dock-to-system time from 4.2 hours to under 2.5 hours.
2. Reduce discrepancy-hold events by 30% through cleaner count procedures.
3. Complete the put-away confirmation step on the same shift as receipt.

**Planned actions**
1. Cross-train one receiving associate per shift to handle both counting and system entry. Owner: Warehouse Manager. Deadline: July 15. Dependency: system access permissions.
2. Revise the count sheet to match the PO line sequence, reducing lookup time. Owner: Operations Analyst. Deadline: July 10. Dependency: none.
3. Shift supervisor discrepancy review from batch (once per shift) to on-demand (within 20 minutes of flag). Owner: Shift Supervisor. Deadline: July 22. Dependency: supervisor scheduling review.
4. Add a mid-shift dock assignment check to reduce wait time. Owner: Dock Coordinator. Deadline: August 1. Dependency: none.

**Milestones and check-ins**
- Week 2: Actions 1 and 2 complete. First data pull on dock-to-system time.
- Week 4: All actions live. Baseline comparison review.
- Week 8: Mid-point check-in. Adjust if discrepancy hold rate has not moved.
- Week 12: Final review against all three objectives. Decision on whether changes become permanent standard procedure.

**Success measures**
At 90 days, average dock-to-system time is at or below 2.5 hours for at least 80% of receiving events. Discrepancy-hold events are down at least 30% versus the 90-day baseline before the initiative. No priority orders missed fulfillment due to an unresolved receiving delay in the final 30 days of the window.

**Risks**
1. Staff turnover during cross-training. Mitigation: document the combined procedure before cross-training begins so institutional knowledge does not leave with a single person.
2. Supervisor scheduling constraints limit on-demand review response time. Mitigation: escalation path to a backup reviewer is defined before the new cadence goes live.
3. Count sheet revision requires IT or system access that takes longer to provision than expected. Mitigation: start the access request in week one, not after the design is finished.

## Customization notes

For teams using a specific improvement methodology (Plan-Do-Check-Act, Lean, Six Sigma), name it in the prompt and the plan will align its structure accordingly. For smaller operations, the plan can be compressed to a one-page format by reducing the actions list to five or fewer items and skipping the formal milestones section. Veterans transitioning into operations roles will recognize this format as close to a corrective action plan or improvement annexure; the vocabulary is civilian but the structure is familiar.

---

From The Logistics, Operations & Project Management Library at vetslearn.com/libraries/logistics-pm