How to Collect Comparable Portfolio Company Metrics

Collect comparable portfolio metrics by agreeing what each measure means, the reporting period, the unit and the evidence owner before asking for numbers. Validate submissions against those definitions. Missing, estimated and incompatible data should remain visible rather than being converted to zero or blended into a misleading average.

This guide teaches reporting operations, not an accounting standard or investment-performance methodology. Use qualified finance or accounting review for financial definitions and calculations. Respect company agreements and obtain appropriate permission before collecting or sharing sensitive information.

1. Define the measure before choosing the dashboard

Start with the decision the report supports. An operating-support team may need to identify companies asking for hiring help, not collect a full financial package. An investment team may have different approved reporting needs. Do not assume the same dataset serves every audience.

Minimum metric-dictionary fields

Field	Decision it resolves	Illustrative entry
Name and definition	What exactly is being counted?	Active paid organizations, excluding free evaluations
Period or snapshot	Is the value a flow or a point in time?	Snapshot at September 30
Unit and currency	Can values be compared?	Organizations, not seats or locations
Evidence owner	Who can explain and correct it?	Named company operations owner
Source and status	Actual, estimate, provisional or missing?	Approved account report, actual
Change history	Did the definition change?	v 2 excludes dormant evaluations

Use company-specific explanations where models differ. A marketplace, a subscription business and a hardware company may not share a meaningful revenue proxy. Do not force unlike businesses into a neat common metric by dropping the details that make it interpretable.

2. Keep the request small and explain its use

Ask for the agreed period, definition version and status beside each value. Allow the company to answer unavailable, not applicable or provisional. Ask for a correction owner rather than repeatedly contacting several people.

State who will see company-level data and what, if anything, may appear in an aggregate. Do not assume removing a company name eliminates the risk of identification in a small portfolio. NIST's least-privilege principle supports limiting access to the reporting task.

Avoid collecting raw customer or employee information when a defined total is sufficient. Keep source evidence restricted and share only the fields needed for the approved purpose.

3. Validate before comparing

1. Check entity and period. Confirm the correct company, business unit and date.
2. Check units. Seats, customers and organizations are not interchangeable.
3. Check definitions. Confirm exclusions, classification and any change since the prior period.
4. Check status. Separate actuals from estimates, missing data and not-applicable responses.
5. Route discrepancies. Ask the source owner for clarification; do not silently “fix” the value.
6. Retain versions. Record corrections and recalculate affected summaries after approval.

For financial measures, have the appropriate qualified person confirm definitions and treatment. This worksheet cannot establish an accounting policy, valuation or investment conclusion.

4. Worked example: three submissions that should not be averaged

Illustrative example: A platform team requests active paid organizations at September 30 for a support-planning report. Harbor submits 34 paid organizations. Juniper submits 120 paid seats across 18 organizations. Delta reports 25 active organizations, including five free evaluations.

Initial validation and correction

Company	Submitted	Validation	Approved reporting value
Harbor	34 paid organizations	Matches definition and date	34
Juniper	120 seats	Wrong unit; owner supplies organization count	18, after confirmation
Delta	25 including 5 free evaluations	Wrong inclusion rule; owner confirms exclusion	20, after confirmation

The corrected sum is 34 + 18 + 20 = 72 company-customer relationships across these three fictional companies. It is not a count of 72 unique customer organizations across the portfolio: the same organization could buy from more than one company. Deduplication would require a separate approved method and appropriate data permissions. This sum is not a portfolio revenue measure or proof of company quality. Before correction, averaging 34, 120 and 25 would have mixed different units and scopes.

Suppose the broader request contained 15 required company-metric cells, of which 12 passed validation by the checkpoint. Completeness is 12/15 =80%. Report the three remaining cells as pending or unavailable, with reasons. Their unknown values are not zero. A later corrected submission changes the cohort receipt and any approved summary that uses it.

5. Copy the metric submission receipt

Company / reporting purpose:
Metric name and definition version:
Period or snapshot:
Unit / currency:
Source owner and approved evidence:
Actual / estimated / provisional / missing / not applicable:
Submitted value:
Validation result and discrepancy:
Correction requested / owner / date:
Approved value and approval:
Who may see company-level data:
Included in which summary:
Prior-period comparability note:

Completion check: Every reported number has a meaning, period and owner; missing coverage is stated; incompatible values are not blended. A qualified reviewer has checked applicable financial definitions before the report is used.

Informational disclaimer

We are not lawyers. This article is for general education only and is not legal, tax, accounting or investment advice. Check with your attorney or accountant before acting on it.