A YES project does not have to place every young person inside your own operation. Community-based models — placements hosted at local SMMEs, funded by the anchor employer — can deliver stronger outcomes and equally clean verification, if they are structured properly.
Most large employers approach a YES Youth commitment the same way: create the placements internally, absorb the young people into existing departments, and manage the year as an HR exercise. It works, but it has a familiar ceiling — meaningful roles run out long before targets do, and the surrounding community sees little of the benefit. There is an alternative structure with a strong track record: the employer anchors the funding while local SMMEs host the placements. Done properly, it serves the scorecard, the community, and the young people better at once. Done casually, it multiplies compliance risk across dozens of small workplaces. The difference is structure. ## The Community-Based Model in Outline In a community-based YES project, the anchor employer funds the programme and carries the commitment; placements are distributed across vetted host organisations — typically SMMEs, co-operatives, and community organisations in the employer's operational footprint; and a managing partner administers contracting, stipends, tracking, and reporting across the whole structure. The YES framework accommodates externally hosted placements, which is precisely what makes the model viable for employers whose own operations cannot absorb their full target meaningfully. For mining houses with social and labour plan obligations, the model has a further attraction: it directs measurable economic activity into host communities — stipends spent locally, SMMEs gaining capacity — in a form that is documented programme by programme. > An internal placement fills a seat. A community-hosted placement fills a seat, develops a local business, and keeps a stipend circulating in the town — with the same twelve months of funding. ## What the Model Demands Honesty requires stating the difficulty plainly: distributing placements across thirty small workplaces creates thirty times the supervision surface of one internal programme. Verification does not lower its standards because the hosts are small. Every placement still requires a valid agreement, verified attendance, reconciled stipend payments, and evidence of genuine work experience. The failures we see in loosely run community projects are predictable — hosts who treated the young person as informal help, attendance recorded from memory, stipends paid outside the documented channel. The corrective is a professionally managed structure: host vetting before placement, standardised contracting, centralised stipend administration, tracking that runs continuously rather than at quarter-end, and a support function that visits workplaces rather than waiting for problems to phone in. These are not optional refinements; they are what makes the model verifiable at all. ## What the Anchor Employer Should Evaluate Three questions determine whether a community-based project will hold. First, host quality: is there a genuine local base of businesses able to offer real work, and has someone with placement experience vetted them individually? Second, management capacity: who carries the administration across the distributed structure, and can they evidence outcomes from previous programmes — completion rates, absorption rates, verification history? Third, continuity: what happens after year one? Programmes designed as annual events rebuild everything each cycle; programmes designed as community infrastructure compound, with returning hosts, known networks, and improving outcomes. ## The Outcome Case Across our network's experience, community-hosted placements consistently produce something internal programmes struggle to match: absorption pathways. A small business that has hosted a young person for a year has already made the onboarding investment and seen the work — and small businesses, in aggregate, hire. Current absorption across our network runs at roughly 25–30%, with host employment the most common route. No structure guarantees employment outcomes, and sponsors should be wary of any claim that one does. What the community model demonstrably creates is more doors per placement. ## Governance That Keeps the Structure Honest Distributed projects need a governance cadence that matches their surface area. The arrangement that works: a steering structure in which the sponsor, the managing partner, and — where the project sits in a defined community — community representation meet monthly against a standing agenda: enrolment and attendance status, stipend reconciliation, host performance exceptions, and risks ahead. Between meetings, the sponsor receives reporting on the same cycle as any internal programme, and retains audit access on reasonable notice. Two governance details repay particular attention. Host performance must be manageable as a portfolio — under-delivering hosts identified by the tracking data and either supported or wound down mid-cycle, not discovered at year-end. And the exit phase deserves a governance milestone of its own: absorption conversations, references, and post-pr...