What is ARC Request?
An ARC request is an inbound professional request from a reviewer, librarian, bookseller, educator, journalist, creator, or other legitimate reader asking the author, publisher, publicist, or review platform for advance access to a forthcoming book. Its job is to establish eligibility and fit for access, not to promise praise or trade a free copy for a favorable review.
What good arc request looks like
A strong ARC request identifies the requester and outlet or role, shows why the title fits the intended coverage or evaluation, follows the stated request process, asks for an appropriate format, limits personal data to what fulfillment actually requires, and preserves complete review or coverage independence.
- Identity and role: who is requesting the copy, which outlet/institution/community they represent, and the relevant audience or professional purpose.
- Title and fit: exact book/author plus one concrete reason it matches the requester’s coverage, collection, classroom, bookselling, or media work.
- Access request: preferred digital/print format, legitimate timing need, and any platform/request-channel details the publisher requires.
- Evidence when useful: recent relevant coverage, outlet page, role information, audience context, or other concise eligibility proof without inflated metrics.
- Independent close: no promised positivity, no implied quid pro quo, and mailing/private information shared only after physical fulfillment is actually approved.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Identity and role: who is requesting the copy, which outlet/institution/community they represent, and the relevant audience or professional purpose.
- Title and fit: exact book/author plus one concrete reason it matches the requester’s coverage, collection, classroom, bookselling, or media work.
- Access request: preferred digital/print format, legitimate timing need, and any platform/request-channel details the publisher requires.
- Evidence when useful: recent relevant coverage, outlet page, role information, audience context, or other concise eligibility proof without inflated metrics.
- Independent close: no promised positivity, no implied quid pro quo, and mailing/private information shared only after physical fulfillment is actually approved.
Choose the right approach
Use the task, reader, and relationship among ideas to choose a structure instead of forcing every situation into one formula.
| Approach | Use it when | Why / what to watch |
|---|---|---|
| You are a reviewer, librarian, bookseller, educator, journalist or similar reader asking for advance access | Use ARC Request. | The requester is seeking access from the rights-holder/publicist/platform before publication. |
| You are the author/publicist asking someone else to consider reviewing the book | Use Book Review Request. | The direction of outreach is reversed and independence safeguards belong to the sender. |
| You are announcing a genuinely newsworthy publication/event/development to media | Use Press Release for a Book. | That is a factual news announcement, not a request for a copy. |
| You need reusable bios, images, fact sheets, interview topics and contacts | Use Author Media Kit. | That is the source-of-truth asset bundle that supports requests and coverage. |
| You need reader-facing promotional messages around release | Use Book Launch Copy. | That surface targets readers/partners rather than requesting advance access. |
| The publisher/platform has a dedicated form or request workflow | Follow that process first. | Do not bypass eligibility or privacy controls simply because email is available. |
Diagnose a weak draft quickly
Use the symptom first: identify what feels wrong, inspect the underlying writing decision, then make the smallest revision that fixes the real problem.
| Draft problem | What to inspect | Revision move |
|---|---|---|
| Requester identity | Can the recipient tell who is asking and in what legitimate role? | Add outlet/institution/role rather than a vague “I review books.” |
| Fit | Is there a specific reason this title belongs in the requester’s coverage or evaluation work? | Name genre/topic/audience/program fit concisely. |
| Policy | Was the current request process checked? | Use the official form, publicist or platform route when specified. |
| Independence | Does the request avoid promising praise, rating, adoption, purchase or coverage? | State consideration honestly and remove quid-pro-quo language. |
| Privacy | Is personal data limited to what access/fulfillment requires? | Delay shipping details until a print copy is approved where possible. |
| Timing | Is the request early enough for the intended coverage but inside the permitted window? | Match publisher/platform timing instead of assuming all ARCs are continuously available. |
See the difference: before and after
A direct contrast makes the writing decision easier to see. The goal is not to copy the stronger sentence, but to understand which underlying choice changed.
Hi! I love free books and I’ll definitely give this five stars if you send me a physical ARC. Here’s my home address.
I review historical mysteries for North Shelf Review, where I cover archive- and research-driven fiction. I’m considering The Missing Index for our October roundup; if review copies are available, I’d appreciate the digital edition. Two recent relevant reviews are linked below. No coverage is guaranteed, of course.
Why this is stronger: The revision establishes role and fit, requests only the needed access, protects independence, and avoids unnecessary personal data.
Revision rule: An ARC request earns consideration through legitimate fit and clear identity—not through promised praise or entitlement to a free copy.
How arc request changes by situation
The core principle can stay the same while the best execution changes with audience, format, evidence, genre, stakes, or length. Use these variations to adapt the technique rather than copying one pattern everywhere.
| Context | What changes | Practical adjustment |
|---|---|---|
| Digital ARC | Prefer the official platform/link route and avoid unnecessary address collection. | Confirm file compatibility and access window. |
| Print ARC | Share shipping information only through the approved fulfillment route. | Copies may be limited by territory or eligibility. |
| Trade publication | Provide deadline and desk/section context. | Do not imply guaranteed placement. |
| Library/store/education | Frame the request as evaluation. | Do not promise acquisition, stocking or adoption. |
| Podcast/media | Ask for access in support of consideration. | Do not label an interview or feature as a review unless it actually is one. |
What to learn next
These links follow the writing decision rather than alphabetical similarity. Use them as a short path from the current concept to the next structural, evidence, revision, or publishing decision.
How to write arc request step by step
- 1Check the publisher, imprint, author, publicist, or platform’s current ARC policy and preferred request route before contacting anyone.
- 2Confirm the title is genuinely relevant to the requester’s review beat, collection, store, classroom, interview, or planned coverage.
- 3Identify the requester, outlet or institution, role, audience, and one or two relevant examples of prior work when useful.
- 4Name the exact title, author, publication timing, and preferred format; do not request several unrelated books in one generic message.
- 5State the intended evaluation or coverage context without promising a review, rating, adoption, interview, purchase, or positive outcome.
- 6Provide a mailing address only when a print copy is approved or the stated form requires it; prefer platform delivery for digital copies when offered.
- 7Follow up only when the stated policy or normal professional practice makes one follow-up reasonable, then stop after a decline or non-response.
16 ARC Request examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
A librarian requests a digital ARC for collection consideration and names the readership served.
A genre reviewer links two recent relevant reviews and requests the ebook format.
A bookseller asks for a print ARC before a planned staff-picks meeting.
A podcast producer explains that the author is being considered for an interview tied to the publication month.
A trade newsletter requests access for a short review section and gives the editorial deadline.
A teacher requests an ARC to evaluate a forthcoming classroom title, making clear that adoption is not guaranteed.
ARC Request templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Subject: ARC request — [BOOK TITLE] by [AUTHOR] — [OUTLET/ROLE].
Body: I’m [name/role] at [outlet]. We cover [relevant audience/topic]. I’m considering [BOOK] for [coverage type] around [time]. If available, I’d appreciate [format]. Recent relevant coverage: [link]. Thank you.
Eligibility block: outlet | audience | relevant links | coverage type | deadline | format.
Common mistakes to avoid
- Treating an ARC as a guaranteed free book rather than discretionary advance access for a legitimate purpose.
- Promising a positive review, high rating, adoption, purchase, interview, or post in order to obtain the copy.
- Ignoring a publisher’s form, eligibility rules, territory limits, format rules, or request window and emailing random staff instead.
- Using follower counts or traffic figures that cannot be supported.
- Sending an unnecessary home address, phone number, ID, or other private information before physical fulfillment is approved.
- Requesting titles outside the outlet’s demonstrated coverage simply because advance copies are available.
- Assuming receipt of an ARC overrides embargoes, platform posting rules, quotation limits, or disclosure requirements.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about ARC Request
What is ARC Request?
An ARC request is an inbound professional request from a reviewer, librarian, bookseller, educator, journalist, creator, or other legitimate reader asking the author, publisher, publicist, or review platform for advance access to a forthcoming book. Its job is to establish eligibility and fit for access, not to promise praise or trade a free copy for a favorable review.
What makes ARC Request effective?
A strong ARC request identifies the requester and outlet or role, shows why the title fits the intended coverage or evaluation, follows the stated request process, asks for an appropriate format, limits personal data to what fulfillment actually requires, and preserves complete review or coverage independence.
How do I write ARC Request?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing ARC Request?
Treating an ARC as a guaranteed free book rather than discretionary advance access for a legitimate purpose. Promising a positive review, high rating, adoption, purchase, interview, or post in order to obtain the copy. Ignoring a publisher’s form, eligibility rules, territory limits, format rules, or request window and emailing random staff instead.
Does every statement about ARC Request need a recent source?
No. Freshness should match the claim type. Current policies, prices, roles, platform behavior, research findings, market conditions, and other changeable facts need current verification. Stable grammar, primary literary texts, manuscript canon, durable craft principles, and original illustrative examples may not need a recent citation at all. First classify the material as fact, interpretation, recommendation, convention, or original example; then use the strongest source and recency standard appropriate to that category, while preserving attribution and uncertainty where they matter.
When should I use a first-party or primary source instead of a secondary source for ARC Request?
Use the first-party or primary source when the exact fact, quotation, current requirement, project/manuscript detail, policy, metric, or source text controls the conclusion. Use a strong secondary source when the job is synthesis, explanation, field-level context, or orientation and the secondary source is appropriate to that job. If a reader could act on the claim, if sources disagree, or if wording depends on an exact passage, number, rule, or current status, escalate to the controlling source of truth and record the source, version/date, and locator before publication.
Should ARC Request show one “last updated” date or track verification at the claim level?
Use a page-level revision date for editorial history, but do not let it imply that every statement was reverified on that date. Changeable facts, quotations, policies, project facts, market data, provider capabilities, and other consequential claims should carry a source record with their own last-verified date or version and a specific recheck trigger. Stable editorial synthesis and original instructional examples can use the page revision/version record instead. When a material correction, retraction, or recommendation change affects what the reader should believe or do, retain the prior record and disclose what changed and why.
How do I know whether a claim or source on a ARC Request guide is stale, corrected, or still active?
Do not infer status from the page-wide update date. Check the controlling source or project record, the exact version/date last verified, and the trigger that could make the item changeable. Keep it active when the source still controls the exact claim; mark review due when a trigger has fired but the conclusion is not yet disproved; mark stale when the old version no longer controls; and use corrected, retracted, withdrawn, or superseded when the editorial history requires it. The correction level should match reader impact: cosmetic edits are not the same as a material factual correction or a critical source failure.