What does a Vindex backlog assessment report contain?

A branded cover, an executive summary, a methodology page explaining INVEST and the scoring scale, a score summary (average, median, quality-gate pass rate, stories reviewed), the INVEST dimension breakdown, a score distribution, the lowest-scoring stories with a top recommendation each, a 'what good looks like' set, quality by epic and by author when those columns are mapped, a capped exemplar appendix, a round-over-round improvement section when the project has two scoring rounds, and an editable next-steps close. The full per-story dataset ships alongside as a spreadsheet.

Is the report white-labeled?

Yes. The cover carries your firm's name and logo as 'Prepared by', the client as 'Prepared for', and the 'Scored by Vindex' attribution in the footer is removable. Author names are anonymized by default and ticket keys can be hidden for sensitive backlogs. The client never needs a Vindex account.

What formats does the report come in?

Every generation is an immutable version with three artifacts: a print-ready PDF, a self-contained HTML file you can restyle or re-house in your own tooling, and the complete scored dataset as an Excel export. Regenerating after edits creates a new version, so a delivered report can always be reproduced exactly.

What's in the report I deliver to a client?

8 min read · Updated September 11, 2026

The report you deliver is a white-labeled backlog assessment: your firm on the cover, the client’s backlog scored story by story against INVEST by a neutral engine, and the findings arranged aggregate-first so the sponsor reads a diagnosis of the backlog rather than a list of complaints about the people who wrote it.

This guide walks the report section by section and says what each one is for in a coaching, transformation, or training engagement. The reference is a real one: download the sample report (PDF, 3 pages). It was generated by the production report builder from a two-story test project, so the numbers are small and the firm name is a placeholder, but every section, table, and footer is exactly what your client receives.

What does the report look like at a glance?

Three pages for a small backlog, longer as the exemplar lists and epic tables grow. Page one is the cover and the executive summary. Page two is the analytical core: methodology, score summary, dimension breakdown, distribution, and the lowest-scoring stories. Page three is what good looks like, the epic and author views, the appendix, and your next steps. In the sample, the footer on every page reads “Prepared by [your firm] · Scored by Vindex”; the Vindex attribution is removable.

What is each section for?

Cover: What it shows: Report title, your firm as “Prepared by”, the client as “Prepared for”, the round number, generation date, and stories reviewed.; Why it is there: The first thing the sponsor sees is your brand and your methodology name, not a tool. The round number matters more than it looks: “Round 2” on a cover is the engagement’s progress in one word.
Executive summary: What it shows: One paragraph, auto-drafted from the aggregates (stories reviewed, average score, share meeting the quality gate, weakest dimension) and fully editable.; Why it is there: The only section the sponsor is guaranteed to read. Rewrite the draft in your voice and add the one sentence the numbers cannot: what you recommend doing first.
Methodology: What it shows: Stock explanation of the six INVEST dimensions, the percentage scale, and the de-identification placeholders such as [NAME] that can appear in excerpts.; Why it is there: This is where your authority comes from. Findings trace to a stated, documented standard applied by a neutral engine, so pushback in the room is with the criteria, not with your taste.
Score summary: What it shows: Average, median, share of stories meeting the quality gate (70% by default, adjustable per report), and the count of stories reviewed.; Why it is there: Your baseline in four numbers. When you re-score after the engagement, these are the four that move.
INVEST dimension breakdown: What it shows: Average score and below-threshold count for each of Independent, Negotiable, Valuable, Estimable, Small, and Testable.; Why it is there: Tells you which workshop to run first. A backlog weak on Testable needs acceptance-criteria coaching; one weak on Small needs a splitting session.
Score distribution: What it shows: Stories in the low (0 to 39%), medium (40 to 69%), and high (70 to 100%) bands, with the share of the backlog in each.; Why it is there: The impersonal picture that lets a sponsor agree with you in front of their team. “Half the backlog is in the low band” is a statement about a dataset, not about a person.
Lowest-scoring stories: What it shows: A capped list (10 by default, 50 at most) with key, title, score, and the top recommendation for each.; Why it is there: The illustrations, shown only after the aggregates. Each recommendation is written in plain language a product owner can act on without you in the room.
What good looks like: What it shows: The highest-scoring stories from the same backlog, same columns.; Why it is there: Sets the bar with the client’s own material. A team copies an internal example faster than a slide about INVEST.
Quality by epic and by author: What it shows: Average score and story count per epic and per author, rendered when those columns were mapped at upload. Authors appear as “Author A”, “Author B” by default.; Why it is there: The epic view sequences the engagement: start where the weakest epic is. The author view tells an engineering lead where one-on-one coaching helps; keep it anonymized in anything the team sees.
Exemplar appendix: What it shows: A capped selection of illustrative stories (25 by default, 100 at most) with scores and recommendations, plus optional analyst notes. The full dataset is never printed here.; Why it is there: Completeness without a 400-page PDF. The complete scored dataset ships as a spreadsheet, which is the right medium for row-level data.
Round-over-round improvement: What it shows: Appears automatically once the project has two or more scoring rounds: overall and per-dimension before and after, and how many stories moved out of the low band.; Why it is there: The proof the engagement changed the work. This section is why you baseline before you coach; without a round one there is nothing for round two to beat.
Next steps: What it shows: An editable closing section. The default reads “We recommend a follow-up review after the backlog is revised.”; Why it is there: Your pitch for the follow-on, in the client’s hands after the meeting ends. Name the epics or teams to work with first and the date of the re-score.

What do I get to change?

Sections: toggle any section on or off and reorder them. Three built-in templates ship out of the box: Full Review, Executive Brief (cover, summary, score summary, dimension breakdown, lowest-scoring stories, next steps), and Improvement Report (built around the round-over-round section). Save your own as a house template and lock it so only workspace admins can change it.
Words: the executive summary, per-section commentary, the recommendations on each story, analyst notes, and the next-steps close are all yours to edit. The engine drafts; you decide what the client reads.
Data shaping: the quality-gate threshold, the length of the worst and best lists, which stories are excluded as junk, whether authors are anonymized, and whether ticket keys are hidden.
Branding: logo, colors, firm name, and an about-us closing block saved once at the firm level and reused on every report.

What does the client receive?

Three files per version: the print-ready PDF, a self-contained HTML file you can restyle or drop into your own client portal, and the complete scored dataset as an Excel export with every story, every dimension score, and every recommendation. Each generation is an immutable version, so the report you delivered in March can be reproduced exactly in September. The client never needs a Vindex account, and nothing is installed in their environment.

How do I use the report across an engagement?

Round one is the baseline: generate it before the first workshop and read it out using the structure in presenting findings to a client. Then coach, train, or run the transformation phase. When the team has revised the backlog, upload the new export to the same project and score again; stories that were already scored cost no credits the second time. Round two’s report carries the improvement section automatically, which becomes the first slide of your closing readout and the evidence behind the renewal. The full loop is in how a project works, and the report builder reference lists every option.

How do I get one for a real client backlog?

Request a workspace and the Vindex team sets it up with 100 free starter credits, enough to score the first 100 stories of a real client backlog and generate this report under your brand before any payment conversation. Request a workspace.

Related guides

How do I audit a client backlog?

The baseline assessment a consultancy, coach, or trainer runs at the start of an engagement: what to ask for, why to score every story instead of sampling, how to package the findings as a deliverable, and how to re-score to show the change.

How do I present requirements findings to a client?

How a coach or consultant delivers hard findings about a client's backlog with the product owner in the room: rest on a stated standard, lead with aggregates, anonymize authors, pair every problem with a rewrite, and close on the re-score.

What does a low-scoring story actually cost?

One story from vague to shipped defect: what a story that looks ready hides, what scoring flags in it, and who pays when nobody acts. The guide to send a product owner who says the team has always worked this way, and the pre-read for a definition-of-ready workshop.