How do you build a weekly plan that survives workshop changes?
A realistic weekly workshop plan connects accepted jobs to available people, materials, equipment and inspection requirements. Keep deadlines separate from scheduled work and define what finished means at each relevant stage of the job. Review urgent requests against existing commitments, then adjust the sequence deliberately and explain changed promises to affected customers.
Keep these in mind
- Select work from readiness and capacity, not only customer pressure.
- Use a daily check to adapt the plan around real blockers.
- Keep quality and safety criteria intact when deadlines move.
Borrow a useful cadence with clear limits
The 2020 Scrum Guide describes short cycles, a goal and regular inspection and adaptation. A fabrication team can borrow a weekly review cadence without claiming it has adopted every part of Scrum. Label the adaptation honestly.
A physical job may need curing, external treatment, inspection or supplier lead time. A planning meeting cannot shorten those requirements. Plan those dependencies explicitly.
The purpose of the routine is to expose them early.
Keep the customer promise distinct from the internal weekly goal. If the team finishes its chosen tasks but misses a committed delivery, the plan needs review.
Choose a weekly goal that means something
A goal such as clear all urgent work can expand endlessly. An illustrative goal is to prepare three approved railing orders for inspection by Thursday. Preserve service cover for existing installations.
The team can test new requests against that commitment.
Before pulling work into the week, confirm drawings, quantities, materials, approvals and the next required specialist. A not-ready column is useful when it shows exactly what is missing and who will obtain it.
| State | Entry condition | Exit evidence |
|---|---|---|
| Ready | Approved specification and required materials | Work accepted by the responsible person. |
| In progress | Capacity available and job pack complete | Physical work meets the next-stage criteria. |
| Blocked | Named missing input or decision | Blocker resolved and recorded. |
| Inspection | Work complete for quality review | Required check passed or rework assigned. |
| Ready to dispatch | Approval and destination confirmed | Dispatch handoff recorded. |
An illustrative midweek change
On Tuesday, a customer asks for a design change to one railing order. The team records the request as awaiting approval and estimates its effect on materials and capacity. Then it confirms the revised promise with the customer.
It does not quietly replace the drawing while fabrication continues.
If the change threatens the weekly goal, the team decides which other work moves. That decision should be visible to sales and dispatch. A changed plan is manageable; two teams acting on different plans is harder.
The Lean Enterprise Institute’s standardized-work guidance supports using clear work methods as a baseline for improvement. A weekly planning routine should preserve the technical and quality requirements of those methods.
Run the daily review at the work
Discuss progress toward the week’s goal, changed facts and blocked work. Avoid reading every card to the owner. Detailed technical discussions can follow with the relevant people.
- Choose a small weekly goal supported by confirmed demand and available capacity.
- Pull only ready work into the committed plan.
- Make missing inputs and blocked items visible with owners.
- Review changes daily and update affected promises.
- At week end, compare completed good work with the plan and choose one improvement.
Define finished carefully
A task marked done may mean fabrication complete, inspection passed or delivery accepted. Use the state that matters at that stage and require the appropriate evidence. Do not compress several different events into one green tick.
Give each job a clear deadline, scheduled work period and current stage. Confirm physical readiness before moving it into the next stage, particularly when materials or inspection are involved. Review changes with the people doing the work.
A useful weekly plan makes trade-offs visible while leaving enough flexibility to respond to genuine breakdowns and customer changes.
Review unplanned work, rework and overtime beside completed jobs. Recurring emergencies deserve a process review. Change the intake, supply or approval step causing disruption instead of treating every occurrence as unavoidable.
Common questions
What makes a weekly workshop plan realistic?
Connect accepted jobs to available people, materials, equipment and inspections. Separate deadlines from scheduled work and review changes together. A plan should expose trade-offs rather than fill every hour with assumed tasks.
How should urgent work enter the week?
Define urgency and assess the effect on existing commitments. Name who may resequence work and inform affected customers. Repeated emergencies may reveal an intake, supply or maintenance issue worth addressing.
Sources & further reading
Primary references for the facts and frameworks discussed. Worked examples and recommendations are Daltn’s own analysis.
- The 2020 Scrum Guide, Ken Schwaber and Jeff Sutherland ↗
Supports short planning cycles and inspection and adaptation; the article explicitly describes an adaptation.
- Standardized Work, Lean Enterprise Institute ↗
Supports clear work methods and continuous improvement.
Published by the team building Daltn. Comparisons are first-party analysis, not independent reviews. Our editorial approach.