Release is a decision
A publish action should be visible, deliberate, and reversible or reviewable according to school policy.
Implementation guide
Prepare exam data, permissions, moderation, report-card templates, and family communication before results release day. See the workflow, ownership, rollout sequence, and boundaries before choosing a school management platform.
At a glance
Prepare exam data, permissions, moderation, report-card templates, and family communication before results release day.
Use the linked product and documentation pages to validate the workflow against your school’s data, roles, policies, and deployment.
Read the supporting materialHow it works
A clear sequence makes ownership, exceptions, and the next system action visible.
Confirm session, subjects, grading scale, venues, roles, and report-card templates.
Check missing marks, outliers, moderation decisions, remarks, and student eligibility.
Record the controller or committee decision to publish the completed result set.
Publish, generate outputs, notify families, and monitor portal access and support questions.
Practical artifact
Copy these checkpoints into a kickoff, vendor demo, or readiness review.
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.
A publish action should be visible, deliberate, and reversible or reviewable according to school policy.
Tell families when results will appear, where to download them, and how revaluation questions are handled.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Straightforward answers for visitors evaluating the product.
The release pattern depends on the configured exam workflow; decide whether the school needs cohort, subject, or session gates.
Use an exception queue and keep the result set unpublished until the responsible role resolves or formally approves it.
Continue exploring
Follow the next link based on the question your team needs to answer.
Exam to report card
Run an exam cycle from session setup and invigilation through marks, moderation, publish gates, and family-facing report cards.
Read the pageExam readiness checklist
Generate an exam-day readiness artifact for sessions, papers, venues, invigilation, marks, publication, and family support.
Read the page
We can walk through the workflow with your school’s roles, calendar, data, and first-term priorities.
Already using Schoolyi? Sign in