🎉 Introducing AIQ — the new platform from Five Blocks that shows you exactly what AI says about your brand. Discover AIQ →

We were told by counsel to avoid all public statements. Can ORM still work under those constraints?

Quick answer

Yes. Under no-public-statement constraints, reputation work shifts to structural channels: owned-property content, editorial correction requests to outlets, Wikipedia Talk-page accuracy work, and entity-layer updates (schema markup, Wikidata). These channels require no public engagement and produce real movement.

No-comment situations, litigation holds, regulatory reviews, sensitive negotiations, are common, and reputation work is still possible. What changes is the channel mix, not the goal.

Two-column channel map contrasting channels removed under no-comment constraint (public statements and executive interviews, PR narrative.
No-Comment Channel Map: which reputation channels close — and which stay open — under litigation holds, regulatory review, or sensitive negotiations.

Channels removed under no-comment constraints

  • Public statements and executive interviews, anything that constitutes a new on-record response to coverage or allegations.
  • PR-led narrative campaigns, proactive press placements that position the company on the contested matter.
  • New public record creation, op-eds, published quotes, or any content that creates an attributable response trail that counsel has ruled out.

Channels available under no-comment constraints

  • Owned-property content, building out the company’s website, leadership bios, and owned publications on background topics that are accurate and uncontested. This establishes authoritative voice without touching the disputed subject.
  • Editorial correction requests, submitting factual corrections to outlets through standard editorial processes. These are private exchanges between the requesting party and the publication, not public statements, and they do not require counsel approval under most litigation holds.
  • Wikipedia Talk-page accuracy work, proposing corrections to factual inaccuracies through Wikipedia’s disclosed conflict-of-interest edit-request process. The request goes to the article’s Talk page and is implemented by independent community editors, not by the party making the request. This is a private proposal, not a public statement.
  • Schema markup and Wikidata entity updates, deploying structured data across owned properties and correcting the entity layer to ensure the company is represented correctly in the Knowledge Graph and AI engine outputs. These technical updates require no public communications.
  • Source-layer AI work, identifying which sources are driving the AI narrative and working the structural inputs (entity signals, authoritative third-party coverage on uncontested topics) that influence what AI engines retrieve and surface about the entity. This work is invisible to the outside world while in progress.

What this looks like in practice

Engagements run entirely within no-comment constraints produce real movement because the structural channels are often more durable than public communications anyway. AI engines and Google’s Knowledge Graph respond to entity signals, source accuracy, and structured data, not to press releases. The work is largely invisible while in progress, which is an asset, not a liability, in a constrained situation.

Last reviewed: 19/05/2026

Sources (2)
Work with Five Blocks

Five Blocks helps companies manage exactly this.

If this is a live issue for you, our team can help. Let's talk about your situation.

Error: Contact form not found.

Skip to content