Your Vendor Comparison Spreadsheet Is Going Stale Right Now, Whether You're Watching or Not

Angle

A first-ever systematic recency audit of a CDP knowledge base this week found that 91 of its 92 technical-side entries hadn't been re-verified against the market in 67 to 120 days — not because anyone made an error, but because re-verification has no natural trigger; nothing breaks visibly when a comparison note quietly stops matching reality. The audit's own conclusion is instructive: rather than manufacturing 91 hollow timestamp updates, it flagged which entries are foundational (most depended-upon) and prioritized those for real re-verification first. The same discipline — routine, prioritized staleness checks rather than a one-time evaluation treated as permanent — applies directly to any organization's internal CDP vendor comparison doc.

Key decision this helps with

Does the organization's CDP vendor comparison or evaluation criteria document have a recurring re-verification cadence, or was it last actually checked against the market on the day the vendor decision was made?

Tradeoffs the article will map

• Re-verifying every claim on a fixed schedule (thorough, but can produce hollow re-stamps with no new information) vs. prioritizing the most foundational, most-depended-upon claims for re-verification first (more efficient, but requires knowing which claims are actually load-bearing)
• Treating an initial vendor evaluation as a permanent artifact vs. treating it as a living document that decays at a knowable but unmeasured rate

Open questions / uncertainties

• What the actual decay rate is for a given organization's own comparison criteria — the audit names an observed range (67-120 days) for one knowledge base, not a universal constant
• Whether staleness in a vendor comparison doc gets caught before or after it drives a decision — there's no alarm that fires when a cited fact goes out of date

Knowledge-graph nodes this draws from

• concept.real-time-decisioning