Read the import receipt and the findings

Steps

1. Open the Import receipt. It counts rows read, new, changed and unchanged entries, unmapped columns and unparsed dates.

2. Where a value could not be read, choose Correct this value on the Import receipt. It adds a new version with your reason; the first version stays as it was.

3. On Findings, read Typed versus produced: which values a person declared, and which a system wrote.

4. Under Point in time, choose a date to see what the register said then, from its recorded versions alone.

5. Under Re-assertion lapses, read “interval not set” first, then the oldest lapse first.

Good to know

• History in a workspace starts at its first import. Dates declared in the file, such as an earlier gate passage, are shown as declared, never as what the register said then.
• A re-import that changes nothing writes nothing and adds no version.
• If an import stops part-way, nothing from that file is written.
• You draft; the model owner or the register owner at the client decides.

Where in the product

• Import receipt
• Findings

These open the prototype, on fictional institutions. People are shown as roles.

Related guides

• Draft a finding

  Write a finding that cites records, says what they show and who decides, then share it with the client.

• Import a register from a spreadsheet

  Upload a CSV or XLSX register, map its columns, and import every row as a typed value.

• Hand a workspace to the client

  Send the claim to the client’s administrator. After the claim, you keep a read-only copy.