The minimum source pack for a useful PE dashboard

Choose one decision the source pack must support

This is a proposed working inventory for the first reporting cycle, not a requirement to move every document the firm owns. Choose a bounded question: can the operating partner see which companies have supplied September reporting, locate the evidence and assign the next follow-up? The existing onboarding guide explains the rollout; this kit specifies the records to assemble.

Keep acquisition targets separate from owned companies. A target's diligence room may inform an investment decision, while an owned company's reporting pack supports an operating review. Give both stable identifiers, but do not count a target as part of the portfolio simply because its files sit in the same folder.

Make the manifest an index of sources

Use one row per expected source, including sources that have not arrived. A file list contains only what exists; a source manifest can also show what the reviewer is waiting for. The same company can have several rows for a period because its financial pack, board materials and operating plan answer different questions.

The blank CSV has fields for a source identifier, company identifier, company name, record scope, reporting period, material type, filename or reference, source version, reporting owner, review owner, received date, collection status, review status and next action. These are proposed planning fields. The worksheet is not an automatic import specification for Agentic Equity.

Use role labels in a public example. In your private copy, use an authorized contact or internal identifier that your team understands. For a missing source, leave its filename and received date blank, mark collection status as missing and record a concrete request. Do not substitute zero for a missing financial figure.

A three-company example with one missing input

Atlas Components, Beacon Field Services and Marlowe Software are invented companies. The downloadable example contains four expected source rows per company for September 2026: a reporting pack, board materials, an operating plan and metric definitions. The company roster is represented by the stable company columns. No source files or customer records are included.

The example has twelve expected sources: eleven marked received and one missing. Collection completeness is therefore 11/12 for this example; it says nothing about approval quality or the proportion of the portfolio that is financially healthy. Received sources are marked pending review so the exercise cannot be mistaken for approved dashboard data.

Marlowe's board materials are missing. Keep Marlowe in the company roster, retain its received reporting pack and assign the board-material request to the company liaison. This makes the gap visible without treating the company as unreported or removing it from the dashboard.

Check your source pack before the review meeting

Paste a completed source-pack CSV into the checker, or start with the synthetic example. It separates collection from review, groups records by stable company identifier, scope and period, and creates a downloadable follow-up list.

The checker reads the declared inventory in this browser tab. It does not upload the CSV, retrieve source files or approve financial figures. Sources omitted from the manifest are outside its denominator, so include every expected source before interpreting collection coverage.

Preserve references when the material changes

A source identifier should remain understandable when a filename changes. Record a source version or revision label alongside the original file. The reporting period describes the business period; the received date describes when the firm obtained the document. A late September pack received in October is still September reporting.

For a corrected pack, add a clear reference to the new source and identify which earlier review it affects. Keep your firm's retention and access rules in force. A revised file can change the answer to a decision even when its filename looks almost identical.

The manifest helps the team plan that review. It does not create an approval history, schedule requests or enforce retention rules by itself. A reviewer should compare the actual source and deliberately record the accepted information in the operating workspace.

Bring the source pack into Agentic Equity

The private workspace supports manual material uploads, source retrieval and human review. Supported inputs include PDF, DOCX, XLSX and UTF-8 CSV or text formats. The current upload limit is 10 MB per file, and extracted text is limited to 250,000 characters. A readable source is still an input to review; it is not proof that its financial definitions or figures are correct.

Assign the material to the appropriate company or deal. For a monthly reporting input, use an explicit YYYY-MM period, such as 2026-09. Review a proposed metric against its source excerpt and reference before approving it. A manifest row marked received should not be described as an approved metric.

PDF, DOCX and XLSX text extraction runs on the hosting server in the current deployment. Scanned material may need a searchable original or a separate OCR process. External AI analysis and third-party Drive, SharePoint or CRM connections require their own configuration and authorized access. This kit begins with manually gathered materials.

Check the pack before expanding the pilot

Use the synthetic manifest to rehearse a review meeting before adding more companies. Ask a reviewer to find the expected sources, identify the missing one and explain why a received pack remains pending. Then substitute your own authorized source references and run the same exercise in the private workspace.

An accepted first source pack means that the team knows which sources it expects, which ones it has and who will resolve each remaining question. Approval of particular figures is a separate step. Record any ambiguous company, period or definition as an unresolved question rather than filling it by guesswork.

• Every participating entity has a stable identifier and a clear owned-company or acquisition-target scope.
• Every expected source has a named reporting owner and review owner.
• Reporting period, received date and source version remain separate.
• The team can retrieve the received original and locate the relevant passage or worksheet.
• Missing sources and pending review are visible without creating false zeroes.
• Each open item has a specific next action before the pilot expands.

Use the manifest to define the setup conversation

Bring the company roster and a small authorized source pack to the setup conversation. Choose one reporting decision, identify the people responsible and agree on what a successful first cycle would show. You can keep the firm's existing CRM and accounting systems while evaluating this bounded workflow.

The source pack is an operating inventory. It does not replace fund accounting, approved valuations or formal investor reporting. If your finance team is reviewing LP reporting formats, ILPA's official templates hub is a useful primary reference. Keep that reporting responsibility distinct from the collection exercise.