Three questions for the next change meeting
- Have the people affected by this change made their decisions?
- What must happen to existing stock, unfinished work and controlled documents?
- Which revision is effective now, rather than merely proposed?
Manage engineering changes through release
Connect requests, affected revisions, reviews and implementation. See what is ready to change—and what still needs to happen before production uses it.
Sign in to explore the example in Jodoo. Screens show fictional manufacturing records.
An approved proposal is not a finished change
Engineering change management software connects a proposed product or process change to its reviews, implementation work and release record. For a manufacturing team, the practical question is whether purchasing, engineering and production can all tell what is changing, what is still blocked and which revision to use.
A manufacturer wants to qualify an alternate bracket supplier. Engineering must assess the proposed bracket revision, purchasing must decide what happens to 40 existing brackets, and manufacturing must address 12 units already in progress. The assembly instruction also needs to change.
One green approval status cannot answer all of those questions. The team needs the proposal, item-level scope, functional decisions and implementation work to stay connected without losing their separate meanings.
The Jodoo example shows that distinction in working records: the supplier change is still being assessed; a different drawing change is authorized but blocked by inspection work; an instruction change has completed its reviewed release.
Follow the decisions, not just a status column
| Decision | What the team reviews | What it allows |
|---|---|---|
| Accept the request | Current item and revision, the problem, proposed change and evidence. | Prepare the change order. Production is not authorized to switch. |
| Authorize the order | Affected items, impact assessments, stock and WIP treatment, and implementation scope. | Start the approved implementation work. Current revisions remain separate. |
| Verify implementation | The completed action, its evidence and any remaining release-critical work. | Clear that action from the open critical-work count. |
| Confirm release | The affected item, completed prerequisites and actual effective boundary. | Update the exact controlled item and retain the original-to-released revision history. |
Reviewers receive assigned tasks and can return work for correction. The requester supplies the proposal; the assigned reviewer makes the decision. Set those responsibilities and access rules for your team before using the App for live changes.
Give each team the view its next decision needs
Engineering: the affected scope
Compare original and proposed revisions item by item. The bracket and the assembly instruction can belong to one order without sharing a revision number or losing their individual release history.
Operations: unfinished work
See critical actions, owners, due dates and verification outcomes. An authorized drawing change still appears with work open when the first-off inspection cannot be completed.
Change coordinator: readiness
Review orders being prepared, unresolved impact reviews and released items together. Open the related records to find the decision or evidence behind a count.
The sample quantities are fictional examples, not customer performance results. The App coordinates disposition decisions; it does not move inventory, post accounting entries or replace the product master in an existing ERP.
Change the review process when your manufacturing work changes
Ask different questions for different changes
A supplier substitution needs a proposed supplier and qualification evidence. A production-process change needs the affected operation. An authorized administrator can adjust these conditional fields without turning every request into a long, generic questionnaire.
Keep technical evidence specific: a drawing note, inspection result or controlled instruction can be linked to the change that requires it, rather than attached to an unrelated task.
Adjust responsibilities and follow-up
Add the review function your category requires, change who receives a task, or create a view for a plant’s overdue implementation work. Jodoo’s forms, linked records, review tasks and dashboards can be configured around the team’s procedure.
A process change still deserves a test. Check existing records, returned tasks, calculations and access rules before applying revised settings to live work.
Use Jodoo for coordination; keep specialist product controls where they belong
A good fit when…
Requests and reviews are scattered across files and messages; the team needs clear item-level scope and implementation follow-up; and business administrators need to adapt the process as products, suppliers or responsibilities change.
The example provides a practical starting point with seven connected forms and native review steps. Start with one controlled change and configure the team’s actual responsibilities.
Consider PLM or PDM when…
Native CAD relationships, BOM redlining, product configurations or enterprise product-data control are central requirements. This App is not a CAD vault, an atomic multi-item release engine or a validated regulated-signature solution.
Compare coordination and specialist engineering-change software before choosing which system should own your revisions.
Build your change process, one decision at a time
Engineering change request
Capture the reason for a change before committing to implementation.
Engineering change order
Plan the affected revisions, existing stock and production cutover.
Engineering change process
Agree responsibilities and release decisions across the full process.
Engineering change software questions
What happens if another change revises the same item first?
Before applying a release, the example checks that the item is active and its current revision still matches the change’s starting revision. A mismatch prevents that release from changing the item. Engineering must reassess the affected scope; this check is not a substitute for concurrent BOM or CAD configuration management.
Can one change order cover a drawing and a work instruction?
Yes. Add a separate affected-item record for each item. Each record keeps its own original revision, proposed revision, disposition and release history. The sample supplier change covers both a bracket and its assembly instruction; they do not become one shared revision field.
Can we use this alongside our existing PLM or ERP?
Use it for the coordination your team needs, but agree which system owns approved product data and inventory. This example does not synchronize with PLM or post ERP transactions. An integration needs explicit identifiers, access rules, error handling and reconciliation before either system is treated as authoritative.
Can business users change the process without rewriting the App?
An authorized business administrator can edit form choices, conditional fields, review assignments and operational views in Jodoo. For example, a supplier change can ask for qualification evidence while a production-process change asks which operation is affected. Test revised rules and permissions before using them for live changes.
Does the example provide regulated electronic signatures?
No. Native review tasks and recorded decisions are not a claim of a validated electronic-signature system. Assess your regulatory obligations, validation approach and required controls separately. The example is intended to demonstrate engineering change coordination.
Explore a change that is still waiting on a real decision
Open the readiness view, inspect the pending purchasing assessment, then compare it with the authorized-but-blocked drawing change. Use those differences to decide what your team needs to see.