PackCleared for Schools

Why schools have this problem in the first place

Field trips are some of the highest-stakes coordination problems schools run all year. A single overnight outdoor education program might involve 60 students across four cabins, thirty parents who need to send the right gear, three teachers on point for medical needs, two bus transfers, and a Packlist that grew from “here's a template” into spreadsheet-plus-email-thread-plus-photocopy chaos over years of iterative edits.

The traditional tools — shared Google Sheets, emailed PDFs, printed handouts, whoever-coordinated-last-year's memory — weren't designed for this. Student data ends up in places it shouldn't be. Allergies get forgotten. Inhalers get left behind. Medical forms end up in inboxes for months after trip end. And every year someone on staff asks “there has to be a better way” — usually while trying to reconstruct the Packlist two weeks before departure.

PackCleared is that better way, built specifically for organizations that handle minor data.

How we keep students safe

The architectural decisions we make on behalf of student safety are the reason this product exists for schools. Not a compliance checkbox — the foundation.

Hard age floors that can't be bypassed

Age below 18, missing date of birth, an explicit minor flag set by a school administrator, or an organization-wide minor-safety mode will each independently force adult-content suppression. No path unlocks them. These checks run before any tier-promotion logic an adult user might encounter on a personal account.

Anti-beacon design

The system never advertisesthe existence of adult content to a curious student. Hidden categories produce no “locked” placeholder, no “show more” affordance, and no error message that reveals what was blocked. A curious student probing for adult features finds nothing to latch onto. This isn't a UI polish detail; it's a protection layer.

Default-deny cross-workspace data flow

The design target is that every cross-workspace read of student data is gated by a per-workspace consent record. This consent system is not generally available yet; until it is, school pilots should avoid storing sensitive student data beyond what the current product actually needs for packing coordination. The planned consent record specifies:

• Who consented (parent, legal guardian, foster parent, district-attested admin, or — for ages 13+ — the student themselves)
• Which specific fields they authorized (dietary, medical, medications, group placement, real name, photo, location history)
• The exact text of the consent prompt they were shown
• An expiration anchored to the student's next age threshold

Absence of a consent record will be treated as a denial when this module ships. Every grant, modification, and revocation must be recorded in an immutable audit log before we sell parent-permission workflows as available.

Silent enforcement

Adult-content suppression is invisible to the student. No banner, no explanation, no information that could be used to optimize a bypass attempt on a future account. The protection is the action; the silence is the safety mechanism.

Parent permissions

Parent and guardian consent is a planned module, not a live promise. The intended flow is field-by-field consent with timestamped prompt text, revocation, and trip-scoped expiry. We will not represent that module as available until the parent dashboard, consent records, and audit trail are implemented end to end.

For now, school deployments should treat PackCleared as a packing and coordination pilot, not as a replacement for your existing permission-slip or medical-consent system.

Real operational value

Safety architecture is the table stakes. The actual reason schools stay on PackCleared is that it makes the trip operators' jobs materially easier.

AI Packlists tuned to your actual trip

You give us destination, dates, activities, and trip modifiers (cold weather, water-based, bus transfer between stops, etc.). We generate a Packlist pre-filled with destination-appropriate Kit items, medication-aware companion supplies for students with health needs, and activity-specific items students might otherwise forget. Teachers review and edit before sending — nothing goes out without a human pass.

Per-student readiness dashboard

Readiness and packing-status reporting are part of the product direction. We will expose only the status views that are backed by shipped code for a given pilot; more advanced targeted parent reminders stay roadmap until implemented.

Specialty Kit coordination

Running an outdoor program with organization-owned Kit? The org inventory feature lets you assign specific Kit items to specific students for a specific trip, track check-out and return, and flag when an item is overdue. No more “who has the green tent poles?” panic the morning of departure.

Medical awareness without exposure

Health and medication data exists in the broader product, but school use requires stricter consent and audit controls. Until those controls are shipped for guardian flows, PackCleared should not be positioned as the system of record for student medical forms.

Procurement posture

We are building toward school procurement requirements, but we separate current capability from roadmap capability.

• Minor-safety gates in code — school/scout/camp workspaces default to minor-safety mode, and adult content requires positive age eligibility.
• Contract review available for pilots — custom privacy terms can be discussed before any school deployment.
• Formal district compliance — NDPA exhibits, SIS sync, guardian consent workflows, and district-scale audit exports are roadmap-gated until implemented.
• Dedicated privacy, trust, and security pages — review-ready. See /privacy, /trust, and /security.
• Annual invoicing + PO support can be handled for approved pilots and enterprise contracts.

Integration with your SIS

For schools running on Veracross, Blackbaud, Clever, or PowerSchool, we're designing roster sync so student and guardian data doesn't have to be re-entered. The goal: sync the student roster and guardian contacts from your SIS, enrich PackCleared-specific fields (dietary preferences, trip-specific medical notes, Kit assignments) in our system, and push nothing back to the SIS that could pollute the source of truth.

Integration priorities, in order of development:

• Veracross — for independent schools. Roster + guardian sync via Veracross's API, with our side treating Veracross as read-only source of truth for identity.
• Clever — for district-level K-12 single sign-on and basic roster sync.
• PowerSchool — for districts using the PowerSchool SIS as their primary student record system.
• Blackbaud Education Management — for private and faith-based schools on Blackbaud's platform.
• OneRoster CSV — the universal fallback for SIS's without a direct integration; nightly-refresh CSV exports work with PackCleared's import tooling.

If your school is on one of these systems and you'd like early access to the integration when it ships (or want to influence which SIS we ship support for first), let us know — we prioritize integrations based on customer demand.

Pricing for schools

Most schools run on our Pro plan at $79/month ($790/year with two months free). That covers up to 50 students per trip, 10 active trips per month, 10 organizer accounts, custom workspace policy, packer profile management with consent, and the full per-student dashboard.

Districts running field trips across multiple campuses typically move to Enterprise ($199/month) for unlimited trips, unlimited organizers, advanced cross-trip analytics, and priority support. Enterprise includes annual invoicing, PO payment, and custom contract terms.

Non-profit and educational discounts are available for 501(c)(3) organizations, public schools, and youth-focused non-profits. See the full comparison at our pricing page.

Want to see the platform without committing to a call? Every school account comes with a 14-day free trial — no credit card required to start. Start your school trial.