Dashboards, scheduled reports, and finance insights
Role based dashboards, a catalog of operational reports, and finance insights with charts, giving leadership visibility without exporting spreadsheets every Monday morning. Principals and heads need answers fast: How are collections? Which classes have attendance dips? Is admissions on track? Schoolyi surfaces setup checklists, operational report catalogs, finance charts, and deep links into the modules behind each number - so leaders act on data instead of assembling it by hand.
Outcomes
Practical results schools report after rolling out this area on the shared calendar and roster.
Leadership sees school health at a glance on day one
Scheduled reports replace manual weekly exports
Finance charts highlight cash flow and spend patterns
Click-through from a metric into the module that owns it
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
Principals and heads need answers fast: How are collections? Which classes have attendance dips? Is admissions on track? Schoolyi surfaces setup checklists, operational report catalogs, finance charts, and deep links into the modules behind each number - so leaders act on data instead of assembling it by hand.
Role based dashboards, a catalog of operational reports, and finance insights with charts, giving leadership visibility without exporting spreadsheets every Monday morning. Because Reports & insights shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this module, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
Focused pages for evaluators comparing specific reports & insights workflows during an SMS rollout.
Workflow
A typical path from setup through daily use on Schoolyi.
Part of the Reports & insights workflow on Schoolyi, connected to roster, calendar, and role permissions.
attendance, fees, admissions, grades, rosters
Part of the Reports & insights workflow on Schoolyi, connected to roster, calendar, and role permissions.
cash flow, spend by category, vendor aging
Deep dive
Long-form context for evaluators comparing modules during an SMS rollout.
Principals and heads need answers fast: How are collections? Which classes have attendance dips? Is admissions on track? Schoolyi surfaces setup checklists, operational report catalogs, finance charts, and deep links into the modules behind each number - so leaders act on data instead of assembling it by hand.
Role based dashboards, a catalog of operational reports, and finance insights with charts, giving leadership visibility without exporting spreadsheets every Monday morning. Because Reports & insights shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with reports & insights and share the same calendar, roster, and role model.
Straightforward answers for visitors evaluating the product.
Principals, Leadership, Finance heads run daily workflows in this module while leadership reviews dashboards and exports when needed.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Dates, working days, and class structure flow from the shared calendar so downstream modules do not maintain parallel date lists.
Set the academic calendar before enabling dependent workflows, then test one holiday and one working-day exception against the resulting attendance or exam view. Keep the school’s local policy as the authority for edge cases.
Schools often launch admissions, roster, and fees first, then add this module when the foundation data is stable.
Choose the next phase only after the team has reconciled one complete operating cycle. Record the data, role, calendar, and support dependencies before widening access.
Role-scoped workspaces show only the tasks each team needs. Most schools run a short coordinator session plus self-serve docs.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
We'll show how this module fits your school's workflows and which teams benefit first.
Already using Schoolyi? Sign in
