Guide
The editor
Where a draft becomes something you are willing to put your name on. It is a normal document editor with two things attached: a preview showing how the piece will look on each channel, and a check telling you where the draft stands before you send it.
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.
Edits are yours and are never overwritten by the system. Regenerating or repurposing always produces a new piece rather than replacing what you have changed.
Preview
The preview 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 with the piece, summarising four separate checks. 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.
- Low human likeness responds to ordinary editing. Vary the sentence lengths, cut the tidy three-part lists, remove the summarising final paragraph.
- 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
| Route | Use it when |
|---|---|
| Copy | You are pasting into something else right now. |
| Export | You need a file — for an archive, an approval trail, or another system. |
| Share link | 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. |
Who can edit what
A piece is either private to its owner or shared with the workspace. 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.