Beta readers

How authors collect early feedback before publication.

FeedbackNotesDiscussion

What you can do here

Beta reading helps authors test a draft before showing it widely. A beta reader can leave notes, discuss weak places, and help polish the text.

Invite trusted beta readers

Collect notes by status

Discuss changes before publishing

Where to find it

Authors manage beta readers from the work edit screen or the work navigation. Beta readers open assigned drafts from their dashboard and can leave notes in the reading interface.

Before you start

Give access only to users you trust with unpublished text.

Explain what kind of feedback you want: plot, style, logic, pacing, typos, or general impressions.

Check the beta notes panel regularly so feedback does not remain unresolved.

Important details

Beta access is private and separate from public publication.

A beta note can point to selected text and include a note type and progress position.

Authors can process notes by status, which keeps accepted, fixed, rejected, and discussion items separate.

If no beta notes exist, the beta-notes shortcut can be disabled in the work navigation.

Main actions

Open beta reader settings for a work
Add a reader with access
Review notes in the author panel
Accept, reject, fix, or discuss each note

If something does not work

A beta reader cannot open the draft.

Check that the user was added to the correct work and is logged into the same account.

The beta notes button is disabled.

It becomes active after notes exist for the work.

Feedback is too vague.

Ask the reader to select exact text and choose a note type before writing the comment.

Common questions

Can anyone become a beta reader?

Only users with access assigned by the author can read beta materials.

Do beta notes publish publicly?

No. Notes are part of the private review workflow.

What do note statuses mean?

They help separate accepted, fixed, rejected, and discussion items.