Skip to documentation content

Agiled Documentation

Understanding Operations Data and Handoffs

Understanding Operations Data and Handoffs

Staff work links several school records. Knowing the owner of each record prevents duplicate work and makes a handoff clear.

Available now. Last reviewed: 19 August 2026.

  1. 1Applicant or family request
  2. 2Staff record and review
  3. 3Authorised decision or correction
  4. 4Updated school record or official document

The records you will encounter

Applicant

A person requesting admission. An applicant record supports intake and review; it is not itself a confirmed student placement.

Attendance exception

A follow-up record for an attendance concern. Resolve it only after reviewing evidence and the school's attendance policy.

Parent service case

A tracked family request or concern. Its status helps Staff coordinate work; use approved school channels for communication and escalation.

Official document

A document generated from school and student records. Its lifecycle is Draft, Submitted, Verified, and Issued. Controlled documents also use stock and serial tracking.

Know when to hand off

  • Send admissions requiring a placement decision to the Principal or designated approver.
  • Ask the School Admin to correct missing accounts, relationships, terms, sections, or permissions.
  • Escalate health, safeguarding, identity, disciplinary, or billing concerns through the school's approved process.
  • Ask the document administrator to resolve official-profile, signatory, stock, or registry problems.

What happens next

A good handoff names the affected person or record, the verified facts, the action requested, and any deadline. It does not include unnecessary sensitive detail.