Handover overview
Understand how Handover inventories a shared Google Drive folder, preserves its files, evaluates document coverage, and builds a request list.
Handover is the gated workspace for receiving a fund-administration document set from Google Drive. An organization admin points a run at a folder shared with the Handover service account. Handover inventories the folder, stores a copy of each supported file in Infra One storage, classifies the documents, checks their integrity, and evaluates a requirements checklist.
Handover reads the shared Drive folder; it does not change the folder or migrate the documents into fund records. Starting a run does create Handover records and stored copies inside Infra One.
What you can do
| Area | What it does |
|---|---|
| Handovers | Search runs by name or folder and compare Name, Status, Files, and Created. |
| New handover | Share a Drive folder with the displayed service-account address and start an inventory from its folder link or ID. |
| Run progress | Follow discovery, storage, classification, integrity checks, and checklist evaluation. |
| Files | Search the inventory; inspect Filename, Folder, Category, Status, Integrity, Review, Size, and Created; and use View or Download for an available stored file. PDFs, images, and videos can render in File Viewer, while unsupported formats keep a download fallback. |
| Requirements checklist | See which required and optional document groups are Present, Degraded, or Missing. |
| Request list | Download missing and degraded checklist rows as CSV or Markdown after the run completes. |
Manual file review and checklist evaluation are separate. Mark reviewed, Mark needed, and Ignore change a file’s review state, but they do not add or remove request-list rows.
How a run works
- Handover validates that the submitted value identifies a Drive folder the service account can read.
- A background worker walks that folder recursively, including supported file and folder shortcuts.
- It downloads ordinary files and exports Google Docs, Sheets, Slides, and Drawings to PDF.
- It stores the collected content, classifies filenames and paths, and records integrity findings.
- It evaluates the complete discovered corpus against the Handover checklist.
Completed means discovery settled and the checklist was committed. It does not mean that every discovered file was stored or readable, or that every checklist requirement is present. A completed run can still contain Failed or Skipped files, integrity problems, and checklist gaps.
Access and discovery
Handover uses the authenticated session shared with Infra One. Its canonical host is handover.infra.one, but the app is hard-hidden from the shared Venture sidebar, app switcher, and command palette while the wider launch decision remains open. Use only a direct link approved for your organization.
The host root requires the organization selector. Until you choose an organization, it shows No organization selected and Select an organization to open its handovers. The selector lists only organizations you belong to. Under the normal rollout it shows flagged organizations; a user-level rollout exception can make all of that user’s organizations visible.
Visibility in the selector is not an authorization decision. Opening or managing a run also requires the organization’s fund_handovers rollout flag or the current user’s rollout exception, organization membership, and the manage_fund_handovers capability. That capability is assigned to organization admins.
Already authenticated users who open legacy Venture Handover links are redirected permanently to the corresponding canonical Handover URL, preserving the path and query string. If an old link requires sign-in and leaves you on Venture afterward, open the approved canonical handover.infra.one link instead. Do not repeat sign-in.
Current operating boundaries
- Share only the intended folder with the exact service-account address shown by Handover, with Viewer access.
- The service account uses Drive read-only access without domain-wide delegation or user impersonation.
- Active HTML, SVG, and XML content is retained as an inert attachment. Blocked executable and script extensions are not stored.
- Archives can be stored, but Handover does not recursively inspect files inside nested archives.
- Checklist evaluation is corpus-wide. Use one fund or vehicle per run when you need fund-specific completeness.
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.
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.