Prototype revision log
Record a revision log documenting how feedback changed your ER prototype.
Prototype revision log: accepted changes tied to criteria or evidence, and at least one rejected alternative with reasoning.
- 1Do thisRecord a revision log documenting how feedback changed your ER prototype.
- 2Use this resource
- 3Submit thisLab report: Prototype revision log: accepted changes tied to criteria or evidence, and at least one rejected alternative with reasoning.
- 4Submit it here
- 1CMSD website. Go to clevelandmetroschools.org and click the Clever button.
- 2Clever. Clever opens. Sign in if it asks.
- 3Microsoft (district) login. Use your district Microsoft account (the one for school).
- 4Schoology. Open Schoology, then your class, then Assignments, and find the file named below.
The file to submit is named: Biotechnology for Health (Biomedical Innovations) › Design brief, floor plan logic, staffing, process flow, safety, and human factors. › Lab reportOpen Schoology
- CER:
- Claim, Evidence, Reasoning — make a claim, back it with evidence, explain your reasoning.
- SOP:
- Standard Operating Procedure — the exact steps to follow (especially in a lab).
- Tracker:
- Your PLTW progress log where you record completed evidence.
- myPLTW:
- The PLTW course site where you do the online activities — you open it through Schoology.
Minute-by-minute · 80-minute block
💡 Big idea: Design revision is not failure -- it is the mechanism by which evidence improves prototypes, and logging it makes the improvement visible.
- 0-10Collect feedback: review peer comments on your floor plan and flowchart from this week
- 10-30Log accepted changes: for each revision, record what changed and why (tie to criterion or evidence)
- 30-50Log rejected alternatives: note one change you considered but decided against, with reasoning
- 50-65Verify that every logged change traces to a criterion or constraint from your design brief
- 65-77Submit the prototype revision log
- 77-80Exit reflection: which revision do you think improved the design most, and what is your evidence?
- • This week you built a floor plan and a flowchart. Now you need to document how feedback changed them.
- • A revision log is not a list of mistakes -- it is proof that your design process is iterative and evidence-driven.
- • Every change you record today becomes part of your portfolio evidence for Problem 1.
- • Including a rejected alternative -- and explaining why you said no -- is a mark of a sophisticated designer.
- 1Collect feedback on your floor plan and flowchart.
- 2List each change you made and the reason for it.
- 3Tie each change to a criterion or constraint.
- 4Note one change you considered but rejected, with reasoning.
- 5Submit the prototype revision log.
- • Your log links each revision to evidence or a criterion.
- • You can justify a design change and a rejected alternative.
- • How to write a revision log entry that links a design change to a specific criterion or piece of evidence.
- • Why documenting rejected alternatives shows rigorous design thinking rather than indecision.
- • How a revision log becomes the primary evidence that feedback improved the prototype.
Your PLTW work today
Design brief, floor plan logic, staffing, process flow, safety, and human factors. · Prototype revision log
Day 5 of this lesson. Open this exact section in myPLTW (reached through Schoology), then do the work below.
Do this: Open Problem 1 in your myPLTW course shell and locate the revision or iteration activity to review the log format.
Mark the revision-log activity complete in your tracker after submitting the log.
The floor plan, flowchart, and all Problem 1 prototype work are done; today you log the changes feedback drove and submit the weekly summative.
Revision log with accepted changes linked to criteria or evidence, and at least one rejected alternative with reasoning.
All PLTW activities are completed inside the PLTW course environment — this page only gives direction. Submit producibles on Schoology.
Today's PLTW tracker
Check things off as you work, then submit. This tells Mr. Mendoza how you're doing so he can help the class. It does not replace turning in your producible on Schoology.
Use the code Mr. Mendoza gave you, not your name. Saved on this device.
Design brief, floor plan logic, staffing, process flow, safety, and human factors. · Prototype revision log
Open Problem 1 in your myPLTW course shell and locate the revision or iteration activity to review the log format.
The floor plan, flowchart, and all Problem 1 prototype work are done; today you log the changes feedback drove and submit the weekly summative.
This is how Mr. Mendoza sees the class keeping pace with PLTW. Be honest, it only helps if it is accurate.
🎯 Record a revision log documenting how feedback changed your ER prototype.
- Collect feedback on your floor plan and flowchart.
- List each change you made and the reason for it.
- Tie each change to a criterion or constraint.
- Note one change you considered but rejected, with reasoning.
- Submit the prototype revision log.
Lab report: Prototype revision log: accepted changes tied to criteria or evidence, and at least one rejected alternative with reasoning.
Submit on SchoologyUpload by 11:29 PM for full credit.
| Task | Who |
|---|---|
| Collect feedback on your floor plan and flowchart. | _______ |
| List each change you made and the reason for it. | _______ |
| Tie each change to a criterion or constraint. | _______ |
| Note one change you considered but rejected, with reasoning. | _______ |
| Submit the prototype revision log. | _______ |
Working solo? Put your own name in "Who" for every row.
- Your log links each revision to evidence or a criterion.
- You can justify a design change and a rejected alternative.
Teacher-posted resources
Classroom documents for this lesson. Ones marked “Open the file” open right here; the rest are posted in Schoology. Use the label on each card to choose the right move.
Open this when the class reaches this activity and use it to complete the required lesson artifact.
Placement rationale
Matched Prototype planning and project management by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:gantt, project management. Score 142. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).
Use this if you were absent, got stuck, or need another pass before you submit the lesson artifact.
Placement rationale
Matched Prototype planning and project management by path:Biomedical-Innovations/Problem-1_Emergency-Room/00_Problem-Overview; keywords:gantt, design. Score 134. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).
Open this when the class reaches this activity and use it to complete the required lesson artifact.
Placement rationale
Matched Prototype planning and project management by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:design. Score 134. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).
How to get there: open the CMSD website, click Clever, sign in with your Microsoft (district) account, then open Schoology from Clever.
Lab & supplies
WebXam practice
Cumulative WebXam review
A quick mixed-review pulling questions from earlier units plus today, so the WebXam material stays fresh.
Where this leads — careers
What today's skills lead to. These are real health-science careers this course builds toward. Tap one to see, on the US Department of Labor's O*NET site, what the job actually involves, what it pays, and how fast it is growing.
What to do if you were absent
Today is individual PLTW work, so do exactly what we did in class, from home: complete the same PLTW target above, then submit your Lab report.
Open Schoology (CMSD) and keep goingHow to get there: open the CMSD website, click Clever, sign in with your Microsoft (district) account, then open Schoology from Clever.
Class still runs. Complete the online activity above (it's self-guided). Need the concept taught without a teacher? Use this authoritative explainer:
NGSS Engineering Design- CompleteEvery required part of the artifact is present, nothing left blank.
- AccurateThe science and the data are correct and match the evidence.
- Scientific reasoningYou explain your claim with evidence and reasoning (CER), not just an answer.
- Professional communicationClear, organized, labeled, and written the way a clinician or scientist would.
- SubmittedTurned in the right way (Schoology for routine work) and confirmed.
Drop your Tue, Feb 16, 2027 · Prototype revision log here. Use a clear file name (your initials + project). Routine work still goes to Schoology (via the CMSD portal).
Upload a project
