Document the purpose, participants, activity, outputs, responsibilities and boundaries in language both organisations can use. Record approvals and changes separately from ideas. The scope should make it possible to tell whether a proposed request fits the current agreement or needs a new decision.
Describe the agreed activity in concrete terms
Begin with the educational purpose and a short account of what will happen. Name the learner group, delivery format, approximate timetable and intended output. Replace broad phrases such as industry collaboration with a description that a new coordinator could use: a practitioner reviews prepared project proposals during two facilitated sessions. Clarity at this level helps both sides recognise what they are actually committing to deliver.
Separate confirmed details from assumptions and open decisions. If the date or contributor is not yet confirmed, say so and name who will resolve it. Do not let a polished document make an unresolved plan appear approved. Include the current version and the people responsible for confirming the scope through the organisations’ appropriate processes.
State responsibilities and support alongside the output
Explain what the institution prepares, what the partner contributes and who coordinates the handover. Include supervision, participant communication, materials and feedback. If learners produce a report, describe the intended audience and whether it is an assessed learning exercise, an exploratory discussion document or something else. A learner output should not be assumed to be production-ready professional advice simply because an employer receives it.
Describe relevant support and escalation routes. Identify who handles ordinary questions and which established institutional processes apply to sensitive concerns. Keep personal support details out of the general scope. Where a specialist agreement or institutional review is needed, refer the matter to the responsible team rather than treating a one-page activity brief as a substitute for that process.
Make exclusions and information boundaries visible
State what is outside the activity: recruitment commitments, access to confidential information, continuing supervision or use of institutional facilities may all need separate decisions. Choose exclusions that address likely misunderstandings rather than a long generic list. Explain them positively in the delivery discussion so neither organisation discovers a consequential limit only after participants have started work.
Agree what material can be shared, who approves it and what happens to outputs after the activity. Public or synthetic material may be sufficient for an initial classroom exercise. Questions about ownership, confidentiality, publication or personal information should follow appropriate institutional review. Do not invent universal legal terms or assume that informal enthusiasm resolves those matters.
Use a change process that people can follow
Define how a proposed change is raised, who considers its effect and who can approve it. A request for an extra presentation may affect learner workload, partner time and assessment dates. Review those consequences before accepting it. Record the changed commitment in the current scope and tell the people whose work is affected, including participants when their instructions change.
At closure, compare the agreed scope with delivery and record any unfinished actions. Archive the final version where the next coordinator can find it. A useful scope supports memory and decision-making; it should not become a document that everyone signs and nobody consults. Review whether its wording was clear enough to prevent the misunderstandings that actually arose.
A fictional scope prevents an unplanned commercial deliverable
A fictional hospitality department and a regional business agree on a classroom exercise using an invented customer-service case. Learners will present improvement ideas and receive practitioner feedback. The scope states that teaching staff supervise the exercise and that the output is for learning discussion, with no operational implementation included.
Halfway through, the partner asks for a detailed rollout plan using live customer records. The coordinator checks the request against the agreed information boundary, workload and purpose. Both sides decide to keep the current exercise unchanged and discuss any later activity separately with the appropriate institutional owners. The scope does not answer every legal question; it makes the changed request visible early enough for a responsible decision.
A checklist for your next step
- Describe the actual activity and intended learner output.
- Distinguish approved details from open assumptions.
- Name delivery, support and change-approval owners.
- State the exclusions most likely to be misunderstood.
- Retain the current scope and final closure record.
Common questions
Can a scope note replace an institutional agreement?
No. A readable activity scope helps people coordinate, but it does not replace agreements, approvals or specialist review required by either organisation. Use the appropriate institutional process for questions about legal responsibilities, information, ownership or participant welfare.
Must every small change be escalated to senior leadership?
Not necessarily. Agree proportionate authority in advance. Routine scheduling adjustments may sit with the delivery owner, while changes to assessment, information access, cost or participant responsibilities may need a different approval. Record the boundary so coordinators do not have to guess.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AcadNexus.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.