What is ARC Request?
An ARC request is a concise professional message asking a publisher, author, publicist, or review platform for an advance reading copy before publication for legitimate review, coverage, bookselling, library, or media purposes.
What good arc request looks like
A strong ARC request identifies the requester and outlet, explains relevant audience or coverage, names the exact title and format requested, respects review independence, and makes it easy for the recipient to assess eligibility.
- Clear subject line with title and request type.
- Brief identity, outlet, role, and audience information.
- Specific reason the book fits planned coverage.
- Requested format, mailing details only when needed, and courteous close without demanding a positive review.
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.
- Clear subject line with title and request type.
- Brief identity, outlet, role, and audience information.
- Specific reason the book fits planned coverage.
- Requested format, mailing details only when needed, and courteous close without demanding a positive review.
How to write arc request step by step
- 1Confirm the publisher’s stated ARC process before emailing.
- 2Use the publicist or imprint contact when one is provided.
- 3Name the title, author, publication date, and preferred format.
- 4Describe relevant past coverage or audience concisely.
- 5State the intended type and approximate timing of coverage without promising a favorable review.
- 6Follow up once only when appropriate and stop if the publisher declines or does not respond.
8 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
- Sending a generic request with no outlet or coverage information.
- Promising a positive review in exchange for the copy.
- Requesting multiple unrelated titles in one vague message.
- Sharing unnecessary personal data before a physical copy is approved.
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 a concise professional message asking a publisher, author, publicist, or review platform for an advance reading copy before publication for legitimate review, coverage, bookselling, library, or media purposes.
What makes ARC Request effective?
A strong ARC request identifies the requester and outlet, explains relevant audience or coverage, names the exact title and format requested, respects review independence, and makes it easy for the recipient to assess eligibility.
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?
Sending a generic request with no outlet or coverage information. Promising a positive review in exchange for the copy. Requesting multiple unrelated titles in one vague message.
When is guidance about ARC Request ready to publish?
Publish when the writing decision is useful and the supporting source is appropriate to the claim: the strongest available source tier has been checked, material disagreement or uncertainty is named rather than hidden, examples do not imply invented facts, and any recommendation is no stronger than the evidence, story canon, authority, usage evidence, or verified project facts allow. If a consequential claim still depends on an unverified source, generated citation, disputed record, stale requirement, or unresolved contradiction, qualify it, revise it, or hold publication until the evidence improves.
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.