> ## Documentation Index
> Fetch the complete documentation index at: https://support.metaview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The Talent Map Method

> Calibrate a role once, save it to your Metaview knowledge, and reuse it on every search for that role.

Most searches start from a job description and a guess. The Talent Map Method starts from evidence: you spend ten minutes calibrating the role once, save the result to your Metaview knowledge, and every search for that role runs against it from then on.

Everything built live in the webinar is below — the prompt used to kick off calibration, and how to get the output into your own workspace.

<iframe src="https://www.youtube.com/embed/CaOD-cLODH8" title="YouTube video player" frameborder="0" className="w-full aspect-video rounded-xl" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen />

<Info>
  **Ten minutes, once per role.** The calibration step is the investment; after that it's reusable context your whole team can search against.
</Info>

## The prompts

Both prompts from the session live in the [Prompt Library](/guides/prompt-library#4-deep-research), under **Deep Research**:

<Columns cols={2}>
  <Card title="4.1 — Calibration context kickoff" icon="crosshairs" href="/guides/prompt-library#41--calibration-context-kickoff">
    Builds deep role context — what the work is, what strong evidence looks like, what looks right but isn't, and where this talent sits.
  </Card>

  <Card title="4.2 — Reverse-map from your current team" icon="diagram-project" href="/guides/prompt-library#42--build-a-reverse-map-from-your-current-team">
    Maps your existing team into feeder companies, tenure patterns and career-path shapes — a description of how the team was actually hired.
  </Card>
</Columns>

Copy either one, paste it into the Sourcing agent, and fill in the blanks with your own role context.

<Warning>
  Both prompts are calibration, not search. They deliberately return **no candidate profiles and no ICP** until you approve the findings — and they stop and ask before saving anything. That gate is the point: you review the evidence, then decide what becomes reusable context.
</Warning>

## Building your Talent Map

Here's a quick step-by-step recap of how to run your talent map calibration in Metaview, then save it to your Metaview knowledge for repeat use.

<iframe className="w-full aspect-video rounded-xl border border-gray-200 shadow-sm" src="https://www.loom.com/embed/6222ed45c0174c1ba358e03196420e51" title="Building your Talent Map" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />

<Steps>
  <Step title="Open Knowledge">
    In Metaview Sourcing, click **Knowledge** (the book icon).
  </Step>

  <Step title="Choose the scope">
    **Personal** is visible only to you. **Workspace** is visible to your whole team.
  </Step>

  <Step title="Add New">
    Click `Add New`.
  </Step>

  <Step title="Set the when-to-use rule">
    **When to use:** `Use this when calibration is requested`
  </Step>

  <Step title="Paste the prompt">
    **What to do:** paste in the entire prompt — [4.1 Calibration Context Kickoff](/guides/prompt-library#41--calibration-context-kickoff) from the Prompt Library.
  </Step>

  <Step title="Create">
    Press `Create`.
  </Step>

  <Step title="Kick it off">
    In a new search, type `Let's calibrate:` followed by your role context. Metaview guides you from there.
  </Step>
</Steps>

<Tip>
  **Real evidence beats a well-built prompt every time.** When calibrating, add your Metaview conversations too — the kick-off call, feedback sessions, your hiring rubric. The more context the agent has to work from, the more closely the output will match what you actually need.
</Tip>

## Using your Talent Map to source

Once you've built the map, save it as context so the agent searches against it directly.

<Steps>
  <Step title="Open Knowledge">
    In Metaview Sourcing, click **Knowledge** (the book icon).
  </Step>

  <Step title="Choose the scope">
    **Personal** or **Workspace**, as before.
  </Step>

  <Step title="Add New">
    Click `Add New`.
  </Step>

  <Step title="Name the role in the when-to-use rule">
    **When to use:** `Use this when searching for [role]`

    Use the actual role you built the map for — that title is what triggers this context later.
  </Step>

  <Step title="Paste the Talent Map">
    **What to do:** paste in the entire Talent Map output.
  </Step>

  <Step title="Create, then search">
    Press `Create`. In a new search, kick off with the same role title: `Source candidates for [role]`.
  </Step>
</Steps>

<Note>
  A saved Talent Map is your stated criteria, written down and reused. Results still reflect alignment with those criteria rather than a judgment about candidate quality, and every decision about who to review or contact stays with you — see [Best practices for Sourcing](/account-management/privacy-and-security/ai-sourcing-best-practices).
</Note>

## Where to go next

<Columns cols={3}>
  <Card title="Prompt Library" icon="wand-magic-sparkles" href="/guides/prompt-library">
    Both calibration prompts, plus prompts for Notetaker, Sequences and Reports.
  </Card>

  <Card title="Talent Mapping" icon="sitemap" href="/guides/tutorials/talent-mapping">
    The Sourcing task for mapping a target company's org and talent distribution.
  </Card>

  <Card title="Market Mapping" icon="chart-pie" href="/guides/tutorials/market-mapping">
    Sizing a talent market before you spend a day sourcing.
  </Card>
</Columns>

Everything above runs in [Metaview Sourcing](/recruiting-platform/ai-sourcing). If you'd rather see it applied to your exact roles, [book a demo](https://www.metaview.ai/demo) and we'll build one together.
