Explain what should change, why it matters and which controlled item is affected. Give engineering enough context to assess the proposal before anyone authorizes implementation.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to explore the example in Jodoo. Screens show fictional manufacturing records.
“Please update the bracket. The new supplier is better and we need it quickly.”
This leaves the reviewer guessing about the item, current revision, reason for the change and evidence of suitability. Urgency does not resolve those gaps.
“Assess an alternate supplier for BRK-104, revision B. The proposal affects the bracket specification and assembly instruction. Review supplier qualification evidence before deciding whether to proceed. Purchasing must confirm treatment of existing stock.”
The proposal identifies a reviewable change without pretending that technical approval or the stock decision has already happened.
| Information | What to enter | Why it matters |
|---|---|---|
| Controlled item | Select the active part, drawing or instruction; retain its current revision. | The reviewer knows the starting point and can detect a proposal based on an outdated revision. |
| Reason for change | Describe the observed problem or business trigger, not only the desired solution. | The team can assess whether the proposed change addresses the actual need. |
| Proposed change | Explain what will be different and which related documents or operations may be affected. | Engineering can identify the scope that needs investigation. |
| Category-specific details | For a supplier change, identify the proposed supplier and qualification evidence. For a process change, name the affected operation. | The form asks relevant questions rather than requiring every possible field. |
| Priority and evidence | State the urgency and attach or reference the supporting material. | Reviewers can prioritize work and inspect the basis for the proposal. |
Jodoo generates the request number and fills in the selected item’s current revision. Requesters can focus on explaining the change instead of looking up identifiers or retyping product information.
The requester selects the item and completes the relevant fields. The form is the start of an assessment, not an instruction to change production.
The reviewer can return a request that needs clearer scope or evidence. Record the correction requested and resubmit the same work, so the conversation does not split into several disconnected versions.
An accepted ECR can be selected when preparing an engineering change order. A rejected proposal should retain its reason; it should not be disguised as a completed implementation.
Use the engineering change order template to identify affected revisions, functional reviews, stock disposition and implementation responsibilities. Acceptance of the request does not release a new revision.
Investigate before inventing an item or revision to satisfy a required field. A useful request can describe a problem, but a controlled implementation needs an identified scope.
Use your quality and nonconformance process for the immediate risk. An ECR is not permission to use nonconforming material while a permanent change is being assessed.
The change request template collection includes price, design and deviation requests. Choose the form for that decision when a controlled engineering revision is not the starting point.
An authorized business administrator can change category choices, help text, conditional questions and review assignments in Jodoo. A plant adding a new supplier-qualification step can ask for that evidence only on supplier changes. A process team can add the operation identifier it uses on the shop floor.
Keep the starting form short enough to complete, but do not remove information that determines the review. Pilot the form with an engineer and a requester: both should understand what is being proposed without reading the accompanying email.
Turn an accepted proposal into a defined implementation order.
See how requests connect to affected items, reviews and release history.
Agree where the ECR decision sits in your engineering procedure.
An engineering change request proposes a change and explains why it should be assessed. An engineering change order defines the approved scope and implementation plan. Organizations use these terms differently, so agree your definitions. In this example, accepting an ECR allows an ECO to be prepared; it does not authorize production to change.
Identify the current controlled item and describe the proposed change clearly. Do not invent a revision merely to make a request look complete. Engineering should confirm the intended revision and affected scope during assessment, before the implementation order is authorized.
Identify the proposed supplier and the controlled item, then attach or reference the qualification material available for review: for example, a sample inspection, material specification or compatibility assessment. Mark missing evidence as pending. The requester provides the basis for assessment; the qualified reviewers decide whether it is sufficient.
Urgency should change the response priority, not silently remove the decision. Contain the immediate risk through your approved quality procedure, then assess whether a permanent design or process change is needed. This ECR example does not authorize deviation from a controlled specification.
No. This form starts from a controlled item and its current revision. A project change request typically concerns scope, cost or schedule. Use the broader change-request process when no product, drawing or instruction revision is being changed.
Preview the form and connected records. Choose “Install with sample data” to copy the App into your workspace, assign your own requesters and reviewers, and try a request through the review process. Member fields and workflow tasks are used in the installed App, not in the public preview.
