| Field | Value |
|---|---|
| Name | |
| Assignment | |
| Date | |
| Reviewer |
Ask the student to explain their code without looking at notes.
| Score | Criteria |
|---|---|
| 10 | Explains flow clearly, understands each step |
| 7 | Mostly correct, minor gaps |
| 4 | Vague explanation, misses key steps |
| 0 | Cannot explain their own code |
Notes: _____________________
| Score | Criteria |
|---|---|
| 10 | Clear reasoning, aware of alternatives |
| 7 | Reasonable explanation |
| 4 | "It just works" / copied without understanding |
| 0 | Cannot explain |
Notes: _____________________
| Score | Criteria |
|---|---|
| 10 | Correct explanation for all |
| 7 | Mostly correct |
| 4 | Struggles with some |
| 0 | Cannot explain basic lines |
Lines asked about: _____________________
| Score | Criteria |
|---|---|
| 10 | Correctly predicts behavior, suggests fix |
| 7 | Mostly correct prediction |
| 4 | Wrong prediction but shows some understanding |
| 0 | No idea |
Edge case asked: _____________________
Ask the student to make a small change on the spot.
(Example: "Add a character limit to the username" or "Change the error message color")
| Score | Criteria |
|---|---|
| 30 | Completes correctly without help |
| 25 | Completes with minor syntax help |
| 20 | Knows the approach, struggles with implementation |
| 10 | Needs significant guidance |
| 0 | Cannot attempt |
Time taken: _____ minutes
Notes: _____________________
Introduce a bug and ask them to fix it.
(Example: Remove a semicolon, change === to =, break a file path)
| Score | Criteria |
|---|---|
| 15 | Finds and fixes quickly |
| 10 | Finds with some effort |
| 5 | Needs hints to locate |
| 0 | Cannot find/fix |
Time taken: _____ minutes
| Score | Criteria |
|---|---|
| 5 | Similar style/complexity to previous assignments |
| 3 | Some improvement (explainable) |
| 0 | Dramatically different (suspicious) |
| Score | Criteria |
|---|---|
| 5 | Solution matches problem complexity |
| 3 | Slightly over/under-engineered |
| 0 | Way too complex for the task |
| Score | Criteria |
|---|---|
| 5 | Reasonable, matches student's usual style |
| 3 | Unusually detailed/perfect |
| 0 | Excessive AI-style documentation |
| Section | Points | Score |
|---|---|---|
| Code Walkthrough | /40 | |
| Live Modification | /30 | |
| Debugging | /15 | |
| Code Quality | /15 | |
| Total | /100 |
- Student demonstrates genuine understanding
- Code complexity matches skill level
- Can modify and debug their own code
- Consistent with previous work
- High - Student clearly wrote this themselves
- Medium - Some concerns but acceptable
- Low - Strong indicators of AI assistance without understanding
- None needed
- Require resubmission with in-class coding
- Schedule additional review
- Discuss academic integrity
- Perfect error handling for edge cases not discussed in class
- Uses advanced concepts (ternary, null coalescing) inconsistently
- Over-commented obvious code
- Cannot make simple changes without looking things up
- Variable names suddenly very descriptive
- Code structure dramatically different from in-class examples
Signature: _____________________ Date: _____________________