Describe the work in observable terms
Start with the problem, the intended outcome, and the context. Name the systems, users, constraints, and decisions the student can influence. Avoid turning a broad wish list into a placement brief.
\nList the skills that are useful without treating every listed tool as a hard gate. Explain what the student can learn and what support the organisation will provide.
\n- One clear question or deliverable.
- A realistic scope and a definition of done.
- The location, language, timing, and access requirements.
- A named supervisor and a review rhythm.
Make the assignment safe to start
Access, data handling, and security expectations belong in the brief, not only in an onboarding conversation. If the work involves production systems or personal data, state the boundary and escalation route explicitly.
\nA student should be able to ask what is allowed before they are expected to act.
\n- State what is in scope and what is not.
- Provide test data or a safe environment where possible.
- Explain how an incident or concern is reported.