How to use BetaQuill
How to run a private reading campaign.
Follow the complete author journey or jump directly to the task you need. Each guide links back to the relevant working section.
Runbook 01 Create, verify and open your accountCreate the correct account role, accept the current platform rules and unlock protected BetaQuill controls. Open runbook
-
01
Open Join.
If you already have an account, use Sign in instead. Do not create duplicate accounts for Author and Reader roles.
-
02
Fill in Your name.
Use the display name other members may see. Agreements can separately request a private legal name.
-
03
Fill in Email address and Password.
Use an email you control. The password must contain at least 12 characters, upper and lower case letters, and a number.
-
04
Choose I am joining as.
Select An author to create workspaces or A reader to build a reader profile. One account can later receive the other role.
-
05
Read and accept the policies.
Open each linked policy, then tick the acceptance box only when you agree with the current revisions.
-
06
Submit and verify your email.
Open the verification message sent by BetaQuill and use its link. Check spam or junk before requesting account help.
-
07
Sign in.
Use Email or username and Password. Account opens the live controls available to your roles.
Runbook 02 Create and select an author workspaceCreate the private ownership boundary for campaigns, manuscripts, agreements and the author-owned reader roster. Open runbook
-
01
Sign in with an Author account.
If Author controls are missing, confirm the account was created or enabled as an author and that its email is verified.
-
02
Find Your private author space.
This is the live workspace creator, not the illustrative preview dashboard.
-
03
Fill in Author or imprint name.
Use the author, pen-name or imprint label that should own the campaigns. Avoid a single book title unless it is genuinely the workspace identity.
-
04
Select Create author workspace.
Wait for the success message. Do not press twice while the request is processing.
-
05
Open Author campaigns or Manage readers.
Use Author workspace to select the new workspace. Every record created next belongs to that selection.
Runbook 03 Create and describe a Beta or ARC campaignCreate the live campaign record, define its scope and save dates readers can understand and meet. Open runbook
-
01
Choose Author workspace.
If the workspace is empty, select Create first campaign. If it already has campaigns, select Open campaign beside the one to edit or Create another campaign.
-
02
Fill in Pen name, Manuscript title and Number of pages.
Use the public author identity and the page count of the version readers will receive. Choose Beta for developmental feedback or ARC for pre-publication reading.
-
03
Choose Primary genre and Status.
Choose the closest genre and keep incomplete setup in Draft. Use Recruiting only when ready to seek readers.
-
04
Set Maximum readers.
Enter a realistic active-reader cap from 1 to 500. It is a capacity control, not a promise that every invitation will be accepted.
-
05
Set the complete timeline.
Set Applications open and close, then Reading starts and ends. Add Release date only when applicable. Leave enough time for selection, agreement acceptance, download and meaningful feedback.
-
06
Write the Manuscript summary.
Use no more than 500 words to explain the manuscript and feedback requested. Do not promise rewards for positive feedback or reviews, and exclude contact details and private terms.
-
07
Choose Reader recruitment.
Keep Private to invite selected readers only. To ask for volunteers, set Status to Recruiting and choose Community. BetaQuill requires the standard manuscript details and timeline before the post can go live.
-
08
Add Private campaign notes if useful.
These optional operational notes remain inside the author workspace and are never included in the community post.
-
09
Select Save campaign.
Wait for confirmation before moving to readers, the agreement or manuscript sections.
Runbook 04 Post or respond to a volunteer campaign requestLet suitable readers volunteer without exposing private campaign material or bypassing engagement acceptance. Open runbook
-
01
Author: complete and post the request.
Open the saved campaign and complete pen name, title, pages, genre, the summary of no more than 500 words, application dates and reading dates. Set Status to Recruiting, choose Community and save. Use Private at any time to stop new responses.
-
02
Reader: check profile eligibility.
Your reader profile must be visible to members or public, use Volunteer or Both, and show Accepting for the matching Beta or ARC role.
-
03
Reader: find and respond.
Open Volunteer campaigns, filter if needed, write why you suit the work and select Volunteer for this campaign. You may withdraw while the response is pending.
-
04
Author: decide the response.
Open Volunteer responses in the campaign. Accept and send offer, or decline. Acceptance creates a no-payment engagement offer but grants no manuscript access.
-
05
Reader: accept the exact terms.
Open My campaigns, read the recorded volunteer terms and accept or decline them. Complete any current campaign agreement before downloading a released copy.
Runbook 05 Build a discoverable reader portfolioPublish only the information a reader chooses to share and make a genuine profile eligible for relevant author searches. Open runbook
-
01
Fill in Public display name.
Use the name authors may see. Keep private contact information out of all public profile text.
-
02
Optionally add a Profile photograph.
Choose a JPG, PNG or WebP up to 5 MB, then choose who may see it. New optional sections remain private until changed.
-
03
Write Reader bio and Experience summary.
Describe interests, approach and relevant experience accurately. Set the audience independently for each section.
-
04
Add Previous Beta and ARC reads.
Use Add previous read, enter the title, reading type, completed year and optional note. Only include genuine work and choose who may see the list.
-
05
Set Beta and ARC availability.
Choose Accepting only for work you can currently consider. Authors search these two roles separately.
-
06
Choose Reader service and capacity.
Select Volunteer, Professional or Both; then enter maximum manuscript words, usual turnaround and supported formats.
-
07
Complete professional fields when applicable.
Professional profiles need a charging basis, GBP rate and a clear description of what the service includes. Payment cannot buy a positive review.
-
08
Add Genre specialities.
Choose a genre, role, experience level and priority for each genuine speciality. Add more rows only where useful.
-
09
Choose Directory visibility and save.
Private hides the profile. Members exposes it to signed-in members. Public also permits public discovery. Select Save reader profile.
Runbook 06 Search and assess available readersFind live profiles using explicit criteria and review shared experience without exposing private reader data. Open runbook
-
01
Start with Reader role.
Choose Beta, ARC or either. A profile must be accepting the selected role to match.
-
02
Choose Reader service and Genre.
Use Volunteer or Professional deliberately. Choose All genres only when speciality is not important.
-
03
Enter Manuscript words.
Use the approximate full word count so readers with insufficient stated capacity are excluded.
-
04
Optionally set turnaround, rate and text search.
Maximum turnaround is in days. Maximum professional rate is GBP. Search checks visible names, biographies and specialities.
-
05
Select Search readers.
Read the result count and indexing explanation. Use Clear filters if a combination is too restrictive.
-
06
Review each profile.
Check service, capacity, speciality, visible portfolio and objective reliability evidence. Reader-declared past work is labelled and is not automatically verified.
-
07
Move to an invitation.
Use Manage readers to invite an existing contact by email. A directory profile never exposes the reader private email to general search results.
Runbook 07 Invite, record and assign a readerBring an existing reader into the private workspace, record the relationship responsibly and assign only accepted readers to a campaign. Open runbook
-
01
Choose the Author workspace.
Invitations and roster records belong only to the selected workspace.
-
02
Send the invitation.
Enter Reader email, choose Invitation type and select Send invitation. The reader must use the same address when accepting.
-
03
Wait for acceptance.
A sent invitation is not yet a campaign assignment. Revoke it if it was sent to the wrong person or is no longer needed.
-
04
Maintain the private roster if needed.
Use Reader name, Email, Relationship status, Consent basis, Consent date, Private tags and Private notes. Record only necessary, factual CRM data.
-
05
Open the intended campaign.
Go to Author campaigns, select the same workspace and open the saved campaign.
-
06
Build the assignment offer.
In Assigned readers, choose the accepted workspace reader and select Volunteer or Professional. The choice must match the service category saved on that reader profile.
-
07
Complete professional terms when applicable.
Enter the rate basis, agreed amount, three-letter currency and clear payment timing. Confirm payment is only for private assessment work and never a public review or positive opinion.
-
08
Send the assignment offer.
Select Send assignment offer. The table records the engagement and shows Offered; this is not manuscript access.
-
09
Reader accepts or declines.
The reader opens My Campaigns, reads the exact terms and accepts or declines. Declining is neutral and does not reduce reliability.
-
10
Check release readiness.
The Offer column must show Accepted. Secure reader delivery excludes offered or declined assignments even if someone tries to call it directly.
Runbook 08 Prepare and publish the campaign agreementCreate a readable, evidence-bearing agreement revision the reader can verify and accept before protected access. Open runbook
-
01
Choose Starter template.
Select the closest Beta, ARC or professional template, or Custom agreement. BetaQuill provides template wording for reference and transparency only; it is not legal advice.
-
02
Enter Author / issuing legal name.
Use the person or organisation issuing the terms, not merely a pen name unless it is also the legal contracting identity.
-
03
Choose Agreement legal basis.
BetaQuill starter templates use an England and Wales governing-law basis. For other appropriately reviewed wording, choose Custom agreement and Custom / locally reviewed terms. This choice does not restrict where either participant may live.
-
04
Complete only the fields shown for that template.
Standard Beta and Mutual Confidentiality need neither extra field. ARC requires an Embargo date. Professional Beta requires exact Payment terms that are not linked to positive feedback or a review.
-
05
Review Agreement title.
Use a title that identifies the campaign and purpose of this revision.
-
06
Review every line of Agreement text.
Replace placeholders, correct dates and names, remove irrelevant clauses and make author, reader and BetaQuill responsibilities clear.
-
07
Obtain independent advice.
Consider the countries or legal jurisdictions where the author and reader live, work, sign or may seek enforcement. Mandatory local law and signing formalities may apply, so obtain advice appropriate to both parties before relying on the agreement.
-
08
Acknowledge, confirm and publish.
Confirm the template disclaimer, immutable revision and issuing intent, then publish. Do not publish as a test; a published revision is frozen and the issuance-intent evidence records the disclaimer acknowledgement.
-
09
Check the published revision.
Confirm the revision number, publication time and fingerprint. A later change creates a new revision that readers must accept again.
Runbook 09 Upload and clear the exact manuscript versionStore a version privately, identify it unambiguously and keep it unavailable until validation and scanning return a clean result. Open runbook
-
01
Prepare the file locally.
Open it on your own device, confirm it is the intended revision and use only a genuine PDF or EPUB within the displayed size limit.
-
02
Fill in Manuscript title.
Use the title readers and agreement records should show.
-
03
Fill in Author display name.
Use the author or pen name readers should see; agreement legal identity is handled separately.
-
04
Fill in Version label.
Use a meaningful label such as Developmental draft, Revised ending or ARC proof. Do not reuse a vague label for different files.
-
05
Choose PDF or EPUB.
Select the exact local file, then re-read the displayed filename before continuing.
-
06
Select Upload private version.
Keep the page open until the upload response appears. Do not repeatedly submit the same file.
-
07
Read the version state.
Quarantined means not available. Clean means eligible for allocation. Rejected, failed or inconclusive means do not release it.
-
08
Escalate a stuck or rejected file safely.
Confirm the file is valid, then email support@betaquill.com with the campaign, version label and state. Never email the manuscript or a password.
Runbook 10 Release one traceable secure reader copyBind one exact clean version to one active reader and create a copy identifier without exposing a public media URL. Open runbook
-
01
Check Release readiness.
Assigned reader and Clean version must both show complete. Follow the corrective link beside any incomplete item.
-
02
Check the agreement state.
A published agreement is strongly recommended for confidential work. The reader must accept the latest revision before download.
-
03
Choose Reader receiving this copy.
Select the intended active campaign reader. Check the name carefully; allocations are reader-specific.
-
04
Choose Clean manuscript version.
Select the exact version label and file intended for this reader.
-
05
Select Validate and release secure copy.
Keep the page open while BetaQuill rechecks the exact clean source, generates the reader-specific file, validates the stored result and records both hashes. The manuscript is not sent as an email attachment.
-
06
Confirm the recorded allocation.
Success is shown only after the allocation is Ready and the generated copy hash, size, generator version, signed forensic-marker digest and time are recorded. An error means no send was confirmed.
-
07
Understand the boundary.
The marker can associate a recovered file with an issued allocation, even if the visible licence page is removed. It is not removal-proof and does not prove who disclosed the file. Revocation prevents future BetaQuill grants but cannot retrieve an earlier download.
Runbook 11 Investigate a recovered reader copyCompare a recovered PDF or EPUB with signed allocations owned by the author account, preserve factual evidence and avoid unsupported accusations. Open runbook
-
01
Preserve the recovered file.
Keep the original bytes and record where and when the file was found. Do not edit, resave or rename it solely for the investigation.
-
02
Open Copy investigation.
Sign in to the verified author account that owns the relevant workspace. The author tool cannot reveal allocations belonging to anyone else.
-
03
Choose the recovered PDF or EPUB.
Use a genuine file no larger than 50 MB. Select Inspect recovered copy. The upload is inspected locally for that request and is not added to manuscript storage.
-
04
Read the result precisely.
A signed allocation match identifies the issued copy, workspace, campaign, version and reader allocation. No match is not proof that BetaQuill never issued the file because markers can be absent or removed.
-
05
Compare download evidence.
Check issue time, first recorded download and download count. A reader allocation with no recorded download needs especially careful investigation.
-
06
Open Factual evidence summary.
Copy the generated identifiers, hashes and interpretation into the incident record. Preserve the recovered file and independent discovery evidence separately.
-
07
Investigate before acting.
A copy match does not prove the named reader personally uploaded or disclosed it. Consider device compromise, forwarded storage, shared accounts and other evidence. Give the reader a fair opportunity to respond where appropriate.
-
08
Choose a proportionate next action.
Use Review reader access to pause or block future workspace access, contact BetaQuill support for platform assistance, and obtain legal advice before making a takedown demand or allegation.
Runbook 12 Accept an agreement and download as a readerVerify the reader identity, accept the exact current terms and use a short-lived single-use manuscript grant. Open runbook
-
01
Sign in with the invited reader account.
Use the account whose verified email matches the accepted workspace relationship.
-
02
Open the assigned campaign.
Read the campaign brief, deadline and current participation state before accepting work.
-
03
Read the complete agreement.
Check title, revision, author identity, campaign, confidentiality, conduct, payment and embargo terms where applicable.
-
04
Request Email verification code.
Use the button once, then check the verified account email. Never share the one-time code.
-
05
Complete acceptance.
Paste Email verification code, type your full legal name, tick the intent statement and select Accept agreement.
-
06
Create the secure download.
Under Private manuscript, select Create secure download only when ready to use it. The grant lasts five minutes and is single-use.
-
07
Keep the manuscript private.
Store it securely, do not forward it and follow the accepted agreement and campaign instructions.
Runbook 13 Record progress and submit useful feedbackMake a deliberate commitment, provide structured private feedback and close the assignment with reliable evidence. Open runbook
-
01
Select Start reading when work begins.
Do not start merely to inspect the page. Starting creates the objective commitment used by the reliability ledger.
-
02
Write Overall summary.
Give the author the main reading response and prioritise the most important points.
-
03
Complete strengths and concerns.
Explain What worked well and What needs attention constructively, distinguishing errors from personal preference.
-
04
Add Specific manuscript references.
Name chapters, scenes or passages precisely enough to locate them without copying long extracts.
-
05
Declare AI assistance.
Choose the accurate category. If AI was used, explain the tool and whether it brainstormed, drafted, rewrote or only corrected language.
-
06
Use Save draft.
Save during longer work and confirm the last-saved time before leaving the page.
-
07
Select Submit final feedback.
Review every section first. Final submission is deliberate and is shown to the author as submitted evidence.
-
08
Select Mark complete.
Use this only when the agreed reading and final feedback are genuinely finished.
Runbook 14 Revoke, remove, close or delete safelyUse the correct lifecycle action, preserve necessary evidence and understand what BetaQuill can and cannot withdraw. Open runbook
-
01
Revoke an unanswered invitation.
Open Manage readers, select the workspace and choose Revoke beside the pending invitation. Expired invitations are also closed automatically.
-
02
Remove an assigned campaign reader.
Open Campaign readers, select Remove, enter a factual and respectful Reason for removal, then confirm. The reason is notified to the reader.
-
03
Revoke a released allocation.
Open Secure reader delivery and choose Revoke beside that copy. Check the resulting status before leaving.
-
04
Pause, remove or block a roster relationship.
Use Manage readers only for the private workspace CRM relationship. This is distinct from a single campaign assignment.
-
05
Close or archive a campaign.
Use Closed when the campaign has finished and Archived when retaining it as history. Save the status change.
-
06
Delete only the intended content.
Use the specific Delete control for a campaign, manuscript version or workspace. Read the confirmation and never use deletion as a substitute for an access revocation.
-
07
Remember the technical limit.
BetaQuill can stop future platform access but cannot prove an earlier downloaded file was deleted or recover it from a reader device.
Runbook 15 Review reliability evidence or request a tribunal reviewKeep reader scoring evidence-based, give the reader full context and provide a human review and appeal path. Open runbook
-
01
Read the event, due date and outcome.
Only commitments the reader explicitly starts or completes can affect the 0–100 score. Invitations, login frequency and author removal alone remain neutral.
-
02
Compare it with the assignment record.
Check the campaign, deadline, start, submission and completion facts before disputing an outcome.
-
03
Select Request a review when evidence is wrong.
Give a concise factual reason explaining the error or relevant context. Do not use the process for abuse or unrelated complaints.
-
04
Wait for human review.
The disputed evidence is excluded from the score while the review remains active.
-
05
Read the recorded decision.
The same evidence panel shows the outcome and reviewer explanation.
-
06
Use Appeal decision where available.
State what was overlooked or why the decision is unsupported. The appeal is handled as a separate human review stage.