A Makerspace Grant in a Fixed Elementary Schedule

Start with the school improvement goal: student talk and argumentation in science. I would co-design three or four curriculum-connected design challenges with grade-level teachers, each with a clear science phenomenon, a constrained build, and a structured talk routine. For example, second graders could design a seed-dispersal model and argue from evidence about which design travels farthest; fourth graders could build a simple circuit and justify component choices. The makerspace would be a station within an inquiry sequence, not a reward. I would retire open-ended 'free build' as the default and keep it as an optional exploration day. I would create a one-page planning template for teachers: phenomenon, standard, build constraint, talk prompts, and reflection. I would also train the aide to facilitate the talk routine, not just manage materials. The grant's six-project requirement should be mapped to specific grade levels and dates so the work is visible and not left to chance.

I would use the fixed 45-minute library block as the delivery vehicle and co-teach with the classroom teacher, rather than adding a separate makerspace time. Each class would come for a three-week sequence: week 1 inquiry launch and build, week 2 test and revise, week 3 argumentation and reflection. The aide would prepare kits and manage checkout; I would handle the instructional design and the talk routine. To avoid losing planning time, I would offer teachers a menu of pre-built sequences aligned to their next science unit, so their planning load is reduced, not increased. I would also use a sign-up calendar with a two-week lead time and cap each sequence at two classes to prevent bottlenecks. If the 3D printer is slow, it becomes a single station with a queue, not the centerpiece. The scheduling principle is integration: the makerspace succeeds when it replaces a worksheet or a lecture segment, not when it competes for time.

Use a mixed-method design tied to the grant's requirements. For the 200-student service count, track unique students by class and project, not just visits. For the pre/post survey, ask three concrete questions about science talk-whether students can explain a claim, give evidence, and listen to a peer's alternative-rather than satisfaction. Add a classroom observation checklist for talk moves during the build and argumentation phases, and collect two student work samples per project scored with a simple rubric. For the first 90-day report, I would report participation, two completed projects, and early pre/post trends, while being explicit that 90 days is too early to claim achievement gains. I would also include teacher feedback on usability and a schedule for the remaining projects. This is credible because it separates implementation from impact and does not overclaim from a small sample.