Sprout Ops
Home Students
Engagement Attendance Behavior Family Contact Log Referrals MTSS Plans
Academics Grades On Track / GPA Branching Minds
EL EL
Assessments i-Ready NWEA FastBridge A FastBridge Early Amira / CogAT IAR College Readiness
Staff Classroom Visits
Reports Report Center List Generator Report Files
Other IPST Meetings
Settings
Demo Dashboard/Plan Settings

Plan Settings

Who the plans product emails, how hard it chases a deadline, and who may read or write a plan before it is approved.

Scope
Which settings you are editing, and for which plan type.

The district default. Every school uses these unless it sets its own. A role here resolves against each school separately; a person you name here is emailed about every school's plans.

Email
Each email goes to exactly the people listed on it — two roles that resolve against the plan itself, plus anyone you name. The person who performs an action is never emailed about their own act, whatever is set here.
Plan submitted

A school submits a plan for review. Name the people who actually review them — nobody is emailed until you do.

Who gets this

Nobody is on this email, so it is written and sent to no one. Add a person, or switch the lane off so it stops being generated.

Roles
Quick add — 9 people, by status
District office
Maple ES
Cedar ES
Oakwood MS
Plan approved

The district approves a plan.

Who gets this
School admins The plan's owner
Quick add — 9 people, by status
District office
Maple ES
Cedar ES
Oakwood MS
School admins — resolves to 3 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Deborah Sanchez
The plan's owner — resolves to 2 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Marcus Bennett
Plan sent back

The district returns a plan with a note.

Who gets this
School admins The plan's owner
Quick add — 9 people, by status
District office
Maple ES
Cedar ES
Oakwood MS
School admins — resolves to 3 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Deborah Sanchez
The plan's owner — resolves to 2 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Marcus Bennett
Plan assigned

The district requires a plan of a school — sent when it is assigned and by the announce sweep.

Who gets this
School admins The plan's owner
Quick add — 9 people, by status
District office
Maple ES
Cedar ES
Oakwood MS
School admins — resolves to 3 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Deborah Sanchez
The plan's owner — resolves to 2 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Marcus Bennett
Due-date reminders

Due soon, due today and overdue — the nightly sweep, and the district’s own “Remind” button.

Who gets this
School admins The plan's owner
Quick add — 9 people, by status
District office
Maple ES
Cedar ES
Oakwood MS
School admins — resolves to 3 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Deborah Sanchez
The plan's owner — resolves to 2 people across 3 schools
  • Maple ES — Patricia Nguyen
  • Cedar ES — Marcus Bennett
  • Oakwood MS — Marcus Bennett
Comment digest

You were mentioned in a thread, or you are already in one. Audience is the person themselves, so only the switch applies.

Timing
These were process-wide settings shared by every district. A value here is this district's own; leave one alone and it follows the deployment default.
Reminder send hour

Tenant-local hour the due-date sweep is willing to send. A sweep that runs before this hour sends nothing. Deployment default: PLAN_REMINDER_SEND_HOUR.

hour (0–23)
Overdue reminders stop after

Days past a due date the daily overdue reminder keeps firing before it gives up. Deployment default: PLAN_REMINDER_OVERDUE_MAX_DAYS.

days
Comment digest settles for

Minutes a fresh comment waits before the digest will mail it — a window for the author to edit or delete. Deployment default: PLAN_COMMENT_SETTLE_MIN.

minutes
Comment digest batch cap

How many queued comments one digest sweep claims. A cap, not a rate limit — the rest go on the next tick. Deployment default: PLAN_COMMENT_DIGEST_MAX.

comments
Who can see and edit a plan
Both ship off. Each widens access for staff at the school in question and nowhere else — approving, sending back, archiving and assigning stay district-administrator moves.
Staff may read a plan before it is approved

D9 ships this off: staff at a school read that school’s plan only once it is Active, so a plan being written in August is invisible to the team it describes.

Widens READ for staff at that school only — never another school, and never the district sentinel.

Non-admin staff may edit their own school’s plan

D10 ships this off: authoring is an admin act, so a plain attendance lead cannot fill in their own school’s plan.

Widens EDIT for staff at that school only. Approve, send back, archive and assign stay district-admin moves whatever this says.

Vocabulary
What your district calls each stage of a plan and each compliance state. Wire values, sort order and every gate above are unaffected — this changes only the words shown to people. District-wide, whatever scope you're viewing above.

Plan status

Compliance board

Saved settings take effect within a minute for background sweeps, immediately for pages.
Loading…

Recent Attendance Trend (Weekly Avg.)

No attendance data yet.

Academics

No academic assessment data yet.

Recent Activity

No recent behavior incidents.