Matching Editing to Specific Needs

A technical document goes through several stages during development and requires multiple reviews before it is complete. Using a combination of internal and external reviewers helps ensure the final product meets its intended goal and contains a negligible number of errors. An external reviewer may be referred to as an editor, but depending on the state of the document, more specific direction may be required. An editor's review can span from complex content analysis to fixing the minutia of the technical paper. It is best to have a clear set of tasks when determining editor requirements rather than use a specific term alone. Often duties can overlap at different times, and editors may use additional terms to define specific tasks. Adding to the possible confusion, when editors use other words to describe their skill-set, the result is often misleading to the detriment of time, budgets, and the quality of the technical document. This article explains potential editing terms and their variants, when to engage editors, the tasks related to the terms, and potential editor titles or skills for which to look.

Developmental and Structural Writing and Editing/Revising

Developmental and structural writing and editing or revising focuses on the content and organization of the document. An external source should complete this review either as the subject matter experts (SME) create a draft document or soon after to avoid rework. During this stage, a writer, editor looks at the document as a whole to determine if the content meets the intended purpose. They check that the content is in a logical order for the audience, not just the SMEs. They also make sure the content makes sense by asking for clarification. For example, a process step was omitted, or the content assumes the reader has specific knowledge of the subject or removes unnecessary information.

Potential editor titles to engage include:

  • Technical Writer/Editor

Consistency Editing

Consistency editing ensures consistency within a document or a group of records. This task is essential when dealing with program documentation, where there are multiple types of documents, and there are numerous documents of each type.

When reviewing for consistency, an editor verifies the single document is consistent within itself, matches records of the same type, and contains the key components that tie all of the program documentation together. This includes looking at the document structure/sections, formatting, and program-specific language.

Potential editor titles to engage include:

  • Technical Writer/Editor

Copy and Line Editing

Copy and line editing focus on the clarity and conciseness of the writing regarding the document's type, style, and audience. For example, legal and standards documents, marketing content, and training papers have different writing styles targeted to the intended audience. This task is most successful once the document is efficiently organized and content is in place, but it can be, and is, done during earlier stages. A copy editor reviews a document as a whole, and a line editor examines the document line-by-line. Still, both have the same focus on overall writing quality and consistency. They review for passive voice, long phrasing, run-on sentences, regional colloquialisms, and unoriginal phrases.

Potential editor titles to engage include:

  • Technical Writer/Editor
  • Copy or Line Editor

Mechanical Editing/Proofreading

Mechanical editing or proofreading is fixing the document minutia. While last in this list, automated editing or proofreading can be performed throughout the editing process and must be done at the end regardless of previous efforts. It is often performed multiple times, primarily if internal reviewers fixate on these small details instead of the content and overall organization. An editor reviews spelling and grammar during this task and checks for consistent capitalization, abbreviations, punctuation, and formatting. When finalizing a document, the editor verifies that no errors were introduced when changes were accepted or rejected, provides a final check, and updates all fields and links in a document, including the table of contents and any figure or table references. They also verify any publication dates, copyright years, or other aspects that may change over time are current.

Potential editor titles to engage include:

  • Technical Writer/Editor
  • Copy or Line Editor
  • Proofreader


Each stage in the editing process improves your final deliverable by improving clarity and reducing errors. In turn, you can trust that your audience is efficiently getting the information they need when they need it. At Radiant Digital, our Technical Writers and editors can support all of your writing and editing needs, no matter the stage of your technical documentation. Contact us today to see how we can help you meet your documentation goals.

Techniques for Outstanding Technical Writing

You can search online for technical writer qualities–clear, concise writing, quickly understand concepts, strong interpersonal skills–but those will only get you through the door. You still need to deliver results. A helpful trick to be an outstanding technical writer is to work smarter, not harder. This article will discuss the techniques and benefits of using guides provided by a client and creating your guides while working on technical communication projects. (If you don’t want to search online for technical writer qualities, see the end of the document.)

Use the guides and templates provided by the client

Most clients will have their brand guides, style guides, and templates. It would be best if you used your initial project ramp-up time to become familiar with any guides and templates. You will need to know where to find them and how often they are updated. Usually, they are not updated too often, but you will need to make sure you have the most recent versions. Knowing the guides and having them up to date helps avoid rework.

Brand and style guides

Read any provided guides and ask any questions you may have. Compile the pages that you may need to reference frequently in a separate document. Organize your compact guide so that it is relevant to you–page order, bookmarks, highlighting. Once compiled, place it in a convenient location.
Outside the Box Use your monitor’s background as a quick reference for essential information. Create an image of helpful information, company color codes, acceptable fonts, registration, trademark lists, etc., and set it as your background.


Some companies have templates for everything–from executive PowerPoint presentations to memos. Acquaint yourself with the templates you will work with and when they should be used. For example, there may be separate templates for internal versus external presentations. While they may look similar, there will be critical aspects on one or all of the slides that help protect company information.
When it comes to templates for documentation, use the styles that are in the document. However, a new style may be needed for one reason or another. When you add to the base template, make sure the style aligns with the rest of the document, including indents, tab stops, and line spacing. Once you have the types you need in a document, that document should be the one you use as the template from then on–don’t go back to the original template unless you imported the new styles. When you start a document that you know has all the correct styles, you avoid reinventing the wheel.
Outside the Box When working with PowerPoint presentations, slides that were initially internal-only may be used in an external presentation when the information is allowed to go public. Always build presentations with this fact in mind, so these internal slides that will eventually be external, are created and formatted in a way that is acceptable for external use.

Create your guides

If a company doesn’t have its guides, a project has specific requirements, or there is just a lot to remember, create your guides and job aids. No doubt you will be taking a lot of notes as you work. Compiling them in a single document or folder will help you locate the information you need when you need it. You also don’t need to start from scratch to create your guides; you can search the internet for a starting point and then adapt as needed. Creating guides helps you and helps any team members get up to speed on a project quickly.

Style guide

Creating your style guide is especially helpful when creating multiple related documents that have similar structures and content. You can list the required sections for a document and describe how to handle differences between them. Create lists of standardized text, phrases, and formatting to keep the documents consistent.

Quality control guide

If you make no other guides, create a quality control (QC) guide or checklist. As you work, you will notice common mistakes and, while you are trying to keep an eye out for them, you will miss some. By listing them in a QC guide, you will remember to look for or to use the search option, when possible, to find any mistakes. Be sure to include a list of words that are spelled correctly but are not the right word. Some may include:
• plot – pilot
• manger – manager
• flies – files
• filed – field
• too – to
• form - from
Your QC guide can also include common formatting errors or a client’s formatting preferences. For instance, making sure a heading stays with the content that follows, that the last word in a sentence is not on a new line by itself, or that a table row does not break across a page.
Outside the Box Use the search and replace it with a formatting option to highlight punctuation marks and make potential errors more visible. Highlight all the periods in a document to find paragraphs that are missing periods, bullet points with inconsistent punctuation and structure, and even find long sentences.

Process documents

Create process documents for your own work needs, especially for tasks you don’t often do. These don’t necessarily need to live up to the standards of your client deliverables–sticky notes are handy for short processes or reminders–as long as you can access and digest the information in a reasonable amount of time, they are worth the effort to create.


Whether you are using guides provided to you or created by you, they allow you to focus on gathering and organizing content and, ultimately, creating quality documentation rather than general aspects of the project. At Radiant, these are just a few techniques our technical writers use daily. Contact Radiant for your technical communication needs, and let us show you how our internal commitment to quality is reflected in our product delivery.


A Technical Writer Should:
• Have an eye for detail
• Be able to see the big picture and focus on the details
• Ask questions (even if they are “dumb”)
• Accept criticism
• Push back, but be flexible
• Avoid overthinking
• Know how to find information
• Solve problems traditionally and creatively


A Technical Writer Can:
• Provide an outside perspective
- Identify any overlooked or extraneous information
- Help consider different approaches
• Understand multiple perspectives and adjust documentation accordingly
- Internal versus external
- Marketing versus process
• Provide experience in a variety of document types and industries
• Work independently and within a schedule and budget