Parent Portal

Carla Reyes, Maya's mother, opens the portal on her phone at pickup time. This is the only part of PTRS built for someone who has never signed in as staff, and it is the module where the most is promised and the least actually connects.

Read this before anything else on this page

Carla cannot sign in and see Maya. No guardian anywhere can, in any installed copy of PTRS, for two separate reasons, either one enough on its own.

PTRS has no way to join a guardian's sign-in to that guardian's own record. There is no registration screen, no invitation, and nothing that ever sets the one column both the sign-in check and every request depend on. And in a development copy built to demonstrate the product, the two halves of that same link were given different values, so even the built-in sample guardian cannot sign in either.

With no link, every screen's request is switched off before it is ever sent. The screens do not show an error. They show their ordinary empty states, the same ones a guardian would see after a perfectly quiet week.

The full chain is in how your account is linked to your child.

What Parent Portal is for

A guardian hands over a child at 3 in the afternoon and hears nothing until pickup. The questions they have are small and constant, and today every one of them is a phone call to a site director who is busy supervising children: did my child arrive, is anything wrong, was the inhaler given, what do I still need to sign, and can I read all of this in Spanish or Haitian Creole.

A working portal turns those calls into a screen a guardian checks themselves, produces a signed, timestamped consent record, and, because Delaware licensing expects a guardian to be told about an injury or a medication given, turns a phone note into a record PTRS can actually show an inspector.

Who uses it

Who can do this

• Parent / guardian

PTRS lets a guardian, an organisation administrator and a super admin all open the portal's screens, wider than what the server actually accepts, which is a guardian account alone.

This is the one policy in PTRS a super admin's account cannot satisfy through the server, because it names one role and nothing else. An organisation administrator who opens a parent web address anyway gets the full portal shell and the same empty screens an unlinked guardian sees, with nothing on screen explaining why.

A day in the life

Carla opens the portal and taps Dashboard. She would see a card for Maya with today's arrival status, and it would be genuinely correct, since it comes straight from the record staff create at the door. She sees nothing instead, because her account was never joined to Maya's record in the first place, and PTRS gives her no way to tell the difference between that and a quiet day.

She taps Messages to ask whether Maya's inhaler was given after gym. There is a box to type in, and pressing send always fails silently: the app sends the message with a value the server cannot use, so nothing is saved and the box clears anyway, as if it had gone through. There is also no screen anywhere in PTRS for a staff member to write back to her, so even a message that did save would reach nobody. Carla calls the front desk instead, exactly as she would have without the portal at all.

What PTRS does for you

• Shows today's real arrival status for each linked child: arrived, sent home, or nothing on record yet, taken directly from the check-in a staff member makes at the door
• Keeps every child's records genuinely separated between families. Two independent checks, on every single request, stop one guardian's account from ever reaching another family's child, even by editing the address in the browser
• Reads a child's actual attendance history rather than the same summary table that leaves several other parts of PTRS empty, so the one figure a guardian is shown is real
• Offers the portal in English, Spanish and Haitian Creole, with all three sets of screen text written out in full and checked against each other, so nothing quietly falls back to English for want of a translation
• Lets a guardian switch language instantly from Settings, with no save button and no delay

The one action here that actually works

Changing the portal's language is the single guardian-facing action in this module that runs start to finish. See change the language the portal is shown in.

What stays your job

• Call your club directly for anything you would otherwise message about. There is no way to send a message to staff from this app, and no way for staff to write back even if there were
• Ask your club by phone about a signed consent, a field trip form or anything else that needs your signature. Nothing your club creates can reach this app yet, so the Forms screen has nothing to ever show you
• Ask your club directly whether a medication was given. The medication log this app would show you can never hold a record, because nothing in PTRS can write one yet
• Treat the portal as read-only information, not an emergency channel. If something urgent happens at your child's site, you will hear about it by phone, the way you do today
• Keep your contact preference and quiet hours in mind as things you tell your club yourself. The Settings screen shows a save confirmation and does not actually send your choice anywhere

What has been built

Five screens, reached along the bottom of the portal.

Screen	What it is	What it can do today
Dashboard	A card per linked child with today's status, plus counters for messages, forms and alerts	The status card is real. All three counters read zero permanently, and the bell icon does nothing
Child	A child's profile, attendance, schedule, weekly summary and health and safety records	Always shows the empty state. Every one of nine working reads behind this screen is connected to nothing
Messages	A conversation with a staff member	Cannot send, and cannot receive, since no staff screen exists to write back
Forms	Pending and completed consent forms, with a way to sign	Always empty, since nothing lets your club create a form yet
Settings	Language, contact preference and quiet hours	Language works immediately. Nothing else is ever actually saved

What happens on its own

Nothing. This module runs no scheduled check of any kind.

A live connection exists and nothing uses either end of it

A real-time connection for this app is built, correctly secured, and even names its messages the same way on both the sending and receiving side, the first time that has been true anywhere in PTRS. Nothing ever sends anything over it, and no screen ever listens for anything either, so it changes nothing about what a guardian sees.

What it connects to

Connects to	How
Members	Reads a guardian's own record and child links from Members. Writes only a guardian's settings, through a save nothing calls
Attendance	Reads real check-in records directly, unlike several other parts of PTRS that read a summary table nothing writes to
Health & Safety	Reads medications, the medication log, emergency action plans and illness records, none of them connected to any screen in this app
Incidents	Reads a child's own incident involvement, unconnected to any screen
Notifications	The only link is a saved phone token for alerts, read by a delivery path that has nowhere to deliver to

Not yet available

A form cannot be created, so none can be signed

The screens and the save that would let a guardian sign a consent form are built correctly, including a permanent audit record of the act of signing. Nothing lets your club create a form for a guardian to sign in the first place, so the Forms screen has nothing to ever show, in any installed copy of PTRS.

What a signature would actually record is set out in full in what is stored when you sign a form, because a signed consent is a legal record and the answer should not have to be guessed.

An emergency alert cannot exist

A full-screen alert, a list, a way to confirm you have seen it, and a service meant to escalate an unconfirmed alert are all built. Nothing anywhere in PTRS can actually raise an alert in the first place, so none of it can ever run.

A guardian is never notified of anything, by any channel

No message, an emergency alert, a form becoming due, or a check-in ever reaches a guardian by email, text message or phone notification. Two of the four contact choices on the Settings screen, text message and phone call, have no delivery method built at all, and the other two are never actually used either, because the setting never reaches the server in the first place.

The Child screen reads a place nothing ever fills in

The screen reads from a spot in the browser rather than from any of the nine working reads PTRS has for a child's profile, attendance, schedule, weekly summary and health and safety records. Nothing in PTRS ever puts anything into that spot, so the screen is empty even for a fully linked guardian with a child checked in on the dashboard this minute.

Where to go next

Do a task:

• Change the language the portal is shown in

Look something up:

• What is stored when you sign a form
• Who can do what in the parent portal

Understand why:

• What you can see in the parent portal
• What a guardian can and cannot be told
• How your account is linked to your child

When something goes wrong: Parent Portal troubleshooting.