# Race-team data-handoff checklist

Source: https://sector4labs.com/resources/data-handoff-checklist

Prepare a workflow or software handoff without sending private files. Use this worksheet locally. Unknown means not yet confirmed, not zero, support, or permission. This is not a compatibility certification or legal agreement.

Do not write credentials into this worksheet. Do not upload telemetry, radio, setup files, or private records through the public contact form. Agree on a safe sharing path first.

## Workflow and owner

- [ ] What recurring job are we trying to improve?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Who uses the output, and who will operate the tool after handover?
  Answer / unknown / not yet confirmed: ____________________

- [ ] What happens if the job is not done at the next event?
  Answer / unknown / not yet confirmed: ____________________

## Inputs and context

- [ ] Which source families and export types or versions are available?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which channels, units, session identifiers, and time references are known?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which inputs, channels, or time references are missing or uncertain?
  Answer / unknown / not yet confirmed: ____________________

## Rights and sensitivity

- [ ] Who may authorize access to each input?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which records are personal, confidential, restricted, or not permitted to be shared?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which safe sharing path must be agreed before any transfer?
  Answer / unknown / not yet confirmed: ____________________

## Output and acceptance

- [ ] What artifact and review question are in scope?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which supplied evidence would establish that the output is acceptable?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which delivery time and revision boundary need agreement?
  Answer / unknown / not yet confirmed: ____________________

## Operation and recovery

- [ ] Where will the tool run, and does it need to work offline?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which dependencies and operating instructions must be handed over?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Who owns updates, and what is the fallback when the tool or a source is unavailable?
  Answer / unknown / not yet confirmed: ____________________

## Ownership and access

- [ ] What source or access terms will be agreed in writing?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which accounts need an owner, and how can the team export its own data? Do not record passwords or tokens here.
  Answer / unknown / not yet confirmed: ____________________

- [ ] Who removes temporary access, and on what agreed date?
  Answer / unknown / not yet confirmed: ____________________

## Limits and maintenance

- [ ] Which inputs are unsupported, unverified, stale, or incomplete?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Which rule, license, logger, or export-version changes could affect the output?
  Answer / unknown / not yet confirmed: ____________________

- [ ] Who owns corrections and future changes?
  Answer / unknown / not yet confirmed: ____________________
