Explore data opportunities across your portfolio.

A portfolio can contain very different operating histories: one company’s support resolutions, another’s dispatch exceptions, and a third’s engineering reviews. A combined inventory can make those opportunities easier to understand, but it should preserve the company behind each archive. Systems, contracts, record quality, and authority may differ even where businesses share an owner or use the same software.

Start with one row per company and a descriptive label. Record the main system or workflow, approximate years of history, and the current review status. The worksheet above is designed for that first pass. Its sample row is illustrative. Changing a status to authority documented records your own planning input; it does not independently verify the position or establish rights across the portfolio.

A headline total of files or messages can hide the differences that matter. One business may retain complete support cases with outcomes, while another has recent snapshots with little history. A software acquisition may have rich repository records but a separate ownership question around commissioned work. Describe these differences before trying to summarize the portfolio as one potential dataset.

Use consistent inventory fields while allowing different answers. A common profile can ask about workflow, systems, dates, connections between records, known gaps, and the responsible person. It should not force every company into the same data category or assume that an acquisition created a unified archive. Where records moved between systems, capture the migration boundary and whether links or history were preserved. A recently acquired business may have a long operating history but only a short period of consistently organized digital records.

A portfolio team may know that an archive exists before the operating company has assessed it. An executive may be interested in exploring the idea before the record owner has reviewed the relevant agreements. A prospective recipient may express interest before any commercial scope is defined. Keeping those milestones separate prevents an early inventory from turning into an unsupported expectation about a transaction.

Assign a responsible person for each company’s next question. That could mean confirming which system holds the history, understanding a migration, identifying a contract owner, or describing the proposed use more clearly. The useful next action is specific and limited. A company that needs more review should remain visible in the inventory rather than being dropped to make the portfolio appear uniformly ready.

You can edit the sample company, add separate businesses, and record high level system and history information in the local worksheet. Download it to keep a copy. The rows remain in the current browser session and are not submitted to a portfolio service or sent to the companies named. Use descriptive labels rather than confidential deal information; the tool is intended to organize a conversation.

For a company that is ready for a more detailed discussion, prepare a separate profile with its operating team. Keep commercial expectations tied to that company’s actual records, proposed scope, and review results. A shared owner does not make the archives interchangeable. The next step is a clear company inventory and review path, with any eventual agreement and transfer handled separately from this website.