The completed workbench derives group routes and station coverage from one three-round grid. It can load the supplied conflict, show S3’s double booking and S1’s empty slot, then restore Green’s round-two destination to S1. The timing stays 42 elapsed minutes, with 18 planned people making 54 participant-station visits.
Declare the planned groups and station capacity
The fictional groups are Amber, Blue and Green, each with six planned participants. Each station is planned for one six-person group at a time:
| Station | Proposed activity | Proposed station lead |
|---|---|---|
| S1 | Paper-pattern matching | L1 stays at S1 |
| S2 | Card-route puzzle | L2 stays at S2 |
| S3 | Paper-design review | L3 stays at S3 |
These are proposed station labels, not completed activities. Actual leaders, materials, space, access arrangements and school approval remain TO CONFIRM. The six-person capacity is a sample assumption, not a supervision ratio or verified room capacity.
TeachEngineering's field-day planning text discusses adapting an event schedule, station leads, concurrent activities and passing time. Those coordination concepts inform this original rotation, not its source event's duration, participant count, competitions or activity rules. Engineering Design Field Day
Use a master grid with transition time
| Planned time | Amber | Blue | Green |
|---|---|---|---|
| R1, 09:00–09:12 | S1 | S2 | S3 |
| Transition, 09:12–09:15 | Planned move to S2 | Planned move to S3 | Planned move to S1 |
| R2, 09:15–09:27 | S2 | S3 | S1 |
| Transition, 09:27–09:30 | Planned move to S3 | Planned move to S1 | Planned move to S2 |
| R3, 09:30–09:42 | S3 | S1 | S2 |
Three rounds of 12 minutes plus two transitions of 3 minutes give 36 activity minutes + 6 transition minutes = 42 elapsed minutes. The block runs from 09:00 to 09:42; it does not represent a full school day. Actual date, local time basis and movement arrangements still require confirmation.
Each round has 18 planned participants, not 54 distinct people. Across three rounds there are 54 planned participant-station visits; the same 18 people account for them. Actual attendance and handoff counts remain blank.
Produce group sheets and station sheets from the grid
The per-group routes are:
Amber: R1 S1 -> R2 S2 -> R3 S3 / Blue: R1 S2 -> R2 S3 -> R3 S1 / Green: R1 S3 -> R2 S1 -> R3 S2
Each group visits each station once. The corresponding station coverage is:
| Station / fixed proposed lead | R1 | R2 | R3 |
|---|---|---|---|
| S1 / L1 | Amber | Green | Blue |
| S2 / L2 | Blue | Amber | Green |
| S3 / L3 | Green | Blue | Amber |
Each station receives one group per round. Leads stay with stations rather than following different groups simultaneously. Confirm actual role acceptance and coverage before labeling the plan ready.
The station sheet also needs task/material references, confirmed lead, actual location, access arrangement, transition check and blank arrival/handoff counts. The group sheet needs its times and destinations. Keep both tied to the same maintained master version.
Repair the conflict before seeking event approval
In a separate flawed variant, change Green's R2 destination to S3. Blue is already assigned there. S3 would receive two groups, while S1 would be empty, violating the one-group-per-station sample.
The correction for this original rotation is to restore Green R2 = S1 and update Green's sheet and the S1/S3 station sheets alongside the master grid. A red conflict flag alone does not repair those destinations or make the event approved.
If regrouping changes the plan later, reconcile all views again. Do not silently carry old destinations or capacities forward. Actual student roster, supervision requirements, space/access checks, weather backup and organizer authorization remain separate confirmations—not implied by a conflict-free table.
Use the group buttons to read a route aloud while a colleague checks the station list. After repairing the example, regenerate every affected view from the same grid. A consistent rotation still leaves actual leads, access arrangements, materials and organizer approval to confirm.
Copy a prompt for this example
Build an original fictional field-day rotation workbench. Amber, Blue and Green each have six planned participants. S1 paper-pattern matching/L1, S2 card-route puzzle/L2, S3 paper-design review/L3; one group per station, leads stay at stations. R1 09:00–09:12 A S1/B S2/G S3; transition3min. R2 09:15–09:27 A S2/B S3/G S1; transition3min. R3 09:30–09:42 A S3/B S1/G S2. Derive group routes and station coverage from the same grid. Show36 activity+6 transition=42 elapsed minutes;18 distinct planned people and54 participant-station visits, never54 people. Conflict button changes Green R2 to S3; flag Blue/Green collision at S3 and emptyS1, and repair button restores Green R2=S1 across all views. Include group selection and reset. Capacity6 is a sample assumption, not a verified room limit or supervision ratio. Actual roster, leads, access, weather backup, materials, counts and organizer approval remain unconfirmed.
Return one complete HTML file. Put the rotation grid, selected group route and station-coverage results together. On a phone, stack the views while keeping round times and group names readable. Give the conflict, repair and reset buttons clear labels, keyboard focus and enough spacing to use comfortably.
Before the organizer briefing, NOS can display this prepared HTML rotation. Load the conflict once to explain the repair, return to the consistent grid, and confirm actual station readiness in the maintained event packet.