What is Secure Document Send and how does it work?
Secure Document Send allows users to upload a pre-existing PDF created outside of TalkingPoints (e.g., a report card or IEP) and deliver that document securely to an individual family. This can be done to large groups using the new Bulk Send or done for one family.
Families receive it to view and they are not asked to fill anything out. These secure documents are received in their preferred channel, for example, through the TalkingPoints Family app, email, or via SMS text. If receiving via text or email, the user will be sent a verification code to authenticate prior to accessing the document. Staff can track open rates for each send from the Secure Documents dashboard.
Secure Document Send will be available in TalkingPoints for Schools product only for 2026-27.
Uploading a PDF for Secure Document Send:
Who has access to Secure Document Send?
At initial release this capability will be for school-level staff (not teachers or district users), for example counselors, attendance staff, and principals.
What types of documents are typically sent using Secure Document Send?
Common use cases include:
Report cards
IEP progress reports
504 plans
Attendance letters
Parent-teacher conference notes
Legal or compliance documents that must be delivered individually per family
How does staff track whether families have opened a secure document?
The Sent Documents view shows open rate and count per send (e.g., "18/24 (75%)"), along with sent date, delivery method, and recipient group.
Are the documents themselves translated?
The uploaded PDFs are generated outside of TalkingPoints and are often legal, formal documents (e.g., IEP, 504 plans, etc.) and these will not be translated.
What does the typical workflow look like for Secure Document Send?
Secure Document Send is delivered similarly to any other TalkingPoints message. It will most often be used in combination with the new Bulk Send capability, which allows a school-level user to send to select groups of students and their families based on a master file, for example, attendance letters, though it could also be used to send one secure document to one family.
A typical workflow would look like:
Admin defines a template, by taking an example document of the type that will be sent (e.g. a master report card file for just a few students), defining where the student ID exists in the document, and saving for future use.
Admin returns later with the master file
Selects template
Uploads the master file
System processes file and splits it apart into one file per student ID found
System reports results (found X students, total of X documents)
User reviews results
If satisfactory, the user generates a message. The “To” field is defined by the resulting files - that is, this is not sent to a pre-existing group or class, but to “whoever has a file”.
Message is sent
Each family receives the document for their student. If they have multiple students, they will receive one document for each.