Plan missions or Free Build, prepare the supplies you have, welcome learners, and review their work.
For approved workshop staff with training and access to an assigned workspace. School teachers using classroom accounts should also read the Teacher guide.
What you will learn
Prepare a workshop with the parts you actually have
Open structured missions or Free Build
Help learners join and keep the room moving
Review mission and Free Build records without mixing their outcomes
01
Open Free Build when children are ready to explore
Free Build is the facilitator name for the child-facing Build Something path. It uses the same coding environment without requiring a mission.
1Open it for the room in one action
Open Group Mode, then choose the Workspace, Workshop and current Session. In the Free Build panel, choose Open Free Build for everyone. This is the quickest fallback when a lesson is unavailable; you do not need to edit curriculum first.
The workshop must be Open before children can enter. You can prepare settings while Paused, then Resume the workshop. Children see Build Something on their individual or team workshop home.
Enlarge screenshot:Open Free Build for everyone when the room needs an immediate mission-independent path.
2Choose the access rule
Available anytime keeps Build Something available whenever the workshop is open. Facilitator-controlled lets you choose Every group or Selected groups. Disabled keeps saved builds in the report but prevents new work.
For selected access, tick the named groups, then choose Save Free Build settings. If another facilitator changed the settings first, reload the controls, review the current revision and save again.
Enlarge screenshot:Selected access shows exactly which groups can use Build Something.
3Match the parts to the room
A saved Workshop Kit or Parts Set is shown first. If no kit is configured, the child-safe supported catalog remains available so Free Build can still be used as a fallback.
Children choose parts, use Review your setup for static connection guidance, then choose Open Build Lab. That review does not validate the configuration. The live Test My Parts check is in Build Lab, where it can see the simulator or a connected micro:bit. Physical hardware validation is still pending. In Build Lab, Console, Board Readout, Pins and Parts share the open area below the workspace. Parts has search and Category filters; a child can drag a part to a compatible empty port, or select the part and port, to create its connection and a block with that port filled in. Select a connected port picture to show its controls.
Enlarge screenshot:Setup review gives static connection guidance; it is not a live wiring or hardware test.
4Read Free Build activity separately
The Free Build report totals active projects, distinct children in active build snapshots and active team-owned projects across the whole selected session. The saved-build list below is limited to the newest 100 summaries and says when more exist.
A team project counts once, even when several checked-in children participated. One team with several projects contributes several team-owned builds. Free Build saves and runs do not count as mission submissions or completions.
Closing the workshop preserves the facilitator history but revokes the shared-device team credential. Do not tell a team that an old sign-in will reopen the build in a later session; later-session child or team remapping is not implemented.
Enlarge screenshot:Read Free Build activity separately from mission submissions and completions.
If you get stuck
The lesson or mission list is unavailable.
Keep the workshop open and use Open Free Build for everyone. The Free Build control and child route use an independent service path.
A child says a sensor did not respond.
Treat the starting review as guidance, not proof of a connection. Recheck the pictures, then use the live Test My Parts check in Build Lab with the simulator or a supported connected micro:bit. Use real hardware only with adult supervision and separate physical qualification.
Group Mode gives each team one workspace. Every child still checks in individually.
1Choose the workshop session and prepare its teams
Open Group Mode and choose Workspace, Workshop and Session. Use Schedule or manage workshop sessions if you need to create a session, then Refresh session choices. Choose Set up Group Mode for a session that has no team setup yet.
Open Team setup and reusable Group Sets. Keep Participation mode on Group Mode, review the preferred and allowed group sizes, then use Auto-assign unassigned children or Add an empty group. In Mission Control, choose Children to review and change each child's Group.
Enable Let children create teams from suggested names only if children should form teams themselves. Offer an individual reflection after group work is optional.
2Save a reusable Group Set
Enter New Group Set name and choose Save current groups as a Group Set. Use Group Set opens a saved-membership preview. Choose Use the same groups to apply an independent copy, or Review and make changes to apply a copy and open session setup. Review assignments before children begin; later edits to the saved plan do not rewrite earlier sessions.
Rename Group Set, Duplicate Group Set and Archive Group Set manage your saved plans. Archive asks for confirmation and leaves existing session copies intact. Create new groups from this roster opens session setup without changing existing teams or saved plans. Use Auto-assign unassigned children or Add an empty group to make the new arrangement. To change a saved membership plan, arrange children in the session and choose Update Group Set from current groups, or save the reviewed arrangement as a new Group Set.
3Check readiness and welcome the children
Review Workshop Readiness, expected shared laptops, the selected Workshop Kit and each mission's material requirements. Resolve Needs attention items and make an intentional plan for warnings, shared equipment or Hardware Stations. Use Review Groups, Review Kit or Review mission to reach the affected controls.
For Shared-device flow available, open the check-in page in a new tab. Confirm that it loads, then select I checked that the team sign-in page opens. This rehearsal does not sign in a child or record attendance.
Use Choose a mission on each group card, then Assign mission to group. Open workshop when preparation is ready, and use Open team check-in on each shared laptop. Each child uses their own sign-in details; one child checks in first and Add teammate brings in the others.
Enlarge screenshot:Current Mission Control with fictional workshop data.
1Switch between group work and individual attendance
Mission Control starts with Groups. Read each team's present count, laptop state, current mission, stage and submission status. Read group work and feedback opens the saved answers and tool-choice explanation.
Choose Children to inspect individual attendance, team assignment and reflection counts. Change Group to correct a wrong assignment. Correct Attendance for an absent or late child; Mark left records departure. Add a late-arriving child from the workshop roster appears when an enrolled child is not yet in this session. On a narrow screen, scroll the Children table to reach attendance and recovery controls; the controls also work with the keyboard.
Enlarge screenshot:Individual attendance stays separate from the team workspace. This picture uses fictional guide data.
2Help, review and revise once per group
Use Response to group and Resolve help request to answer the team's question. Dismiss duplicate request closes a duplicate without creating extra work.
For a submitted workspace, enter Feedback or revision request. Choose Return for revision when the team needs to improve, or Mark group mission complete when its work meets the mission. Reopen for revision requires a reason and keeps the earlier submission history.
3Recover a laptop or change a team
Open Manage or recover for the affected group. Release laptop for transfer asks for confirmation, keeps saved work, and lets the children check in on a replacement laptop. The old laptop cannot continue writing as that team.
Rename group and Save equipment label help identify teams and trays. Split selected children leaves the original team's work in place and gives the new team an empty workspace. Merge groups keeps earlier projects with their original groups and continues the group you selected. Review these choices with the children first.
If you get stuck
A child is not on the workshop roster.
Use the existing authorized roster and individual credential flow in Workshop access first, then add that child to this session. Do not lend another child's identity.
The workshop changed while I was editing.
Choose Refresh workshop and review current state before retrying. Do not repeat a different action under an old request.
Workshop participation keeps Children enrolled, Children attending, Groups active, Group projects, Group submissions, Group completions and Individual reflections separate. Four children who share one submission are four participating children and one submission.
Use Export workshop report for the structured session report. It includes attendance, membership, group work status, revisions, help, tools and reflection completion. It does not include child PINs or individual reflection answers.
Close workshop after reviewing incomplete work and pending revision; closure preserves history and cannot be undone. Have each team choose Sign out this laptop before another team uses it. For the next session, apply a saved Group Set and review the new session's roster, kit and curriculum again.
In Workshop access, select your Verified workspace. Enter a Workshop name in Create a workshop. Add Starts and Ends if useful; both are optional.
Choose Create workshop. The new workshop becomes the selected workshop. Choose Choose Workshop Parts to open the parts editor. Your staff profile is assigned to it automatically.
Enlarge screenshot:Workshop creation belongs to the selected workspace; a session is scheduled separately.
07
Build a reusable kit
You do not need a premade kit. Start with a person and problem, then choose hardware, tools and materials that help the group investigate it.
1Save a kit for repeated workshops
Open Kit Studio, select your workspace and choose Create kit. Enter a Kit name and Description. Choose the Hardware platform when your kit includes electronics.
Use Add hardware from Parts Library for reviewed hardware. Add familiar tools and materials with the quick-add buttons, or choose Add custom item for local supplies such as recycled cereal boxes. Record the actual quantity and any preparation or supervision notes.
Choose Save reusable kit. The kit belongs to your staff profile in this workspace. Edit it for future use, Duplicate it for another plan, or Archive it when you want it hidden from the active list. Restore makes an archived kit available again.
Enlarge screenshot:Current Kit Studio interface with fictional workshop data. Choose the supplies you can actually provide.
In Workshop access, choose your workspace and assigned workshop, then open Plan workshop kit. Choose Use a saved kit, select the kit, review it and choose Use for workshop. You can also choose Build a workshop kit without saving a template first.
Edit workshop kit changes this workshop's copy. Add or remove supplies, confirm quantities and choose Save workshop kit. Save as reusable kit makes a new template from the workshop copy.
Changing a reusable kit later does not change workshop copies already made from it. Applying a kit again replaces the current workshop selection, so review it first. Other workshops and previously opened sessions keep their own copies.
Workshop Parts is the hardware view of your workshop kit. Use it for exact electronics, connection support and hardware lesson checks. Add scissors, paper and other local materials in the workshop kit.
1Find and select the available parts
Open Edit Workshop Parts for the selected workshop. Choose the Workshop platform, then use Search Parts Library, Category or KidsEngine support to narrow the list.
Select each available part. The card shows the technical name and child-friendly name. Check safety and supervision notes as you choose.
Enlarge screenshot:Search by name or capability; select only tools you can supply.
2Check quantities and save
Review Selected for this workshop. Set Quantity available where you know it, add a teacher note if needed, and remove anything unavailable.
Choose Save Workshop Parts and wait for the saved result before leaving. Open sessions keep their saved materials; these edits prepare future sessions.
Enlarge screenshot:Saved hardware prepares future sessions. Each opened session keeps its own materials for assignments and learner tools.
If you get stuck
The editor says parts changed elsewhere
Refresh the current parts, review the other changes, then reapply your intended edit. Avoid overwriting a colleague’s saved inventory.
A selected part does not support the platform
Remove the incompatible selection or choose the correct workshop platform before saving.
10
Check materials and quantities before assigning
1Read the mission's complete requirements
In Workshop access, choose Browse compatible curriculum, then Plan mission materials. Search the mission library by title or ID, or switch Mission source to Workspace missions.
Required items need enough available quantity. Optional items do not block readiness. For Choose one alternative, supply one complete option in the group. An unconfirmed quantity is not proof that enough stock is available.
Use Add item × N or Set item quantity to N only when those supplies are available for this workshop. The saved workshop copy and readiness result update here. Compare a saved kit previews another reusable plan without editing it or your workshop.
Enlarge screenshot:Actual mission planning for a fictional workshop. Review previews are labelled, and missing supplies remain explicit.
Choose Browse compatible curriculum in Workshop access. Start with Ready with my parts. Use the other views to inspect lessons that need additional parts.
Read each readiness label and any Missing requirement. Optional parts do not block a lesson. Only use Add for a missing part when that part will really be available; otherwise choose another lesson.
Enlarge screenshot:Readiness uses the saved platform and Workshop Parts, not an assumed complete kit.
2Read missing requirements before changing the inventory
Open Almost ready to see the missing requirement for each lesson. Choose a different lesson if you cannot supply it. Only add a part to the saved inventory when it will actually be available.
Enlarge screenshot:Missing requirements show the specific tools that still need to be supplied.
3Prepare the assignment and sequence
Open Curriculum management, choose a mission and open its assignment page. Select Teacher workspace and Class or group, then choose the pathway, participation modes, group size, required evidence and Teacher notes.
Set Available from and Due at where needed. Save assignment draft while preparing. When a workshop session is open and the parts check succeeds, choose Check inventory and assign.
In Mission playlists, enter Playlist title, choose First mission, select Assign to classes, then choose Create playlist. The editor lets you change existing item titles, use Move up or Move down, Remove an item and Save playlist. Duplicate makes a separate copy. Continue assigning new missions through the curriculum workflow; this editor does not have an add-item control.
Enlarge screenshot:An active assignment is tied to the chosen activity version and workshop context.
Start with the participant and design question. Choose only the tools needed for the core mission and any optional investigation your group can use.
1Save the exact models and check readiness
In Workshop Parts, set KidsEngine support to All support levels so the Grove Shield accessory is visible. Select micro:bit, Grove Shield for micro:bit v2.0, the exact Grove modules, and real quantities. Distinguish Light Sensor (P) from the older photoresistor and the rotary angle knob from the encoder. Save the Parts Set.
Use Compatible curriculum to check Ready with my parts and Missing requirement. The optional tool investigations in a lesson do not block its core mission. Check their own minimum age, connection instructions, and limits before choosing one.
Enlarge screenshot:Save only the models and quantities actually available for this workshop.
2Check the physical route and socket budget
Use sentence-like examples: light level at socket [P0/P14], when button at socket [P1/P15] pressed, and distance in cm at socket [P0/P14]. Have learners choose the socket matching the physical shield label before running or uploading.
Signal modules use P0/P14, P1/P15, or P2/P16 as offered. Gesture and acceleration use I2C/P19/P20. The encoder and Heelight serial module each occupy both signals of their selected socket.
Turn off power before changing Grove cables.
For multiple compatible I2C modules, use the Connection Hub and distinct addresses. It does not multiply analog or digital capacity. Keep the joystick physical route gated on its qualified two-signal adapter. Check power and module-specific preparation in the hardware guide; software simulation does not establish bench verification.
3Demonstrate the actual controls and stop behavior
Demonstrate when gesture [Wave] at socket [I2C], using No gesture between identical simulated gestures. For when Heelight at socket [P1/P15] hears code [12], receive 12 twice and then a different code; only the two matching arrivals run the handler. Sound Sensor and Loudness Sensor provide relative levels, not speech or calibrated decibels.
Demonstrate button A → vibrate at socket [P1/P15] for [500] ms and button B → stop vibration at socket [P1/P15]. Timed vibration schedules a stop while following blocks continue. Confirm comfort before a real trial and provide a visible or partner-operated alternative. Physical timing depends on the program servicing its event loop.
For Turn Dial, use reset dial position at socket [P1/P15] to set a healthy delivered position to zero. Reset does not remove pending turns or recover lost tracking; restart the program after a tracking fault.
4Review the learning evidence
Ask learners for three comparable trials, one unexpected or unavailable reading, participant feedback, and a tested revision. Include raw observations and honest units; environmental sensors do not provide health or safety decisions.
Review saved blocks and simulator evidence with the project Test and Remix notes. Distinguish a simulated result from a supervised physical observation. Return specific feedback when a comparison or limitation is missing, then review the resubmission before marking the project completed.
Confirm the selected workspace and workshop. Count the hardware, tools and materials on the tables, update the workshop kit, then check the exact mission's required quantities and alternatives in Plan mission materials.
Check your roster, learner access method, activity instructions, required evidence and due date. Confirm your session timing and connectivity plan. Finish kit changes before the session's first Open, which freezes its materials for assigned work.
In Mission Control, use Setup. Select Activity assignment, set Duration (minutes) and Team size, then choose Generate and save setup. It uses that assignment's saved session materials. Review Groups and roles and Materials, safety, display, and evidence before the learners start.
Enlarge screenshot:Keep the learning goal, safe materials and evidence expectations visible before the session.
14
Review the opened session’s materials
1Read the exact saved session copy
From the assignment page, choose Open session readiness and reset mode. Select Workspace, Class or workshop, and Open workshop session. Read Session materials for hardware, tools, everyday materials and custom supplies.
The listed quantities and notes belong to the saved opening kit. Later workshop changes prepare future sessions. If supplies change during class, help learners adapt safely without rewriting the opening record.
Use Age controls to review the selected activity’s adult guidance. Follow the Session reset checklist when putting away the supplies.
Enlarge screenshot:The opening kit remains unchanged when the future workshop copy is edited.
1Repeat the preflight for each week's investigation
Use one recognizable program kit as a reusable starting plan. The eight-week shared-spaces sequence moves from listening and observing to building, testing, feedback, revision and a final demonstration.
Before each class, open that week's workshop copy and mission. Count supplies for the 20 learners and planned teams, replace used materials, and check required items, optional investigations and alternatives. A ready result for last week's mission does not prove this week's quantities.
Check people and problem first, then the mission's evidence goal, learner access and safety notes. Open the session after this review, assign its mission, and retain its saved project and material record. Update future workshop copies when the program kit changes.
Do I need to buy a premade kit? No. Use suitable supplies already available, add custom local materials, and choose missions that fit them. Hardware is needed only when the mission requires it.
Will editing a saved kit update every class? No. A saved kit is a reusable template. Workshop copies and material records frozen at a session's first Open stay independent.
What if something is missing? Before opening a session, record the available quantity or choose a suitable alternative in mission planning. If an opened session's supplies change, ask the lead adult to adapt the activity safely; editing the future workshop kit does not rewrite that session's history.
In Workshop access, use Add a workshop participant. Enter a Workshop alias and optionally an Age band and Locale, then choose Add workshop participant.
This creates an alias-only profile and generated ID. It does not issue a sign-in credential. To add an existing learner, use Existing generated learner identifier and Add generated ID.
Enlarge screenshot:Use an alias suitable for the workshop; the roster is scoped to the selected workshop.
2Issue a private PIN or one-time workshop token
Find the correct generated learner in the roster and choose Issue/reset PIN or Mint workshop token. Read the named learner and confirm the credential action.
Follow the one-time reveal instructions. Share the credential privately with that learner or their supervising adult, then clear the reveal. Learners use the workshop PIN or QR/token entry shown to them.
If a reveal is lost, start a fresh confirmed credential action. Use unused-token revocation when a token should no longer be accepted.
Enlarge screenshot:Confirm the intended learner before issuing access. The guide does not display usable credentials.
Open Mission Control and choose the correct Workspace and Class. Under Session controls, fill Session title, Starts, optional Planned end and Connectivity plan. Choose Schedule session.
Find the scheduled session and choose Open. Wait until the session row says Open. Return to your mission assignment, select this open session and finish Check inventory and assign if you prepared a draft.
Give learners their private join instructions. Use Roster to watch attendance and sign-in status as they arrive.
Enlarge screenshot:Opening a session and assigning a mission are separate actions.
Use Roster to check who has joined. Current project state shows each team, learner alias, activity, stage, project status, help and last save.
Choose Help queue to jump to Who needs me? Use the project and learner context to decide where to go next. Review saved blocks opens the saved code for that project.
Mission Control reports explicit saves, evidence and help requests. A quiet card is not a measure of attention or emotion.
Enlarge screenshot:Use saved state and requests to support learners without ranking them.
20
Respond to a help request
1Read the request and visit the learner
When a learner asks for help, their request appears in Who needs me? Read the category and summary, then match it with their current project context.
Help the learner with the next practical step. Choose Resolve once the request is addressed. The request moves to recent history; Reopen restores it if more help is needed.
Move first changes the priority. Dismiss removes a request that does not need a response. These controls manage the request; they do not send a chat reply.
Enlarge screenshot:Each request reflects an explicit request for support.
2Confirm the learner can continue
Check that the request is resolved in the queue history and ask the learner to continue. If the request was resolved by mistake, choose Reopen.
Enlarge screenshot:Resolved requests remain recoverable through Reopen.
21
Pause and resume
1Pause the session for a room-wide stop
In Session controls, choose Pause on the open session. Wait for Paused. Tell learners to keep their work open while you resolve the interruption.
Choose Resume when the room can continue. Wait for Open before learners retry saving or requesting help.
Enlarge screenshot:Paused sessions can resume; closed sessions cannot.
22
Inspect a learner’s work
1Follow the project’s evidence
Find the learner in Current project state. Use Review saved blocks to inspect their saved code when available.
For submitted work, open Workshop Missions project records and choose Workspace and Group. Read the intended user, problem, design criteria, test evidence, failure, revision and next step.
Open versioned evidence to inspect saved versions and structured tests. Use what was recorded to guide your discussion.
Enlarge screenshot:The project record keeps the learner’s saved design-cycle evidence together.
In Workshop Missions project records, find a Submitted project. Read its evidence before choosing a review action.
In Reviewer feedback, name what worked and one concrete next step. Decide whether the learner needs a revision or the work is ready to complete.
Enlarge screenshot:Review actions are available for submitted projects.
If you get stuck
The queue is empty
Confirm Workspace and Group, then check whether the learner submitted. Saving a project does not submit it.
24
Return work for revision
1Send feedback and wait for resubmission
Enter actionable Reviewer feedback and choose Return for revision. Wait for Project returned for revision with feedback.
The learner returns to their project, makes changes and submits again. Refresh the correct project record and review the new evidence before completing it.
Enlarge screenshot:A returned project needs the learner’s changes and a new submission.
If you get stuck
Return for revision is unavailable
Read the explanation beside the control. A closed assignment, elapsed deadline or unavailable workshop can prevent the learner from revising; resolve that condition before requesting changes.
25
Mark the project completed
1Finish the review when the evidence is ready
After reviewing a Submitted project, add final Reviewer feedback and choose Mark completed.
Wait for the completion notice and Completed status. The historical activity and project versions remain preserved. Completing a project does not close the workshop session.
Enlarge screenshot:Project completion records the review outcome for this work.
26
Prepare Demo Day and sharing
1Open the authorized class view
Open Demo Day from Mission Control and select the class you intend to present. Review the presentation preview and redaction controls before showing it to the room. Check the required sharing consent; completing a project does not make it eligible to present.
Use BuildShare for the separate publication-review workflow when sharing is available. Project completion is not permission to publish a learner’s work.
If the selected class shows a load error, use Try again. A failed load does not mean there are no projects.
Enlarge screenshot:Review the selected class and presentation protections before presenting.
Ask learners to save and submit any finished work first. In Setup, review the End-of-class record, add a Next-session note and choose Save end-of-class record where a setup exists.
In Session controls, choose Close on the correct session. The current UI applies this directly without a second confirmation. Wait for Closed and check the session title.
Closed sessions have no Resume action. Closing does not submit unfinished projects or mark them completed.
Enlarge screenshot:Check before choosing Close: the session cannot be resumed from this control.
28
Review the workshop afterwards
1Use the saved records for reflection
Return to the same Workspace and Class in Mission Control. Review current project states, resolved and open help, staff observations and any saved end-of-class note.
Use Complete class record totals and Browse complete project history for saved projects beyond the recent list. Review submitted, returned and completed records in Workshop Missions project records.
Where a workshop rehearsal report exists, read its explicit scope and dates. A missing report is not an empty class result. Use these records to plan the next session without treating them as attention or ability rankings.
Enlarge screenshot:Post-workshop information comes from saved projects, evidence, observations and requests.
29
Recover from common interruptions
1Return to the correct saved workshop
After a browser restart, sign in through workshop staff entry, select the same Workspace and Class, then check Session controls. Use Refresh now to confirm durable session state.
If a learner cannot join, check their workshop, identifier and credential. Reset only the intended learner’s PIN or issue a fresh confirmed token if needed.
If the network drops, keep unsaved work open. Reconnect, check whether the session is Open and retry the action. Do not treat an error or missing receipt as proof of a save.
Before opening a session, update the workshop kit and check compatibility if supplies are missing. For an open session, help learners adapt safely; plan replacements for a future session.
Enlarge screenshot:Refresh the selected workshop before continuing after an interruption.