Buyer-side method · free template

A case-study template that separates verified evidence from illustrative scenarios

Project write-ups are only useful when a reader can tell which numbers were measured and which were assumed. This template makes that distinction explicit, field by field.

Commissioning reports, signed acceptance sheets and a KPI chart on a tablet on a plant engineer's desk

Short answer

Give every result in a case study one of three labels. Verified: measured before and after with the same method, with a document the customer agrees to stand behind. Partially verified: measured, but over a short period, with a changed method or without customer sign-off. Illustrative: a hypothetical scenario with stated assumptions — useful for explaining a method, never presented as an outcome. Record the baseline period, measurement method, data source and who confirmed it next to each figure.

What do the three evidence levels mean?

Verified

Definition: Before and after measured with the same method and period length

Evidence required: Baseline report, acceptance or KPI report, customer written consent to publish

How to present it: State the figure with its period, method and source

Partially verified

Definition: Measured, but short period, method change or no customer sign-off

Evidence required: Available records, with gaps described

How to present it: State the figure as an early or unconfirmed observation, with limits

Illustrative

Definition: Hypothetical scenario built to explain a method

Evidence required: Stated assumptions only

How to present it: Mark clearly as hypothetical; never as a customer result

Label	Definition	Evidence required	How to present it
Verified	Before and after measured with the same method and period length	Baseline report, acceptance or KPI report, customer written consent to publish	State the figure with its period, method and source
Partially verified	Measured, but short period, method change or no customer sign-off	Available records, with gaps described	State the figure as an early or unconfirmed observation, with limits
Illustrative	Hypothetical scenario built to explain a method	Stated assumptions only	Mark clearly as hypothetical; never as a customer result

Which fields should every case study record?

Use the same structure for every project so readers can compare them. Leave a field empty rather than fill it with an estimate.

Context: Sector, type of site, region at the level the customer allows, existing equipment; Evidence type: Customer-approved description
Required outcome: The measurable result the buyer defined before sourcing; Evidence type: Project brief or URS
Baseline: Value, period, unit and measurement method for each KPI; Evidence type: Historical operating reports
Scope and RFQ: What was specified, how many comparable proposals, evaluation criteria; Evidence type: RFQ and comparison sheet
Selected solution: Technical approach and reasons; supplier named only with consent; Evidence type: Evaluation record
Acceptance: FAT/SAT or commissioning tests and their criteria; Evidence type: Signed test protocols
Result: After value measured the same way as the baseline, with its label; Evidence type: KPI report after stabilisation
What did not work: Delays, changes, deviations and how they were handled; Evidence type: Change log, meeting notes
Confirmation: Who confirmed the figures and when; consent to publish; Evidence type: Written approval

Download the case-study template (CSV)

Opens in Excel, Google Sheets or LibreOffice. One row per figure, with label and evidence columns.

Checklist before publishing a case study

Every figure carries one label: verified, partially verified or illustrative
Baseline and result use the same unit, method and period length
Illustrative scenarios are visibly marked and kept apart from customer results
The customer approved the text, the figures and any name or location in writing
No claim implies a guaranteed saving, output, price or financing outcome for other buyers
Our role is described accurately: buyer-side procurement support, not manufacturer, lender, engineering contractor or trade association
Problems and deviations are reported, not only successes

Frequently asked questions

Can an illustrative scenario appear in a case study?

Yes, to explain a method or show what a calculation looks like — but in a separate, clearly marked block, with its assumptions, and never mixed with the customer's measured results.

What if the customer will not allow their name?

Describe the context at the level they approve (sector, region, size range). The evidence label still applies: an anonymous result can be verified if the records exist and the customer confirmed the figures.

How long after commissioning should results be measured?

After the operation has stabilised and over a period comparable to the baseline. A first-weeks figure is usually partially verified, not verified.

Do you publish customer case studies?

Only with the customer's written approval of the text and figures. This page is a method and template, not a case study, and contains no customer results.

Planning a project you will want to measure?

Define the outcome and baseline first; the project team can then help prepare a structured RFQ and compare proposals on the same basis. The buyer service is free and carries no obligation.

Prepare a structured RFQ Build your baseline from operating data

Sources on substantiating published claims

These are general references on truthful testimonials and claims; they are not legal advice and their applicability depends on the market.

Global B2B Group provides supplier-neutral, buyer-side procurement planning. It is not a manufacturer, lender, engineering contractor or trade association.