David Okafor is the Vice President of AI at TransAxis, a freight and logistics company, and he holds a Level 5 credential. This month he faces a requirement that catches many senior leaders off guard: the credential is not permanent. To revalidate, David must show that over the past year he did more than hold a senior title. He must document meaningful contributions that advanced artificial intelligence, inside his company and beyond it.

Why Revalidation Rests on Real Contribution

The logic behind annual revalidation is straightforward. A visionary credential certifies not a fixed body of knowledge but ongoing leadership in a field that changes every few months. A leader who stopped contributing a year ago is no longer at the frontier, regardless of what they once knew. Revalidation exists to keep the credential meaningful by asking a simple question every year: what did you actually move forward? A credential that never asked would eventually certify only that someone once passed an assessment, which is a claim about the past rather than about current leadership.

David's first instinct is to list his job duties. He shipped features, ran his team, hit his targets. But doing your job well is the baseline expectation, not a contribution to the field. The chapter's first hard lesson is the difference between activity and contribution. Activity is what you were paid to do. Contribution is the lasting change you created that outlives the task and helps others, whether that is a safer deployment pattern your peers adopt, a person you developed into a leader, or a standard you helped shape.

The distinction is uncomfortable precisely because it does not track effort or seniority. A demanding year of excellent execution can produce almost nothing that qualifies, while a modest write-up done in an afternoon can change how a dozen teams work. David's late-night bug fix helped TransAxis; his write-up of the failure pattern that a dozen other teams then used to avoid the same mistake is a contribution to the field. Once he sees that, the revalidation requirement stops looking like an administrative burden and starts looking like a question about how he spends the leverage his position gives him.

What Counts as a Meaningful Contribution

Contributions at this level fall into a handful of recognizable categories. David learns to see his year through these lenses rather than as an undifferentiated list of tasks.

• Applied advancement: shipping something that pushes practice forward, for example a responsible-AI deployment pattern that becomes the template others reuse, not just another feature.
• Knowledge sharing: writing, talks, open publications, or teaching that transfers hard-won lessons to a wider audience.
• Mentorship and talent development: deliberately growing other practitioners and leaders, measured by the people who advanced, not the hours spent.
• Field building and community impact: creating or sustaining the infrastructure of the profession, such as founding a practitioner group, running an event, or maintaining a shared resource.
• Governance and policy: shaping standards, contributing to policy consultations, or helping define norms that others will operate under.

The common thread is leverage. A contribution counts when its benefit extends beyond you and beyond the moment. Both halves of that test matter independently. Work that helps many people but evaporates when you stop doing it fails the second half; work that will last but only ever helped your own team fails the first. The categories are useful mainly because each represents a different route to satisfying both, which is also why a portfolio drawn from several of them is stronger evidence than a deep pile from one.

David also learns to watch for vanity contributions, activities that look impressive but move nothing. Sitting on a panel because it flatters the ego, collecting speaking invitations that repeat the same talk, or lending a name to an initiative he never actually worked on: these fill a page without advancing anyone. The test is not visibility but consequence. If David disappeared, would the contribution still stand and still help people? A pattern other teams now depend on passes that test. A logo on a conference program does not.

From Personal Achievement to Field Building

Earlier in a career, success is personal: master the skills, deliver the results, earn the title. At the visionary level the expectation inverts. The question is no longer how good you are, but how much better you made the people and the field around you. This is the shift from being a strong individual contributor to being a multiplier, and it is genuinely difficult for leaders whose entire track record was built on personal excellence, because the habits that earned the seniority are not the habits the seniority now calls for.

David sees why the later work in this block, field building and community impact and the honest assessment of his own continued growth, follows naturally. Revalidation is not a hoop; it is a forcing function that keeps senior leaders investing in others. A leader who spends a year only advancing their own standing has not met the bar, no matter how impressive that year looked on paper. The credential is a claim that you are lifting the field, and the portfolio is the evidence for that claim.

The Contribution Portfolio Categories

To make the abstract concrete, David builds a portfolio scorecard. It lists each category, what a real example looks like, the evidence he can attach, and a rough weight reflecting how much lasting leverage that category tends to carry. Weights are a planning aid, not an exact science; the point is to force honest self-assessment.

Read the evidence column carefully, because it is where most portfolios are weakest. Every entry names something external to the claimant: an adoption record rather than an assertion that others found it useful, a mentee's own testimony rather than the mentor's recollection, adopted language rather than a submission that vanished. The scorecard is the usable artifact of this chapter. David keeps it open all year and drops evidence into it as things happen, rather than reconstructing a year from memory the week before his deadline.

Building Your Annual Contribution Portfolio

David turns the scorecard into a working process.

• Keep a running log, not a year-end scramble. Each time David does something that might qualify, he adds a one-line entry with a link. By December the portfolio assembles itself.
• Separate activity from contribution. For every candidate entry he asks: did this help someone beyond me and beyond this task? If not, it is good work but not a field contribution.
• Attach evidence, not adjectives. "Mentored juniors" is an assertion. "Grew Ana and Beto into tech leads; both now run their own projects" with their confirmation is evidence.
• Balance the portfolio. A credible year shows contribution across at least a few categories, not five entries that are all the same kind of work.
• Look ahead. Where the portfolio is thin, David plans a deliberate contribution for next year, such as a talk or a standards submission, rather than hoping one materializes.

The running log is the step that quietly determines everything else. Evidence is easy to capture at the moment something happens, when the adoption message is still in a thread and the mentee's promotion is fresh, and nearly impossible to reconstruct eleven months later. Leaders who wait until the deadline do not just write a weaker portfolio; they systematically lose their strongest entries, because the contributions with the widest reach are usually the ones that travelled onward without them and left no trace on their own calendar.

Evidence and Metrics for Your Portfolio

Not all evidence is equal. David grades his entries on two axes: reach, meaning how many people or teams benefited, and depth, meaning how significant the benefit was. A talk seen by five hundred people but changing nothing scores lower on depth than a mentoring relationship that produced a new leader. A strong portfolio has a mix: a few high-depth, narrower contributions and a few high-reach, broader ones.

Useful measures David records include the number of teams that adopted a pattern he created, the number of people he demonstrably helped advance, the reach and any documented follow-on use of his published work, and the continuity of any community he built. A meetup that survives to its second year is worth more than one that ran once. He deliberately avoids inflating numbers, because a reviewer trusts a modest, verifiable claim more than an impressive, unverifiable one. That asymmetry is worth internalizing: a single inflated figure that does not hold up casts doubt over every other entry in the portfolio, including the true ones.

David's Contribution Log, Worked

Here is David's year, scored against his own template. The point tally is a hypothetical device he uses to sanity-check whether his portfolio is balanced and sufficient, not an official grading scheme. He sets himself an internal target of roughly 100 points across at least three categories.

• Applied advancement, 40 points: Built a model-monitoring pattern for TransAxis that three other logistics teams then adopted. Evidence: design doc, three adoption records.
• Knowledge sharing, 25 points: Wrote a widely read internal post and gave one external talk on why the monitoring pattern matters. Evidence: talk recording, audience of about two hundred.
• Mentorship, 30 points: Grew two engineers into tech leads. Evidence: their new roles and written confirmation.
• Field building, 20 points: Co-founded a city logistics-AI meetup now in its second quarter. Evidence: attendance list, schedule.
• Governance, 0 points: Nothing this year. This is the gap.

David's total is 115 points across four categories, comfortably above his internal target, with one obvious weakness: no governance or policy contribution. Rather than pad the number, he does two things. He submits the portfolio honestly, and he plans a governance contribution for next year by volunteering to comment on an emerging industry standard. That is exactly the behavior revalidation is designed to produce: an accurate account of real contribution, plus a deliberate plan to keep contributing.

It is worth noticing how the entries reinforce each other. The monitoring pattern is the applied advancement, the talk about why it matters is the knowledge sharing that carried it to people outside TransAxis, and the meetup is the venue where that kind of exchange keeps happening after the talk is over. A portfolio built around one substantial piece of work, extended deliberately through several categories, is easier to evidence and more credible than five unrelated entries assembled to fill the template.

The scoring also protects David from a subtler failure: a lopsided year. Suppose he had earned 120 points but all of it in a single category, five variations of the same conference talk. The tally would look strong and the portfolio would be weak, because a visionary leader who only ever does one kind of contribution is not really lifting the field, just repeating themselves. Spreading the points across categories is not bureaucratic box-ticking; it reflects the reality that field building, mentoring, applied advancement, and governance each reach different people in different ways. David reviews the shape of his portfolio, not just its total.

Finally, David writes a short narrative to sit on top of the log. Numbers show breadth, but a reviewer wants to understand the story: what he set out to advance this year, what actually changed as a result, and where he intends to push next. The narrative turns a list of entries into evidence of a leader who is deliberately shaping the field rather than accumulating credentials. That combination, an honest log plus a clear story of impact, is what a strong revalidation looks like.

Anti-Patterns to Avoid

Weak portfolios are weak in predictable ways, and most of them look busy rather than empty.

• Listing job duties as contributions. Shipping features, running a team, and hitting targets are the baseline expectation. Excellent execution of your own role is not, by itself, a contribution to the field.
• Vanity entries. Panels taken for the flattery, invitations collected for the same talk repeated, a name lent to an initiative you never worked on. Visibility is not consequence.
• The year-end scramble. Reconstructing twelve months from memory the week before the deadline, which loses precisely the contributions that travelled furthest without you.
• Adjectives instead of evidence. "Mentored juniors" is an assertion. Names, before and after roles, and the mentee's own confirmation are evidence.
• The lopsided portfolio. A strong-looking total earned entirely in one category, which certifies repetition rather than field building.
• Inflated numbers. Stretching reach or adoption figures, when one claim that does not hold up casts doubt over every other entry including the true ones.
• Padding around a gap. Manufacturing weak entries to disguise an empty category instead of naming the gap and planning to close it.

Practice Prompts

Run these against your own last twelve months, with real names, links, and dates rather than intentions.

• Sort your year. List everything significant you did and sort each item into activity or contribution using the single test: did this help someone beyond me and beyond this task?
• Fill the categories. Place your surviving entries into applied advancement, knowledge sharing, mentorship, field building, and governance. Which category is empty?
• Attach the evidence. For each entry, name the external artifact that proves it: the adoption record, the mentee's confirmation, the adopted language. Any entry you cannot evidence is a claim, not a contribution.
• Apply the disappearance test. For your three strongest entries, ask whether the contribution would still stand and still help people if you vanished tomorrow. Discard anything that fails.
• Grade reach against depth. Score each entry on how many people benefited and how significant the benefit was, then check whether your portfolio has a mix rather than clustering at one corner.
• Start the log and plan the gap. Set up the scorecard and add the first entry today, then name one deliberate contribution in your emptiest category for the coming year, with a date and a first step.

Reflection

Ask the disappearance question about your own year, honestly. If you had left your organization six months ago, what would still be standing that you built, and who would still be benefiting from it? Most senior leaders find this uncomfortable, because the work that consumed the most attention, the demanding, visible, hard-won execution, frequently leaves nothing behind that outlives the task. That is not a judgment on the work; it is a statement about which kind of effort compounds and which does not.

Then look at where your contributions cluster. Almost everyone has a natural category and one they have avoided for years while telling themselves they will get to it. For David it was governance, and the honest thing he did was report a zero rather than dress up something adjacent. Which is your avoided category, and what would the smallest genuine first step look like next quarter?

Glossary

• Revalidation: The annual requirement to demonstrate continued leadership contribution in order to retain a credential that is not permanent.
• Activity: What you were paid to do. Good execution of your own role, which is the baseline expectation rather than a contribution.
• Contribution: A lasting change you created that outlives the task and helps others beyond you.
• Leverage: The property that makes a contribution count, namely that its benefit extends beyond you and beyond the moment.
• Vanity contribution: An activity that looks impressive but moves nothing, judged by visibility rather than consequence.
• Reach and depth: The two axes for grading evidence, covering how many people or teams benefited and how significant the benefit was.
• Portfolio scorecard: The running artifact listing each category, the example contribution, the evidence attached, and an indicative weight.

Related Lessons

This chapter is the assessment counterpart to the work it measures. Building Your Annual AI Contribution Portfolio goes deeper on assembling and presenting the portfolio itself, and Revalidation & Renewal covers the wider requirement this sits inside. Continued Evolution & Growth takes up the honest self-assessment that follows a year's review.

For the categories themselves, Field Building & Community Impact develops the community infrastructure work, Mentoring & Knowledge Transfer covers the talent development that produces the mentorship entries, Publishing & Writing and Speaking & Public Engagement address the knowledge-sharing routes, and Contributing to AI Standards Development is the practical entry point for anyone whose governance category is a zero. Building Learning Infrastructure is the applied advancement most likely to still be standing after you leave.

Closing

Revalidation is not an administrative hoop attached to a credential. It is a yearly question about how a senior leader spends the leverage their position gives them, and the portfolio is simply the evidence. A leader who executed superbly and left nothing behind has answered that question honestly, and the answer is that this was a year of activity rather than contribution.

What makes David's submission strong is not its total. It is that every entry names something external that can be checked, that the entries reinforce each other rather than being assembled to fill a template, that a zero is reported as a zero, and that the gap comes attached to a plan. Keep the log running, evidence things as they happen, watch the shape of the portfolio rather than the tally, and write the short narrative that explains what you set out to advance and what actually changed. Do that and revalidation stops being a deadline and becomes the annual review a leader at this level should be doing anyway.

Key Takeaways

• Revalidation rewards contribution, not tenure. Keep a running, evidence-backed portfolio across several categories, distinguish activity from lasting leverage, and treat gaps as next year's plan rather than something to disguise.
• Activity is what you were paid to do; contribution is the lasting change that outlives the task and helps others. Excellent execution of your own role is the baseline, not the bar.
• The five categories are applied advancement, knowledge sharing, mentorship, field building, and governance and policy. The common thread is leverage beyond you and beyond the moment.
• The disappearance test settles most doubtful entries: if you vanished, would the contribution still stand and still help people?
• Attach external evidence rather than adjectives, since adoption records, mentee confirmations, and adopted language are checkable and assertions are not.
• Keep the log running all year. Reconstructing twelve months from memory loses exactly the contributions that travelled furthest without you.
• Grade entries on reach and depth, and aim for a mix rather than a cluster; shape matters more than total.
• Report gaps honestly and plan them, because a reviewer trusts a modest verifiable claim more than an impressive unverifiable one, and one inflated figure discredits the rest.

Frequently Asked Questions

Does doing my job well count? No, not on its own. Shipping features, running your team, and hitting your targets is the baseline expectation attached to the role. The question revalidation asks is what you moved forward beyond that. David's late-night bug fix helped TransAxis; the write-up of the failure pattern that a dozen other teams then used to avoid the same mistake is what counts as a contribution to the field.

What if I have nothing in one category? Report the zero. David had no governance or policy contribution and put that in his portfolio as the gap rather than padding it with something adjacent, then planned next year's contribution by volunteering to comment on an emerging industry standard. An honest account with a named weakness and a deliberate plan is precisely the behaviour revalidation is designed to produce.

How many categories does a credible year need? More than one, and ideally several. David's internal sanity check is roughly 100 points across at least three categories, which is a personal device rather than an official scheme. The reasoning behind it is that field building, mentoring, applied advancement, and governance each reach different people in different ways, so a total earned entirely in one category certifies repetition rather than breadth.

What evidence do reviewers actually trust? Anything external to you. Design docs and adoption records for a pattern, links and documented follow-on use for published work, names and written confirmation from the people you mentored, attendance and continuity for a community you built. Note the asymmetry on numbers: a modest verifiable claim is worth more than an impressive unverifiable one, and a single figure that does not hold up puts every other entry in doubt.

When should I start assembling next year's portfolio? Today, as a running log rather than a document. Each time something happens that might qualify, add a one-line entry with a link, and the portfolio assembles itself by the deadline. The alternative is not merely more work later; it systematically loses your best entries, because contributions that travelled onward without you leave no trace on your own calendar to remind you they happened.