Learning Targets
- Write a clear evidence-based problem statement.
- Document a proposed change and identify affected parts or records.
- Create measurable acceptance criteria and a verification method.
Focus question: How do engineers document a proposed design change without losing control of the original design?
Use this page with the lesson presentation and your engineering notebook.
The request separates the current design from the proposed revision and includes a testable success condition.
Think first, then be ready to share a short response that connects the question to engineering communication.
A controlled record preserves the current design, explains the reason for the change, identifies affected information, and makes the revision traceable and testable.
An Engineering Change Request records a proposed revision without erasing the current design.
The proposal should be supported by observations, measurements, fit issues, or user needs.
Acceptance criteria define how the team will decide whether the change works.
Complete the four evidence fields for the sample change, then choose the appropriate reviewer decision. Each field needs enough detail for another engineer to act.
Identify one evidence-based improvement to the rocket assembly and document it as a controlled proposal.
Quality check: The request must be specific enough for another engineer to implement and verify.
Submit one controlled change document and one decision summary.
Submission standard: Preserve the original design record and identify which documents would need a later revision.
Use the lesson slides for guided practice, interactive checks, and the exit ticket.
Return to the IED course hub for units, resources, certifications, and current course information.