Role confirmation before anchoring in strategy added

When you anchor a strategy on a specific person, you want to be sure it's the right person.

We found examples of people who were no longer at the company still showing up in playbooks, because the evidence of them leaving was never there. That's common practice: companies announce who they hire, not who left.

In one case, Legatus listed a Head of Marketing as the person to approach at an account, and the whole strategy pointed at her. She had left the company eight months earlier. Three separate directories still showed her in the role, none of them dated, and she had changed her surname, so a search on her old name and the company turned up nothing to contradict them.

Legatus now treats an undated directory listing as identification, not as proof that someone still holds the job. To call a role current it needs a live profile, a dated mention from the last twelve months, or the company's own team page. It also runs a departure check on the name by itself, which is what catches a name change.

When none of that confirms the role, Legatus marks it as low confidence and notes when the title was last publicly confirmed. The strategy then puts verification as the first step rather than building an approach on a person who may have moved on.

The wider rule is the same one everywhere in the playbook now: a fact Legatus couldn't verify can't carry the argument. It won't anchor Why now, Why us or the first move on something unconfirmed, and where the research contradicts itself, it shows you the conflict instead of quietly picking a side.