August Schools

• Organizations that require extensive publicly documented security certifications prior to procurement and cannot obtain artifacts from the vendor.
• Organizations that require a full SIS/ERP rather than a health/wellbeing-focused platform.
• Organizations that require a mature ecosystem of independent third-party reviews as a gating criterion and cannot proceed without them.

• Limited public reviews and benchmarking data reduce the ability to validate reliability and support quality externally.
• Public security documentation is incomplete in reviewed materials: while ToS and privacy policy exist, detailed certification scope and security architecture are not fully documented publicly.

• No public scale benchmarks (maximum records, documented performance SLAs, or uptime history) were found in the reviewed materials. Buyers should request SLA details, uptime statistics, and reference calls with similarly sized customers.

• Competitors with a longer presence in the student health records category have more extensive independent review footprints.
• SIS/ERP vendors may be preferable when the primary requirement is consolidation and reduction of vendor sprawl for schools already committed to those ecosystems.

• Gartner Peer Insights: no accessible listing or reviews were identified in the searches performed.
• G2: the vendor has a product/seller presence, but the listing captured in this research showed no visible third-party reviews at the time of review; this limits independent third-party validation.
• TrustRadius: no product page or reviews were identified in the targeted searches performed.

Vendor-published testimonial snippets on the homepage emphasize improved data access, reduced paper handling, positive service interactions, and ease of form creation. These snippets are vendor-selected and unattributed; they are useful as directional signals but should not be treated as independent validation without named references and dates.

• A vendor-hosted Seattle Academy case study PDF is available on August's site. A named case study provides more detail than anonymous snippets, but it remains vendor-published and should be validated (for example, by asking for a customer reference call to discuss baseline, timeframe, and outcomes).

• Searches on Reddit and Hacker News did not surface substantive product-specific discussions in the reviewed results.

• Centralization of fragmented workflows for student health and wellbeing teams
• Family portal features with form packets and approvals to reduce paper collection
• Messaging functionality that is recorded into student files to reduce reliance on email
• Automation around immunization compliance and medication workflows

Given the limited independent review footprint, public churn reasons are not well-documented. Category-consistent reasons include:

• Cost relative to incumbents such as Magnus or SchoolDoc or health modules bundled with an existing SIS
• District procurement and privacy/security requirements
• Integration complexity (SIS/rostering, IdP integration, nurse/counseling workflow edge cases)
• Change management and staff training requirements

• Evidence: a named case study exists in vendor-hosted materials.
• Utility: provides an implementation narrative and outcomes as reported by the vendor.
• Caveats: vendor-published case studies often omit implementation challenges, additional staff time required for data cleanup, or costs. Buyers should request details on baseline conditions, measurement timeframe, and whether improvements were operational or student outcome driven.

• The vendor published a School Nurse Insights report (2025) that reflects market observations and vendor perspective. Its methodological transparency should be reviewed to determine independence and representativeness.

• Likely fits:
  • Single independent/private schools with small-to-midsize student populations that need modernized health/wellbeing workflows and family form management.
  • Mid-sized districts evaluating consolidation of behavioral-health documentation and care coordination.

• Schools with substantial health-enrollment and compliance tracking needs (immunizations, screenings).
• Schools or districts with discernible behavioral-health and counseling documentation requirements.
• Organizations that require multiple care roles to share context while maintaining controlled permissions.

• Decision makers: Director of Student Services, Head of School, district health services leadership, IT leadership, compliance/privacy officers.
• End users: nurses, counselors, psychologists, social workers, athletic trainers, and administrative staff managing forms and reporting.

• Organizations seeking to reduce paper and centralize documentation.
• Organizations willing to commit resources to implementation (data cleanup and process changes).
• Organizations prepared to support integration work with existing SIS and identity providers.

• Primary market: K–12 schools and districts; the vendor's messaging emphasizes deployments in private/independent schools with expansion toward public districts.
• Primary users: school nurses, counseling teams, wellbeing staff, and school operations/administrators.
• Positioning statement (paraphrased): a platform intended to reduce paper processes and consolidate fragmented tools for school health and wellbeing documentation and coordination.