Host-Community First: The Jobs a Development Creates
Every development announcement includes a jobs number. Almost all of them count the same thing: construction headcount at peak. It is the least durable figure available.
Construction employment is temporary by definition. It ends when the building ends. A community that hosted a two-year build and then watched every worker leave has not gained an economy — it has hosted one.
The employment that changes a neighbourhood is the employment that starts at handover.
The permanent bench
A functioning court needs people, permanently and every day. Security posts run three shifts. Grounds and landscaping need tending or they revert within a season. Common areas need cleaning. Power, water treatment, waste systems, pumps and generators need routine maintenance and someone competent on call when they fail. Facilities management needs a coordinator who knows the compound. Retail and convenience space inside a court needs operators.
None of those roles ends. They scale with the number of courts, they compound across a portfolio, and they are the roles most easily filled from within walking distance.
The construction phase is a burst. The operating phase is an economy.
Why "local hiring" fails when it is a policy and works when it is a design
Most developers state a preference for local hiring and then do not achieve it. The failure is usually structural rather than insincere.
If maintenance is contracted to a single outside firm on a portfolio-wide contract, that firm brings its own crew. If security is outsourced to a national provider, the guards are posted from a central roster. If the estate has no on-site management office, there is nobody to hire anyone locally in the first place. By the time anyone asks why the host community is not employed, the decisions that determined the answer were made months earlier, in procurement.
Getting it right requires deciding it early:
- Scope the roles at design stage. Know how many security posts, maintenance rounds, cleaning hours and grounds staff the compound will actually need, and write them into the operating model before handover, not after the first complaint.
- Contract in a way that permits local hiring. A service contract that specifies outcomes and staffing levels, and requires host-community sourcing where the skill exists, produces different crews than one that simply buys a national service.
- Train for the gap rather than importing around it. Most of these roles are learnable. Pump maintenance, biogas system operation, solar and battery upkeep, and access-control administration are trainable skills, and training a local operator produces someone who lives near enough to respond at two in the morning.
- Put a management presence on site. An estate office is what turns hiring intent into hiring practice, and it is also what keeps standards from drifting once the developer's attention moves to the next project.
The second-order effect
There is a further return that rarely gets counted. A resident of the host community who maintains the estate has a direct stake in its condition. Vandalism, informal dumping and encroachment — the three failure modes that quietly degrade estates across Lagos — are far less likely where the people around the wall have an economic relationship with what is inside it.
A court that employs its neighbours is cheaper to protect than one that is defended against them. That is not sentiment; it is the practical difference between a compound that holds its condition for a decade and one that needs a refurbishment in year six.
The commitment
Afrihood's position is that host-community-first hiring is part of the standard, not a corporate-responsibility line item — because the alternative produces a development that extracts from a neighbourhood while promising to lift it.
The jobs number worth publishing, then, is not peak construction headcount. It is how many people from within the host community hold permanent roles two years after handover, and whether the number is still growing.