Turn an accepted change into an implementation plan: identify each affected revision, decide what happens to stock and unfinished work, and record when the change actually takes effect.
Sign in to explore the example in Jodoo. Screens show fictional manufacturing records.
A supplier substitution can affect more than the purchased part. In the fictional example below, the bracket specification changes and its assembly instruction needs an alternate-supplier inspection step. Keeping both on the same order helps coordination; keeping their revision pairs separate prevents ambiguity.
| Affected item | Revision change | Existing material or work | Decision needed |
|---|---|---|---|
| BRK-104 bracket | B → C | 40 brackets in stock; 12 units in work in progress. | Purchasing confirms stock run-out. Manufacturing defines rework for the 12 unfinished units. |
| WI-208 assembly instruction | Rev 04 → Rev 05 | No physical stock quantity for the instruction itself. | Add the supplier-specific inspection step after qualification; communicate the applicable production boundary. |
A blank released-revision field is meaningful here: these are proposed changes, not proof that production has switched. The current revision should remain unambiguous until the release decision is made.
Identify the quantity and where it is held. Decide whether it may be used as-is, consumed before cutover, reworked, returned or otherwise handled under the approved procedure. A pending supplier answer should remain visibly pending.
Do not use “Not applicable” for a material quantity that still needs a decision. The instruction must be specific enough for the people handling the stock to apply it.
Identify work already started and the operation at which the change matters. State whether that work finishes to the old revision, requires rework or must wait for a technical decision.
Stock run-out and WIP rework are different actions, often owned by different people. Finishing one should not make the other disappear.
| Weak instruction | More usable instruction | Still to confirm |
|---|---|---|
| “Use the new revision next week.” | Name the site, affected work or lot, planned date and the person confirming readiness. | What happens to work already started and stock remaining at the boundary? |
| “Update the drawing.” | Identify the controlled drawing and revision, and the related instruction or inspection method that must change. | Who verifies that obsolete copies are removed from use? |
| “Training completed.” | Record the affected roles, instruction revision and evidence of the required briefing or qualification. | Can the team performing the work find and apply the effective instruction? |
Four editable sheets cover the order, affected items, impact reviews and implementation. Use the sample records, dropdowns and formulas to plan one change and its affected revisions.
XLSX · 30 KB. Decisions are entered manually. The workbook does not route approvals or synchronize with the App.
Connect functional assessments to the same order. Record findings and a native review decision, so the coordinator can see what remains unresolved.
Assign the work and distinguish critical release prerequisites from other follow-up. Completion evidence goes to a review task instead of becoming an unchecked “Done” label.
A reviewed release confirmation updates the selected controlled item. The affected-item record retains its original and released revisions, rather than overwriting the before-and-after comparison.
Business administrators can adapt the order fields, required review count, task assignments and views to the procedure. Reviewers still need to confirm that the right functions have contributed: a count of completed assessments alone does not establish that every necessary discipline approved the change.
Start with an assessed proposal before preparing the order.
Define approval, implementation and release responsibilities.
Inspect the connected records behind change readiness.
Record the accepted request, the change scope, each affected item and revision, the impact decisions, treatment of existing stock and work in progress, implementation responsibilities, and the release boundary. A target date alone is not a complete cutover instruction.
No. The workbook records information and decisions entered by your team. It has four sheets: Change order, Affected items, Impact reviews and Implementation. It does not assign native review tasks, enforce member permissions or synchronize with the Jodoo App.
The App retains a release confirmation for each affected item. Agree whether your real change requires an all-at-once release before using that behavior. The example does not provide an atomic release transaction across several product records.
Choose a boundary that operations can apply, such as a production lot, work order, site and dated cutover. Explain what happens to work already started. A date can be suitable, but it should not leave two shifts interpreting the same stock differently.
Not in this example. A future cutover belongs in the implementation plan. The release confirmation records a cutover that is now effective; it is not a scheduler for future product-data activation.
Open the affected-item view to compare revision pairs and disposition decisions, then follow the implementation and release views.
