What to do first

These changes move the grade, in order of effect. The check each one cites appears with it in the “Each check” section below.

1. Assign an owner to $8.7M of ARR. 261 active accounts have no rep. The top rep holds 25.5% of ARR. The parent field is the least-covered tag. Owner coverage drives both the tag coverage check and the owner concentration check, so one pass of assignment moves Multi-Dimensional Insights toward B.
2. Add a definitions tab. Write one line for each term the definitions do not yet cover: MRR, GRR, new, and reactivation. Keep the existing lines for ARR, NRR, churn, expansion, and cohort. Written definitions let anyone reproduce the KPI table, and they raise the score on the definitions check. The diligence-ready view also needs the 2 High findings closed and either unit and price data or payment data.
3. Normalize 2 tag fields. The segment and status fields carry case or spacing variants of the same value. One normalization pass removes them and moves Multi-Dimensional Insights up one band.
4. Prepare for the checks that could not run. The tag-stability check needs each account’s tags exported as of each month, not just once. The product-copy check had nothing to test because no single month moved the whole book. Covering these raises the share of the cube that is graded rather than assumed.
5. Re-grade after each month-end close. A monthly re-grade catches broken ties, duplicates, and status drift before they reach the board pack. This keeps Audit-Grade Accuracy where it is.

Where the grade comes from

Inputs: 2 file(s), 8 sheet(s), 109,461 rows. Hazards handled: none. Checks run: 39 of 41. The 2 that could not be checked are listed below.

• Unified, Finance-Approved Foundation: 87.3 (B+)
• Audit-Grade Accuracy: 100 (A+)
• Cohort-Centric Design: 100 (A+)
• Multi-Dimensional Insights: 77.5 (B-)
• Anomalies: 100 (A+)

Audit-Grade Accuracy, Cohort-Centric Design, and Anomalies came through with no open findings. The two lower pillars trace to the owner gap, the definitions text, and tag spelling.

Each check

Each item below is one part of the rubric. The heading says what was tested, and the short code is the citation.

Unified, Finance-Approved Foundation

Bookings with no product or no owner

Unified, Finance-Approved Foundation. Cited as CP-05, owner.

This check measures how much of the latest book has no product and how much has no owner.

In this file, every dollar carries a product (0% unassigned). Ownership is the gap: 261 accounts, or 25.6% of the book, have no owner. Check score 30. A buyer would ask who manages renewal and expansion on those accounts today.

Next step. Assign a product and an owner to the unassigned book before the next export.

The words in the definitions were written down

Unified, Finance-Approved Foundation. Cited as CP-07.

This check looks for the standard terms in the definitions text. It does not test whether those words match the numbers.

In this file, the definitions cover 5 of the 9 terms. ARR, NRR, churn, expansion, and cohort are written down. MRR, GRR, new, and reactivation are not. Check score 56. A buyer would ask how GRR and new ARR are defined before relying on them.

Next step. Write a short definition for each headline term the summary uses, in the same words the rubric expects.

Came through clean: Enough history to follow a customer (CP-01); Months where the whole book went quiet (CP-02); A customer goes quiet without a churn mark (CP-03); Revenue with no customer behind it (CP-04); the product half of Bookings with no product or no owner (CP-05, product); The product file covers the same months as billing (CP-06); Billed customers appear on the customer list (CP-08).

Audit-Grade Accuracy

Every check in this pillar passed. The bridge foots, the detail ties to it, and the KPIs reproduce.

Came through clean: The bridge foots on its own (CR-01); Customer detail matches the bridge ending (CR-02); Movements rebuild from the customer rows (CR-03); Product lines tie to billing (CR-04); The amount matches the status word (CR-05); Statuses tell a legal story over time (CR-06); Headline KPIs can be reproduced (CR-07); The bridge and the KPI table agree (CR-08); Product and segment totals add up (CR-09); Duplicate dollars that break the tie (CR-10).

Cohort-Centric Design

Every check in this pillar passed. Start dates, contract end dates, and the history behind trailing metrics all hold.

Came through clean: Customers have a start date (CO-01); The start date matches the first revenue month (CO-02); Too many customers share one start month (CO-03); A returning customer kept the same key (CO-04); Contract end dates exist and fall after the start (CO-05); Retention looks earned, not just unexpired (CO-06); A trailing year has a year of history behind it (CO-07).

Multi-Dimensional Insights

One owner does not hold the book

Multi-Dimensional Insights. Cited as SG-06.

This check measures the top owner’s share of the latest book and the share with no owner.

In this file, there are 3 reps. The top rep holds $8.6M, a 25.5% share. The unassigned portion is about the same size as the top rep’s book. Check score 30. A buyer would ask what happens to coverage if one rep leaves, and who holds the accounts no one owns.

Next step. Reassign concentrated accounts and fill the unassigned ones so the book is not one rep’s.

Those tags actually cover the book

Multi-Dimensional Insights. Cited as SG-02.

For each tag, this check measures how much of the latest book sits on accounts with a real value.

In this file, tags cover 79.1% of the book on average across 6 tags. The owner field and the parent field carry the gap, with parent the least covered. Check score 55. A buyer would ask whether the book can be cut by parent customer and by owner.

Next step. Fill the blank tags on the accounts that carry the book, starting with product and owner.

The same idea is spelled one way

Multi-Dimensional Insights. Cited as SG-04.

This check groups tag values that match once case and spacing are removed, and scores how many spellings each idea has.

In this file, 2 tag fields, segment and status, carry more than one spelling of the same value. Check score 80. A buyer would ask whether a segment cut double-counts a category spelled two ways.

Next step. Pick one spelling for each category and apply it across the file.

Came through clean: The cuts a buyer expects are present (SG-01); A tag is a category, not free text (SG-03); Parent accounts are used (SG-05).

Anomalies

Every check in this pillar passed. No spikes, mass events, duplicates, or failed talking-point claims were found.

Came through clean: One customer spikes for a month and reverts (AN-01); A customer drops to zero and comes back unmarked (AN-02); One month moves the whole book (AN-03); Amounts do not match the file’s own format (AN-05); Duplicate rows (AN-06); The book sits in a few customers (AN-07); Prices did not move where an escalator was promised (AN-08); A sentence in the talking points does not match the file (AN-09).

What we could not check

• A new product line copies a price the account already had (AN-04). No mass-attach month was found. No single month moved the whole book, so there was nothing for this check to examine.
• Tags stay stable over the year (SG-07). Tags are not historized. The file stores one tag per account rather than one per month, so segment drift over the year cannot be measured yet.

How this was graded

Weights: Unified, Finance-Approved Foundation 25%, Audit-Grade Accuracy 30%, Cohort-Centric Design 15%, Multi-Dimensional Insights 15%, Anomalies 15%. Bands: A ≥ 90, B ≥ 75, C ≥ 60, D ≥ 45. Bridge convention detected: monthly_sum. Rules version caeb8e512330.

Lenses:

• Decision-ready: not yet. Two High findings are current: the owner gap and the owner concentration.
• Diligence-ready: no. The same 2 High findings are open, and the file has neither unit and price data nor payment data.
• AI-ready: yes.

Next step

The Strategic Revenue Intelligence Assessment walks through these findings with a FinQore analyst and shows what a decision-ready and diligence-ready cube looks like for your business. Your files are retained in FinQore infrastructure for the stated retention period and deleted on request.