Private learner accounts
Each student, parent and corporate contact sees only their own records, invoices and requests.
A language school runs its paperwork through email, messaging apps and the front desk at once. A customer portal website for language schools gives students, parents and corporate clients one secure place to find documents and follow every request.
Most service businesses see a customer once. A language school keeps the same learner for a term or a year, and each term brings new paperwork: a placement result, a level change, an installment invoice and an attendance letter for an employer.
International students add a layer that generic sites handle poorly. A learner on an F-1 visa at an SEVP-certified school depends on a Form I-20 from the school's Designated School Official, and that document must be found quickly when a visa appointment is booked. Those international student documents need one clear home.
The portal gives each student a private account and each document a fixed place, so the school stops answering the same question across three inboxes. It also builds a language school student portal that the front desk can rely on every day.
Admissions usually runs on a shared inbox, a learner spreadsheet and a folder tree that has grown for years. A request to move from a Tuesday evening B2 class to a weekend group arrives by email, goes to the academic coordinator and is confirmed by phone, while three staff members answer it in parallel. Without student request tracking, nobody knows which version is current.
The breakdown points are predictable. Documents sit in personal email threads and disappear when a coordinator leaves. Payment reminders depend on a sheet the finance lead updates by hand, and the front desk checks three systems before a teacher can release a certificate.
The useful test is practical: a student should see only their own file, staff should see every open request in one list, and the school should be able to show who changed what and when. We would walk through those checks on a staging copy before launch.
Secure document sharing for schools also needs a rule for what leaves the building. Files should open only inside the account, and every download should be logged the same way an upload is.
Each student, parent and corporate contact sees only their own records, invoices and requests.
Passports, enrollment agreements, placement results and I-20 copies are stored with version history.
Every class change, transcript request or payment query has an owner, a status and a readable history.
Installment plans and corporate invoices sit in the account, with receipts ready to download.
One announcement reaches every active student, and reminders for missing paperwork follow a schedule the school sets.
Front desk, academic and finance staff each see the queue that matters to them, with search across every file.
A returning learner receives an invitation after enrollment and sets up a password with a second sign-in step. The home screen lists what is still missing, such as a passport copy, and the learner uploads it from a phone.
Three weeks into the term, the learner asks to move up a level. They pick the new class, name two time slots and attach their latest placement result. The request routes to the academic coordinator, and the status changes to received.
The coordinator approves a slot from the staff view. The learner gets an email and an in-portal message, the new timetable appears, and the price difference joins the account history. The completion certificate appears in the same place at term end.
Many language schools run intakes on fixed dates, so paperwork arrives in short windows. Summer programs for teenagers add a second spike, and visa season brings a steady stream of I-20 questions before the fall intake.
A portal built for those spikes copies the document checklist for each intake and gives each request category its own deadline. A visa case is never queued behind a timetable change.
Pricing for this kind of portal runs from $300 to $2,200, depending on scope. The main drivers are the number of user roles, the document types stored, whether invoices and card payments connect to accounting software, and how much data must move out of spreadsheets.
We begin with a free scoping call and put the scope and price in writing before build work starts. Timelines follow the same drivers and the school's approval speed, so approval steps are written into the scope from the start.
No. Access is set by role, and a learner sees only their own file. Staff permissions can be narrowed further, so a teacher sees progress notes without payment details. We confirm the permission map during scoping and test it before launch.
Not necessarily. Many schools keep their existing records system and use the portal as the front door for students and documents. We review what the current system can share during the scoping call before recommending a single source of truth.
We plan a one-time move of the most useful files, such as current enrollment agreements and active visa paperwork, and leave older archives where they are. The move is a line item in the written scope, so nothing is copied without a decision.
No. The portal stores, routes and tracks documents, but the school's Designated School Official still decides what is issued and when. We build the workflow so those decisions are easy to find and record.
Post-launch support is available on a schedule the school chooses. That covers fixes, adding a request type, updating notice templates and reviewing access when staff change roles.
Book a free scoping call with SIZ Group and receive a written scope and price for your language school portal.