Hyperlocalise logoHyperlocalise logo
Request a Demo

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.

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

How it works

Guidelines take effect when you connect the documents your team already maintains — brand books in Google Drive, voice pages in Notion, legal standards in SharePoint, or rules typed directly in Hyperlocalise. You choose which collections apply to which workspaces and languages, and the system keeps them indexed as sources change. New hires and agents read the same corpus instead of hunting for the latest PDF. Inside every draft, Guidelines run as a continuous check rather than a one-time import. Agents pull relevant passages for the content type and market, compare proposed copy against tone, terminology, and compliance rules, and surface mismatches with citations to the source doc. Reviewers see why a phrase was flagged and can accept a fix, override with a note, or update the underlying rule when the brand evolves. Outputs show up where people already write. Flagged segments appear in Content Studio and Automation Workflow runs, blocking publish steps until critical issues clear or an owner approves an exception. Over time, accepted decisions feed back into the knowledge base so the next campaign starts closer to on-brand, and leadership can audit which rules fire most often across locales.

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.

A few things you might ask.

Getting to know Guidelines.

Any more questions?

Contact us

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.