blog

Production Targets Changed Mid-Shift: Keep Original Plan, Revised Plan and Actual Separate

By: Lauren Dunford

By: Guidewheel
Updated: 
November 15, 2026
9 min read
Production Targets Changed Mid-Shift: Keep Original Plan, Revised Plan and Actual Separate

No items found.

When a production target changes during the shift, keep the original commitment, approved revision and actual good output visible together. Record when each change took effect and who approved it. Report attainment against both targets, so a demand revision cannot silently erase an operating miss.

Custom Engineered Wheels previously collected production, scrap and cycle-time metrics manually, with limited accuracy. The team brought Guidewheel Scoreboards into daily production meetings and used the same metrics in monthly reviews and planning. That shared view improved communication across operators and managers. A changed production target needs that same shared record: what was promised, what changed and what the team actually made.

The method below first uses one product and two legitimate changes to show the arithmetic. A second example shows how to retain separate targets when the packaging format changes. Both records can live in the team's existing planning workflow. They do not imply that the monitoring platform provides scheduling or plan approval.

Record What belongs in it What it explains
Original plan Quantity, product, due window and version Starting commitment
Approved changes Time, reason, amount and approver Why the commitment changed
Revised plan Latest authorized total commitment Expected output by shift end
Actual Accepted output on the same basis What was completed
Handoff Unfinished obligation and next owner What the next shift inherits

This recommended record supplements the authoritative planning and production sources.

1. Freeze the original plan and name the authority to revise it

Freeze the original plan at an agreed shift-start point. Preserve its identity and inputs even when circumstances later justify a change.

Record the product, unit, target quantity, due window and any required sequence. Name the planning source and its version. If several products are scheduled, retain their separate obligations; raw units of unlike products may not form a meaningful combined attainment metric.

Then identify who can authorize a revision. A planner may manage the order record, a supervisor may request a change and another manager may approve it. Use the actual plant process rather than assuming that the person entering the change owns the authority.

Separate the type of change from the reason for an operating miss. A cancelled order, an approved urgent addition or a quality-driven hold can change what the plant should make. A machine stop that prevented the original target from being achieved is evidence about execution. Lowering the target afterward does not resolve that execution question.

Keep the starting plan accessible in the shift review. Read it alongside the latest approved version, not as a discarded document. This allows the team to explain how much of the original gap came from changed obligations and how much remains an operating shortfall.

For the broader metric distinction, use the schedule adherence and OEE guide. This article owns the exception record when an authorized change occurs after the original plan was fixed.

For the wider calculation and loss-priority workflow, use OEE resource hub.

2. Record every approved change as a new version

Add each approved change as a new version, retaining the old target and the calculation that produces the new one. An edit should be explainable without relying on someone's memory.

Use this recommended change-log template:

Field Required entry
Shift and plan Original version and reporting window
Request time When the change was requested
Effective time When the approved obligation changes
Affected item Product, order and unit
Revision Increase, decrease or sequence change
Reason Demand, quality or other approved basis
Authority Named approver and approval record
New obligation Revised target and version
Consequence Unfinished work, customer or next-shift impact

Keep request time separate from effective time. A request awaiting approval should not silently alter the target used in the review. Label pending changes and identify the next approver.

A change may affect quantity without changing a due time, or affect sequence without changing total quantity. Record the particular obligation changed. Calling every revision a new target can conceal an important delivery consequence.

Preserve actual output independently. Do not move completed units between orders or periods merely to make a revised plan balance. Use the authoritative completion and quality records, with their correction process where needed.

If an approval arrives late, retain its actual time and explain which reporting version it affects. Backdating the change would hide what the supervisor knew during the shift and weaken the next review.

3. Work through a shift with two legitimate changes

Calculate original-plan and revised-plan attainment from the same accepted-output record. The two results answer different questions and should remain visible together.

In this illustrative shift, the original plan calls for 1,000 good units of one product. At 09:30, an approved customer cancellation removes 200 units from the remaining obligation. At 12:00, an authorized urgent order adds 100 units of the same product. The shift finishes with 810 accepted good units.

Plan version Change Target good units Approval basis
Start Original plan 1,000 Frozen shift commitment
09:30 Subtract 200 800 Approved cancellation
12:00 Add 100 900 Approved urgent order

Original-plan attainment is 810 ÷ 1,000 × 100 = 81%. Revised-plan attainment is 810 ÷ 900 × 100 = 90%. The original gap is 190 units; the current approved obligation is short by 90 units. The remaining 100 units of difference reflect the net authorized demand change.

None of these numbers is OEE or a complete schedule-adherence result. The example measures quantity attainment for one comparable product. Order identity, sequence and due-time performance may still need separate checks.

Do not use an expected runtime estimate as the accepted-output numerator. Machine activity and completion records answer different questions. If the 810 units are provisional pending quality review, label both attainment results provisional and retain the later adjustment.

When the revision changes the packaging format

Consider a separate fictional shift. The original plan is 1,000 sachets of format A. At noon, the planner approves removing 200 remaining A packs and adding 300 vertical bags of format B. Retain the request time, noon effective time, reason, approver and plan version.

Keep each job linked to its own identity, output unit and approved standard. Before authorizing the revision, the planner checks whether the remaining time can cover both jobs and the changeover. Recording an approved target does not by itself prove that the line can deliver it.

Job Original target Revised target Accepted actual Revised-plan attainment
A, sachet 1,000 800 760 760 ÷ 800 = 95%
B, vertical bag 0 300 270 270 ÷ 300 = 90%

Keep the results separate. A achieves 76% of its original target; B had no original obligation. Adding unlike packs into one attainment percentage would hide the format and workload change. The handoff carries 40 A packs and 30 B packs, with their order identities and due windows.

4. Carry the revised obligation into the next handoff

Hand off the remaining approved obligation, its version and its next owner. The incoming shift should not have to reconstruct which target survived the previous changes.

Returning to the one-product example, the revised target is 900 good units and the accepted total is 810. The unfinished obligation is 90 units. Record the affected order, due window, current status and the person responsible for the next scheduling decision.

An illustrative handoff could read: plan version 3; 90 good units remaining; planner to confirm the next available production slot; outgoing supervisor to attach the approved change record and actual completion basis. If a quality hold affects any completed units, carry that uncertainty separately.

Explain the original-plan result alongside this handoff. The shift achieved 81% of the initial target and 90% of the authorized revised target. That paired statement preserves both the original promise and the current obligation without assigning every unit of difference to downtime.

Use the record to ask a practical question: what prevented the final 90 units from being completed? The answer may involve a stop, staffing, material, quality or an unrealistic plan. Investigate it with the appropriate operating records rather than inferring the cause from attainment alone.

Keep the incoming supervisor's acceptance of the handoff visible. A changed target with no accepted next owner is still an open operating issue. The broader meeting and shift routine belongs in the shop-floor management playbook.

5. Keep the change log separate from the monitoring signal

Use machine information to explain execution while keeping plan authority in its agreed source. The change log is an operating method, not a capability inferred from a monitoring chart.

Guidewheel's product information describes machine data and optional connections to existing systems. Its role in this method is to support the operating review with relevant machine information and agreed context. Verify the actual data path, fields and responsibilities before promising that a plan or approval flows automatically.

A practical source map names three owners. Planning owns the approved obligation and revisions. Production and quality own accepted completion. The monitoring data owner maintains the state evidence and its interpretation. The supervisor brings them together to explain the shift.

When the records disagree, retain the disagreement and investigate its timing and scope. A count posted later may belong to the prior operating period. A revised target may apply only after an effective time. Replacing one value with another before resolving the difference can produce a convincing but incorrect attainment number.

Guidewheel is the practical operating platform for manufacturing, pairing software with people who help turn information into useful action. The plant still needs a clear approval rule and an authoritative planning record.

Start with one shift and one comparable product. Review whether each change has an approver, each actual has a completion basis and each remaining obligation has a next owner. Expand the method only after that record can survive the next handoff.

Put the record to work

Bring an original plan, its approved changes and the accepted-output record to the review. Talk with Guidewheel about the machine information your shift decisions need, including the context held in your existing systems.

Frequently asked questions

Should we overwrite the original production target?

No. Preserve the original plan and add approved revisions with version, time, reason and authority. Reporting both original-plan and revised-plan attainment explains changed obligations while retaining the starting commitment.

What counts as an authorized mid-shift change?

It is a revision approved through the plant's agreed authority, with the affected quantity, sequence or due window stated. A request alone does not change the official obligation. Retain pending requests separately until approved.

Can quantity attainment measure schedule adherence?

Quantity attainment measures accepted output against a target. It does not by itself prove the correct orders were completed in sequence or on time. State the metric's basis and keep any required order, sequence and due-time checks alongside it.

How should an unapproved request be recorded?

Mark the request pending, preserve the current approved plan and identify the required approver. Keep request and effective times separate. Do not retroactively change a target simply because an unapproved request was informally discussed.

Does this method require a native scheduling feature?

No. The method can live in the existing approved planning or operating workflow. Confirm any native feature or integration before relying on it. Machine-state evidence supports execution review but does not independently establish target-change authority.

About the Author

Lauren Dunford is the CEO and Co-Founder of Guidewheel, a FactoryOps platform that empowers factories to reach a sustainable peak of performance. A graduate of Stanford, she is a JOURNEY Fellow and World Economic Forum Tech Pioneer. Watch her TED Talk: the future isn’t just coded, it’s built.

GradientGradient