# Incident-to-fix completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/incident-to-fix-completeness-checklist
Last updated: 2026-11-04

An incident-to-fix evidence trail breaks in five places: coverage (some incidents or years are missing), linkage (the issue key never reached the fix), timestamps (the status update predates the last merge), outcomes (nobody recorded what finally worked) and gaps nobody has named. The scorecard below turns each of those into checks a platform lead can answer from memory or configuration, with a pass, partial or fail guide, so a partner can describe the trail without opening a record.

This scorecard belongs to the [incident-to-fix guide](/guides/chain-incident-to-fix). The [record chain page](/guides/incident-to-fix-record-linkage) explains every key in the sequence; this page grades whether those keys were actually used.

## How to run the scorecard

Run it as one 30-minute conversation with the person who owns the on-call process, usually a platform engineering manager or engineering operations lead. Ask each question as written. Record pass, partial, fail or "unknown," plus the name of whoever answered.

Three rules keep it at metadata level:

1. **Every check is a question about structure.** "Do emergency fixes carry the ticket key?" is a structure question. "Can I see one?" is not, and the partner never asks it.
2. **Estimates come from the company.** If a share or count is needed, the company states it as a rough range. The partner does not count anything.
3. **Unknown is a valid answer.** Write down who could find out, and move on.

## Coverage checks

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| C1. Incident thread coverage | Where were incidents handled, and can those channels be exported on the current Slack plan? | Public channels, or an approved export covers private ones | Some years in public channels, later years private and not yet approved | Incidents ran in private channels or DMs with no export route |
| C2. Issue coverage | Did every incident above a set severity get its own issue? | Yes, by written policy | Yes for severity 1, informal below | No consistent issue for incidents |

Slack's export rules drive C1. On Free and Pro plans, owners and admins can export public channels, while private channels and DMs are exportable only in limited circumstances after an application. Business+ and Enterprise owners can apply for a broader self-serve export. The plan and the channel type matter more here than the age of the workspace.

## Linkage checks

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| L1. Key in the thread | Is the issue key posted in the incident channel as a habit? | Standard step in the runbook | Usually, not always | Rarely or never |
| L2. Key on hotfix branches | Roughly what share of hotfix PRs carry the issue key? | Most, by the team's estimate | About half | Few, or nobody knows |
| L3. Non-default branch fixes | Do incident fixes merge to release or hotfix branches? | No, fixes go to the default branch first | Sometimes, then reach the default branch later | Often, and stay on release branches |

L2 is the single most informative question. Atlassian's documentation says the work item key in a branch name, commit message or PR title links the work to the Jira item in connected tools such as GitHub, so an emergency fix without the key is invisible from the ticket. L3 matters because GitHub's auto-close syntax links a PR to a GitHub issue only when it targets the default branch; a fix merged elsewhere closes nothing through it.

## Timestamp and outcome checks

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| T1. Status update versus last merge | Is the resolved message ever posted before the final linked merge? | Rarely, and the issue is reopened when it is | Sometimes, with no reopen step | Often, and nobody tracks it |
| T2. Timestamps survive | Do both the message time and the merge time survive in the systems of record? | Yes, in both | One survives, the other is uncertain | Unknown for both |
| O1. Review recorded on fixes | Do branch protection rules require approvals on release and hotfix branches? | Yes, same rules as the default branch | Default branch only | No review rules |
| O2. Final outcome recorded | Does the issue or postmortem say which change fixed the incident? | Postmortem cites the key and the final change | Postmortem exists, does not cite the key | No postmortem or resolution note |

On O1, GitHub's protected-branch settings can require a set number of approving reviews before a merge and can dismiss approvals made stale by new commits. Whether those rules covered release branches is a configuration question for the platform owner. If they did not, a reviewed patch on main and an unreviewed hotfix can sit inside the same incident. The [root cause analysis records page](/data-types/root-cause-analysis-records) covers postmortems as a record type of their own.

## Gap check and an Illustrative scored result

The tenth check asks whether anyone has already named the gaps.

| Check | Question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| G1. Known gaps named | Can the team name the periods, teams or branches where the chain is known to break? | Yes, specific and written down | Roughly, from memory | No one has looked |

Illustrative: a fictional 340-person B2B software company scored as follows.

| Group | Checks | Result |
|---|---|---|
| Coverage | C1, C2 | C1 partial (private channels since 2022, export application not made); C2 pass |
| Linkage | L1, L2, L3 | L1 pass; L2 partial (about half of hotfixes carry the key); L3 pass |
| Timestamps | T1, T2 | Both pass |
| Outcomes | O1, O2 | O1 fail (release branches unprotected); O2 pass |
| Gaps | G1 | Pass: hotfixes from one mobile team named as the main break |
| Total | 10 | 7 pass, 2 partial, 1 fail |

That is a sound description to hand over: strong linkage on the main path, a named weak spot on hotfixes, and no review evidence on release branches. It says nothing about contents, and it overstates nothing. The [missing-context page](/guides/incident-to-fix-missing-context) shows what a failed L2 looks like in a real sequence of events.

## Who signs off before an introduction

The platform lead answers the scorecard; the CTO or another executive with authority over company data decides whether to discuss a license; counsel checks customer contracts. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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: how much of the trail survives export, whether customer data limits use, and whether there is demand. Partners sign the Channel Partner Agreement before submitting an introduction. For the baseline screen, use the [incident and on-call introduction checklist](/resources/a-company-introduction-checklist-for-incident-and-on-call-records); ticket-first companies can also read the [ServiceNow incident page](/systems/servicenow-incident-data-for-ai-training).

## 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 the scorecard shows a mostly linked trail with its gaps named, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send the introduction.

## Sources

- https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue
- https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches
- https://slack.com/help/articles/201658943-Export-your-workspace-data
- https://support.atlassian.com/jira-software-cloud/docs/reference-issues-in-your-development-work/
- https://refer.sourcex.si/terms
