gaash.ai

Authority & Mentions · 9 min read · September 25, 2026 · , gaash.ai

Confidential work as evidence: what a consultancy can publish

Confidential work can still be shown, in forms the agreement and the client allow: anonymized cases stating the industry, size band, region, problem, approach and the kind of outcome measured, with dates and scope; named cases only with written approval; the method as the firm's own writing; talks and articles under the partner's name; references on request. Counsel reads the agreement, and the client approves every case.

What does a confidentiality agreement let a firm publish?

Only the agreement can answer that, and reading it is work for the firm and its counsel, not for a page like this one. Agreements differ in what they protect: the client's name, the fact that there was an engagement at all, the client's data, the work product, or all of these. Two agreements that look alike can draw the line in different places.

What this page can do is make the question for counsel specific. Rather than asking whether the firm may publish a case study, bring one case written out field by field and ask which fields the agreement allows. Whatever counsel says, the client sees the text before it goes up. A description with no name in it can still point at a client for anyone who knows the industry, and the client is the one who can tell.

Five kinds of evidence, and whose approval each needs

Not every piece of evidence waits on one client's permission. The method involves no client at all, and a partner's talk involves one only when a single engagement shows through it. A case needs its client's yes. A reference needs the referee's agreement every time a buyer calls.

The forms a consultancy's evidence can take, what each states, whose approval it needs, and what a reader gets from it.
EvidenceWhat it statesWhose approvalWhat a reader gets
The method, written as the firm's ownHow the firm approaches a problem: the first questions, the stages, what the client receives at eachThe firm's, once it has checked that nothing from one client's material is in itHow the firm works, before any engagement is described
A talk or article under a partner's nameThe partner's view of a problem, on a dated page that may belong to someone elseThe host's, and a client's too if one engagement can be recognized in itA named person tied to a problem by a page the firm did not write
An anonymized caseIndustry, size band, region, problem, approach, the kind of outcome measured, dates and scopeThe client's, for the exact text that will be publishedEvidence that the firm has done this kind of work, and when
A named caseAll of the above with the client's name, plus any figure the client has confirmedThe client's, in writing, for the name, the text and each figureA claim the reader can check with the client
References on requestWhich kinds of engagement references exist for, and at what stage they are offeredEach referee's, every time a buyer callsProof the firm expects to be checked, without publishing who will vouch

The rows are not ranked. A method page and three dated anonymized cases can tell an operator more than one named case with a logo and two sentences. What every row needs is the same: facts a reader can weigh, and nothing the firm could not defend if the client read it.

Dates and scope: what lets a reader weigh an anonymized case

Without dates and scope, an anonymized case cannot be weighed. "We helped a manufacturer improve its margins" could describe a two-week workshop or a nine-month program, finished last quarter or eight years ago, and the reader has no way to tell which. With them, the reader can hold the case against their own company, and a sentence that states the dates and the size keeps them when it is quoted. That is what citability comes to for a case.

The fields of an anonymized consulting case: how to state each, and when it becomes specific enough to identify the client.
FieldStated asToo specific when
IndustryThe kind of company: "a family-owned [industry] distributor"Only a handful of companies of that kind exist in the region named
SizeA band: "[number] to [number] employees" or "[revenue band] in revenue"It is the exact headcount or revenue, which a reader can look up
RegionA country, a state or province, or a wider regionIt names the town where the client is the only company of its kind
ProblemAs the client put it when they first called: "[the problem in their words]"It quotes an internal document or names a product line
ApproachWhat the firm did, in order, and who from the firm did itIt describes a system or process only that client has
OutcomeThe kind of measure and how it was taken: "[measure], from the client's own reports, before and [number] months after"It carries a figure the client has not approved in writing
DatesStart and end, by month and year: "[month year] to [month year]"Hardly ever; the risk is leaving them out
Scope and teamLength, team, what was in and out: "[number] weeks, [number] consultants led by [partner name], implementation by the client"Hardly ever; a comparison needs this field more than any other

The outcome row needs the most care. State the kind of outcome and how it was measured, and add a figure only when the client has approved that figure, in writing, in the sentence that will carry it. A number on the page goes wherever the page is quoted, and a client who never agreed to it has every reason to object.

Dates belong in the text first. In the JSON-LD, the case page can be an Article with the partner who led the work as its author, datePublished for when the case was written, and temporalCoverage for the engagement itself, which schema.org defines as the period the content describes. Mark up only what the visible page states, as Google's introduction to structured data asks.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Problem] for a [industry] company of [size band], [region]",
  "author": { "@id": "https://www.example.com/people/[partner]#person" },
  "publisher": { "@id": "https://www.example.com/#firm" },
  "datePublished": "[YYYY-MM-DD]",
  "temporalCoverage": "[YYYY-MM]/[YYYY-MM]",
  "about": { "@id": "https://www.example.com/services/[problem]#service" }
}

The client's approval, step by step

Approval is a separate step from counsel's reading, and it comes second. The client approves a text, not an idea, so what they see is exactly what goes up.

  1. Write the case in full, every field filled, on the page where it will sit, and mark whether it names the client.
  2. Where there is doubt about what the agreement covers, have counsel read the text against it before the client sees it.
  3. Send the client the text as it will be published, with the page address, and ask them to approve it or mark what to change.
  4. Remove any detail the client asks you to remove, rather than blurring it into something vaguer that still points at them.
  5. Keep the written approval with its date, the text it approved and the name of the person who gave it.
  6. Publish with the dates in the text. Ask again whenever the text changes, and take the case down if the client withdraws.

A figure needs its own yes. A client happy to be described may still not want their margin or their headcount on another company's website, and approval of the case as first written does not cover a number added later.

Evidence with no client in it: the method, the talks, the articles

The firm's method, written from its general practice rather than from one client's material, is evidence that does not wait on any client. A method page says how a [problem] engagement starts, which questions the first weeks answer, the stages and what the client receives at each, and how long each stage runs in the firm's practice. If an agreement assigns work product to a client, counsel will know whether a framework built during that engagement is the firm's to publish.

On a specialty page, the method sits beside the count of engagements and the cases, as the article on stating a specialty sets out. Publishing figures from the firm's own records is a separate subject, covered in thought leadership a machine can count.

Talks and articles under a partner's name put the partner and the problem on a page the firm did not write: a conference program, a trade association's newsletter, an industry journal, a podcast's episode page. The firm's own site cannot do that for itself. Each is a brand mention of the partner, and of the firm when the host names it. List them on the partner's page with the date, the host and a link, so the partner's author profile and the host's page describe the same person doing the same work.

Mentions and digital PR covers earning those pages honestly, and Google's guide to generative AI search says seeking inauthentic mentions across the web is not as helpful as it might seem. One caution belongs to consulting in particular: a talk that walks through one client's situation is a case, whatever the slides call it, and it needs that client's approval like any case page.

References on request, and the sentence that says they exist

Some evidence is better offered than published. A reference, a former client willing to take a buyer's call, is a check the buyer runs directly, with someone who was there, and it belongs at the stage where an operator is choosing between two firms, not on the homepage. What belongs on the page is the sentence saying it exists: "References from [industry] clients for [problem] engagements are available after a first conversation."

Offer only what a referee has agreed to, ask them before each call, and publish no referee's name without their consent. The sentence tells a reader, and anything that reads the page, that the firm expects to be checked. Whether the answers ever cite a case or a talk is one of the columns in a consultancy's panel record. Before a panel exists, the free visibility check gives a first reading: send a website and an email address, and a person replies within 48 hours with whether Claude names the firm and who it names instead.

The rest of what a consulting firm's site states is on the page for consulting firms. Documenting reference projects covers write-ups in general, including photos and where project pages sit on a site.

Common questions

Can we publish a case if the client never replies?

No. Silence is not approval, and a case the client has not seen is one they can object to after it has been quoted. Keep the text on file, describe that kind of work on the method page instead, and ask again at a natural moment: a follow-on engagement, a change of contact, or the client's own announcement of the result.

Is an anonymized case worth publishing at all?

Yes, when it carries dates and scope. An operator reading a case is holding it against their own company: the industry, the size, the problem, how long the work took and who did it. An anonymized case that states all of that is evidence they can weigh. One that says only "a leading manufacturer" gives them nothing to check.

Can client quotes carry review markup?

Not to any effect. Google's review snippet rules make a business ineligible for review stars when it controls the reviews about itself, on its own site, in markup or through an embedded widget, and they rule out aggregating ratings from other websites. Quote a client as text, in words they approved, attributed as they agreed, with the date. If advertising rules where you work cover testimonials, ask counsel.

Should an anonymized case name the partner who led it?

Yes, where the partner agrees and the client's approval covers it. A case that says who led the work lets an operator connect the engagement to a person they may meet, and it gives the partner's page something specific to link to. If the partner has since left, say so in the case: "[name], then a partner at the firm".

Sources

Nothing on this page is legal advice: what an agreement allows is for the firm and its counsel to read, and rules on testimonials differ by jurisdiction. What schema.org's Article carries and what Google asks of markup, reviews and mentions come from the documents linked where each is used.

Sources: documenting reference projects so they count as evidence · mentions and digital PR · schema.org, Article · Google, introduction to structured data · Google, review snippet · Google, guide to generative AI search

All articles