Running Your First Job

You don’t need to write a brief. The Engine already knows your brand — your identity, your products, your latest visibility report, and anything you’ve uploaded — so a first job can be as simple as one click or one sentence.

The Easiest Start: Follow the Checklist

If your brand is new, Mission Control shows a Getting Started checklist that sequences everything for you: report → audit → first fixes → content plan → first piece. Each step is one click, later steps unlock as earlier ones finish, and the list ticks itself. You can genuinely just follow it.

Past the checklist, the Mission Control layer cards remain the quickest launch points:

• Run your first audit (Technical Foundation) — pick a focus and click Start audit.
• Plan your first content (Content Authority) — optionally give a direction and click Start planning.

Both end in the same place: a queue of proposed work waiting for your approval. Approve what you want, dismiss the rest.

Or Just Ask

The Engine workspace has a command bar at the top. Type what you want in plain English:

• “Audit my blog for SEO issues”
• “Write a comparison page about us vs. [competitor]”
• “Plan five posts targeting mid-market buyers”

The Engine figures out the right job to run. Depending on your request it will start immediately, ask a quick clarifying question, or show a Proposed Plan with numbered steps you can run or dismiss.

Below the command bar, quick actions open short forms when you’d rather fill in fields:

• Audit — pick a scope and click Start Audit. Full Site covers everything in one pass (the default for a first audit); Content Only checks what your pages say; Technical / SEO checks what AI can read; Brand Consistency checks whether pages agree with each other and your brand profile.
• Plan — describe your objective, choose how many pieces, click Start Plan.
• Write — a topic, content type, and length (from Short at roughly 350–800 words up to Comprehensive at 2,200–3,800), then Start Draft. Optionally add the query you want to rank for, a favourite post to emulate, extra context, or reference images.
• Optimise — describe what should change on a page (URL optional) and the Engine finds and patches it.
• Refresh — asks the Engine to re-audit your site and propose updates for stale content.

The first time you open the workspace, a How it works panel spells out the loop right above the command bar: point it, it proposes, you approve, you review. Dismiss it anytime; the How it works link brings it back.

Choosing a Destination

Draft and optimise jobs include a Destination picker, pre-filled from what you’ve connected:

• CMS draft — an unpublished draft in WordPress, HubSpot, Webflow, or Contentful. You review and publish it there; it never goes live on its own.
• GitHub PR — files on a branch in your connected repo, opened as a pull request. Nothing reaches your site until you merge.
• Google Doc — a shared Doc for commenting and revision rounds; push it to your CMS or repo later, once approved.
• Direct — the draft stays in BrandViz. Read it, copy it, or send it on afterwards.

Using Google Docs

Google Docs needs no setup in Integrations — it works through sharing:

• Drafting into a Doc: choose Google Docs as the destination and the Engine creates the Doc in a shared drive for you.
• Giving the Engine a Doc to read or build from: share that Doc with agent@brandviz.ai (Viewer access is enough — Editor if you want it edited in place) and paste its URL into the job. If a Doc isn’t shared, the job tells you exactly what to fix before it starts.

Watching It Run

Your job appears at the top of the Activity tab and moves through statuses:

Most jobs finish within minutes; big audits can take longer (jobs get up to an hour). You can Cancel a running job and Retry a failed one. When it reaches Ready for Review, it’s your turn — see Reviewing & Approving Work.