Define the system boundary
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
A recruitment system includes people, policies, information and technology. Changing one part can move work elsewhere. Define where your responsibility begins and ends, who uses the result, and which constraints cannot be changed. Separate a business outcome, such as a team being able to run a new shift, from a recruitment output, such as three accepted offers. The output may contribute to the outcome without guaranteeing it. A useful charter names the problem, affected users, evidence, scope, owner and decision date. Document assumptions as questions to test rather than presenting a preferred tool as the solution.
Worked example
Fictional manufacturer Alder needs a second shift in twelve weeks. The recruitment team can improve search and assessment, but training capacity and equipment readiness belong to operations. Its charter targets qualified starters by week ten and records training availability as a dependency.
Put it into practice
Write the boundary and charter for a fictional expansion requiring four technicians. Identify two dependencies outside recruitment.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
A workable charter separates four accepted offers from four trained, productive starters. It names an operations owner for induction capacity and a recruitment owner for offer readiness. It does not promise production output solely from faster hiring.
Sources and further reading
Original Academy teaching and fictional examples. These references provide context, not endorsement. Edition 2026.09; updated 2026-09-24.
- CIPD: Recruitment
Professional context for the recruitment lifecycle.