By Cathy Tingle
In a recent SfEP blog I talked about the benefits of working with an assistant, which really came down to three things: speed, safety and society. I complete more projects in the limited time I have; I feel that as a team we are more thorough than I could be alone (there really is no substitute for that extra pair of eyes); and, joyous or frustrating, we can chat about the work, which really helps.
So that’s the ‘why’. But how do we work together?
From batphone to batches
Once I get notice that a project is on its way, the first thing I’ll do is contact Helen via the batphone (which is what we call our DocEditor WhatsApp group). This is to book her time – I can fill her in on the details later.
Then I will look at the manuscript. This might involve a lie-of-the-land review (everyone does this differently but I do mine with the help of PerfectIt) or, because this is the way our biggest client works, I’ll edit a sample chapter to kick off the process. This gives me a sense of the issues so I can brief Helen, and it also means that she can see how I’ve approached things in the sample.
My brief can be anything from a short email to a longer Word document, but it has become snappier over the years as Helen has got to know what I’m after. What I should do is set up a version of a style sheet which not only contains information about the manuscript but also incorporates tick boxes for tasks. One fine day (perhaps when our respective kids have gone off to college) that may happen.
Then it’s over to Helen for a few days. Sometimes I get the project back in one go, but more often she sends it back in batches for me to start while she’s still working on it.
Sharing out tasks
I have asked Helen to undertake various editorial tasks while we’ve worked together, but over time I’ve realised that my needs can be crystallised into one request: ‘Help me focus on the text in front of me.’ To labour the already groaning ‘DocEditor’ extended metaphor that the branding of my business rests on, she’s a bit like a nurse handing me the equipment and information I need to fully concentrate on the presenting patient.
At a recent meeting of the Edinburgh SfEP local group, members talked about the joys of using a second, or even a third, screen so they can review different parts of a document at the same time. In a sense Helen does this job – making visible certain elements from elsewhere in a chapter or a manuscript, or from further afield. She checks:
- citations against reference lists, to make sure they match;
- proper nouns in an internet search – that spellings are correct, that any dates tally up, and then that those proper nouns and related facts are completely consistent within the manuscript;
- weblinks, to make sure they work, and if they can be shortened/neatened in the text;
- other internal cross-references – that descriptions of other sections or chapters are accurate, and that what’s in the text matches lists of contents, illustrations, abbreviations, cases or glossary terms;
- that any numbering – of sections, or of illustrations, for example – runs chronologically.
If our clients asked for tagging/coding she could also do that, but there hasn’t been much call recently.
In the past, Helen has:
- checked if quotations in body text are over the length which requires an indented extract;
- checked if multiple citations are in chronological/alphabetical order as per house style;
- changed hyphens to en dashes in number ranges;
- changed double quotation marks to single (or vice versa);
- executed basic style amendments – standardised ise/ize/yze endings, for example.
But these are things I can happily do as I review the text page by page, and so they’ve fallen away from her task list.
An obvious task for an assistant would be to format references. This is something that other editorial assistants (for there have been others, at various points) have done for me in the past. However, there’s something about a reference list that keeps you close to the heart of a text so I like to do it myself. And I just have this feeling that it’s not something Helen would enjoy.
From all this I hope you’ll gather that every editor/assistant relationship is different. There are tasks that you want to keep for yourself, and tasks that you can’t wait to give away. There are particular talents that your assistant will display and that you will want to encourage, and tasks that won’t suit them. However, in terms of the essentials of a project, the following tips should work for most teams editing documents in Word:
- Always, always get your assistant to track changes, in case of slips of the keyboard or rogue deletions. Happens to the best of us.
- Ask your assistant to post comments in the text (with Review/New Comment) to alert you to anything. Make sure they always begin a comment with a word that’s easily searchable – Helen addresses notes to me personally and at the end I run a search for ‘Cathy’ (there are precious few other ‘Cathy’s in the books we edit) to catch any strays.
- It helps if your assistant can adopt an editorial assistant persona in their comments (they can do this in Word with Review/Tracking/Track Changes Options/Change User Name). I am ‘Cathy Tingle (DocEditor)’ but Helen is ‘DocEditor’, which means that I can adapt any notes she writes, perhaps to query a discrepancy between a citation and a long, complicated reference, with only a little retyping.
- Make the most of highlighting. If your assistant has checked a fact/name/web address online or an internal cross-reference, get them to highlight the first letter (we use pink) to indicate it’s done and correct. If something is not correct, a comment can be left. You can use different colours for different purposes – a green for ‘Is this right?’, for example, if your assistant spots what they think might be a mistake in punctuation or grammar.
- If you are asking your assistant to run checks but not to actually amend anything in the text, you could work with two versions of the manuscript. Simply go through the assistant’s version before you start your own edit. This might be a good method in the first few projects with an assistant, while you’re both getting used to the process.
And don’t forget
- Always let clients know that you are using an assistant. All of mine have been delighted to have this extra pair of eyes on their work for no extra fee.
- Create a non-disclosure agreement and ask your assistant to sign it. If you’re doing this for clients, your assistant will need to do this for you.
- Your assistant deserves recognition. If it wasn’t for them, you might not have done such a thorough job within your deadline. I always include Helen’s name at the bottom of any handover notes that I write for the author so that if an acknowledgement is forthcoming she also gets a look in.
- Make sure your assistant logs their hours – this helps you to understand how it’s all going, but it also means that if they want to join the SfEP, or upgrade, they can use this information as part of their application.
- If you can, write a feedback document at the end of a project. I can’t say I have done this every time, but I’ve always been glad when I have. In taking a few minutes to review what your assistant has done this time, you can see how you can brief them better next, or streamline your processes in future. And it gives you a chance either to ask them to make doubly sure of a certain area of work in the next project or to praise them for specific achievements, which is more valuable than a vague ‘Great job!’
- Buy your assistant a mug. Much tea or coffee is likely to be imbibed in the process of getting your projects done. Then, if you’re very lucky, when you’ve been working together for three years and your original mugs are getting chipped and faded, a lovely client might send you a smart new set.
Cathy Tingle, an Advanced Professional Member, came to freelance copy-editing after a PhD, a decade in marketing communications and four years as editor of a popular Edinburgh parents’ guidebook. Her business, DocEditor, specialises in non-fiction, especially academic, copy-editing.
Posted by Abi Saffrey, SfEP blog coordinator.
The views expressed here do not necessarily reflect those of the SfEP.