A dark fountain pen, an ivory ruled notebook with translucent cyan tabs and a coral revision slip on terracotta.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

An article draft source pack connects the draft's factual statements to the material that supports them. Deliver the text, a claim-to-source record and a clear review state together. Mark unresolved points before handover, keep quotations separate from paraphrases, and identify the exact draft the editor is being asked to review.

This guide proposes a writing workflow. Its repair-cafe example is fictional, with no real interview, commission or audience results behind it. The aim is a draft another person can check and revise. It doesn't promise a writing job, publication or search performance.

1. Give the draft one reader problem

For the practice assignment, imagine an editor requesting a short article about what a visitor should bring to a repair cafe. The reader's problem is preparing for a visit. A history of repair culture, an account of running a venue and a directory of repair businesses would each require a different brief.

Write down the intended reader, publication format and next action before researching. Also record what the assignment excludes. In this exercise, the draft won't advise readers on electrical repairs or promise that an item can be fixed. Those decisions require information the fictional brief doesn't provide.

Agree who can answer questions about the brief. A writer can propose a narrower angle, but should not silently turn an assigned explanation into an endorsement. The keyword research brief covers choosing the page question before this writing stage begins.

2. Make a claim record while you write

Give each checkable claim a short identifier. Record the draft location, the proposed wording, the source URL or supplied document, and the passage that supports it. Include an access date for web material and a version or page reference for a document. A long bookmark list alone makes the editor repeat your research.

For the repair-cafe exercise, a proposed sentence might say that visitors must book a place. The claim record would need the particular organiser's current booking instructions. Without those instructions, mark the statement unresolved or remove it. Don't use another venue's practice to fill the gap.

Keep the strength of the wording close to the evidence. A page saying a service may be available doesn't support a promise that every visitor will receive it. For background research, the desk research brief guide explains how to separate a useful lead from evidence for a specific statement.

3. Separate quotations from your own explanation

Copy any necessary quotation into a clearly marked working field with its source location. Then write your explanation independently. This reduces the risk that a copied phrase becomes an unattributed sentence after several revisions. Don't turn an interview summary into quotation marks or invent a speaker to make a passage sound personal.

In this fictional assignment, an editor might supply an organiser's approved wording about what visitors should bring. Record whether the writer may quote it, paraphrase it or only use it as background. If the permission or intended attribution is unclear, ask the editor before including the statement.

Build a paragraph around the reader's decision, rather than following the sequence of one source. Explain what the evidence permits the reader to conclude and what remains unknown. An article assembled in the same order as another author's piece still needs a new structure, even if every sentence has different words.

4. Review wording without hiding decisions

Choose a review method the editor can actually use. Google Docs' guidance on suggested edits explains that suggestions leave the original text in place until the owner accepts them. A person with commenting or editing access can suggest changes. This makes proposed wording visible, but it doesn't verify a claim's accuracy.

Keep a factual question in a comment or issue record with the relevant claim identifier. Replacing an uncertain sentence with a polished one doesn't answer the question behind it. For example, changing “booking is required” to “reserve your place early” still implies a booking process that must be checked.

Ask the editor to distinguish changes required for accuracy from preferences about style. The writer can then respond to the evidence question without treating every wording suggestion as a new research assignment. Agree who makes the final editorial decision; the tool's buttons don't define that responsibility.

5. Read the draft as a visitor

Set the claim record aside briefly and follow the draft in reading order. Can a visitor tell what information they should obtain from their own organiser? Does a heading promise a checklist that the section never provides? Do examples look like real events despite being invented?

For this exercise, a useful draft would make local uncertainty visible. It could tell the reader to check their venue's booking instructions and item restrictions, without inventing either. It should avoid advice on handling a damaged item when the brief offers no reliable basis for that advice.

Check links at the point where they appear. The linked page should support the nearby statement, rather than merely cover the same broad subject. Remove decorative citations. Use the proofreading service guide for a separate final pass after the factual and structural questions have been resolved.

6. Freeze an identifiable draft

Google Docs' version history guidance describes reviewing earlier versions with editing access and naming versions to identify stages. A named draft can help the participants refer to the same state. It doesn't mean the editor has approved the article, and it doesn't give a recipient access automatically.

Label the submitted draft with its review state and include the matching claim record. If an editor reviews a downloaded file, keep that file's identity beside the handover note. Don't quietly replace it while comments are arriving. Record a later revision as a later version and say which questions it addresses.

7. Hand over questions the editor can answer

Finish with a short note covering the intended reader, the draft being submitted, outstanding factual questions and the person expected to decide each one. State whether image selection, publishing and later updates are included. A writing handover should make the next decision possible without implying that unfinished work has been accepted.

For a practice run, deliver the repair-cafe draft with unresolved venue-specific claims clearly marked. Ask a reviewer to trace one sentence back to its source and identify the current version without your help. If either task is difficult, repair the pack before adding more prose. The book editing handover guide covers the later stage of working on an existing manuscript.