How We Verify Practitioners — And Why It's Different From a Profile Review
A self-submitted profile is not verification. Here is what independent verification actually involves, why it happens before you ever see a brief, and what it protects.
The word verification is used loosely in the expert network industry. In most cases it means the person confirmed their name, their employer, and their job title. Sometimes it means a reference was called. Occasionally it means a credential was checked. In almost every case it means the practitioner was asked to tell you who they are, and then you decided whether to believe them.
That isn't verification. It's a profile review with an extra step.
Real verification answers a different question: not "does this person say they have the experience the brief requires?" but "does the evidence confirm that they do, independently of what they claim?" Those two questions produce very different answers. The difference between them is often the difference between a session that changes a decision and one that confirms what the seeker already believed.
This distinction is not academic. Organisations making decisions that depend on practitioner intelligence are not simply looking for someone who sounds credible. They are looking for someone whose account of the market they can build a decision upon. That requires something more than a self-submitted claim. It requires a process that is independent of the person being assessed.
What verification is actually checking
Kofa's verification process is not a credential check. Credentials tell you what courses someone completed and what qualifications they hold. They do not tell you whether the knowledge required by the brief is genuinely present.
Verification is checking six specific things — each of which a self-submitted profile cannot confirm and a simple reference call cannot establish.
The separation rule — why the person who finds cannot confirm
The most important structural feature of Kofa's verification process is one that is easy to overlook: the coordinator who identifies and introduces a practitioner is never the coordinator who verifies them.
This is not procedural caution. It is the recognition that the social dynamics between a coordinator and a practitioner they know well, the relationship, the loyalty, the natural human inclination to advocate for someone you introduced, will always make self-assessment more generous than independent assessment. Not through dishonesty, but through the way familiarity shapes judgment.
The coordinator who introduces a practitioner wants them to succeed. That's loyalty, not dishonesty. But when verification depends on the same person, it stops being verification — it becomes a second introduction.
What the recorded interview produces
The verification interview is the core of the process. Not because interviews can't be wrong — they can — but because a structured, recorded conversation, run by a coordinator with no stake in the outcome, surfaces things that no profile and no reference call will ever reach.
The interview is recorded for a specific reason. The record exists for accountability, not primarily for review. A practitioner who knows their account is recorded tends to be more precise, more conditional, and more honest about the limits of what they know. The record also means that the verification account can be reviewed against the session if questions arise about the match between what was claimed and what was delivered.
Current work — not career history
The interview opens with what the practitioner is doing right now, not what they have done. The specific decisions they have made in the last three to six months. What they are currently responsible for. Who they are currently accountable to.
This is not the opening question in most profile reviews — which tend to start with background. Kofa starts with the present because the brief requires current knowledge, not historical familiarity.
Specific geography — not regional familiarity
The interview asks about specific geographies, not regional or national experience. The answers are expected to name the place: "Nyeri," not "Kenya"; "Western Kenya," not "East Africa." The level of specificity reveals whether the knowledge is operational or secondhand.
A practitioner who has genuinely worked in a specific geography answers differently from one who has read about it or worked in a neighbouring area. The specificity of the geography in their answers is itself evidence about the depth of their knowledge.
Failure and exception — not success narrative
The most important questions in the verification interview are about what did not work. What the practitioner tried that failed. Where the standard approach broke down in their specific context. What they were wrong about and what they learned.
These questions separate practitioners who have deep operational knowledge from those with sector familiarity. Someone with genuine proximity to the work has a rich account of failure — because failure is where operational knowledge is earned. Someone with secondhand knowledge produces generic answers about "challenges in the sector."
Brief-specific experience — not general competence
The final section of the verification interview is structured around the specific brief. Not generic sector questions — the exact experience the brief defined as necessary. The practitioner is not told the full brief, but they are asked questions that are specifically calibrated to reveal whether their experience matches what the brief requires.
This is what distinguishes Kofa's verification from a general capability assessment. The brief defines what relevant looks like. The interview confirms whether it is present.
How verification holds over time
Entry verification — the structured interview before a practitioner's first engagement — is the beginning of the verification process, not the end of it. A practitioner who passes an entry interview and then consistently delivers shallow or inaccurate sessions has not maintained verification. They have passed a test they subsequently failed.
Kofa's verification is ongoing — maintained through how practitioners show up in sessions, not just through what they said in an interview before they had any.
Already know who you want to speak with? They still enter verification. The coordinator reaches out to confirm their experience and onboard them before the brief proceeds — so the record that protects your engagement is identical whether Kofa sourced the practitioner or you brought them. The platform's standard does not change because you supplied the person.
What this means for the organisation on the other side
When an organisation posts a brief to Kofa and a verified practitioner joins the prep room, the session that follows happens at the end of a trust chain — a series of relationships and processes that began before the organisation ever saw the practitioner's name. The two people in the room are strangers only in the formal sense.
The practitioner — the knowledge source
Someone whose experience was earned through years of proximity to the work. Not self-selected for this engagement — identified because a coordinator who knows their community recognised that their specific experience matched what the brief required.
Sourcing coordinator — the trusted introduction
A person embedded in the practitioner's community who has known them over years — not through a database search but through the kind of sustained proximity that produces reliable judgment about who someone actually is. Their introduction carries weight because their reputation is what makes the practitioner take the approach seriously.
Verifying coordinator — the independent confirmation
A different coordinator — independent of the introduction — who conducts the structured recorded interview. They have no stake in whether the practitioner passes. Their job is to establish, through direct conversation, whether the experience the brief requires is genuinely present. The record they produce is independent evidence, not a second endorsement.
Kofa — the platform's review and the record
The verification interview and the brief are reviewed together. The match is assessed. The practitioner's verified profile is created — not from what they claimed, but from what the independent interview established. This is the account that reaches the seeker.
The seeker — the organisation on the other side
The organisation that posted the brief. They do not see the verification interview. They do not need to. They receive what the process established — a practitioner whose experience has been confirmed through a process that is independent of the practitioner themselves. That is what they build their decision on.
An expert network is only as trustworthy as its verification process. Verify by self-submission and you have a directory. Verify independently — through structured interviews run by people with no stake in the outcome — and you have something different. Not perfect, but evidence-based in a way a profile review isn't, and accountable in a way a reference call isn't.
The organisation that posts a brief does not need to know every detail of this process. They need to know one thing: the practitioner who joins the session is there because the experience they hold has been confirmed independently — before the brief was matched, before the prep room opened, before anything was asked of the seeker except posting the question they needed answered.
Aminu Rabiu
Founder, Kofa Insights Limited
Start a brief. Every practitioner on the other side is independently verified.
Not a profile review, and not a self-submitted credential: a structured recorded interview conducted by a coordinator who has no stake in the outcome — reviewed against the brief before any match is made. Bring your own practitioner, and the same standard applies.
Start a Brief→Kofa's verification process is designed around one principle: the person who confirms a practitioner's experience cannot be the person who introduced them. Inside the platform, every verification interview is recorded, reviewed against the brief, and maintained as an ongoing standard across sessions — not established once and assumed to hold indefinitely.