Most African subsidiaries hear the same message: “Follow global, move fast, spend less.”
That’s hard when policies live in SharePoint, templates differ by country, and Legal is juggling people issues, disputes, and urgent deals.
Here’s a 90‑day playbook any regional or subsidiary GC can run – without waiting for a global re‑org.
Days 1–15: Get the X‑Ray
Find out where time and value are leaking:
- Map your top recurring matters and score them on volume, cycle time, and pain.
- Compare the local templates you actually use with the global versions and note the clauses that cause friction every time.
- Ask Sales, HR, Finance, Procurement one question: “Where does Legal slow you down and why?” Capture one fix per function.
Days 16–45: Build a “Commercial Desk”
Make Legal predictable and easy to use:
- Publish a simple service catalogue: what Legal will turn in under 5 business days (NDAs, standard T&Cs, low‑risk DPAs, routine HR letters).
- Work from one core template and a short clause library, with clear rules on when you can localise and who approves.
- Use a short intake form and a visible SLA board (Excel/Trello/Teams) so everyone can see status and deadlines.
Days 46–75: Lock People and Data Risk
Tighten the two areas that quietly create the most risk:
- With IT, enforce role‑based access and one‑hour offboarding for privileged users.
- Standardise employment packs, fix obvious contractor misclassifications, and centralise personnel files.
- Pre‑approve a short DPA and keep a vendor list with data‑risk tiers.
- Have a basic incident playbook and two email templates (regulator + customer) ready.
Days 76–90: Prove It
Show Group and the business you’re in control:
- Share a one‑page “delta” document: where you follow global, where you don’t, and why.
- Move local firms to matter‑based pricing or caps, with speed and outcome metrics.
- Publish a simple monthly dashboard: matters completed, cycle times, blockers removed, and upcoming risks.
You don’t need a global restructure to run a sharp regional legal function.
You need a service catalogue, a playbook, JML discipline, and a dashboard.
Do that, and the business stops treating Legal as a gate – and starts using it as a lane.
