Student Engagement
Student-Led Learning: Run a Bounded Student-Directed Task
This is an implementation guide for running a bounded student-directed task after valid choices have been designed. It does not repeat the broader explanation of agency. The teacher still supplies necessary direct instruction, protects access and safety, sets common criteria, and acts when checkpoint evidence is late, incomplete, or misleading.
Decide whether a student-led structure fits
| Condition | Decision |
|---|---|
| Students can use the required knowledge and routine with available support | A bounded choice of topic, route, role, or format may be appropriate. |
| A concept, safety procedure, tool, or response routine has not been taught | Teach it directly before releasing the task. |
| Routes do not produce comparable evidence | Revise or remove the unequal route. |
| A student misses a milestone or requests help | Add instruction, reduce scope, change support, or schedule another checkpoint; do not wait for the final product. |
Record teacher-retained responsibilities
- State the learning objective, common evidence, and assessment criteria.
- Teach prerequisite content, routines, tool use, and help-seeking.
- Provide every required accommodation, language support, and accessible route.
- Approve materials, technology, privacy, safety, and collaboration boundaries.
- Set milestones, review individual evidence, and make final instructional and assessment decisions.
Run the route-equivalence check
For every route, ask whether students address the same objective, use evidence of comparable depth, receive an accessible way to respond, and meet the same deadline and criteria. A poster, paragraph, model, presentation, or recording is not equivalent merely because each is a product. Remove a route when its format changes the construct or its workload cannot be made proportionate.
Set the milestone schedule and individual evidence
| Point | Required individual evidence | Teacher decision |
|---|---|---|
| Launch | Chosen route, first step, needed support, and feasible scope | Approve, narrow, or supply instruction |
| Checkpoint 1 | Question or claim plus first source, example, calculation, or observation | Continue, model, replace a source, or revise the plan |
| Checkpoint 2 | Draft section and explanation of progress or obstacle | Continue, add support, reassign a role, or reduce scope |
| Exit | Final response plus brief evidence-based review | Accept, request revision, reteach, or end the route |
Plan collaboration roles without hiding individual work
Record each role, the contribution it produces, the evidence owned by each student, and the handoff between roles. Rotate or revise a role when it blocks access or supplies no evidence of the objective. A group product may accompany, but should not replace, the required individual evidence used for a consequential judgment.
Teach a help-request procedure
- Name the exact task step.
- Show what has already been tried or completed.
- Identify the point of confusion, missing resource, access barrier, or group problem.
- Request a model, explanation, material, role change, deadline review, or conference.
- Record the agreed next step and checkpoint.
Use a checkpoint conference script
Teacher: “Show the evidence due at this checkpoint. Which part meets the criterion? What is incomplete or blocked? What support have you used? The next required step is ___. We will check it on ___.”
Student: “My current evidence is ___. The obstacle is ___. I need ___, and I will bring ___ to the next checkpoint.”
Respond to a late or incomplete checkpoint
Do not treat lateness as proof of motivation, responsibility, or ability. Check instruction, task size, access, approved technology, group dependency, absences, and workload. Then choose a proportionate response: teach the missing step, narrow the route, provide an individual alternative, revise the milestone, or return temporarily to direct instruction. Apply applicable school requirements and student plans.
Check workload and feasibility
- Estimate teacher review time and student work time for each route.
- Confirm that required materials and approved tools are actually available.
- Keep out-of-class work within local expectations and provide an in-class route.
- Limit the number of formats and checkpoints to what can be supported well.
- Stop or simplify a route when monitoring cost exceeds its instructional value.
Completed example: four-day local-source explanation
Objective and routes: Students explain how two local planning decisions affected one public space using two teacher-approved sources. They may submit an 800-word illustrated explanation or a four-minute narrated slide sequence. Both routes require the same claim, two source citations, comparison, and limitation.
Day 1: The teacher models source attribution and supplies six approved sources. Each student submits a question, route, two sources, and one-sentence claim. Unsupported or overbroad claims are revised before work continues.
Day 2: Each student submits one cited paragraph or one narrated slide with a transcript. The teacher checks source fit, explains any missing reasoning, and records help requests. Group members may divide source notes, but each student owns a claim-and-evidence record.
Day 3: Students exchange feedback against the common criteria, revise, and submit a second checkpoint. A student whose technology fails uses the in-class paragraph route without losing access to the objective.
Day 4 and exit: Students submit the final response and identify one supported conclusion and one uncertainty. The teacher decides accept, revise, or reteach from the individual evidence, not presentation polish or group participation.
Blank implementation record
Task and learning objective: When direct instruction is required: Teacher-retained responsibilities: Student decisions: Route-equivalence result: Milestone dates and required individual evidence: Collaboration roles and individual contribution: Help-request route: Checkpoint conference decision: Late/incomplete checkpoint response: Workload and feasibility check: Exit evidence: Continue, revise, reteach, or stop: Reason:
Make the exit and review decision
Compare the final individual evidence with the objective and milestone record. Continue the structure only when routes remained equivalent, required support was available, checkpoints informed decisions, and workload was feasible. Revise, narrow, return to direct instruction, or stop when those conditions did not hold.
What changed: Rebuilt this page as a bounded implementation guide with route equivalence, milestones, individual evidence, help procedures, workload checks, a multi-day example, and an exit decision.