Skip to content

TransitPin — Customer Onboarding Document

Purpose: collect everything IT Pro Partner needs from a prospective white-label transport client to build and launch their TransitPin instance. Use this to vet the client, then drive the build. After vetting, this checklist becomes the online registration form (see "Post-vet" notes).

Status: DRAFT. Date: 2026-08-14.

  • [ ] NDA signed — before showing a functional demo (see NDA.md). Protects proprietary architecture, pricing, and roadmap.
  • [ ] Client tier confirmed (Starter / Pro / Enterprise) — determines white-label feature flags.

1. Organization & contacts

Field Notes
Legal business name
DBA / brand name shown to parents
Primary contact (name/email/phone)
Billing contact (if different)
Email for staff invitations (transitpin-it-staff group)
Service area / metro

2. Brand & white-label assets

  • [ ] Logo (SVG or high-res PNG, transparent)
  • [ ] Brand colors (primary / accent)
  • [ ] Font preference
  • [ ] Domain for white-label hub (<client>.transitpin.com or client-owned domain?)
  • [ ] Any existing website / portal to match

3. Service scope

  • [ ] Service area (city / county / radius)
  • [ ] Fleet size (number of vehicles)
  • [ ] Number of drivers
  • [ ] Expected student count (peak)
  • [ ] Operating schedule (school days only? aftercare? summer?)
  • [ ] Special transport types (ADA/wheelchair, field trips)

4. Schools & zones

  • [ ] School list (name, address, bell times — start/end)
  • [ ] Zones / service regions (if any)
  • [ ] One school per route, or multi-school routes?

5. Students & registration data (parent portal)

  • [ ] Required fields (student name, grade, school, address)
  • [ ] Transport need per child — morning only / afternoon only / both (this drives one-way vs two-way billing)
  • [ ] Emergency contact structure (1 or 2 contacts?)
  • [ ] Any medical / allergy / ADA flags to collect
  • [ ] Parent auth method (email/password via auth2)

6. Routes & dispatch

  • [ ] Manual route building, AI-assisted route building, or both?
  • [ ] Driver app (geolocation tracking every N seconds)?
  • [ ] Dispatch map (live bus positions, student counts)?
  • [ ] Stop-level ETA / parent notifications?

7. Billing

  • [ ] Billing interval (weekly / biweekly / monthly — client dictates)
  • [ ] Rates — one-way $/wk, two-way $/wk (default $120 / $175)
  • [ ] Sibling/multi-child discounts?
  • [ ] Split-billing — any parents splitting a bill with another parent (co-parent outside household)? How (50/50, per-child, fixed)?
  • [ ] Payment provider — Square (current Village Express flow) or Stripe? → requires OAuth/credentials from client's account
  • [ ] Late-fee / outstanding-payment policy
  • [ ] Invoicing contact + address

8. Notifications

  • [ ] SMS provider / sender (BrightArrow, Twilio, etc.)
  • [ ] Email (MXroute mailbox for client?)
  • [ ] Which events notify parents (route changes, delays, sign-in/out)?

9. Domain & DNS

  • [ ] Domain registrar + DNS access (needed for white-label DNS cutover)
  • [ ] Existing MX/email to preserve

10. Go-live checklist

  • [ ] All above collected + signed NDA
  • [ ] Tenant created + theme applied
  • [ ] Schools, students, routes, drivers imported
  • [ ] Billing rates + interval + payment provider configured
  • [ ] DNS + TLS verified
  • [ ] Staff training + handoff

Post-vet (future online registration)

Once a client is vetted (NDA signed, tier confirmed), the "Organization / Brand / Billing" sections above become a self-service online form (tenant onboarding), while "Students / Schools / Routes" are entered via the live parent + admin portals.