Teach Early Escalation of Identity Ambiguity

A researcher can spend an hour building a detailed brief about the wrong company. The mistake often begins in the first minute, when a familiar name is treated as sufficient identity evidence. Training should therefore assess when someone notices ambiguity, not just whether they eventually fill the right fields.

Use a staged exercise that rewards an early, well-explained pause. Escalation is not failure when the next action depends on an identity the available sources do not establish.

Make the unit explicit

Ask whether the task concerns a legal entity, operating brand, buying site, or corporate group. These units can share a name and website while requiring different records. A researcher cannot resolve identity reliably if the brief itself switches between them.

GLEIF's GLEIF: The Legal Entity Identifier describes the LEI as a unique twenty-character code associated with legal-entity identification. That scope matters: an identifier can support a legal-entity match without identifying every branch, brand, or project. Do not assume every candidate has an LEI or that its absence makes the business invalid.

Use issuer and jurisdiction context for other identifiers too. A bare number copied without its source may not distinguish anything outside the original system.

Stage one: present a tempting match

In a fictional training case, a request names Harbor Technical and supplies a group website. The existing CRM contains Harbor Technical Services and Harbor Technical Components. Both use the same brand domain, but the task asks about maintenance at a named operating site.

The learner sees three facts: a shared domain, similar names, and different internal account IDs. The expected action is not to choose the more complete CRM record. It is to state that the requested site has not yet been linked to either candidate.

Ask the learner what would be unsafe to do now. Suitable answers include merging the records, copying an existing relationship owner to the site, or treating a prior contact restriction on one record as irrelevant because the names differ.

Stage two: add evidence that narrows but does not settle

The next synthetic extract lists Harbor Technical Services as providing maintenance nationally. Another lists Components as a manufacturer. That makes Services plausible for the activity, but it does not prove Services operates the named site.

A good learner writes a candidate hypothesis and identifies the missing relationship. They do not treat commercial plausibility as identity confirmation. The exercise should make this temptation visible: the most useful-looking account can still be the wrong entity.

The instructor now asks for a short escalation packet rather than more general browsing. The packet contains:

• Blocked decision: which existing account, if either, represents the named operating site.

• Candidates: the two internal IDs, preserved separately.

• Evidence: shared brand domain and the two scoped service descriptions.

• Gap: no source yet connects the site to a specific operating entity.

• Requested resolution: data steward or established relationship owner to verify that relationship through an approved source.

• Holding state: site research may continue; merging and affected contact action remain paused.

Stage three: test the response to authority pressure

A fictional account owner says they are sure Services is the right company but provides no supporting context. The learner should acknowledge the useful lead and ask what evidence establishes the site relationship. Seniority can authorize a commercial exception within someone's remit; it cannot by itself turn an uncertain identity into a verified fact.

If the owner provides a relevant, authorized internal record, the learner checks its scope and date. If not, the case stays unresolved. Silence after escalation is not approval to merge.

Assess the decision point, not only the final label

Record when the learner first identified ambiguity, what they held, which evidence they sought, and whether the escalation question was answerable. An eventual correct guess should not receive the same assessment as a supported decision.

Do not create a speed contest. Some ambiguity is subtle, and an overly tight timer can reward careless matching. The useful behavior is recognizing the consequence before acting on the assumption.

Finish with a new case involving a branch and a trading name rather than the same two companies. If the learner can preserve separate candidates and escalate the missing relationship there too, the exercise has begun to test transferable judgment instead of memorized names.

Continue with Plan a First Sales Hire's Research Training or Create a Useful Sales Research Service-Level Agreement.