Student registration and enrollment management
Matrica moves new student enrollment and annual registration online. Configurable forms, document collection, acknowledgements, signatures, fees, review workflows, and student information system sync, all in one platform.
New student enrollment
Annual registration
Configurable forms
Document verification
Fees and payments
Review and approval
Multilingual portal
Student system sync
Built for districts, private and charter schools, education networks, and multi campus institutions.
Amara Whitfield
Grade 6 · Northside Middle School
Returning student registration
Registration checklist
Illustrative interface. Data shown is sample content.
Retire the paper packet
Forms, policies, documents, and fees move into one guided online journey that families can finish on a phone.
Stop asking twice
Known student and family details arrive pre-filled from your existing systems, so families verify instead of retyping.
Know what is missing
Every registration carries a live checklist of incomplete forms, unverified documents, open corrections, and unpaid fees.
Send it back clean
Approved registrations sync to your student information system, so records are reviewed before they land.
01 · The two journeys
A family enrolling for the first time and a family confirming an existing record need opposite experiences. Matrica runs both from the same configuration, the same forms, and the same review workspace.
A guided journey from account creation to enrollment approval, configurable step by step for each institution.
Annual registration built around confirmation rather than data entry. Families check what you already know and change only what moved.
Change review
02 · Form builder
Registrars create, edit, clone, preview, publish, and retire forms without a developer or a release cycle. Sections, ordering, required fields, and validation are all configuration.
Version control
Publishing a new handbook or policy creates a version. Completed registrations stay attached to the version the family actually signed, so an audit years later still shows the exact wording.
Field types available in the builder
Conditional logic, live
Rules can show or hide a field or section, make it required, attach a document requirement, add a form, trigger a fee, or route the registration to a different workflow.
Resulting form
03 · Packets and the rules engine
Nobody should hand a kindergarten family a parking pass form. Combine forms into packets, then let rules decide which packet, documents, fees, and approvals apply based on school, grade, program, student type, academic year, and previous answers.
Change the inputs on the right and watch the requirement set recompute the way it does for a real family.
Forms in packet
Documents required
Fees presented
Approvals
Fee amounts are configured per institution and are not shown here.
04 · Parent and guardian experience
A parent with three children in two schools signs in once. Each student carries a profile, a status, and a short list of what is left to do.
Parent dashboard
Signed in as j.whitfield@example.orgAmara Whitfield
Grade 6 · Northside Middle
2 items left
Theo Whitfield
Grade 9 · Riverbend High
Submitted 2 August 2026
Isla Whitfield
Kindergarten · Northside Elementary
Opens 1 July 2026 · Deadline 14 August 2026
Student profile holds
Personal details, preferred name, identifiers, demographics, languages, enrollment history, addresses, transportation, technology, meal program, and any custom fields your institution defines.
Guardians
Multiple guardians per student with relationship, custody information, communication preferences, pickup authorization, and institution defined mandatory fields.
Emergency contacts
Unlimited contacts with priority order, alternate numbers, and pickup authorization, plus a completeness check before submission.
05 · Administrative workspace
One workspace shows the student, the family, every response, every document, every signature, the payment record, the missing requirements, internal notes, and the full change history.
Configurable workflow
Add or rename statuses such as pending documents, pending payment, incomplete, rejected, or withdrawn to match how your office already works.
Okonjo, Daniel
Pending reviewRequirements
Internal notes
M. Reyes · 3 Aug 2026 11:02
Called guardian about the transcript scan. Replacement expected this week.
System · 2 Aug 2026 09:41
Duplicate check matched an archived 2023 record. Flagged for review.
Internal notes stay internal unless an administrator explicitly shares them with the family.
New submissions, pending review, missing documents, corrections outstanding, pending approval, and completed, each filterable by school, grade, program, year, and status.
Route applications manually or automatically by school, grade, or team, so reviewers open a list that is genuinely theirs.
Send reminders, reassign, change status, export, and generate reports across a filtered set rather than one record at a time.
06 · Documents, acknowledgements, signatures
Required documents are driven by the same rules that build the packet. Every upload moves through a status that both the family and the reviewer can see.
Reviewers can also reject a file, request a replacement, and attach an internal comment explaining exactly what was wrong.
Privacy notices, technology policies, media permissions, transportation rules, and legal notices are all acknowledged the same way, against the version in force at the time.
07 · Fees and payments
Registration related charges appear inside the journey, scoped by school, grade, and program, and marked required or optional. Payment is handled through your payment provider.
Card details are not stored by Matrica when a compliant external payment provider is used. The platform keeps the payment record, not the instrument.
Each fee carries a name, description, amount, eligibility scope, availability window, and whether a family may decline it.
08 · Communications
Reminder rules watch the registration itself. If a document is missing on day five, the message goes out on day five, to exactly the families it applies to.
Account verification, registration invitation, reminders, missing document notices, correction requests, payment confirmation, submission confirmation, approval, rejection, and enrollment confirmation, each editable as a template.
Template variables
Build an audience from the same filters used in the work queues, then send once.
Audience
School is Riverbend High
Grade is 9
Status is Incomplete
Missing document is Immunization record
Recipients resolve at send time and messages follow each family's language preference.
Multilingual registration
Step 3 of 9
Enter the name exactly as it appears on the birth record.
Save and continueLanguage applies across the parent portal, forms, instructions, validation messages, buttons, notifications, and email. Families choose their own language, and additional languages can be added over time without rebuilding the forms.
Right to left layouts are supported. Translated content is maintained per organization so local terminology stays local.
09 · Integrations and data
Matrica sits between families and the systems you already run. Known data flows in so forms arrive pre-filled, and approved registrations flow back out once a human has checked them.
Connection methods
Inbound
Matrica
Registration layer
Outbound after approval
Token based authentication, scoped authorization, rate limiting, request logging, error tracking, and payload validation.
Upload a file, map columns, validate, catch duplicates, preview the result, then commit, with a full error report if rows fail.
Students, registrations, form responses, document status, payments, and reporting data as CSV or spreadsheet compatible files.
10 · Dashboards, reporting, analytics
School administrators see their building. Organization administrators see every school side by side. Both work from the same live registration data.
Organization dashboard
Filtered by academic year 2026 to 2027| School | Started | Submitted | Pending review | Approved | Completion |
|---|---|---|---|---|---|
| Northside Elementary | 612 | 548 | 61 | 487 | 80% |
| Northside Middle | 438 | 401 | 44 | 357 | 82% |
| Riverbend High | 905 | 743 | 118 | 625 | 69% |
| Lakeshore Academy | 274 | 258 | 19 | 239 | 87% |
Sample figures shown for illustration.
Registration summary, registration by school, grade and program, status breakdown, incomplete registrations, missing forms, missing documents, approvals, payment summary, and submission timeline.
Completion rate, average time for a family to finish, average administrative processing time, registrations by date, abandonment points, and the fields and documents that go missing most often.
11 · Multi school and multi organization
Each organization keeps its own users, students, schools, forms, documents, registrations, payments, reports, configuration, and integrations. Organization data stays logically isolated.
Every organization configures its own portal: logo, title, welcome content, registration instructions, support details, and email templates. The underlying product stays generic.
Academic year controls
Create a year, copy last year's configuration, set registration open and close dates, run campaigns against eligible students, then archive and keep historical registrations accessible.
Role based access, example matrix
| Role | Applications | Forms | Payments | Reports | Users | Config |
|---|---|---|---|---|---|---|
| Organization administrator | Full | Full | Full | Full | Full | Full |
| School administrator | School | School | View | School | School | Limited |
| Registrar | Review, approve | View | View | School | None | None |
| Enrollment reviewer | Assigned only | View | None | Limited | None | None |
| Finance user | View | None | Full | Payments | None | Fees |
| Reporting user | View | None | None | Full | None | None |
| Read only | View | View | None | View | None | None |
Roles and permissions are configurable. The matrix above is an illustrative starting point, not a fixed model.
12 · Security, privacy, accessibility
Health records, custody documents, and identity papers pass through this platform. Access is scoped by role, every consequential action is logged, and families can see what they agreed to and when.
Audit trail
| Timestamp | User | Action | Record | Change |
|---|---|---|---|---|
| 2026-08-03 11:02 | M. Reyes | Document rejected | 2026-RH-0413 | Under review to Rejected |
| 2026-08-02 09:14 | J. Whitfield | Acknowledgement signed | Handbook v2.0 | Not signed to Acknowledged |
| 2026-08-01 16:47 | A. Duarte | Permission changed | USR-2291 | Reviewer to Registrar |
Logins, profile updates, form changes, submissions, uploads, verifications, status changes, approvals, permission changes, and integration activity are all recorded with user, action, timestamp, record, and previous and updated values where applicable.
13 · Implementation and support
Implementation is sequenced around the academic calendar, because a registration platform that arrives in September has missed the point.
Ongoing support covers ticket management, issue tracking, incident escalation, and a knowledge base. Maintenance covers fixes, security updates, performance work, compatibility, and integration upkeep.
14 · Capability index