# Alert-to-repair completeness checklist | SourceX

Canonical: https://refer.sourcex.si/resources/alert-to-repair-verification-completeness-checklist
Last updated: 2026-11-04

Gaps in identifiers, timestamps, versions and outcomes break the trail. Eight checks find them at metadata level: coverage, alert-to-job linkage, reading resolution, sensor versioning, threshold history, the verification rule, repeat-failure linkage and the migration gap. Score each pass, partial or fail from answers the company's service leads give, never from records, and the total tells you how much of the history can be trusted before anyone promises an AI data opportunity.

This scorecard is part of [alert-to-repair-verification records](/guides/chain-alert-to-repair-verification). The [record linkage page](/guides/alert-to-repair-verification-record-linkage) maps the keys; this page turns them into checks you can run in one conversation.

## How to score the checklist

Each check scores 2 for pass, 1 for partial and 0 for fail, for a maximum of 16. Write the answer and the years it covers next to each score.

| Total | Reading |
|---|---|
| 13 to 16 | The chain is largely intact; describe it with confidence |
| 8 to 12 | Discuss with named gaps; say which years and checks are weak |
| 0 to 7 | Records exist, but the trail is mostly broken; still worth a mention if the company qualifies, without promises |

## The eight checks

| Check | Question to ask | Pass | Partial | Fail | Who usually knows |
|---|---|---|---|---|---|
| 1. Coverage | "Which years and how many assets does each system cover?" | All three systems overlap for several years | Overlap for a short period | One system only | Service operations lead |
| 2. Alert-to-job linkage | "Can you tell which alert led to a work order from last year?" | Work order carries the asset and alert ID in fields | Alert ID typed in descriptions | Work orders name the site only | Dispatch lead |
| 3. Reading resolution | "How long do you keep raw readings, and at what interval?" | Raw readings kept for years | Raw for months, then averages | Daily averages only, so the alert moment is lost | IoT or controls engineer |
| 4. Sensor versioning | "When a sensor is replaced, what changes in the system?" | Sensor tracked as an asset with a replacement record | Swap appears in parts or notes | Same stream continues with no record | Field service manager |
| 5. Threshold history | "Do you keep a history of alert limit changes?" | Each change dated and kept | Current limits only, changes in email | No history | IoT or controls engineer |
| 6. Verification rule | "What has to be true before a repair counts as verified?" | A measured rule, written down | A rule exists but varies by technician | Verified means the job was closed | Service operations lead |
| 7. Repeat linkage | "Can you see that a work order repeats an earlier one?" | Parent or related work order field used | Typed notes | No link | Field service manager |
| 8. Migration gap | "Have any of these systems been replaced, and what was kept?" | Full history migrated with original dates | Archive kept outside the new system | Old history discarded | IT or finance systems manager |

A few product details help with the follow-up questions. Salesforce's WorkOrder object has an AssetId field and a ParentWorkOrderId field, so checks 2 and 7 can pass on system fields when teams use them. Salesforce documents an AssetRelationship object for recording a replacement between assets, which is what a pass on check 4 looks like. In AWS IoT SiteWise, each raw measurement is a data stream with an alias, and calculated values such as a limit test are expressions defined on top of it, which is why check 5 asks where limit changes are recorded. For check 5 in Salesforce specifically, standard field history is kept for 18 months in the interface and up to 24 months through the API unless the company extends it; see [field history tracking retention](/questions/salesforce-field-history-tracking-retention).

## The case to test: a sensor replacement that changes the baseline

Ask one extra question: "If a technician replaces a sensor during a repair, how do you know what normal looks like afterward?" Three answers are common, and each maps onto check 4.

1. **Baseline reset by rule.** The new sensor gets a settling period and its own baseline before verification. Pass, from the date the rule started.
2. **Recorded but not used.** The swap appears in parts or notes, so the history can be corrected later, but verified statuses from that era need rechecking. Partial.
3. **Not recorded.** The same data stream continues and nobody knows which readings came from which instrument. Fail.

Any of the three can still be worth an introduction. The answer tells SourceX which years of verified outcomes mean what they say. The [missing context page](/guides/alert-to-repair-verification-missing-context) shows one case where the answer was the third.

## A scored example (Illustrative)

**Illustrative and fictional.** A 230-person elevator service company monitors door and drive faults on client buildings.

| Check | Score | Answer recorded |
|---|---|---|
| 1. Coverage | 2 | IoT since 2019, Field Service since 2017, ERP since 2015 |
| 2. Alert-to-job linkage | 2 | Faults open work orders automatically with the unit ID |
| 3. Reading resolution | 1 | Raw readings for 13 months, then hourly averages |
| 4. Sensor versioning | 1 | Controller swaps in parts records, not tracked as assets |
| 5. Threshold history | 0 | Limits edited in place, no history |
| 6. Verification rule | 2 | Written rule: no repeat fault for 72 hours |
| 7. Repeat linkage | 2 | Callbacks linked to the original job |
| 8. Migration gap | 1 | Pre-2017 jobs in a read-only archive |
| Total | 11 of 16 | Discuss with named gaps: threshold history and sensor swaps |

This is a solid introduction with two honest caveats, not a perfect archive.

## After scoring: authority and what stays unknown

Scores do not authorize anything. The CEO, usually the owner in an owner-run firm, authorizes a licensing discussion, often with the COO or head of service as internal sponsor; client agreements may limit use of readings from client equipment. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. What stays unknown until SourceX reviews it: buyer interest, de-identification needs and what the company would be paid. If a system is being replaced, the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) applies; for checklists in a deal context, see the [MSP acquisition due diligence checklist](/resources/msp-acquisition-due-diligence-checklist). Other record locations are on the [systems hub](/systems).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a service company you advise can answer the eight checks and name its sponsor, whatever the score, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce it.

## Sources

- https://developer.salesforce.com/docs/atlas.en-us.228.0.object_reference.meta/object_reference/sforce_api_objects_workorder.htm
- https://developer.salesforce.com/docs/platform/object-reference/references/standard-objects/object-assetrelationship.html
- https://trailhead.salesforce.com/content/learn/modules/field-audit-trail-basics/get-started-with-field-audit-trail
- https://docs.aws.amazon.com/iot-sitewise/latest/userguide/asset-properties.html
- https://refer.sourcex.si/terms
