Secure parent accounts
Each family signs in to see only its own children, forms and requests, with password reset and optional two-step sign in.
A customer portal website for after school programs gives parents, guardians and partner schools one private place to sign forms, check enrollment status and send requests to the office. SIZ Group builds that portal around how your program already runs, so the front desk stops answering the same questions by phone.
Most after school programs run on a mix of paper packets, shared spreadsheets and text threads. A parent completes after school enrollment forms in the lobby on a Monday, then emails a pickup change on Thursday, and a second parent asks the same question by phone while the front desk is handling a sign-out line. Each channel works on its own, but nobody can see the whole family record in one place.
The breakdown usually shows up in three spots: the first week of a new session, when forms come back incomplete; the moment a late pickup request needs approval; and the end of the term, when the office chases signatures for field trip permissions. Each gap costs staff time and makes families feel the program is harder to deal with than it should be.
The first release should cover the tasks that happen every week for every family: logging in, reading the current schedule, completing forms and seeing whether a request was received. Those four things remove most of the repeat calls that reach the front desk. Everything else can be layered on once the core is in daily use.
A clean first release also keeps the data simple. We would store each child's enrollment record once and link forms, sign-offs and requests to it, so a pickup change the office updates appears in the same place the parent checks. Reporting, payment plans and a full messaging feed can wait until staff have used the basics through a full session.
Picture a parent who needs to move a Tuesday pickup to a grandparent for one week. She signs in from her phone, opens her child's profile and sees the current authorization list, with the grandparent already on file in a different role. She selects a one-time change, chooses the dates and adds a short note explaining the reason.
The request lands in the office queue with the child's record attached. The staff member sees the authorization on file and the last change made, so they can approve or ask a question without searching a binder. When the change is approved, the parent receives a confirmation and the Tuesday sign-out list updates.
Each family signs in to see only its own children, forms and requests, with password reset and optional two-step sign in.
Enrollment, consent and emergency forms are completed once, saved for returning families and signed on screen.
Parents submit one-time or ongoing changes, and the office approves each one from a single queue with the full record attached.
Handbooks, calendars and permission slips live in one library, with a notice to families whenever a file is replaced.
Every request shows its status from received to approved, so families stop calling to ask whether it went through.
Directors, front desk staff and site leads see only the records their role needs, and every view is logged.
Many programs already rely on after school program software such as Brightwheel or Procare Solutions for attendance and billing, and keep documents in Google Workspace or Microsoft 365. The portal should sit beside those tools and handle the family-facing work, not replace them. That keeps the billing cycle and staff habits intact.
Before promising any connection, we would check whether the current system offers an export or an API and how often it updates. If sync is not available, the portal can send a daily summary file that the office imports by hand. We name the exact approach in writing during the scoping call.
The most common mistake is building a portal that copies the paper packet page by page. Parents then have to fill out a long form on a phone, abandon it and call anyway. We would split long forms into short steps, save progress and pre-fill returning families from the record already on file.
The second mistake is treating the portal as a launch event rather than a daily tool. If staff keep using email for pickup changes, the portal becomes one more place to check. Give the office one rule from day one: every change goes through the portal, and the front desk answers from the same queue.
A third is storing sensitive information where staff cannot control it, such as medical forms attached to open email threads. Limit who can view health details and log each access.
Start with one site or one session rather than every family at once. Invite a small group of parents to test the login, one form and one request, then fix anything confusing before the full list receives access. Explain the after school parent portal in the welcome message, and keep a printed guide at the front desk for families who prefer a paper hand off.
Staff need a clear routine. Decide who checks the request queue each afternoon, which requests count as urgent enough for a phone call and how the office handles a request sent to the wrong place. After launch, support stays available for workflow changes and for the questions that come up during the first busy weeks of a session.
No. Each parent account is linked only to the children on that family's enrollment record, and a sibling link needs an approval step so no one can add a child by guessing a name. We test those permissions with sample families before launch and keep a log of who viewed which record.
No. The portal is built to sit beside tools such as Brightwheel or Procare Solutions, handling the family-facing side of enrollment, documents and requests. Whether data moves automatically depends on what your current system supports, so we confirm that during the scoping call instead of assuming it.
Keep a staff-assisted path open. The front desk can complete a form for a parent during pickup on a tablet or the office computer, and the record shows that staff entered it. Printed copies of current forms should stay available, because a portal that excludes some families creates more work than it saves.
Urgent changes should still go through a phone call to the office, and the portal should say so. The request can be entered afterward so the record is complete, and staff can mark it urgent so it appears at the top of the queue. The portal supports the process; it does not replace a safety call.
Websites range from $300 to $2,200, depending on scope. The number of user roles, the depth of the document library and any connection to your current system move the figure, and we confirm the final price in writing after a free scoping call.
Tell us how families enroll and request changes today, and we will map a first release your front desk can run from the opening week.