Project Atlas AetherDev project hub
Atlas project production

BJHS Nightly ParentSquare and Google Classroom Readiness Channels

Runs a BJHS-focused nightly sync so incoming families and students stay aligned to readiness communications in ParentSquare and Google Classroom.

Internal-only entry. Do not publish externally without review.
Type
Component
Lifecycle
Active
Last touched
2026-03-24
Visibility
Internal

Purpose

Document the BJHS-specific implementation pattern for incoming-student readiness channels that sit inside the broader ParentSquare and Google Classroom sync workflows.

Current state

This page now represents school-specific implementation context rather than a standalone integration. The BJHS pattern remains useful, and related BOHS incoming or grad-year groups follow the same general model, but the custom tool details and support handoff remain under-documented.

Next step

Document the custom tool location, owner handoff, and which BJHS or BOHS readiness-channel variations are currently active.

Interfaces

Inputs
  • incoming-student and family data
  • channel membership rules
Outputs
  • ParentSquare readiness group
  • Google Classroom readiness roster

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Contributes in this stage.

Human Interfaces

Not in scope.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Incoming-student data defines channel membership.
  • ParentSquare and Google Classroom are delivery surfaces, not source systems.

Safe handling

  • Restrict family communication data to approved staff.
  • Limit access to channel-management tooling.

Operational notes

Reliability posture

Nightly automation lowers manual burden, but the custom tool location and monitoring are not yet centrally documented.

Observability

  • nightly sync checks
  • vendor membership review
  • manual channel spot checks

Security and privacy

Restricted student and family communication data; internal only.

Dependencies

Upstream
  • accurate incoming-student data
  • custom sync tooling
Downstream
  • orientation and readiness communications

Ownership

Owners

Technology Services, Josh Barton

Users

BJHS administration, Technology Services, Josh Barton (owner)

BJHS Nightly ParentSquare and Google Classroom Readiness Channels

Operational Notes

  • The registry treats this as a district-specific nightly automation with clear user value.
  • It spans both ParentSquare and Google Classroom rather than living fully inside either platform.
  • Failure leads to outdated readiness communications and manual list maintenance burden.

Registry Alignment

  • Former standalone registry entry INT-019 is now treated as school-specific implementation context within ParentSquare Custom Contact Groups Sync and Aeries to Google Classroom Sync.
  • Registry clarified: Atlas keeps this page as the component-level implementation note for BJHS-style readiness channels rather than as a standalone integration.
  • Validation gaps: capture the custom tool location, monitoring, long-term support owner, and the full school implementation inventory.