Review a handover and export a request list

This guide produces a reviewed Handover result and a request list containing the required and optional documents that are missing or unusable.

Before you begin

You need organization-admin access to the organization that owns the run. Open the run only after confirming that it belongs to the intended fund or vehicle.

Wait for Completed before treating the checklist as final. A completed run can still contain failed, skipped, unreadable, or missing documents; completion means that discovery settled and the checklist was committed.

Open the run

1. Open https://handover.infra.one/your-organization-slug/handovers.
2. In Handovers, search by run name or folder with Search by name or folder….
3. Compare Name, Status, Files, and Created, then select Open for the intended run.
4. Confirm the folder name and run status before reviewing its files.

When the list is empty, it shows No handovers yet and Point a run at the Drive folder an outgoing fund administrator shared, and off it goes.

Check progress and outcomes

1. Wait for the status to reach Completed, Failed, or Canceled.
2. Compare Files found, Stored, Skipped, Failed, and Integrity problems.
3. Treat Integrity problems as a focused count of corrupt and password-protected files. Scanned PDFs without a text layer can still degrade checklist results even though they are not included in that count. Empty files that otherwise pass storage safety rules are also excluded, but the ingestion pipeline classifies them as Note (filename is the message), so they do not match or degrade checklist requirements.
4. If the run failed or was canceled, resolve the cause before relying on the checklist or export.

Evaluating checklist… is a declared run label, but the current finalizer never writes the evaluating state; a normal run can move directly from Fetching files… to Completed.

Review the file inventory

1. In Files, use Search by filename or folder… to locate a document.
2. Compare the default Filename, Folder, Category, Status, Integrity, Review, and Size fields. Use the field picker to add Created when you need it.
3. Look for files whose status is Failed or Skipped, or whose integrity is Empty file, Corrupt at source, or Password-protected.
4. Open the row’s actions menu for an available stored file. Select View to open it in File Viewer or Download to save the original response. File Viewer renders supported PDFs, images, and videos. Office documents, archives, messages, active content, text files, and unknown formats use the unsupported-preview state and retain Download.
5. When a PDF is implicated in a checklist gap, inspect it in File Viewer or download it. Handover internally samples the first three pages and uses 50 characters after trimming leading and trailing whitespace as its text-layer threshold, but the current file table and File Viewer do not display that assessment. A scan can be stored successfully but still degrade checklist evaluation; an assessment Handover could not determine does not itself degrade the match.
6. Use Mark reviewed, Mark needed, or Ignore to record the team’s manual review decision.
7. If a statistic or checklist drill-down is active, select Show all files to clear that focus and return to the underlying inventory view. Search, Entity Browser filters, and the selected folder remain active; clear those separately when you need the full inventory. The inventory still shows 50 files per page, so continue through its pages when reviewing the complete corpus.

A zero-byte source file that otherwise passes storage safety rules is stored and shown as Empty file rather than skipped. File shortcuts inside the walked folder are supported and fetched through their targets. Handover can internally recognize exact duplicates, but the current file table does not expose a duplicate label.

Manual review does not change checklist matching. Mark needed does not create a request-list row, and Ignore does not suppress one.

Interpret the requirements checklist

1. Open Requirements checklist and note the summary in the form N gaps · N present.
2. Review required rows first, then the Nice to have rows.
3. Interpret Present as at least one healthy matching document.
4. Interpret Degraded as one or more matching documents where every match is unusable because it is corrupt, password-protected, or a scanned PDF without text.
5. Interpret Missing as no matching document in the discovered corpus.
6. Use Show present or Hide present to change the checklist view. Use View N files to trace a result back to its matches.

One healthy match makes the row Present even when other matches are unusable. The checklist evaluates the whole run, not separate funds or vehicles inside it.

Some requirements expand from evidence in the corpus. Investor requirements use investors inferred from investor-specific documents. Quarterly requirements span continuously from the earliest to the latest observed reporting quarter. Yearly requirements use observed reporting years. Drawdown notices expand from number 1 through the highest inferred number. When no expansion domain is inferred, the requirement remains as one unscoped row and is evaluated against every matching file; it is Missing only when none matches.

Download the request list

1. Confirm again that the run shows Completed.
2. Select Request list.
3. Select Download as CSV for a table with Requirement, Scope, Severity, and Status, or select Download as Markdown for a human-readable list.
4. Confirm that the export contains only Missing and Degraded checklist rows. Satisfied rows are omitted.
5. Store the downloaded file in an approved location and share it only with the intended handover participants.

The Markdown export starts with Request list — run name and Documents we could not find (or could not use) in the handover folder:. It adds Required and Nice to have headings only when the corresponding severity has rows. A degraded row is marked present but unusable, please re-send. The generated filename is sanitized from the run name.

Handover renders request-list downloads in every run state. Before Completed, an initial run exports no checklist rows and a re-run continues to export the previous checklist snapshot, which can also have no rows, until final evaluation atomically replaces it. Wait for Completed before interpreting or downloading either export.

Recover or remove a run

• Re-run becomes valid after the run settles. Confirm Restart handover; the confirmation says Unchanged files are re-classified without re-downloading. For rediscovered regular files and direct targets, unchanged entries are reclassified without another download, while eligible entries detected as changed, failed, or skipped are fetched again. A known shortcut-only entry is not redispatched on re-run; use a new run or add the direct target when it must be refreshed.
• Cancel stops queued or executing work and keeps each file in the state it reached. The confirmation explains: Files keep whatever state they reached. A terminal run cannot be canceled.
• Delete removes the run and its stored file records after you confirm Delete handover and Its stored files go with it. If work is still active, Handover cancels it first. Stored blobs are deleted asynchronously.

Success check

The run shows Completed, the file inventory and Requirements checklist have been reviewed, and the exported CSV or Markdown contains exactly the checklist rows currently marked Missing or Degraded. A sampled export row agrees with its checklist status and matched-file evidence.

Troubleshooting

• If No files discovered yet. appears after the run has settled, first clear any statistic or checklist drill-down, search, and Entity Browser filters, then return to the root folder. If the empty state remains and Files found is zero, confirm that the shared root contains accessible files and check the terminal run status.
• If a document is Present despite an unusable copy, select View N files. Another healthy match overrides degraded matches for the same requirement.
• If Integrity problems is zero but the checklist contains degraded rows, select View N files, then use the row’s View action for an available stored PDF or Download it. Handover’s internal text-layer assessment can degrade a scanned PDF without increasing the counter, but neither the current file table nor File Viewer displays that assessment. Empty files that otherwise pass storage safety rules are also excluded from the counter, but they are classified as Note (filename is the message) and do not create degraded checklist rows.
• If an initial request list is empty, confirm that the run is Completed. Controls are visible before the first checklist is committed.
• If a re-run still shows old gaps, wait for the new run cycle to reach Completed. The previous checklist remains visible until final evaluation replaces it.
• If a source document was removed after a prior run, the settled historical item remains as evidence across re-runs. A re-run walks current Drive contents but does not purge that terminal item; use a separate new run when you need a current-only inventory.

Related pages

• Start a handover
• Handover overview
• Handover permissions and states
• Troubleshoot Handover