Guidelines

Keep the docs you have. Put them to work.

Connect Google Drive, Notion, and SharePoint, or type guidelines in. Agents read them and flag what does not match.

Request a Demo See a guideline check ↓

Acme · Brand review

Connected guidelines

Drive, Notion, and SharePoint stay the source of truth

Brand & claims policy

Confidential · Page 2 of 6

Use this policy when reviewing campaign copy. Agents must cite the clause that applies.

2.1 Health claims

Do not use "clinically proven" or "klinisch erwiesen" unless the wording is on the approved claims list.

3.2 German advertising

Do not use superlatives such as einzigartig, beste, or sensationell in German ads.

4.3 AI features

Pages that mention KI or AI must include the EU AI Act disclosure from this policy.

Guideline check

Check copy against the PDF

Ask the agent to read Brand-claims-policy.pdf and flag anything that breaks a clause.

From Drive, Notion, SharePoint, or typed guidelines into every draft.01 Connect02 Read the file03 Flag the issues04 Ship

Where your guidelines already live

Drive. Notion. SharePoint.

Leave brand PDFs, market notes, and policy libraries where legal and brand already keep them. Or type a guideline in Hyperlocalise. Agents read either one.

The PDF stays in Drive.

Connect brand-voice and claims PDFs from Google Drive. Agents cite the clause in the file when they flag a draft.

From style guides to claims policies ↗

Brand-claims-policy.pdf

Legal · 6 pages · Connected

3.2 German advertising — no superlatives

Used while you work

The file is the source of truth.

When a draft opens in Content Studio, the connected Drive PDF, Notion page, or SharePoint policy sits beside it. Reviewers and agents read the same document.

Explore Content Studio ↗

Attached to this draftFrom Google Drive ✓

FileBrand-claims-policy.pdf

Last cited3.2 German advertising — no superlatives

StatusTwo flags still open on this draft

Daily compliance auditEvery day at 07:00

ChecksProduct copy · app and CMS stringsWebsite · live pages

AgainstBrand-claims-policy.pdf · Google Drive

Last run · this morning

DE homepage3 flags · clause 3.2

JP product page1 flag · clause 2.1

FR websiteClear

Automations

Audit product and the website. Every day.

Schedule an Automation to check live pages and product copy against the same Drive, Notion, or SharePoint files. Flags show up in the morning instead of after a launch.

Explore Automations ↗

Guidelines that travel with the work.

Apply the same files in the studio. Automate the checks in your workflows.

Multilingual Content Studio ↗Automation Workflow ↗

A few things you might ask.

Getting to know Guidelines.

Any more questions?

Leave the guidelines where they are. Let agents read them.

Connect Drive, Notion, or SharePoint, or type guidelines in, and check the next draft against them.

Request a Demo No second playbook to maintain.

Connected guidelines

Drive, Notion, and SharePoint stay the source of truth

Brand & claims policy

Confidential · Page 2 of 6

Use this policy when reviewing campaign copy. Agents must cite the clause that applies.

2.1 Health claims

Do not use "clinically proven" or "klinisch erwiesen" unless the wording is on the approved claims list.

3.2 German advertising

Do not use superlatives such as einzigartig, beste, or sensationell in German ads.

4.3 AI features

Pages that mention KI or AI must include the EU AI Act disclosure from this policy.

Guideline check

Check copy against the PDF

Ask the agent to read Brand-claims-policy.pdf and flag anything that breaks a clause.

Keep the docs you have. Put them to work.

Drive. Notion. SharePoint.

The PDF stays in Drive.

The file is the source of truth.

Audit product and the website. Every day.

Guidelines that travel with the work.

A few things you might ask.

Do we have to move our guidelines into Hyperlocalise?

What kinds of files can agents use?

How does an agent flag a compliance issue?

Can Automations audit the product and website every day?

What happens when legal updates the PDF?

How do Guidelines work with Content Studio?

Can we use more than one source?

How does Guidelines fit with the rest of Hyperlocalise?

Who should own the connected files?

Leave the guidelines where they are. Let agents read them.

Keep the docs you have. Put them to work.

Drive. Notion. SharePoint.

The PDF stays in Drive.

The file is the source of truth.

Audit product and the website. Every day.

Guidelines that travel with the work.

A few things you might ask.

Do we have to move our guidelines into Hyperlocalise?

What kinds of files can agents use?

How does an agent flag a compliance issue?

Can Automations audit the product and website every day?

What happens when legal updates the PDF?

How do Guidelines work with Content Studio?

Can we use more than one source?

How does Guidelines fit with the rest of Hyperlocalise?

Who should own the connected files?

Leave the guidelines where they are. Let agents read them.