What an RFP should say about parent portals and family communication

Describe the school problem

A family-communication RFP should state the outcomes sought: reliable delivery, accurate audiences, accessible content, two-way response, clear consent, manageable corrections, lower duplicate work, safer support, or better reporting.

Define students, households, authorised contacts, relationships, campuses, languages, channels, notices, forms, events, responses, attachments, integrations, local requirements, retention, safeguarding, internal capacity, and implementation boundary.

Require observable behaviour

Ask vendors to demonstrate ordinary notice and form plus new family, multiple children, separate households, changed guardian, bounced message, no connectivity, translation, accessibility, duplicate response, withdrawn consent, correction, safeguarding concern, and outage.

Require expected and observed audience, delivery, rendering, response, acknowledgement, consent, permissions, audit, manual work, support response, limitation, configuration, dependency, evidence date, and owner.

Specify responsibility and lifecycle

Request ownership for relationship-data cleaning, content, approvals, translations, accessibility, integrations, migration, training, support, privacy, security, records, safeguarding, backup, recovery, renewal, data return, deletion, and exit.

Separate supplier capability from school responsibility for local policy, relationship accuracy, safeguarding judgement, family support, accessibility, records, and qualified legal or privacy review.

Make evaluation fair

Publish scoring anchors, required evidence, assumptions, weights, acceptance tests, conflicts, limitations, implementation capacity, fallback, owner, approval, and review date. Do not award points for roadmap items as if they were demonstrated.

At 30, 60, and 90 days after launch, compare cost, delivery, completion, response time, corrections, wrong audiences, support demand, accessibility barriers, safeguarding escalations, incidents, and outcome.

Make the next improvement testable

Use this guidance to improve one bounded part of what an RFP should say about school parent portal software. Name the owner, family-service record, evidence, correction route, support path, and review date so staff can apply it consistently.

Check an ordinary family interaction and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, approval, accessible instruction, or safeguarding route.

Record what changed, what remains manual, and who reviews the result before the next notice, form, event, response, or support cycle.

Keep the decision beside its evidence so the next family-service colleague can understand the rule without relying on informal memory.

Use the review to decide whether the change should be expanded, repaired, narrowed, consolidated, or held.

Recheck the boundary when a student, household, guardian, campus, language, channel, integration, calendar, or local requirement changes.