Tutoring centers
Draft progress notes and parent updates
Progress updates usually slows down when tutor notes, assessments, lesson plans, attendance, and parent goals do not tell the same story, or when a progress update is due or a parent asks about student movement. Imagine keeps those sources in view, prepares a progress summary, next-step recommendation, and parent update draft, and separates the ready work from the judgment calls. After review, the approved update goes back to the student record and parent thread, so parents hear what changed without tutors writing from scratch.
The manual reality today
-
01
Too many tabs before progress updates can move
tutor notes, assessments, lesson plans, attendance, and parent goals each hold part of the answer, so the team burns time piecing together what happened before they can respond.
-
02
Progress updates can stall until someone notices
When a progress update is due or a parent asks about student movement, the next step can sit until someone checks the right queue, thread, portal, or spreadsheet.
-
03
The progress updates history is hard to defend
Approvals, notes, and updates end up in side channels, making it hard to tell what was sent, what changed, and who signed off.
How Imagine handles it
-
01
Read the progress updates signals
Imagine watches tutor notes, assessments, lesson plans, attendance, and parent goals for new activity, stale items, and changes that affect the work.
-
02
Separate routine progress updates work from judgment
Messages, records, dates, and prior decisions are grouped so the next step starts with the facts already attached.
-
03
Draft the next progress updates touch
Imagine drafts a progress summary, next-step recommendation, and parent update draft using your rules, tone, and thresholds, then flags anything that needs judgment.
-
04
Write the progress updates result back
After review, approved actions are recorded in the student record and parent thread with the context, approver, and timestamp preserved.
Works with the tools you already run
- Teachworks
- TutorCruncher
- Google Docs
- Notion
- Gmail
- Slack
What changes
Decisions around progress updates surface sooner
Prep work and status checks run continuously, so the team sees the few items that actually need a decision.
Progress updates communication feels less random
Each next step follows the same rules and cadence, so customers, clients, candidates, and vendors get a reliable experience.
The progress updates record is easier to explain
Source context, approver, and destination update stay together, so the workflow is easier to audit or explain.
Frequently asked questions
How does Imagine handle progress updates?
Imagine watches tutor notes, assessments, lesson plans, attendance, and parent goals, spots when a progress update is due or a parent asks about student movement, and prepares a progress summary, next-step recommendation, and parent update draft for review. Approved actions sync back to the student record and parent thread with the supporting context attached.
What parts of progress updates can stay manual?
You decide what can move automatically and what needs review. Anything outside your rules is routed to the responsible person before the student record and parent thread is updated.
Which tools feed progress updates?
This workflow can connect to systems such as Teachworks, TutorCruncher, Google Docs, Notion, Gmail, Slack. Imagine works on top of those tools instead of replacing the system of record.
How does progress updates feel different?
The team stops rebuilding status by hand. They open a queue that shows what changed, what is ready, and what still needs approval so parents hear what changed without tutors writing from scratch.