Describe your district's directory-information notice, the categories families may restrict, and where responses should go. Makeform turns the details into a clear parent form with student identification, disclosure choices, acknowledgment, signature, and registrar-ready routing.
Route submissions to email, Google Sheets, Slack, and Zapier.
Sample prompts for school administrators
Choose a complete prompt, adapt it to your annual notice, or send it to the Makeform builder. The displayed structure is an example, not a live result.
Audience
Parents and eligible students across a K–12 district
Format
Full restriction request with annual-notice acknowledgment
Prompt size
545 chars
Example form structure
Full restriction request with annual-notice acknowledgment
Student, ID, grade, and school
Parent or guardian contact
Restrict all listed directory information
Notice and deadline acknowledgment
Signature and submission date
Suggested routing tags
Full restriction
Selected categories
Registrar review
Use the exact directory-information categories and submission deadline from your current annual notice; definitions and available choices can differ by school or district.
Step 1
Identify
match the request to the correct student record
Step 2
Choose
record the disclosure restriction offered by policy
Step 3
Acknowledge
capture the submitter's role, signature, and date
Step 4
Route
send the request to the appropriate records contact
A clearer annual process
A directory information opt out form should help a family understand what is listed, identify the right student, and send an unambiguous request to the staff member who updates records.
Use the categories and selection model your institution actually offers. Families see a complete list beside the choice instead of interpreting an open text box.
Required student ID, school, grade, and birth date give records staff enough structured detail to distinguish students with similar names.
Confirmation messages reassure families that the form arrived, while routing rules send campus-specific submissions to the responsible records queue.
Adapt to your institution
Start with the workflow closest to your annual notification process, then replace every example category, deadline, and contact with the wording your school has approved.
Collect relationship, contact details, the student's identifiers, the available restriction choice, and a signed acknowledgment in one sequence.
Swap the parent section for student identity confirmation and a self-submission acknowledgment while keeping the records-office routing intact.
Use a school dropdown and conditional routing so each response reaches the campus or district office that maintains the record.
If policy permits category-level choices, show structured checkboxes and store each selection independently for review and export.
Build the workflow
Makeform helps administrators turn established policy language into a usable online form. Your institution remains responsible for reviewing the wording, choices, timing, and records process.
Give the builder your institution's exact directory-information categories, who may submit, the response deadline, and the office contact. Avoid borrowing another district's definitions.
Review the resulting fields, make the identifiers required, remove categories your school does not use, and add conditional paths only for choices your process supports.
Send families a receipt containing their selections and submission date. Notify the designated staff inbox, with school-based routing when campuses process requests separately.
Have authorized staff check identity details, duplicate submissions, deadlines, and policy-specific exceptions before recording the request in the institution's system.
Choose a collection method
The policy decision belongs to the institution. The form improves how families submit the choice and how staff receive consistent, reviewable information.
Field guide
These six sections create a practical intake and review path. Adapt them to the definitions, decision options, deadlines, and retention practices established by your institution.
Student match
A name alone is rarely enough in a district. Collect only the identifiers your authorized records staff need to match the request without turning the public-facing form into an unnecessary data collection exercise.
Submitter details
The form should distinguish a parent or guardian submission from an eligible student's own submission. Conditional logic can show the right relationship and identity fields for each path.
Directory categories
Directory information is defined through the institution's notice, so generic category lists should remain examples. Place the current approved wording directly beside the available restriction choice.
Scope and timing
Families need to know which student, school year, publications, and disclosure settings the request addresses. State the submission deadline and explain where policy answers about timing can be found.
Acknowledgment
Show the relevant notice language before the final fields. An acknowledgment, typed name, signature, and date make the request clear for administrative review without promising a particular legal outcome.
Internal handling
The public form is the intake point, not the final records action. Send each response to authorized staff, attach a status, and retain the submitted details according to institutional practice.
Related tools
Connect the opt-out intake with enrollment, parent communication, permission, media preference, and records-request forms built for the same school community.
Create a separate workflow for requests to authorize sharing education-record information with a named recipient.
Open toolCollect parent decisions for school activities and other programs through a structured consent workflow.
Open toolGather student, household, and school-placement information during the enrollment process.
Open toolBuild a focused preference form for photo and video use when your institution handles that choice separately.
Open toolStandardize requests for transcripts and other academic records with clear destination and delivery fields.
Open toolInvite structured family feedback about communication, programs, and the school experience.
Open toolFAQ
Practical answers for administrators designing a clear intake and records-review process.
It is a school form used by a parent, guardian, or eligible student to request a restriction on disclosure of information the institution has designated as directory information. The form typically identifies the student, displays the relevant categories or restriction choice, records an acknowledgment and signature, and routes the request to staff for review. The institution's current notice and policy determine the wording and available options.
Use the exact categories in your institution's current annual notice. Common examples may include a student's name, contact details, photograph, grade level, attendance dates, honors, activities, or athletic information, but an example list should not replace your approved definition. If your process allows only a complete restriction, do not imply that families can opt out category by category.
Collect enough information for authorized staff to match the correct record: usually student name, student ID, date of birth, grade, school, and school year. Add parent or guardian identity and contact details when they submit. Limit fields to what your process needs, explain how the information will be handled, and provide another submission path for families who cannot use the online form.
Yes, if the institution's workflow accepts it. Use a repeating section that requires a separate student identity and restriction selection for each child. Route each student's data to the appropriate school, and make the receipt list each selection clearly. If policy requires one signed request per student, generate separate forms or submissions instead.
Yes. Add a signature field along with the submitter's typed name, role, acknowledgment, and date. Whether that method meets your institution's requirements depends on its policy and review process, so have the responsible administrator approve the final setup. Makeform records the submitted fields for staff to review; it does not determine the request's legal effect.
Display the deadline and effective-period language from the current notice, then provide a contact for late requests, corrections, or changed preferences. The receipt should preserve the submission date and selected choice. Staff can use statuses such as received, needs clarification, and recorded, but the institution should decide how timing affects processing and communicate that decision to the family.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge. You can still customize the student fields, notice language, restriction choices, confirmation message, and routing on the unlimited free offering.
No. A form builder cannot certify compliance or decide whether an institution's notice, categories, deadlines, identity checks, or records practices meet its obligations. Use the generator to create the intake workflow, then have the appropriate school administrator or qualified adviser review the final wording and process against current requirements and institutional policy.
Make the annual privacy choice easier to submit.
