Multi-Agency Collaboration in Education

Proof required

Submit your structured meeting notes (minimum 600 words) using the following headings: agencies and roles represented; key information each agency contributed; decisions and actions agreed; your own contribution or observations; and a 150-word reflection on what you observed about professional boundaries and information-sharing constraints in the meeting.

What gets checked

• All agencies present are identified by type and professional role (e.g., 'Educational Psychologist,' 'Family Support Worker') — not by name or identifying employer details
• Notes distinguish what each agency contributed as distinct from the others — not a merged narrative that loses the multi-agency dimension
• Reflection specifically addresses information-sharing boundaries — what could and could not be shared, and why

Common mistakes

• Attending a meeting where only school staff are present — a multi-agency meeting requires representatives from at least two different agencies or services
• Writing up the meeting from memory days later — notes should be taken contemporaneously or written up within 24 hours while detail is retained

Resources

What a verifier looks for

• Current enhanced DBS clearance is a prerequisite — multi-agency meetings concerning children require this without exception. Confirm it is documented.
• Recognised safeguarding training module completion must be documented — verify module name and completion date are stated.
• Supervisor approval from a qualified professional (SENCO, school SEND lead, or university placement tutor) must be obtained before the meeting is attended — retroactive approval does not satisfy this standard.
• All notes must be fully anonymised — no student names, school names, specific local authority identifiers, or combinations of details that could triangulate identity. Reject submissions with identifying information.
• The meeting must involve at least two distinct agencies — an intra-school meeting between teaching staff does not qualify as multi-agency.

You'll sign in first, then come straight back here.

Proof required

Submit your anonymised professional contribution document (500–800 words, in the appropriate professional format for your context) including: a summary of your direct professional observations; your recommended provisions with rationale citing evidence; and a brief note explaining which element of the student's plan your contribution addresses and what your professional role's boundary is.

What gets checked

• Document is written in professional register appropriate for a multi-agency audience, not academic essay style
• Recommendations are evidence-based — each cites a specific source (named EEF strand, SEND CoP provision, or named approach) not 'it would help to'
• Professional boundary is clearly stated — what falls within your role to assess/recommend versus what requires another agency's expertise

Common mistakes

• Writing a document that reports everything about the student from all perspectives rather than clearly scoping to your own professional observations and role
• Making recommendations outside your professional scope — a student teacher should not be making clinical recommendations; these must be explicitly flagged as requiring specialist referral

Resources

What a verifier looks for

• All SAFEGUARDING prerequisites apply — this document is based on real student case data. Confirm enhanced DBS, safeguarding training, and supervisor approval are documented.
• Named qualified supervisor (SENCO, placement coordinator, or university tutor) must review the document before submission — peer review is not acceptable for a professional contribution of this kind.
• Check that the document clearly scopes to the student's educational context and the writer's professional role — any clinical or medical recommendations should be flagged as requiring specialist referral, not made independently.
• Full anonymisation must be confirmed — including indirect identifiers such as specific school year groups, unusual combinations of needs, or localised programme names that could identify the student.
• Professional register check: the document must read like a professional report for a multi-agency audience, not an academic essay.

You'll sign in first, then come straight back here.

Proof required

Submit: (1) your written critical reflection (700–900 words, fully anonymised); (2) a written record of the supervisor discussion (200-word summary of key points raised and your responses, attributed to role not name).

What gets checked

• Reflection identifies specific contributions from at least two distinct non-school agencies — not a general statement about multi-agency benefit
• The tension moment is described specifically and the analysis goes beyond 'it was resolved' to examine how professional roles, information constraints, or values shaped the resolution
• Practice change is concrete and personally grounded — not 'I will be more collaborative' but a specific, observable change to how you will work with other agencies

Common mistakes

• Writing a descriptive account of the multi-agency meeting rather than a critical reflection on inter-professional dynamics — description is not analysis
• Addressing information-sharing only superficially ('there are rules about sharing data') without engaging with the specific tensions this created in the meeting context

Resources

What a verifier looks for

• All SAFEGUARDING prerequisites apply throughout this milestone — enhanced DBS, safeguarding training documentation, and named supervisor sign-off.
• University supervisor or SENCO (not a peer) must conduct the post-reflection discussion — and be named by role in the written record.
• Reflection must be fully anonymised — check for indirect identifiers including specific meeting contexts that could identify the student or family.
• Critical analysis of tension and information-sharing must be substantive — a submission that only describes what happened without analysing why is incomplete.
• Practice change must be personally grounded and specific — generic professional development aspirations do not meet this standard.

You'll sign in first, then come straight back here.