An editing brief should help two people make the same decision about the work. The client needs to know what they are buying, and the editor needs to know what they can change. A useful brief records the reader, the purpose, the stage of work and the route for questions. It can be short enough to read before opening the manuscript while still preventing several common handoff problems.
Begin with the current document rather than a generic service label. A request to polish a report may mean anything from reorganizing its argument to checking punctuation in a designed proof. Ask what has already been approved and what will happen after editing. The answer determines where the assignment belongs in the publication sequence and what kind of deliverable will help the next person.
Describe the reader's task
Write one sentence explaining who will use the document and what they need to do with it. A trustee reading a funding proposal needs a different level of background from a technician following a maintenance procedure. Be specific about knowledge the reader can reasonably bring. If the document has several audiences, identify the primary one and explain how the secondary audience will use it.
Then state the document's purpose in a way that can guide an editorial choice. A help article might need to take a new account administrator through one configuration task. A report might need to explain findings and support a decision at a board meeting. When a paragraph seems interesting but unnecessary, the purpose gives the editor a basis for asking whether it belongs.
Include any real constraints on language. Defined legal wording, approved quotations, scientific terms or interface labels may need to remain exact. Mark where those constraints come from and who can resolve a conflict. An editor should not have to guess whether an awkward sentence is negotiable or formally required.
Name the stage and intervention
Separate structural decisions from sentence-level work and final proof checks. The CIEP's introduction to editing and proofreading explains why the distinction matters before a project begins. The practical next step is to state the actual remit in the brief. List the changes the editor may make directly and the changes they should raise as queries.
For a stable manuscript, the editor might correct grammar, improve unclear sentences and record style decisions. A change to a substantive claim may need author approval. For an early draft, the work might instead focus on a revised outline and a memo about missing evidence. Describe that output explicitly so neither party expects a different kind of file at delivery.
A representative sample can test this agreement. Give the editor a passage with ordinary prose, technical language and a recurring formatting issue. Review a small number of changes together. Record the decisions that should carry through the rest of the manuscript. The sample is most useful when it settles a question that would otherwise recur on every page.
Make the source file unambiguous
Identify the file that will be edited and give it a stable version label. State whether other people may continue changing it during the assignment. If the answer is yes, agree how those changes will reach the editor. Untracked parallel revisions can erase work and leave people debating which file contains the current wording.
Put supporting material in a clearly named folder. Include the relevant style reference, approved terminology, source documents and any earlier decisions that still apply. Distinguish required references from optional background reading. A folder containing twenty unexplained files gives an editor more sorting work before the assignment can begin.
For web content, identify the final publishing format. A word-processing file may omit link destinations, alternative text, heading levels or interface context. The editor needs to know which of those elements are included in the assignment. A preview of the real page can reveal issues that are invisible in a plain text export.
Set the query route before questions arrive
Choose one person to coordinate answers. That person can consult colleagues and return a consolidated response. Define where queries will live: comments in the document, a separate table or a review system. Use a method that preserves the connection between a question and the text it concerns.
A good query identifies the issue, offers an interpretation when possible and asks for a decision. For example: the introduction gives one eligibility date and the table gives another; which date should be used throughout? That is easier to answer than a comment saying unclear. The brief can include an example so the author knows what kind of response will help.
Agree what happens if an answer arrives after the planned delivery date. The editor may deliver the completed work with the question clearly flagged, or the assignment may pause pending an answer. The right choice depends on the publication schedule. Recording it in advance gives the team a practical way to handle a delay.
Include accessibility in the relevant checks
For web material, a readable sentence is only part of the assignment. Headings should describe the section they introduce, and link text should make sense in context. The W3C's writing tips give a concise basis for discussing these content choices. Decide which checks the editor will make and which require a designer or developer.
A brief might ask the editor to check heading wording and logical order while the publishing team verifies the HTML structure. It might include alternative text drafting but reserve subject accuracy for a specialist. Write down the division. Accessibility work becomes easier to carry forward when each participant can see the task assigned to them.
Avoid adding a broad accessibility approval to a brief whose scope is limited to prose. Name the checks that will actually be performed. The handoff can then state which content elements were reviewed and which need a later technical check in the published environment.
Define a delivery someone can use
List the files expected at handoff. A typical copyediting assignment might return a tracked file, a clean reading copy, a style sheet and a short delivery note. Specify which version the client should use for the next stage. The delivery note should identify unresolved questions and any change that affects several locations.
Keep the style sheet focused on decisions made for this publication. Record recurring names, spellings, capitalization, abbreviations and number treatment. Link to the broader style manual rather than duplicating it. A compact sheet is easier for the next editor or designer to apply when a new passage is added.
Finally, ask both parties to read the brief as if they were joining the project tomorrow. Can they identify the current file, the allowed changes, the person who answers questions and the expected delivery? If so, the brief has done its main job. For a founder building an editorial business under a name such as HumanEditors, that kind of repeatable handoff is a concrete standard to put behind the introduction.