Authorized pickup people

By default, only the adult who did check-in can pick the minor up. The family can expand that list to additional explicitly authorized people.

Who can add someone

• The parent (member) from app or web.
• An org_admin or campus_admin, with verbal or written confirmation from the parent.

No one else. A kiosk volunteer cannot add someone to the list.

Authorized person fields

• Full name
• Relationship to the minor (grandparent, aunt, nanny)
• Contact phone
• Photo (optional but strongly recommended)
• Authorization start and end dates (optional, useful for temporary cases)

The pickup flow with an authorized person

1. The person approaches the room.
2. Volunteer requests their photo ID.
3. Volunteer looks up the minor on the tablet and opens their authorized list.
4. Visually verifies the person matches the registered photo.
5. Asks for the security code from the receipt (which the parent gave this person).
6. If everything matches, releases the minor.
7. The system logs pickup with the authorized person’s ID, not the parent’s.

Special cases

Shared custody

For children of separated parents with shared custody:

• Register both parents as authorized.
• If there’s a court restriction, mark the restricted parent with “NOT authorized for pickup”. The system blocks pickup and alerts the coordinator.
• Attach the court document to the family record (visible to org_admin only).

Occasional babysitter

If the sitter comes one Sunday:

1. Parent opens the app before the service.
2. Family → Authorized pickup → Add temporary.
3. Fills the data and picks “Only today”.
4. Authorization auto-expires at end of day.

Emergency pickup by unlisted person

If an unlisted family member must pick up (emergency, parent unreachable):

1. Volunteer calls the registered responsible adult.
2. Adult authorizes by phone.
3. Campus coordinator logs temporary authorization with call recording (recommended).
4. Release.

Audit

Every list change is logged:

{
  "action": "minor.authorized_pickup.added",
  "minor_id": "m_42",
  "added_user_id": "u_91",
  "actor_user_id": "u_18",
  "expires_at": "2026-12-31T23:59:59Z",
  "occurred_at": "..."
}