FindingcurrentGTM data

"Left the company" has many writers and many meanings

Departure sits in status picklists and checkboxes that other processes fill.

SymptomPeople marked as departed are still at their company, or people who left still show as current, depending on which field the sync reads.

The standard move is to read one "departed" field and drop the person from the account. In real CRMs, departure has no single home.

Departure often sits in one value of a status picklist that mostly holds qualification buckets. Such picklists often mix departure with qualification values.

Or it sits in a checkbox that more than one process can tick. An enrichment write-back can tick it from a single email-validator result, which is about an address rather than a person.

So read departure through curated rules that map the field and value pairs for each CRM. Give the employment edge an end date and a reason, and reopen it when the signal behind it is withdrawn.

Check your setup read-only

List every contact field that can mark a person as departed, from the CRM's field metadata. Count the values in each picklist that describe departure and the values that describe qualification. List the automations and integrations that fill each checkbox. A departure that rests on 1 enrichment or email-validation result alone is a gap.

Passes ifEvery process that fills a field marking a contact departed needs more than 1 enrichment or email-validation result.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Map the exact field and value pairs that mean departure in each CRM. Ignore the rest of the picklist.
  2. 02Record an end date and a reason on the employment link instead of dropping the person.
  3. 03Keep the field and value that ended the link with the reason. A reader can then see what said the person left.
  4. 04Reopen the link when the field or value that ended it is withdrawn.
Applies ifA job marks contacts departed, or reads a CRM status field, checkbox or enrichment flag to end a person's tie to an account.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.