Most organisations aren't short of alliance data. It's just scattered, a spreadsheet here, a CRM field there, a fact that only one person carries in their head. Individually, each piece might be accurate. Together, they rarely add up to a single reliable picture.

Unreliability rarely announces itself as bad data. It shows up as two reports giving different numbers for the same partner, a status update that turns out to be several months stale, or a piece of critical context that only surfaces because the one person who knew it happened to be in the room. Ask where the definitive, current record of this partnership actually lives, and whether more than one person could find it.

The risk isn't that anyone is being deliberately misled. It's that decisions get made on whichever version of the truth happened to be closest to hand.

Signs this is happening

• The same partner's status could be described differently depending on who you asked
• Critical information about a partnership exists mainly in one person's knowledge, not in a shared record
• Reports are compiled manually and take real effort to reconcile before a review
• Data used in the last major partner decision was more than a quarter old

This condition is frequently paired with the organisation lacks a clear view of its ecosystem, since a fragmented record at the partner level is usually what produces a fragmented view at the portfolio level.

Addressed early, this is a consolidation and ownership fix, a single source of record, clearly maintained. Left unexamined, it's the reason every alliance conversation starts with an argument about whose numbers are right.

This is an Evidence condition within the Alliance Oversight Gap framework. The Baseline Assessment tests whether your alliance reporting is consistent, current and trusted, or fragmented across systems and individuals.

This is one of five areas the Gap Detector Assessment measures. Find out where you stand.