A style guide allows an editor and their client to establish a set of standardized rules and guidelines that unify the voice, tone, and appearance of the client’s content. These rules can include guidelines on language usage, tone, and inclusive writing, thereby ensuring that the content is understandable and respectful and that it caters to diverse audiences.
Style guides also help in streamlining the content creation process. They establish clear rules for grammar, punctuation, capitalization, and formatting, reducing ambiguity and the need for constant decision making. This saves time and effort, especially in collaborative environments in which multiple contributors are involved.
Launch the microlearning module below to learn more about using a style guide and to test your knowledge using our interactive quiz.
Alternatively, read on for a text-only version of the microlearning.
Style guides can be tailored to serve the needs of individual clients; they cover ambiguous or subjective issues that might have several “right” answers. Consider the following:
All of these can (and should) be covered by a good style guide.
So your client has provided you with (or collaborated with you on) a style guide that answers many of the editorial conundrums listed in the previous section.
Now you’ve got it, how do you make best use of it?
Before you start any work on the client’s document(s), look through the style guide to familiarize yourself with its content.
Ask yourself:
If there is anything that you do not understand or that doesn’t quite seem right, resolve this with the client before starting work.
If it is not possible to do so, you will need to make sure that the client is aware of the approach you have chosen to take (usually by leaving a comment on the document) and that any other editors working on the same project are taking the same approach.
Quite often, it won’t be possible to memorize everything contained in a style guide. Some run for hundreds of pages, while others (while shorter) are for work that needs to be returned quickly.
Your pre-checks will come in handy here; if you’ve noted down what goes against the norm, it’s very likely that you’ll remember these issues when you come across them.
Consider what the style guide’s priorities are, and keep checking for potential issues as you’re working. For example, consider the style guide’s stance on punctuation, capitalization, dialect, tone of voice, and inclusive language.
Text in tables and figures is a particular area where style guide elements will come into play, so do watch out for capitalization, abbreviation, and formatting of text in this context. Quite often, tables and figures will have different rules to the main text.
However detailed it is, no style guide will be able to cover every possible issue.
Style guide creators generally take one of two main approaches to this conundrum:
You should check to see whether the client has a preferred secondary (or tertiary) authority and use it as appropriate.
For anything not covered by any authority, follow the stylistic lead given by other elements of the style guide. For example, if a client wants you to capitalize job titles, they may well want you to capitalize department titles as well.
Once you’ve edited the document, have a final check through your notes and the style guide to see if anything crops up that you remember seeing in the document. Again, consider the main editorial elements (punctuation, capitalization, tone of voice, etc.) and pay particular attention to anything that goes against your usual habits.
Find + Replace (Ctrl+H/Cmd+H) is often quite useful in this instance, as even if you think you’ve caught everything, one or two instances will often slip through.
After that, do a final check through of the document itself, and you should be good to go.
As noted above, sometimes style guides may contain errors or omissions. They may also contain elements that you think will be ugly and/or impractical, or things that may cause inconsistencies or issues down the line.
For example:
There is no one correct way to deal with these issues; how you approach them depends on several factors, such as how many documents you are doing for that client, how many editors are working on the same project, and how far into the project you are.
Here are some likely options.
If it’s impractical to question the style guide for whatever reason, you’re only working on one or two documents for the client (or have almost finished the project), and the issue is only minor, then you could just follow the instructions in the style guide (leaving a comment if appropriate).
If it’s a minor, one-off issue, and you’re only working on one or two short documents for a client, you could choose to go against the style guide and leave a comment to the client explaining your decision.
Be very careful about doing this, and make sure that the decision is communicated to any other editors working for the same client.
If appropriate, you could choose to go with the approach given by a secondary authority (ideally, one listed by the client in the style guide, or if none have been listed, one that seems appropriate for the field you’re writing in).
Leave a comment explaining your decision, unless the client has requested no comments.
If there are other editors working on the same project, it’s crucial that you get their opinion on any such issue and their buy-in to the solution. This may be to follow the style guide implicitly, take a different approach, or contact the client for clarification.
Especially if you’re at the start of working on a large project, and even more so if the issue will have an impact throughout, it is sometimes worth contacting the client for confirmation.
You may just tell them which approach you’re taking, or give a number of options and let them decide.
If you’re working with other editors or on a large project, make sure the style guide is updated with any decisions or amendments and that all the other editors are aware of this change.
Style guides allow content to be refined and standardized, but they do add extra complexity for editors. Here’s a summary of what we’ve covered here:
Got a high volume of content to edit?
Let’s talk about the support you need.
Δ
