You’ve loaded the shop schedule into a new system. Then a request changes, and someone updates the old sheet.
Now the planner is looking at one quantity, the foreman has another, and the crew has to ask which one to follow.
Moving the file is only part of the change. Your team also needs to agree where new work enters, who updates the plan and when the old sheet stops being used for production.
Gather the active work and review it with the people who maintain the schedule.
Check the job references, quantities and required dates. Identify what is already complete, what is underway and what is waiting on drawings or material. Keep the field’s requested date distinguishable from the dates you’ve planned in the shop.
You don’t need to move every archived row to establish the current plan. Keep the history your business needs, but give it a separate home from work the crew still has to finish.
Also check what a row represents. It might be a whole package, one assembly or a production task. That affects how the work should be organized in Building Swell.
Say a package is listed as twelve assemblies. During setup, the project team changes the request to sixteen.
Use that change to check how your team will work:
If the answer still involves updating two production schedules, decide why both are needed.
You may keep a comparison copy while checking the setup. Make clear which plan the crew follows and who maintains the other. Otherwise, comparing the systems becomes another daily job.
The test is whether the change reaches the people doing the work and their progress reaches the person planning what comes next.
Before relying on the new plan, compare a selection of orders with their source records. Include work that is underway or on hold, rather than checking only new jobs.
Confirm that quantities, date meanings and production stages survived the transfer correctly. Open the work as someone on the floor would. Can they identify their assignment, find the drawing and record what they’ve completed?
An Excel import transfers a snapshot. It does not keep later edits connected. If you use a Smartsheet connection, confirm which fields update, in which direction and who handles changes that fail. Don’t assume the two methods behave the same way.
Once the team has checked the work and can use the new plan, agree when production updates move to Building Swell.
Tell everyone where to enter new work, change an order and record progress. Keep a dated archive of the old production sheet and restrict editing where practical. Update links and bookmarks so people don’t return to it by habit.
Some spreadsheets may remain useful for analysis or project coordination. Keep their purpose clear. A report drawn from the production plan should not quietly become a second place to reschedule the shop.
Choose the changeover scope with the people responsible for making it work. One department may move first, or several may need to move together. What matters is that everyone affected knows which work is covered and where its current plan lives.
Bring your working schedule and a recent change. We’ll walk through how the work enters Building Swell, how your team updates it and what you need to check before retiring the old production sheet.
