IqOrg
How it works

Map what could break, before it does — and hand it over cleanly when people leave.

Start with a Continuity Map: choose a critical role, workflow, team or restructure, and IqOrg scores how fragile the work is and names every single point of failure with a ranked fix list. When someone does leave, the same workspace runs a guided handover, from resignation to successor.

Continuity Map

Map what breaks, before it does.

In the same workspace as your handovers, map a critical role, workflow, team or restructure — no documents, no integrations, just plain operating structure.

Choose what to protect

Start from a critical role, a workflow, a team, or a restructure scenario.

Answer plain-English questions

A short set of plain-English questions about owners, steps, approvals and dependencies.

Watch the map build

The dependency map and fragility score build live as you answer.

Export the fix list

Take the single points of failure and ranked fix list with you as a PDF.

Handover

A handover that runs itself, in four steps.

The departing employee and the manager do not need an account. Each receives a single secure link, scoped to one handover.

1

People and Culture starts the handover

When a resignation lands, your People and Culture team opens a handover and sends a secure capture link to the departing employee.

2

The departing employee completes a guided capture

The employee records their role, the processes they own and the knowledge their successor needs, then uploads their key emails and documents. No account is required.

3

The line manager reviews and approves

The manager opens a secure review link, reads the full pack, leaves comments and approves it, or requests changes. No account is required.

4

The organisation builds a living map

Every approved handover adds to a living map of who knows what, so the next departure is visible before it hurts.

What gets captured

Everything a successor needs, in one place.

01

People and Roles

Who does what, where they sit, and how roles relate across teams and reporting lines.

02

Responsibilities

The decisions, approvals and outcomes each role genuinely owns — mapped, not assumed.

03

Processes and Workflows

How work moves end to end, including the informal routines that keep the business running.

04

Systems and Decisions

The tools work depends on and the recurring decisions that shape operational outcomes.

05

Knowledge and Continuity

The institutional context that protects continuity when people change roles or leave.

IqOrg Intelligence Core

Ask IqOrg

Ask how your organisation works.

Leaders, managers and successors query the captured handovers in plain language and receive structured answers grounded in your organisation's own captured data, not generic summaries.

Leadership prompts

IqOrg Ask
Grounded · Permissioned
Show me where we rely on a single person.

4 critical single-person dependencies identified.

01

Month-end reconciliation

Owned solely by D. Okafor — no documented backup.

02

Vendor onboarding approvals

Routes through one operations lead.

03

Production access provisioning

Single approver, no secondary.

Recommend documenting and cross-training the top two before Q3.
Ask about roles, processes, dependencies or knowledge…
Get started

Find your single points of failure before they find you.

Build a Continuity Map: choose a critical role, workflow, team or restructure, score how fragile the work is from 0 to 100, and get a ranked fix list — built from plain operating structure, nothing sensitive.