Implementation & onboarding
Move your school forward without losing track of the details.
Replacing a school system affects people, records and everyday routines. Pensuh onboarding follows a structured approach so teams can inspect the data, test important workflows and prepare for a considered rollout.
The rollout process
Six steps from discovery to confident use.
The work and timing depend on the condition of your records, the modules you choose and how many teams or campuses are involved.
- 01
Discover the school you actually run
We review your academic calendar, classes or programmes, grading, fees, campuses, existing software and the people responsible for approvals.
Deliverable: A documented scope, owner list and open decisions
- 02
Audit the records you already have
Identify the source of student, staff, academic and finance information. Check duplicate profiles, missing identifiers, historical sessions and inconsistent formats.
Deliverable: A data inventory and quality findings
- 03
Configure the institution and test a sample
Set up academic structures, permissions and selected modules. Map imported fields, rehearse a representative import and record mismatches before scaling.
Deliverable: Configuration review and mapped sample data
- 04
Reconcile with the people who own the records
Registrars verify enrollment and student history; academic leads check results; bursars compare invoices, payment allocations and balances. Exceptions are investigated before acceptance.
Deliverable: Exception log and sign-off checkpoints
- 05
Train teams by the jobs they perform
Teachers need attendance and assessment workflows; bursars need reconciliation; administrators need permissions and correction procedures. Train real users with realistic examples.
Deliverable: Role-specific training and support responsibilities
- 06
Pilot, launch and review
Agree a go-live checklist, rehearse critical journeys, confirm support escalation and review the first operating cycle rather than treating deployment as the finish line.
Deliverable: Launch decision and follow-up plan
What helps us prepare
Bring what your school uses today. Even imperfect files help establish what needs attention.
- Sample student and staff exports
- Current fee schedule and a balance report
- Recent result sheet or academic policy
- List of existing systems and integrations
- The people who will approve data and configuration
Migration controls
An import is not finished until the school can trust it.
Counts, balances and historical records need different forms of validation. We use sample checks and owner sign-off to establish which records have moved correctly and which require attention.
01
Student records
Review identifiers, duplicate pupils, withdrawals, transfers, previous classes and guardian information. A current class list is not a complete school history.
02
Academic history
Check subjects, sessions, grade scales, result approvals and report templates. Pay special attention to older terms and exceptional outcomes.
03
Fees and balances
Compare assessed charges, allocations, discounts, refunds and outstanding balances against the source records. Agree how historical adjustments will be represented.
School responsibilities
Clear ownership keeps projects moving.
Pensuh can guide the work, but the school remains the authority on its enrollment, financial and academic policies.
- Appoint a project owner and department reviewers
- Approve the academic structure, grading and fee rules
- Provide lawful access to source records and resolve inconsistencies
- Attend testing and training with the staff who will use the system
- Approve readiness and agree the cutover plan
A practical go-live checklist
Before daily work moves to Pensuh, review the journeys that matter most.
- New student admission and class allocation work as expected
- Teachers and approvers have the correct access
- Sample results match institutional grading rules
- Fee balances reconcile to accepted source totals
- Staff know the support and escalation path
Common questions
Answers to the questions raised during a school migration.
Get started
Start with your current records, not a sales assumption.
Share your institution type, systems and migration priorities. We’ll make the next discussion specific.
Prefer to explore independently? Create a workspace using sample school records.