Braintree staff present OpenArchitects platform; teachers and parents ask about privacy and parental access

Braintree Public Schools staff presented OpenArchitects (OA), a centralized student-data and MTSS platform, saying it combines assessment, attendance and intervention tracking into a single interface to help teachers and interventionists monitor student growth.

Presenters from elementary and middle schools described OA’s features: a student-explorer view that filters students by performance bands, widgets for DIBELS and STAR assessment data, an interventions widget where interventionists log goals and progress, and progress logs that can link scanned documents. "So OA is open architects ... it's an open platform for us to share in school, look at all different variety of data... We can understand progress," one presenter said.

Teachers said OA reduces manual data entry and enables vertical tracking so that a student’s kindergarten, first- and second-grade scores can be viewed cumulatively. Interventionists described using the platform to form targeted intervention groups and to document district-approved resources used in interventions.

Privacy and access questions: Committee members and teachers asked whether parents can access the platform and how sensitive notes are handled. Presenters said there is not a general parent portal; staff can generate readable reports for parents and should walk families through what each metric means. Presenters emphasized district guidelines and local review of notes to ensure they are factual rather than opinion-based. One teacher noted, "I think it's important that you don't set up alerts when there's no alerts... But anytime there is alerts, staff always notify families that there are alerts of why they're getting groups." Another staff member said access is role-limited: teachers see only their current classes, and interventionists have appropriate building-level access.

Editability and audit trail: Committee members asked whether entries are permanent and whether changes produce an audit history. Presenters said notes are editable and deletable in OA; they were not able to locate a version-history UI during the presentation and suggested OA or the vendor could clarify audit capabilities.

What happens next: Staff will continue training and refining guidelines about what is appropriate to log in OA; questions about audit trails and parent-facing reporting will be followed up with the vendor and reported back to the committee.