When placements are spread across thirty small businesses instead of one big employer, the people work changes shape. What HR looks like when the workplace is an entire community.
Traditional programme HR assumes a perimeter: one employer, one site, one set of policies, and everyone inside the same gate. Community-based programmes tear that assumption up. Fifty young people placed across thirty small businesses in one town is not one workplace — it is thirty workplaces, most of which have never supervised formal staff, connected only by the programme that binds them. The people work does not shrink in this model. It changes shape, and programmes that fail to redesign for it fail in slow motion. ## What Actually Changes In a single-employer programme, HR leans on the employer's own machinery: induction processes, supervisors who have managed people before, payroll systems, someone to phone when things go wrong. In a distributed community programme, most hosts have none of that machinery. The programme's people function has to supply it — portably, repeatedly, and at a scale of one or two placements per site. Practically, that means induction that happens thirty times in thirty settings; supervisors who are business owners first and mentors second, and who need preparation for the difference; records that are captured consistently across sites with wildly different admin habits; and support that travels — because a struggling placement at a panel-beater on the edge of town will not walk itself into an office. > In a community programme, the host provides the work. Everything else that makes it employment — structure, support, records, fairness — has to arrive with the programme. ## The Supervisor Is the System Strip a distributed programme to its load-bearing wall and you find the host supervisor — usually the owner. Whether a placement succeeds depends less on the young person's CV than on whether that owner sets expectations, gives feedback, and flags problems early. Yet most programmes spend their preparation budget entirely on the youth and none on the supervisors. The people partner's job is to close that gap: a practical briefing before the placement starts (what to expect in month one, how to run a five-minute check-in, what to do when attendance slips), a named human to call, and light-touch visits that catch drift before it becomes crisis. Where we have done this properly, host problems drop to a fraction of what unsupported programmes experience — not because problems stop, but because they get caught at flag size. ## Fairness Across Thirty Workplaces Distributed placements raise a fairness question single-site programmes never face: the same stipend can buy very different experiences. One host gives real work and mentorship; another quietly uses a placement as free labour for a job nobody else wants. Consistency is a design duty — clear host agreements about what the placement includes, check-ins that ask the young person as well as the host, rotation or intervention where a site is not delivering the experience, and records that make the differences visible. A community programme's reputation in its own town is set by its worst placement, not its best. ## The Record Question, Multiplied Every compliance point that applies to one employer applies to each host: attendance, supervision evidence, incident records, exit documentation. The workable answer is centralisation — the programme's people partner carries the records for everyone, capturing at each site on a fixed rhythm, so that thirty informal businesses produce one verification-ready file. Expecting each host to run its own compliant HR administration is the design error that sinks these programmes at audit time. ## Exits, Multiplied by Thirty The exit phase — where our people-first approach always concentrates — takes on community dimensions in a distributed programme. Thirty hosts means thirty possible absorption conversations, each needing the month-nine prompt that owners rarely initiate themselves; thirty references to confirm; and one town-sized opportunity that single-employer programmes never have: cross-host referrals. The young person whose own host cannot hire is often exactly what the business three streets over needs — but only if someone is holding the whole map. The programme's people partner is that someone, and the exits are where the map pays out. Done well, a community programme's final quarter looks like a town quietly sorting its young people into futures: absorptions confirmed here, referrals walked across the street there, next-programme entries and self-employment starts supported everywhere else. Done poorly, it looks like thirty simultaneous endings nobody prepared. The difference is somebody's job — and it should be in the design from day one. ## Where Abamandla Fits This distributed people work is Abamandla's home ground: sourcing and screening across a community, preparing hosts as well as youth, travelling support, centralised records, and exits managed properly at every site. For sponsors and programme designers planning a community-based project, the people structure is the difference be...