What an IT lead should document about admissions and enrollment

Document the system boundary

List applicant, guardian, relationship, document, assessment, decision, offer, acceptance, waitlist, enrollment, withdrawal, communication, user, support, export, and temporary-work records. State system, purpose, owner, sensitivity, users, and retention.

Document what is authoritative and what is derived. A diagram without ownership cannot explain a wrong status or duplicated identity.

Document data movement

For every integration, record source, destination, fields, transformation, identity match, frequency, validation, failure alert, retry, reconciliation, owner, and manual fallback.

The U.S. Department of Education data-quality guidance connects business rules, validation, infrastructure, and professional learning. Include correction and monitoring, not only transport.

Document access and suppliers

Specify view, create, edit, approve, publish, export, correct, archive, and delete rights for staff, families, support, campuses, suppliers, and subprocessors. Record incident, backup, recovery, export, retention, deletion, and contract-end responsibilities.

GOV.UK guidance recommends minimum necessary data, access control, security, supplier accountability, incident notification, and end-of-contract handling.

Document support and change

Keep owner, escalation, evidence, severity, temporary-work, reconciliation, update, and review rules beside the architecture. Revisit them at 30, 60, and 90 days and whenever the school adds a role, campus, field, integration, or supplier.

Make the next action clear

Use this guidance to improve one bounded part of what an IT lead should document about school admissions software. Name the owner, affected record, evidence needed, and review date. Keep the test small enough for admissions staff to complete and specific enough for a later audit.

Check both an ordinary application and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the next step ready.

Record what changed, what remains manual, and who reviews the result before the next admissions cycle.