A SCHOOL-DAY EXAMPLE
One need.
A connected week.
BASAAS prepares the planning outputs that move work forward. Follow the information as it becomes a support plan, a proposed schedule and a progress report.
Fictional example · Sample student · Grade 6
01 / MONDAY
Identify needs
Bring priorities into focus.
The coordinator has a few minutes between student check-ins. A math teacher has noted difficulty with fractions and two incomplete assignments. The team needs a clear starting point for follow-up.
Review the resource matches →THE CONCRETE OUTPUT
- What is known
- Two incomplete assignments; fraction practice needs review.
- What needs a conversation
- The reason for incomplete work has not been established.
- Support to review
- Small-group math support and guided homework practice.
- Immediate next step
- Check the student’s perspective and review available support.
02 / TUESDAY
Draft and coordinate
Prepare plans and align support.
Staff return to the work between other duties. The draft brings the goal, selected support, responsible role and next review together. A common availability window becomes a proposal.
Edit the sample plan →THE CONCRETE OUTPUT
- Goal
- Two guided practice sessions and review of independent attempts.
- Selected support
- Small-group math support; guided fraction practice.
- Proposed session
- Wednesday, 1:30–2:00. Monday protected instruction is excluded.
- Responsible role
- Support coordinator; math teacher reviews skill evidence.
03 / FRIDAY
Generate reports
Share progress and next steps.
The team meeting starts with a concise update. Staff can see what was completed, which evidence is missing and who owns the next action.
Open the progress report →THE CONCRETE OUTPUT
- Participation
- Two practice sessions completed; one tutoring session attended.
- Evidence still needed
- New independent attempts before judging progress on the skill.
- Next action
- Math teacher reviews attempts; coordinator confirms the next window.
- Team decision
- Continue or adjust support after reviewing the available evidence.
WHY THIS MATTERS
Work that continues
between interruptions.
The information carries into the next step: fewer repeated explanations, less document assembly and a clearer handoff for the team.
Outputs from this example
Repeat this workflow throughout the month: the Sapphire scenario includes 40 plan drafts, 30 reports and 60 scheduling tasks, alongside daily workflows for eight active staff.
See the 110-hour / $6,600 monthly illustration and assumptions →
- A resource shortlist with next actions
- An editable support-plan draft
- A proposed availability-based schedule
- A progress report and follow-up responsibilities