Guide
The editor
Where a draft becomes something you are willing to put your name on. It is a normal document editor with a strip of four stages across the top — Review, Humanise, Approve, Publish — that says where the piece is and what comes next. Every stage is open to you at any time; the strip opens on the first one not yet done.
The four stages
A finished stage shows a tick, the current one says Now, and each stage has one main action that takes you to the next. Click any stage to open it.
| Stage | What it holds | Done when |
|---|---|---|
| Review | The body editor with an Edit / Preview switch, the publish check, the sources the writer checked, and any claims to check. | You press Reads right — continue. This is remembered in your browser for the piece. |
| Humanise | The human score, how many passes it took, a before-and-after comparison, and Run again. | A humanise score is recorded on the piece — most drafts arrive with this done. |
| Approve | The reviewer, the saved revision, whether the piece is shared with the company, and the approve button. | A manager or admin approves the saved revision. |
| Publish | Whether the piece has gone out, then Publish (your website), one card with the other ways out — download or copy, a share link, Send to — then Mark as published elsewhere, where the piece went, and its search settings. | A delivery is recorded — one BrandKind made, or one you added. The stage then reads Published. |
Approval is a record, not a lock
Editing
Type, format, restructure — it behaves as a document editor should. Your work saves automatically as you go; there is no save button and nothing to lose by closing the tab. The save state and word count sit under the title on every stage.
Edits are yours and are never overwritten by the system. Converting a piece to another content type, or improving it in a voice, always produces a new piece rather than replacing what you have changed.
A piece is one content type — a blog, a LinkedIn post, a newsletter. To get the same story as another type, use Convert to another content type in the piece menu; it creates a separate piece that links back to this one. There is no per-piece channels section: a post for another platform is its own piece.
The piece menu — the three dots beside Share — holds Version history, Convert to another content type, Move to folder and Move to Archive. Archiving takes you back to the library; the piece can be restored from the Archive page for 30 days, and that page is the only place a piece can be deleted for good.
Preview
The Edit / Preview switch on the Review stage shows the piece rendered as its channel will render it, inside a frame that matches the medium. It is a genuine reading check, not decoration — a paragraph that reads well in an editor can be unreadable as a social post, and this is where you find that out.
- Switch device to see the piece at phone and desktop widths. Most newsletters are read on a phone.
- Proofread at true size. A one-to-one zoom renders the text at the size a reader actually sees, which catches the things a scaled-down preview hides.
- Check the image side. Where the feature image sits is part of the layout, and the preview keeps your choice as you move between views.
The publish check
A single verdict sits on the Review stage, summarising four separate checks. Brand fit, accessibility and reading age are listed there; the human-likeness row lives on the Humanise stage, where you can act on it. It is there to tell you where you stand before you commit.
It never stops you
The four checks
| Check | Question | Affects the verdict? |
|---|---|---|
| Brand fit | Does this sound like the brand voice it was written in? | Yes |
| Human likeness | How likely is this to be flagged as machine-written? | Yes |
| Accessibility | Are there structural problems for assistive technology? | Yes |
| Reading age | How demanding is the text to read? | No — information only |
Reading age is shown because it is useful, and excluded from the verdict because BrandKind does not know your audience. A piece for a technical readership should read older, and a tool that marked that down would be wrong.
Where the lines sit
| Score | Reads as |
|---|---|
| 7.5 and above | Pass — recognisably your brand voice. |
| 5 up to 7.5 | Warning — related to your brand voice, not obviously it. |
| Below 5 | Fail — this does not sound like you. |
| Score | Reads as |
|---|---|
| 75 and above | Pass — few AI patterns. |
| 50 up to 75 | Warning — some AI patterns remain. |
| Below 50 | Fail — strong AI patterns. |
These are not the same numbers the library uses
How the overall verdict is decided
The verdict is the worst status among the checks that actually ran. One failing check fails the piece regardless of how well the others did — an averaged verdict would let a serious problem hide behind three good scores.
A check that could not run is not counted. Too little text to assess reading age does not make a piece worse; it means that check has nothing to say. This is why a very short social post can show a verdict built from fewer checks than a blog.
Acting on it
- Low brand fit is a voice problem more often than a piece problem. One low score is noise; a pattern means the voice needs work — see Brand voices. Make it more on-brand on the Review stage creates a separate draft in a voice you choose.
- Low human likeness responds to ordinary editing. Vary the sentence lengths, cut the tidy three-part lists, remove the summarising final paragraph — or press Run again on the Humanise stage. Drafts under 250 characters (every X post) are below the humaniser's minimum and are left as written; the stage says so and offers no re-run.
- Accessibility flags are usually a two-minute fix: describe the image, stop a heading skipping a level, make link text say where it goes.
- Reading age needs a judgement, not a correction. Decide whether it suits your reader, and move on.
Getting the piece out
Every route out lives on the Publish stage. Export is also in the piece header, because it is the one you reach for most.
Sharing a link or exporting does not mark the piece as published: BrandKind cannot see where a copy ends up. A Send to that succeeds is recorded for you. For anything else, press Mark as published under Mark as published elsewhere, the last card on the Publish stage. The status line at the top then reads Published, with the date and time and the destination where one is known. Someone who can only read the piece sees the same status on their view of it, without the buttons.
Edit the piece after it has gone out and the card says it has been updated since it was published, and offers Mark as published again for when the new version goes out too. The library offers the same thing for the same pieces.
A piece that is live on your website and has not been edited since opens on a summary instead of the four stages: where it is published and when, its address with View live and Copy link, its keywords and search title, the approval and humanise record, and the website’s own controls.Edit this piece brings the stages back. Editing never changes the live page by itself; Update website does.
Pressed it by accident? The confirmation carries Undo, which takes back that one mark and leaves any earlier one alone. Mark as not published stays on the card afterwards and removes every mark on the piece. Neither touches anything else: a delivery BrandKind made stays on the record, and a place you added yourself is removed under Where it went.
| Route | Use it when |
|---|---|
| Export | You are pasting into something else right now (copy it formatted, as HTML, Markdown or plain text) or you need a file (Word, JSON, Markdown or HTML). |
| Share | Someone without an account needs to read it. Read-only, no sign-in — see Library and sharing. |
| Send to | It is going to your CMS. Requires a configured destination. |
| Where it went | You want the record of what happened after it left — deliveries BrandKind made, and ones you add yourself. |
Who can edit what
A piece is either private to its owner or shared with the workspace — the switch is on the Approve stage. Members can edit shared pieces and their own; viewers can read but change nothing, and the controls they cannot use are explained rather than silently hidden. See Team and access.