FICTIONAL SAMPLE
AI CONCIERGE FOR SCHOOLS
More time for teachers.
More room for students.
From staff training to school policies and parent communication. Shape an approach to AI that fits your school.
See the support process
FICTIONAL SAMPLE
School AI usage guide (draft)
FICTIONAL SAMPLE
Parent information sheet (draft)
Fictional sample materials. AI-generated photo · not actual staff.
SOLUTION
Choose support around your school’s needs.
Explore draft deliverables and the review steps that stay with teachers. Scope is agreed individually.
All examples are fictional, not case studies or guarantees. This demo does not send information to an AI service.
Learn the basics. Try them in lesson preparation.
Explore a practical task after learning how generative AI works. Teachers review and adapt every draft to their school’s policies and classroom needs.
Prepare the brief
Lesson goals and constraints
- Year group: Grade 8 (fictional)
- Subject: language arts
- Topic: expressive writing
- Goal: notice choices in expression
Fictional inputs
Review a draft
Staff workshop worksheet
Create an opening question.
“How does the impression change when we describe the same scene differently?”
Choose an expression in groups and discuss why it works.
Sample · not approved
Teacher review
Review checklist
- Rewrite in your own words
- Adapt difficulty to the students
- Check timing and lesson objectives
Connect the opening question to a familiar experience.
FLOW
Start small. Build a school-wide approach.
Begin with one task, review it with teachers, and adapt the approach before expanding.
01Clarify the need
Review current tasks and agree on a priority.
02Train and try
Explore agreed tasks in staff workshops.
03Review at school
The school reviews drafts, rules and outputs.
04Support adoption
Refine procedures and the agreed support arrangements.
Illustrative sequence. Deliverables, session counts, timing and ongoing support are specified in the proposal.
SCOPE & RESPONSIBILITY
Scope and responsibilities
Support covers AI usage policies, staff training, implementation and adoption. It does not include full outsourcing of school administration or automated replies to parents.
Y Technologies
The sales brand and customer contact. We clarify your needs, scope, quotation and next steps.
FwAI
The provider responsible for delivery and project management. Any information sharing with third parties must be clarified beforehand.
Your school
Retains final decisions and approval over tasks, tools, information and outputs. A school contact, reviewer and approver need to be assigned.
LET’S START WITH ONE TASK
What would you like to explore first?
Bring your questions. We will clarify the scope, responsibilities and next steps together.
Do not send student personal data or internal documents through the inquiry form.

Learn together ↗
Training + one-to-one review

Stay connected ↗
Chat + practical update notes

Make it usable ↗
Reviewed drafts + workflow design
01 / TRY THE WORKFLOW
From a question to something you can review.
Interactive reconstruction using fictional data. These screens do not call a live integration.
A staff training notice
Fictional school: prepare a staff training notice. The date is unconfirmed. Include no pupil information.
What is implemented, and what is a sample?
Implementation evidence: local code and synthetic tests exist for research-to-draft, weekly HTML/PDF reports, and multilingual post/image preparation with approval gates. Live integrations are not validated. This walkthrough is a reconstruction, not a recording of those systems.02 / LEARN, DISCUSS, TAKE ACTION
Staff training, made concrete.
01 · Remove sensitive data
Fictional school: prepare a staff training notice. The date is unconfirmed. Include no pupil information.
Text-based lesson storyboard, not a recorded training video. Learn research, editing preparation and analysis; a finished-video production pipeline is not promised.
One hour. A written next step.
- 00–15 Clarify one workflow
- 15–40 Review a safe example together
- 40–60 Agree owner, checks and next action
A consultation-format example. School meeting frequency and duration follow the agreed education scope.
03 / BETWEEN MEETINGS
Useful updates, with a next step for your team.
Before using a new AI workflow
Keep sensitive data out, mark unknown facts, and put human review before sharing.
A school notice must not introduce pupil data or unconfirmed dates.
Try one fictional example with this checklist ↗What should we do with a detail we cannot verify?
See what the support can leave behind.
Review checklist
- ✓ Approved input only
- ✓ Facts checked against sources
- ✓ Human sign-off before sharing
What you take away
An editable outline to review together, not a claimed customer deliverable.
School support follows the existing education scope; page production is a separate scope discussion.
Review scope and commitment →Keep the agreed school scope
Education has separate plans and annual-contract reference terms. Meeting cadence, chat support and training scope must be agreed for your school.
Existing school pricing and scope →A PRACTICAL TAKEAWAY
Staff AI use and workflow checklist
An original, reusable worksheet—not a personalised audit. Preview its outline below; after a successful enquiry you can open or download the full guide here on the site. No additional email subscription.
What is inside?
- A safe input checklist
- A reusable prompt and fictional example
- Human review, exceptions and a next-step worksheet
