Adoption Roadmap

This roadmap describes how to move from Level 1 (Aware) to Level 3 (Practicing) as an individual, and from Level 1 to Level 3 as a team or organization. It is organized as phases rather than calendar months because adoption speed varies significantly by context, resource availability, and the complexity of the claims being documented. Estimated timelines are provided as reference points, not commitments.

Read Getting Started before this chapter. This roadmap assumes you have completed at least one full VERA claim.

How to Use This Roadmap

The roadmap has six phases. Most practitioners pass through all six, though not always in linear sequence. Phase 0 (Assessment) should be completed before any other phase. Phases 1 through 3 address individual practice. Phases 4 through 6 address team and organizational adoption.

If you are an individual practitioner who is not currently trying to scale VERA to a team, Phases 1 through 3 are your primary path. Return to Phases 4 through 6 when organizational adoption becomes relevant.

If you are leading team adoption, work through Phases 1 through 3 yourself first — you cannot effectively advocate for what you have not practiced — then run a compressed version of Phases 1 through 3 with your team before moving to Phase 4.

If you are an organizational leader commissioning VERA adoption, read all six phases, identify which phase your organization is currently in, and focus on the governance and obstacle-handling content in Phases 4 through 6.

Phase 0: Assessment

Duration: 1–2 days

Before building anything, establish an honest baseline. Phase 0 is a maturity assessment — not of aspirations, but of current state.

Conducting the Assessment

Work through the Maturity Model Overview and the six domain definitions. For each domain, answer the observable indicator questions with specific evidence — not general impressions.

Use the self-assessment checklists in the Level chapters as your primary assessment tool. Be conservative: if you are uncertain whether an indicator is met, score it as not met. The cost of underestimating your current level is low (you do easier work than necessary). The cost of overestimating is high (you skip foundational development and find gaps when they are harder to fix).

Assessment Outputs

Produce a simple profile document with:

• Your current level in each of the six domains (1–2 for most people starting here)
• The specific evidence for each rating (a sentence or two per domain)
• The single domain where you are strongest (your leverage point)
• The single domain where you are weakest relative to your goals

The assessment document is itself a VERA-adjacent exercise. It is not a full VERA claim — it does not go through the Verification Protocol — but producing it with evidence and explicit reasoning is good practice.

Common Starting Profiles

Solo practitioner, no organizational context: Typically Level 1 across all domains. Begin at Phase 1.

Small team with a motivated champion: Evidence and Reasoning typically at Level 1–2 (champion has been applying VERA informally); Governance, Sovereignty, and Integration at Level 1. Begin at Phase 1 individually; plan Phase 4 for Month 3 or 4.

Organization with a prior quality initiative (ISO, CMMI): Governance often at Level 2–3 (processes and mandates exist); Evidence, Reasoning, and Verification often at Level 1 (the quality framework doesn’t specifically address epistemic quality). Begin at Phase 2 for the governance-adjacent domains; Phase 1 for the epistemic domains.

AI-heavy organization: Evidence often at Level 1 (AI-mediated evidence is not documented systematically); Sovereignty often below Level 1 (sovereignty implications of AI tool use have not been considered). Begin at Phase 1 with a strong emphasis on VERA-P-0003.

Phase 1: First Practice

Estimated duration: 2–4 weeks | Target: Level 2 in Evidence and Reasoning

Goal

Complete three full VERA claims — all five phases, all the way through to a Verification Record — and understand what the protocol actually requires in your specific work context.

Week 1: The First Claim

Follow the Getting Started walkthrough. Choose a claim that matters. Complete all five phases. Expect this to take longer than you think. Do not shorten Phase 4.

Milestone: One complete claim record, one Verification Record, one claim registered (even if “the registry” is a row in a spreadsheet or a file in a folder).

Weeks 2–3: The Challenging Claims

The second claim should involve a problem that your first claim didn’t: missing evidence, a conflicted source, contrary evidence that resists easy resolution, or a compound claim that requires decomposition.

The third claim should be one where you have genuine uncertainty about the conclusion — one where the verification process might change your mind. This is the test of whether you are doing VERA or doing VERA-shaped compliance.

Before each claim, apply the relevant patterns from the Patterns Library. If the second claim involves missing evidence, use VERA-P-0001. If it involves an AI-assisted evidence search, use VERA-P-0003. The patterns are designed to be applied to real claims as you work; this is their first real use for most practitioners.

Milestone: Three complete claim records, three Verification Records. At least one claim where the verification process revealed a problem that required revising the claim statement or evidence set.

Week 4: Reflection and Self-Assessment

After three claims, conduct a brief retrospective:

1. What took the most time? If Phase 1 is consistently long, you are over-decomposing or writing imprecise claim statements. If Phase 3 is consistently long, your evidence search is happening in Phase 3 rather than Phase 2 (you are building reasoning chains before the evidence is complete). If Phase 4 is consistently short, you may not be verifying rigorously.

2. What did you skip or abbreviate? Be honest. The prospective search plan? The adversarial checklist in self-verification? Independent verification? Identify the step you find hardest to do and treat it as the step most worth doing.

3. What surprised you? The gap between what you thought you knew and what verification revealed is the measure of VERA’s value so far.

4. Re-assess your maturity profile. Compare to your Phase 0 assessment. Update the domains where your practice has genuinely developed.

Milestone: Updated maturity assessment with specific evidence. Evidence domain and Reasoning domain at Level 2 (observable indicators met per Level 2 checklist).

Phase 2: Building the Habit

Estimated duration: 6–10 weeks | Target: Level 2–3 in Evidence, Reasoning, Verification

Goal

VERA becomes a regular part of how you work with significant claims, not a separate exercise you do occasionally. By the end of Phase 2, you produce VERA documentation as naturally as you produce any other professional output.

The Habit Infrastructure

Habit formation requires friction reduction and trigger identification. For VERA:

Trigger identification: Identify the specific moments in your workflow where VERA should begin. These are the moments when a significant claim first appears:

• When you are asked to recommend something
• When you are beginning a research document
• When you are preparing a presentation that makes factual assertions
• When a team decision is documented

At each of these trigger moments, the first action should become: “Open a new claim record and write the claim statement.”

Template setup: Create a claim record template in whatever tool you use for writing. The template should have the fields from the Verification Protocol pre-populated with prompts. Remove the friction of remembering the structure so that the cognitive effort goes to the substance.

Registry setup: By Phase 2, your registry needs to be more than a mental note. Create a simple shared document — even a plain table — where claims are logged with their ID, statement, verification state, and review date. This registry serves two functions: it prevents you from re-documenting claims you have already documented, and it makes your VERA work visible to others.

Expanding to More Claim Types

Phase 1 claims were chosen for tractability. Phase 2 expands to harder types:

Claims with sparse evidence. Some important claims lack the Primary-tier data that makes Phase 1 claims clean. Apply VERA-P-0001 (absent evidence) and VERA-P-0002 (conflicted sources) as needed. Practice writing reasoning chains that honestly reflect the evidence’s limitations without abandoning the claim if it still has valid support.

Claims with compound structure. Apply VERA-P-0006 (Compound Claim Decomposition) to at least one claim. Experience the dependency tracking required when sub-claims must be verified before parent claims can be.

Claims involving AI-generated content. If you use AI tools in your work, apply VERA-P-0003 (AI-Generated Evidence Documentation) to at least one claim where AI contributed to the evidence. Experience the difference between Tier A (source retrieved) and Tier B (AI output without verified source) handling.

Expanding the Verifier Pool

Phase 1 likely relied heavily on self-verification. Phase 2 should involve at least two peer verification events — situations where someone other than you reviews a claim record and evaluates it against Phase 4 criteria.

The first time you share a claim record for peer verification, prepare your peer by walking them through the criteria checklist. The goal is genuine evaluation, not a rubber stamp. If the peer finds nothing in Phase 4, either the claim is exceptionally clean or the peer needs guidance on what adversarial verification looks like.

Milestone: 8–12 claims documented. At least two peer-verified. Claims span at least three different types of evidence situations. Registry is maintained and findable. A review cadence exists for the oldest claims.

Phase 2 Obstacles

“I don’t have time for this.” VERA takes more time upfront and less time later — when the claim is challenged, when evidence needs updating, when someone needs to understand where a conclusion came from. Track your total time on claims, including revision and challenge handling, not just documentation time. For most practitioners, VERA time pays back within three to five significant claims.

“My claims keep changing during Phase 3.” This is correct behavior — Phase 3 is supposed to reveal whether the claim as stated is actually what the evidence supports. Revising the claim statement after building the reasoning chain is not a failure; it is verification working. Build the expectation into your process: claim statements are provisional until Phase 4 is complete.

“I can’t find independent verifiers.” At Phase 2, Peer independence (someone with relevant competency and no stake) is the target. This does not require a VERA expert — it requires someone who will read your claim record carefully and try to find problems. The peer does not need to know the VERA criteria by name; they need to understand that their job is skeptical review, not endorsement. Walk them through the criteria informally.

Phase 3: Reaching Level 3

Estimated duration: 4–8 weeks | Target: Level 3 in Evidence, Reasoning, Verification; Level 2 in Governance and Sovereignty

Goal

VERA practice reaches the Level 3 definition: any significant claim you produce can be audited against the Verification Protocol. The practice is reproducible — it does not depend on which phase of your month it is or how pressured you feel.

What Level 3 Actually Requires

Level 3 is defined by all significant claims, not most. This requires a precise definition of “significant” — one you apply consistently, not case-by-case. Write that definition down. It should be specific enough that you can apply it to any given claim without deliberation.

Example definition for an individual practitioner: “A claim is significant if it (a) will appear in an external communication, (b) informs a decision with consequences I cannot easily reverse, or (c) is cited to justify resource allocation.”

The Level 3 test: look at everything you have produced in the last four weeks that meets your significance definition. Are all of it VERA-documented? If yes, you have Level 3 coverage. If no — if there are significant claims that are undocumented — you are still at Level 2 regardless of how good your documented claims are.

Sovereignty Assessment

Phase 3 includes completing the formal sovereignty assessment described in the Sovereignty Principles chapter. Work through the five sovereignty assessment questions for each principle. Be specific: do not answer “generally yes” — answer with a specific, named tool, process, or policy.

Common Level 3 sovereignty findings:

• S1 (Data): Evidence stored in proprietary tools with uncertain export capability. Document the gap and its remediation plan.
• S2 (Reasoning): Reasoning chains are visible to the practitioner but not to other stakeholders who might be affected by the claims.
• S4 (Process): Verification criteria are documented in this framework but have not been published in a stakeholder-accessible form in your specific organizational context.

Document each finding with a remediation plan that is specific enough to execute: named owner, specific action, target date.

Establishing a Review Cadence

By Phase 3, your oldest claims from Phase 1 are approaching their review dates. Conduct your first scheduled review:

• Check whether the evidence is still current (apply VERA-P-0005 decay classes)
• Check whether any upstream claims have changed state (apply VERA-P-0012 cascade check)
• Re-read the reasoning chain: does it still hold?
• Update the Verification Record if anything has changed

The first scheduled review is instructive. It reveals how much claims drift from their verification baseline over three to six months and whether your review cadence was calibrated correctly.

Phase 3 milestone: Full Level 3 maturity assessment meeting all Level 3 checklist criteria. Sovereignty assessment completed with gaps documented. At least one scheduled review completed. Claim registry is active and current.

Phase 4: Team Adoption

Estimated duration: 2–4 months | Target: Level 3 across team; Level 2 Governance

Goal

VERA practice is shared across a team. Multiple practitioners produce VERA-compliant claim records consistently. The team has a shared registry, shared evidence quality calibration, and a functioning peer verification process.

Pre-Conditions for Team Adoption

Team adoption should not begin until the team leader (or at least one practitioner) has reached personal Level 3. Leading a team through VERA adoption without having personally experienced Phase 1 through 3 produces the worst outcome: governance before substance, compliance surface before epistemic depth.

The Team Kickoff

Begin team adoption with a working session, not a training presentation. The format:

1. 30 minutes: One of the experienced practitioners presents a real claim record from their own work — full evidence set, reasoning chain, Verification Record. Not a simplified example: the actual artifact from Phase 1 or 2, with its imperfections.

2. 60 minutes: The team selects one current claim — something they are actually working on — and works through Phase 1 and 2 together, with the experienced practitioner facilitating. Produce a real claim stub and evidence set, not an exercise.

3. 30 minutes: Debrief on what was harder than expected, what was clarifying, and which claims in current work most need VERA treatment.

Do not spend the kickoff explaining VERA. Demonstrate it. The documentation exists for explanation; the working session is for experiencing.

Team Calibration

Different practitioners rating the same evidence will produce different quality tier ratings and different confidence ratings. The first task after the kickoff is calibration.

Evidence quality calibration: Produce a set of five evidence items from your domain. Have each team member rate each item independently. Compare ratings. Where there is disagreement greater than one tier, discuss the evidence and agree on the correct rating and why. Document the agreed ratings as your team’s calibration examples — your mini version of the Patterns Library anchor examples.

Confidence calibration: Share two or three completed claim records with confidence ratings. Have team members assign their own ratings independently before seeing the assigned rating. Compare and discuss gaps. This is an early version of VERA-P-0013 (Claim Confidence Calibration).

Shared Registry Design

The team registry is more complex than the individual registry. It needs:

• A standard claim ID format that avoids collisions across practitioners
• A clear ownership model (who is responsible for maintaining each claim?)
• A significance threshold definition that all team members apply consistently
• A process for registering upstream dependencies at claim creation time (for VERA-P-0012)

Choose the simplest registry tool that meets these requirements. See Tooling & Integration for specific tool options.

The First Team Peer Verification

The first team peer verification event — where one practitioner verifies another’s claim using the full Verification Protocol — is a high-leverage moment. It often reveals:

• Calibration gaps between the claimant and verifier
• Patterns in what the claimant consistently omits
• Evidence quality standards that differ between practitioners

Make this a learning event, not an evaluation. The verifier’s goal is to produce a Verification Record that helps the claimant improve future claims, not to produce a pass/fail judgment.

Governance Foundations

At Phase 4, the team needs its first formal governance element: a documented significance threshold. This is a one-page document that defines:

• What claims require VERA treatment (the significance threshold)
• Who has responsibility for the claim registry
• What the standard for peer verification is (who can verify whom)
• What happens when a claim is contested

This document does not need to be complex. It should be specific enough that any team member can determine, for any given claim, whether VERA treatment is required.

Phase 4 milestone: Team Level 3 maturity assessment across all team members. Shared registry live and used. Significance threshold documented. At least three cross-practitioner peer verifications completed.

Phase 5: Institutionalization

Estimated duration: 4–8 months | Target: Level 3 Organization; Level 3 Governance

Goal

VERA is organizational policy, not team practice. The mandate exists. Ownership is formal. Training is part of onboarding. The claim registry is organizational infrastructure.

The Governance Mandate

Institutionalization requires an explicit decision by someone with organizational authority that significant claims will be documented and verified in VERA format. This decision produces a policy document with:

• Scope: Which claims require VERA treatment (the significance threshold, defined at organizational scale)
• Ownership: Who is responsible for the VERA framework within the organization (the VERA owner role)
• Standards: The Verification Protocol version in use and any organizational amendments
• Enforcement: How non-compliance is handled (at minimum: undocumented significant claims are not treated as verified in organizational decision-making)
• Training: How practitioners are trained and what the baseline competency requirement is

Getting this mandate requires making the business case for VERA. The business case is not abstract. It should draw on concrete examples from Phases 1 through 4:

• A specific claim where verification revealed a problem that would have been expensive to discover later
• A specific decision that was better because the claim supporting it was traceable
• A specific instance where VERA’s traceability allowed an error to be corrected cleanly

Abstract arguments for epistemic quality rarely secure mandates. Evidence of value from real work does.

Training Infrastructure

Organizational Level 3 requires that new practitioners receive VERA training as part of onboarding. This training should:

• Be mandatory, not optional
• Include a hands-on component (completing a practice claim, not just reading documentation)
• Include access to the team’s calibration examples and patterns library
• Establish contact with a VERA mentor (an experienced practitioner available for questions during the first month)

Training should be owned by the VERA owner role, not by individual champions.

Registry as Infrastructure

At organizational scale, the registry can no longer be a shared spreadsheet. It needs search capability, dependency tracking, ownership attribution, state management, and review cadence alerts. This does not require purpose-built VERA software — many wiki or knowledge management platforms can be configured to meet these requirements. See Tooling & Integration.

Phase 5 milestone: Documented VERA policy with named ownership. VERA training included in onboarding. Claim registry on organizational infrastructure with search and dependency tracking. First formal VERA quality review conducted by the VERA owner.

Phase 6: Governance Maturity

Target: Level 4 (beginning of)

Goal

VERA quality is measured and improving. The governance function reviews metrics, identifies patterns, and makes evidence-based investments in VERA quality.

Phase 6 is beyond the scope of this roadmap’s detailed guidance — it requires the organizational infrastructure established in Phase 5 and typically begins in Year 2 of adoption. The Level 4 chapter describes what Level 4 looks like across all six domains. The Level 4 self-assessment checklist is the practical starting point.

The transition from Phase 5 to Phase 6 is marked by one change: the VERA owner stops asking “are we doing VERA?” and starts asking “how well are we doing VERA?”

Handling Common Obstacles

“Leadership isn’t interested.”

Leadership interest in VERA follows from demonstrated value, not from explanations of the framework. The sequence that works:

1. Apply VERA personally until you have three to five high-quality documented claims (Phases 1–2).
2. Use one of those claims — specifically one where verification revealed a problem — in a leadership conversation. Do not say “VERA found this problem.” Say “When we documented the evidence for this claim carefully, we found that [specific problem].”
3. Offer to apply VERA to one claim that leadership cares about. Make the offer specific: “Can I document the evidence and reasoning for the [specific assertion] we’re going to present to the board?”
4. The experience of having a claim they care about go through verification — especially if verification reveals something — creates leadership interest more effectively than any explanation.

“VERA is slowing us down.”

VERA does slow down claim production. It speeds up claim use, claim updating, and error correction. The net time balance depends on how often your claims are challenged, revised, or used downstream.

If VERA feels purely like overhead, the most likely causes are:

• The significance threshold is set too low (you are applying VERA to claims that don’t warrant it)
• The claim registry is not integrated with your workflow (VERA is parallel work rather than primary work)
• The claims you are documenting are not being used downstream (VERA’s value is in the downstream)

Address the root cause rather than relaxing the standards.

“We can’t find independent verifiers.”

At Phase 2: self-verification with adversarial stance (VERA-P-0010) is the interim solution. At Phase 4: cross-practitioner peer verification within the team. At Phase 5: the organizational verifier pool. Not everyone needs to verify everything; a small group of practitioners trained to Expert-level can verify high-stakes claims for the whole organization.

If the domain is genuinely too specialized for internal peer verification, VERA-P-0011 (Expert Verifier Onboarding) provides the path to engaging external domain experts without requiring them to be VERA-trained.

“People are filling out the forms but not doing the thinking.”

This is the compliance surface problem described in the Level 3 chapter. It means verification is not rigorous enough — claims are being passed that should not be.

The fix is not more documentation requirements — it is better verification. Specifically: the first-pass verification rate needs to be meaningful. If 95% of submitted claims are verified on the first pass, the criteria are not being genuinely applied. A first-pass rate of 60–80% indicates real scrutiny.

Examine the Verification Records being produced: do they have per-criterion findings, or just a final state? Do they have confidence ratings with written justifications, or just numbers? Records that are substantively thin are a signal that verification is in compliance mode.

“Our most important claims can’t be verified without revealing confidential information.”

This is a real constraint, particularly in competitive intelligence, legal, and regulatory contexts. The solutions:

• Compartmented verification: The verifier has the same clearance/access level as the claimant; the independence requirement is met without disclosing beyond the authorization boundary.
• Verification of structure, not content: A verifier reviews whether the reasoning chain’s structure is valid and whether the evidence quality ratings are appropriate, without necessarily seeing the evidence content directly. This is lower independence (the verifier cannot check E5 chain-of-custody directly) but better than no verification.
• Third-party verification with NDA: An external verifier with appropriate agreements can satisfy independence requirements in cases where internal verifiers cannot.

Document whatever constraint applies and its impact on the verification’s independence level. A Verification Record that honestly states “Peer independence achieved within security clearance boundary; verifier did not directly review evidence content” is more honest and epistemically useful than one that conceals the constraint.

Roadmap Summary

Proceed to Tooling & Integration for guidance on the tools and workflows that support VERA practice at each phase of this roadmap.