# Check the artifact before making it public

The final draft, permitted sources, rights and intended external audience.

Updated October 27, 2026

## Reviewing content before publication, in short

Reviewing content before publication is checking the exact version that will go public for three failures: a retired procedure, a claim with no source, and an image or quote without confirmed rights. It suits content directors and training managers who publish guides outside the company and have been caught by one of those before. Elvina checks each statement against approved sources and each asset against your rights register, and a review step before publishing is available now. Approval names the destination it covers, and a new version gets a new review.

## What happens on the free demo

- Book 30 minutes. Pick a time with Elvina's team. The demo is free and runs on Zoom.
- Show the team your goal. Bring one role or one procedure. The team shows how Elvina would handle it, using sample materials.
- Agree on the next step. You leave with a plan for the first step and its price. Nothing reaches your team until you approve it.

## What you bring and what Elvina returns

| You bring | Elvina returns, for your approval | Status |
|---|---|---|
| The exact guide version going public and its rights register | A list of retired steps, unsourced claims and assets without cleared rights, before publishing | available now |
| The section that still cites an older procedure | That section edited to the current version, with the change shown for review | available now |
| Brand standards kept in Google Drive | The standards connected as an approved source the review checks against | available now |

## Who this is for, and when

A content director at a marketing agency is about to publish a client-facing training guide on brand voice. Last time, a page went live with a procedure the client had retired, a claim about results nobody could source, and a photo the agency did not own. She wants a review that catches those three failure types on the exact version that would go out, and knows that content approval is not the same as permission to post it everywhere.

## How it works in Elvina

A content review catches an outdated procedure, an unsupported claim and an image without confirmed rights.

- She submits the final draft, the permitted sources, the rights register and the intended audience for review in the Web workspace.
- Elvina checks each factual statement against Company Knowledge and flags anything that cites a retired revision or no source at all.
- Elvina lists every image and quote and matches it to the rights register, marking items with no confirmed rights.
- She resolves each flag, records the destination this approval covers, and marks the version reviewed.

## A worked example

A fictional agency, Copperleaf Creative, produces a 30-page brand-voice guide for a client's dealer network. Sources are the client's Brand Standards v5 and a Tone Guide. The draft includes 14 images, two customer quotes and a section on social-media approval steps.

- Three flags: the approval-steps section cited Brand Standards v4, which the client retired; one sentence claimed an engagement lift with no source; one image had no entry in the rights register.
- The director replaced the section, deleted the claim and swapped the image for a licensed one.
- The review record names the reviewed version and states that approval covers the dealer portal only.

## What to check before relying on it

Content approval does not authorize every destination. Review the actual version that would be published.

- Every factual claim in the draft maps to an approved source at its current revision.
- Every image and quotation has confirmed rights for the intended audience.
- The review was run on the exact version that will be published.
- The approval record names the destinations it covers.

## Where a person stays in charge

Elvina reviews against the sources and rights register it was given; it cannot confirm rights that were never documented, and it does not publish anything. Approval of content for one destination does not extend to another. The content director and the client's owner sign off, and a new version means a new review.

## Who this is not for, and when another tool fits

### This is not the right fit if

- You want facts checked against the open web.
- Image rights were never documented and you need Elvina to confirm them.
- You need legal review of the content.

### Another kind of tool may fit better

- A lawyer or a rights specialist, for licensing questions and legal review.
- An editor, when the issue is voice and style rather than sources and rights.

## Questions

**Q:** Can Elvina check facts against the open web?

No. It checks against approved sources only, which is the point: a claim with no approved source is flagged, not researched.

**Q:** What if the client approves the guide but wants it on a different site later?

Record a new destination and run a short re-review. Audience and rights can differ by destination.

**Q:** What counts as an unsupported claim?

Any statement of fact, result or number that does not trace to an approved source at its current revision. Elvina points it out, and the content director adds a source, softens the sentence or removes it before publication.

## Two things you can check on this site

- See a sample on the demo. [Book a demo with my team](https://calendly.com/o-dutchak-smartexpert/30min?utm_source=elvina-site&utm_medium=proof)
- Every lesson, plan and quiz stays a draft until you approve it. [Check the approval step in the chat](/skills/review-content-before-publication#talk-to-elvina)

Checked October 27, 2026.

No launch date is committed for planned features.