People Infrastructure Portal
Telinno Consulting · Phase 5 — Process Sovereignty

The Organisation Owns
the Process. Not the Person.

Every role has a Job Success Profile that defines what the role is. This phase defines how the work actually runs — the Standard Operating Procedures behind every function. When a person leaves, is sick, or moves KADs, the process continues. No individual holds the company to ransom by being the only one who knows how something works.
ScopeAll 148 roles
Coverage4 KADs · 6 Countries
OwnerKAD Leads + HRBP
Phase5 of 5
Depends OnJSP (Phase 4a)
⚠
This phase closes the key-person risk gap
A JSP tells you what a role is responsible for. An SOP tells you how the work is done — step by step, system by system, handover by handover. Without SOPs, every person who holds a critical process is also holding the organisation hostage. This phase ensures that when someone leaves, is promoted, or is absent, the work does not stop. The process belongs to Telinno. Not to the individual who currently runs it.
Section 01
Three Principles of Process Sovereignty
These define why this phase exists and what it is trying to protect. Every SOP produced under this framework exists in service of one of these three principles.
Principle 01
The process belongs to the organisation, not the person
Any process that can only be executed by a single named individual is a liability. The moment that person is absent, promoted, or no longer willing, the process fails. SOPs transfer process ownership from individuals to the institution. The person runs the process. They do not own it.
Principle 02
Documentation is not bureaucracy — it is institutional memory
Experienced people leave. New people join. Markets evolve. An organisation that does not document how it works is perpetually starting from scratch. Every SOP produced here is a transfer of knowledge from a person's head into a form the organisation can hold, update, and rely on regardless of who is in the role.
Principle 03
A role without an SOP is an undocumented risk
The risk register for any organisation running critical functions — network operations, financial controls, regulatory compliance — must include undocumented processes. Operating across 6 countries with 4 KADs, Telinno cannot afford for knowledge to be trapped in individual heads. Every undocumented process is a single point of failure.
Section 02
What Every SOP Must Contain
These are the minimum required fields for a valid SOP at Telinno. An SOP that omits a MUST field is not complete and does not count toward Phase 5 readiness. SHOULD fields are required for critical and high-risk roles. MAY fields are discretionary.
01
Process Name & Purpose
The name of the process and one sentence on why it exists — what business outcome it serves and what fails if it is not done.
e.g. "Monthly Payroll Submission — ensures all 148 employees receive correct, on-time compensation in line with compensation register and country-specific statutory obligations."
Must
02
Process Owner & Backup
The named role (not person) responsible for the process, and the named role that covers it in their absence. Both must be able to execute without reference to the primary owner.
e.g. "Owner: HRBP KAD 2. Backup: HRBP KAD 1. Escalation if both unavailable: HR Lead."
Must
03
Trigger & Frequency
What starts this process — a date, an event, a request, or a system signal. How often it runs. Whether it is time-bound or event-driven.
e.g. "Triggered: 15th of each month. Frequency: Monthly. Also triggered by: new hire confirmation, salary amendment approval."
Must
04
Step-by-Step Procedure
Numbered steps a person new to the role could follow and produce the correct output. Each step names the system, tool, or document involved. Decision points are explicitly branched. No assumed knowledge.
e.g. "Step 1: Open HR data register in [system]. Step 2: Filter by KAD. Step 3: Verify each name against payroll input form. Step 4: Flag discrepancies to Finance within 24h before submission."
Must
05
Systems, Tools & Access Required
Every system, application, shared drive, or external platform the process touches. Login or access level required. Who grants access and how long it takes.
e.g. "Requires: HR data register (request access from IT, 2 working days). Payroll system (Finance admin access — request via KAD lead). Country payroll portals: NG, ML, NE, CI, CM."
Must
06
Output & Success Criteria
What is produced when the process is complete. What the correct output looks like. What a failed or incomplete output looks like. Who receives the output and by when.
e.g. "Output: Payroll submission file submitted to Finance by 20th. Success: Zero payroll errors for the month. Failure signal: Any correction required after submission."
Must
07
Failure Modes & Escalation Path
What can go wrong in this process, and what to do when it does. For each failure mode: the signal that it has occurred, the immediate action, and who is notified.
e.g. "Failure: System access unavailable. Action: Contact IT immediately. Escalate to Finance if not resolved within 4h of deadline. Manual submission form as fallback."
Should
08
Country Variations
Any step that differs by country jurisdiction. Statutory requirements, local portals, different deadlines, or language requirements for submissions in Mali, Niger, Côte d'Ivoire, or Cameroon.
e.g. "NE & ML: Government portal submissions require French-language documentation. CM: Statutory deduction rates differ from NG. CI: Separate Caisse de Sécurité Sociale submission required."
Should
09
Handover Checklist
A specific checklist for transitioning this process to a new owner. What the outgoing person must transfer, what the incoming person must confirm receipt of, and what a completed handover looks like.
e.g. "Handover: [✓] System access transferred [✓] In-flight processes documented [✓] Contact list for country counterparts shared [✓] New owner has run process once with outgoing owner present"
Should
10
Version History & Review Date
Date the SOP was created, by whom, and when it was last reviewed. Scheduled next review date. Brief log of what changed and why.
e.g. "Created: Jan 2025 by HRBP KAD 2. Last reviewed: Apr 2025. Next review: Oct 2025. Change: Added CM statutory deduction update per Finance instruction."
May
Section 03
The SOP Register
Every role type at Telinno is listed below. For each role: the key-person risk level if this process is undocumented, the SOP status, and the named owner. Update this register as SOPs are drafted and activated. The register is saved in your browser.
— Not Started — Draft — Active
Role / Function KAD Key-Person Risk SOP Status Owner (Role)
Section 04
Handover Protocol
SOPs only protect the organisation if the handover is executed. This protocol defines what must happen — and when — every time a role changes hands, regardless of whether it is a planned exit, a promotion, or an emergency.
Trigger
Planned Exit or Promotion
30 days
before exit
  • HRBP confirms SOP register status for all processes owned by the departing role. Any SOP not at "Active" status is escalated immediately.
  • Outgoing person identifies their backup (from SOP register). HRBP confirms backup is current on all critical processes — not just named, but operationally capable.
  • Outgoing person runs each critical process once with their backup present. Backup must be able to execute independently before handover is declared complete.
  • System access list produced. IT notified for access transfer. No access removed until backup confirms transfer is complete.
  • All in-flight processes documented with current status, next action, and deadline — not handed over verbally.
HRBP initiates.
KAD Lead signs off.
Trigger
Unplanned Absence
Day 1
of absence
  • HRBP pulls the SOP register and identifies all processes owned by the absent role. Backup owner activates immediately for all Critical and High risk processes.
  • If no backup is named or backup is also unavailable, HRBP escalates to KAD lead within 4 hours. Process does not pause waiting for escalation to resolve — interim owner is assigned on the same day.
  • If the absence extends beyond 5 working days, the interim owner documents any gaps they encounter in the existing SOP. These become updates when the process owner returns.
HRBP owns.
Same-day action.
Trigger
New Hire Into Role
Weeks 1–4
of onboarding
  • SOP register for the role is included in the induction pack on Day 1. New hire reviews all SOPs for their role in Week 1. Questions logged and fed back to HRBP for SOP improvement.
  • New hire is walked through each Critical and High risk process by their manager or backup owner — not just given the document. Confirmation of understanding is logged.
  • New hire is observed executing each Critical process at least once before they are considered the active owner. Observation is recorded in their onboarding file.
  • Any SOP gaps identified during onboarding are escalated to HRBP as SOP deficiencies — not treated as "things to figure out on the job."
Line manager.
HRBP tracks.
Trigger
KAD Restructure
Before
restructure live
  • HRBP maps all SOPs affected by the restructure before any announcement. A process that has no clear owner in the new structure is a blocker — the restructure does not proceed until all Critical and High processes have a named owner in the new structure.
  • Cross-KAD process transfers require formal SOP handover — the same protocol as a planned exit applies. Verbal agreements do not constitute a transfer.
  • SOP register is updated to reflect new owners before the restructure is live, not after.
HRBP + KAD Lead.
ELT informed.
Section 05
Review & Maintenance Cadence
An SOP that is not reviewed becomes inaccurate, and an inaccurate SOP is worse than no SOP — it creates false confidence. Every SOP has a mandatory review schedule tied to its risk level.
Monthly
Critical Risk Processes
  • Payroll submission across all 6 countries
  • Network incident escalation procedures
  • Regulatory filing and compliance submissions
  • Any process where a 24h delay has financial or legal consequence
  • Reviewed by: Process owner + HRBP + KAD Lead
Quarterly
High Risk Processes
  • Client billing and contract invoicing
  • HR data audit and people records
  • Procurement and vendor management
  • Cross-border assignment documentation
  • Reviewed by: Process owner + HRBP
Bi-Annual
Medium Risk Processes
  • Performance review administration
  • Recruitment and onboarding workflows
  • L&D plan management
  • Leave and absence management
  • Reviewed by: Process owner
Annual
Low Risk Processes
  • General admin and correspondence
  • Internal reporting formats
  • Archiving and records management
  • Non-time-sensitive team coordination
  • Reviewed by: Process owner
Phase Gate
Phase 5 Is Active When…
Process sovereignty is not achieved when the SOPs are written. It is achieved when the organisation can operate without any single person being irreplaceable. These are the criteria.
All Critical-risk SOPs are ActiveEvery process rated Critical in the register has a completed, reviewed SOP — not in draft. A named backup exists and has executed the process at least once.
No process has only one person who can run itFor every process in the register, a second named role can execute it without reference to the primary owner. This is tested, not assumed.
SOP register is live in all 4 KADsEach HRBP maintains an active register for their KAD. Statuses are current — not filled in once and forgotten. The register is reviewed in the monthly HRBP–KAD Lead sync.
SOPs are included in every inductionA new hire into any role receives the SOPs for that role on Day 1 as part of their induction pack. This is a mandatory induction item, not optional reading.
Handover protocol has been used at least onceThe handover protocol has been executed for at least one role transition — planned or unplanned — and the process was not disrupted. The protocol is credible only if it has been tested.
Country-specific variations are documentedAll SOPs for processes that touch more than one country include documented country-specific variations. No HRBP is informally carrying country-specific process knowledge that is not written down.
Telinno Consulting · SOP Framework · Phase 5 · April 2026
4 KADs · 6 Countries · 148 People