School District App Intake Form

What does it do?

Name the app, the need, and who would use it.

Your name

Your district email

Campus or department

App name

Current status

What problem does this solve?

What does the app do?

Who will use it?

Is there already an approved tool?

What data does it use?

Sort the risk before anyone falls in love with the demo.

LowPublic or non-sensitive data, no district systems

MediumStaff data or internal workflows

HighStudent records, FERPA-covered data, SSO, or live district systems

What data will the app collect, store, display, or share?

Public or already-published data Staff names or work emails Internal workflow notes Student names or IDs Grades, attendance, behavior, or discipline IEP, 504, health, financial, or government ID data Uploaded files, images, or audio No data stored

Choose every option that applies. Sensitive student data should trigger full review.

Where does the data live?

Does it touch student data?

Retention and deletion plan

Third-party services or APIs

Who maintains it?

Ownership matters after the clever person transfers campuses.

Primary owner

Backup owner

Where is the code stored?

Where are credentials stored?

Handoff plan if the builder leaves

Who approves updates and handles support?

Final check

This is a triage step, not a full security audit.

Before live use, which checks have already happened?

Tested failure cases, not just the happy path Ran an OWASP-style security review prompt Confirmed server-side validation Checked role-based access or row-level controls Protected API keys, tokens, and secrets Ran an accessibility check Reviewed with IT or data privacy staff Not yet reviewed

Anything else the reviewer should know?

Required fields are marked with an asterisk. This mockup stores data only when connected to your district Apps Script web app.