These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Parent-Teacher Communication
- Who it's for
- School districts
School districts
A district team can define each school or operating unit as an organization and assign its community definitions. The operator prepares cases for the relevant community; the reviewer sees the same source revision before deciding. The useful starting question is who owns the case and who can decide on its revision. Give the team a shared case number, source reference and dated record before delivery work begins. Keep the school community on the case so the reviewer and delivery team can read it in the right context.
How Parent-Teacher Communication is set up for you
District office
Confirm the organization and maintain its school community definition, including effective dates. Confirm the people who can own, verify and review cases in that scope.
School office
Prepare the school conversation with its event detail and evidence. Submit a revision only when the record is ready for another person to assess.
Shared service team
Review decisions and delivery attempts by revision. Investigate unknown provider outcomes against the original receipt before another send is considered.
A district team can define each school or operating unit as an organization and assign its community definitions. The operator prepares cases for the relevant community; the reviewer sees the same source revision before deciding. The useful starting question is who owns the case and who can decide on its revision. Give the team a shared case number, source reference and dated record before delivery work begins. Keep the school community on the case so the reviewer and delivery team can read it in the right context.
Choose one organization and one active school community for a pilot. Bring a real case with its message date, owner, source record and supporting evidence. The operator submits that case for independent review. The reviewer records a decision against the revision and gives a reason if it is returned. Follow an approved case into a delivery run, then match the provider reference to the receipt before calling the case delivered.
Add an exception to the rehearsal. A document can remain unverified, or a provider attempt can have an unknown result. Assign follow-up to a named person and keep the original case history intact. The team should be able to answer which version was reviewed, what was attempted, and what remains open.
[Plan the first setup](/parent-teacher-communication/implementation) with the people responsible for these decisions.
Features to start with
Roles on the team
- Read Only Analyst
- Reads authorized summaries and aggregates across every table plus the four portal pages. No record creation or editing, no schema or administrative capability.
- Parent-Teacher Communication Operator
- Prepares assigned work: record entry on School Conversations, Communication Events, Follow Up Actions and Evidence Documents, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
- Parent-Teacher Communication Reviewer
- Reviews independent assigned work: record entry on Review Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
- Parent-Teacher Communication Administrator
- Maintains approved configuration: record entry on School Communities, read-only on all operational, review and provenance tables, and access to all four portal pages. No schema editing, deletion, bulk operations or export grants.
Set up Parent-Teacher Communication your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.