A lead freshness SLA should name each material field or event, its authoritative source, the timestamp that starts its clock, the decision it supports, its target age or review band, and the action taken when the threshold is crossed. Publish only thresholds supported by current evidence and operational capacity. This framework proposes a method, not a Partner Connector performance promise or universal benchmark.
1. Define freshness for a decision
Ask what could become misleading between qualification and purchase. A historical conversation remains accurately dated even if the person’s current role changes. A current-title claim may become wrong. A company-size estimate can change or use a different source definition. “Updated yesterday” means little unless it says which field, source, and event changed.
The ICO’s accuracy guidance emphasizes that accuracy depends on what the record is intended to show and that source and status should be clear. Apply qualified legal review where personal data and applicable law require it.
2. Build a field-level freshness register
| Evidence | Clock starts at | Crossing action |
|---|---|---|
| Qualification statement | Dated conversation or submitted response. | Keep as historical evidence; disclose age; revalidate if required for purchase. |
| Role or title | Named source verification event. | Warn, recheck, or remove current-state claim. |
| Company attributes | Source retrieval date and source version. | Refresh affected fields without rewriting the original event. |
| Contact channel | Verification or authorized use event. | Reverify under policy or mark unknown; do not guarantee response. |
| Ownership/conflict check | Buyer-scoped comparison event. | Rerun at reservation or purchase. |
These examples do not prescribe durations. Set initial numbers from your observed change rate, dispute history, buyer needs, source cost, and risk. Preserve the rationale and confidence behind every threshold.
3. Choose an SLI before an SLO
A service level indicator describes what is measured. Examples include the percentage of active listings whose required fields remain within their documented review band, or the percentage of purchases where the buyer conflict check completed within a bounded time. Define numerator, denominator, exclusions, window, data source, and late-arriving events.
Only then set an objective. Google’s official SRE Workbook guidance on SLOs recommends documented targets, stakeholder agreement, measurement detail, rationale, reviewers, and a process for revision. Lead data is not a web service, but the discipline—explicit measurement tied to action—is useful.
4. Make the freshness state visible
Show the field or evidence name, as-of time, source type, current/historical meaning, threshold band, and next action. Prefer “job title verified from named source 18 days ago; recheck required before purchase” over “92% fresh.” A composite badge can hide one critical expired field behind several stable attributes.
Carry the details into the partner-ready lead record. The buyer’s acceptance criteria should state which fields must be inside which band at listing, reservation, purchase, and outreach.
5. Define breach actions before a breach
For each threshold, choose one or more actions: warn, remove from search, block reservation, require seller revalidation, rerun a source check, ask for buyer review, cancel under policy, or open a quality investigation. Name the owner and response time. A red badge without an enforced action is reporting, not an SLA.
Use an error budget only when the indicator and stakeholders support it. If too many active listings cross the target, pause expansion or freshness-sensitive changes and focus on source reliability, reconciliation, or review capacity. Do not punish sellers for a measurement defect or dependency outage without a versioned policy and review.
6. Preserve historical truth while correcting current claims
When a person changes role, do not delete the dated qualification event. Mark the historical statement and update the current-state field with source and time. When a source conflict appears, preserve both attributed values until the rule or reviewer resolves it. The accepted snapshot remains part of transaction evidence even after correction.
Connect a challenged freshness claim to the dispute evidence packet. Correction and commercial remedy are related but separate decisions.
7. Monitor sources and synchronization
Track source latency, failed checks, webhook delay, retry exhaustion, clock skew, missing timestamps, stale caches, and reconciliation mismatches. A recent marketplace timestamp can merely reflect a delayed sync of old source data. Store both observed-at and effective/source-event times where the distinction matters.
For CRM fields, define deduplication and ownership before applying updates. The deduplication runbook prevents a refresh from attaching current evidence to the wrong identity.
8. Review and revise the SLA
- Document authors, reviewers, approvers, effective date, and next review.
- List every SLI, source, calculation, threshold, exclusion, and rationale.
- Compare breaches with validated disputes and buyer decisions by segment.
- Record false alarms, missed stale records, dependency failures, and manual toil.
- Tighten, relax, split, or remove thresholds when evidence changes.
- Version the rule so historical transactions retain their applicable SLA.
Sources and next step
Primary references: the ICO’s accuracy principle; Google’s Implementing SLOs chapter and example error budget policy. Their SRE examples are operational inspiration, not marketplace benchmarks.
Measure whether fresher evidence changes downstream decisions using the marketplace attribution ladder, with cohort dates and confounders rather than a whole-property click total.