What is still uncertain?
Record the actual constraint: a device permission, a room, a timetable or an approval.
Bring the people, devices and timetable into one workable plan. Use this guide to identify what is ready, what needs a decision and who can make it happen.
Readiness becomes useful when someone can act on it.
Record the actual constraint: a device permission, a room, a timetable or an approval.
Identify the educator, technology owner, local operations lead or budget contact.
Agree a realistic access test, confirmed schedule or written scope before setting expectations for families.
Open each area and note what your team knows. This guide does not store answers, score readiness, or approve a launch.
Name the grade range, approximate group size, interests, and learning purpose. Identify what a useful first project or pilot would help you understand.
Discuss with: the educator or program lead.Prepare the planning conversationA few clear details are enough to start. Keep student records and sensitive information out of the initial inquiry.
Share the organization, location or time zone, grade range, and the kind of experience you want to offer.
Bring your preferred timing, available devices, local staffing, and any known approval or access constraints.
Identify what you want to compare or clarify. An unknown is a planning input, not a reason to guess.
Review the current school offering before the conversation. Specific tools, delivery responsibilities, access, timing, and pricing need to be agreed for your program.
Read the current school offering↗Bring the people who know the timetable, the learners, and the technology. Start with a planning conversation; confirm commitments only when the scope is clear.