Writing groups and classes run better when writing group feedback has one clear route: the author shares the draft they want read, readers leave notes in context, and the author reviews those notes without sorting through attachments. That avoids the familiar Tuesday-to-Thursday scramble of emailed chapters, stale Google Drive copies, Word comments, and group-chat replies with no obvious place in the manuscript.
The important setup point is simple: each writer should use their own Pendrilo account. Pendrilo is a hosted writing service built around individual accounts, not a shared customer login or a group license. A small team or coach-and-student deployment can support multiple accounts, but each author should retain control of their own books, drafts, comments, and account access.
For the workshop itself, use Pendrilo’s beta-reader share links. An author can share selected chapters with readers who do not need Pendrilo accounts, collect inline notes, and see the feedback inside the normal editor. It is a practical way to run a critique round without giving the group access to the author’s whole workspace.
How Writing Group Feedback Works With Beta-Reader Links
Start with the author, not the organizer. When a chapter is ready, the author opens their book’s Workshop → Beta readers page and creates a new share link. They can give the link an internal label, choose all chapters or a specific selection, set an optional expiry date, and add an optional passphrase.
The author also chooses whether that share allows comments. If comments are off, the link is a private read-only copy. If comments are on, readers can leave both general chapter notes and comments on selected passages.
Readers open the link in their browser. No Pendrilo account is required. They see only the chapters included in that specific share, in the book’s theme and reading order. They cannot edit the manuscript, download it as an EPUB or PDF, or browse chapters that were not included.
For a weekly group, the rhythm might look like this:
- By Monday, each author creates a link for the pages they want discussed.
- Readers open the link during the week and leave passage-level notes or broader chapter feedback.
- Before the meeting, the author reads the comments in Pendrilo and identifies questions worth discussing aloud.
- After the meeting, the author revises their own manuscript in their own account.
That is cleaner than passing one editable document around. The reading copy and the working manuscript are connected through feedback, but readers do not become collaborators on the author’s draft.
Control What Readers Can See
Use a separate share link for each feedback round. This gives you a clean boundary around the material under discussion and prevents readers from seeing ahead by mistake.
For example, a novelist might share chapters 1–3 for the first meeting, then create a new link for chapters 4–6 the following week. A coach running a class might label links by student and assignment: “Morgan — opening scene, week 3” or “Workshop B — revision packet.” Labels are internal, so they help the author keep track of active links without appearing to readers.
An expiry date is useful when your group has a firm reading deadline. Set the link to expire after the meeting, or leave it open while the author is still considering feedback. If plans change, the author can edit the share settings, revoke the link, or restore a revoked link later.
A passphrase adds another layer of control. It is optional, but sensible for a paid course, a private coaching cohort, or unpublished work with a limited audience. Readers enter it once per session. If the author changes the passphrase, previously unlocked readers must enter the new one before continuing.
Share links are private rather than public publishing pages. Treat the URL as a secret and send it only to the people invited to read. A passphrase helps, but it does not replace basic good judgment about where links are posted.
Keep Feedback Separate for Each Reader
Pendrilo keeps beta-reader feedback siloed by share link. If Sarah reads through Share A and Mike reads through Share B, Sarah does not see Mike’s notes, and Mike does not see Sarah’s. The author sees both sets of feedback in the editor, tagged with the share each reader used.
This is especially useful for classes and coaching relationships. You can give one reader or subgroup a particular chapter selection without exposing another subgroup’s reactions. It also lets an author compare feedback from different rounds without asking readers to work inside a shared document.
When a reader highlights a sentence and comments, the note is anchored to that passage. They can also use the chapter’s notes panel for general feedback that is not tied to one line. The author can reply, and the reply appears for that reader when they next load the share page. The author can also mark comments resolved.
Inside the editor, comments remain part of the author’s working process. They do not appear in the book’s published output. That matters when you are preparing an EPUB or PDF after a revision pass: reader highlights and margin notes are not carried into the export.
Use the Revision Inbox after a busy round
For a chapter with dozens of notes, do not try to solve every comment while reading it. If the feature is enabled on your site, the Workshop → Revision inbox helps the author organize feedback without changing the original comment or its attribution.
Authors can filter feedback by chapter, state, and priority; mark an item New, Planned, Resolved, or Dismissed; and add a private topic such as “opening stakes” or “dialogue clarity.” They can also create a linked To-do item. The task points back to the reader comment rather than copying it into a second system.
This is a better fit for feedback than treating every reader note as an instruction. A comment is evidence of one reader’s experience. The author can group similar reactions, decide what they mean, and then choose whether a revision is warranted.
A Faster Workshop Cycle Without a Shared Account
A shared login looks convenient until it creates problems. Everyone can see every manuscript, organizers become responsible for other people’s drafts, and nobody has a clean boundary between private writing and group work. It also makes account security and ownership unnecessarily messy.
Individual accounts solve that. Each author creates and edits their own book, manages their own codex and planning material, and decides what to share. The group only interacts with the selected reading copy through a beta-reader link.
For an in-person critique group, the organizer can still run the calendar: assign reading order, set deadlines, and remind members to post their links. But the organizer does not need everyone’s password or need to create books inside one shared account.
For a class, the instructor can provide a simple routine:
- Students create their own book and draft in their own account.
- Each student makes one beta-reader link for the assigned pages.
- Students send that link to the assigned readers or post it in the private class space.
- Readers comment before the deadline.
- Writers bring two or three questions from the feedback to the live discussion.
This also works for a coach with several clients. Each client remains the owner of their manuscript, while the coach receives a link to the chapters currently under review. A coach can give feedback without needing access to every private note, unfinished scene, or unrelated project in the client’s library.
Set Up Your First Feedback Round
Begin with one author and one chapter, not a full-group migration. The author should create their own Pendrilo account, make or import a book, and save the chapter they want feedback on. New accounts start with a free trial limited to one book, seven days, and 3,000 cumulative manuscript words. That is enough to test the workflow on a short sample, but regular multi-book use requires paid access.
Once the author has active studio access, they can open Workshop → Beta readers and select New share link. Choose a clear internal label, select the chapters, decide whether comments are allowed, and set an expiry date if the round has a deadline. Add a passphrase if the material needs it.
Then copy the link or use Pendrilo’s email option to send it to a reader with a short note. The reader does not need to register. They open the browser link, read, enter their name when posting a note, and comment on passages or leave general chapter feedback.
After the deadline, the author reviews comments in the editor’s Comments panel or sorts them in the Revision inbox where available. Before making a major revision, take a snapshot from Book details. A snapshot preserves a point-in-time copy of the book’s manuscript and settings, so the author can compare or restore an earlier state later. Reader comments survive a text restore, which is useful when feedback should remain available even after a risky revision is rolled back.
What This Workflow Does and Does Not Do
Beta-reader links are for collecting reactions to selected material. They are not a replacement for co-authoring in the same live document, and they do not give readers a way to edit the text. If your group needs several people to draft one shared anthology manuscript at the same time, agree on a separate editorial workflow rather than sharing one Pendrilo account.
They also do not remove the need for clear critique-group rules. Tell readers what kind of feedback the author wants: big-picture pacing, character motivation, line-level clarity, or factual accuracy. Ask them to distinguish “this confused me” from “you should change this.” The first is useful evidence; the second may or may not fit the author’s intent.
Finally, beta-reader links require the author to have active studio access. If access expires, publishing exports and public reader links become unavailable until access resumes. Keep that in mind when scheduling a workshop near the end of a trial or subscription period.
Test the Process Before Your Next Meeting
Run a small dry run before asking the whole group to change habits. One author can share a two- or three-page chapter with one trusted reader, allow comments, and set the link to expire in a few days. Have the reader leave one passage note and one general note. Then check how the comments appear in the author’s editor and whether the group’s normal discussion style fits the process.
If you need an account for that test, start a Pendrilo free trial. Keep the test small enough to learn the mechanics first. Once the group knows where links live, how comments work, and who owns each manuscript, the weekly feedback round becomes much easier to repeat.
