SUBSCRIBE VIA RSS
SUBSCRIBE VIA EMAIL
Hazel Bird is privileged to project manage, copy-edit and proofread sometimes dizzying quantities of interesting words for clients ranging from global academic and trade publishers to government policy units to publishers of creative non-fiction. Her focus is on developing dynamic collaborations with her clients in order to help make their goals a reality. Her biggest project to date was a twelve-volume international encyclopedia with over a thousand contributors. She lives in the stunning countryside of the Wye Valley in Herefordshire, UK, and spends her free time trying to corral her ancestors into some sort of order and attempting to offset a severe doughnut preoccupation with heavy lifting.
ABOUT THE BLOG
The Wordstitch Blog brings together my experience working in publishing on both sides of the client–freelancer relationship (often simultaneously). It aims to foster great working relationships, from a belief that the best text products (of whatever kind) emerge out of genuine collaboration and excellent communication.
- Disengage, re-engage: 13 tips for proofreading text you’ve already copy-edited
- Difficult feedback: should you send it and, if so, how?
- When editorial project managers expect too much
- How to use bubble charts to get a snapshot of your clients’ value to your business
- How to close an editorial project effectively
- Proofreading pitfalls: Nine tips to improve your proofreading strategy
- A day in a life of a freelance copy-editor and editorial project manager
- Plagiarism: How to spot it and what to do about it
Tag Archives: CPD
I recently received a thought-provoking comment from a fellow freelance editorial professional who has been working alongside me on a project I’ve been managing. The projects I manage are typically very large (hundreds of thousands or even millions of words), and there are inevitably hiccups that arise and have to be resolved. So I found it interesting when the other editor commented that I am more understanding than some other project managers about these kinds of hiccups.
My first reaction, I’ll admit, was an irrational sense of worry: Am I a soft touch? Am I checking editors’ work thoroughly enough? Am I setting high enough standards?
It’s always good to self-evaluate when such questions arise, and there will always be things I can learn about my management of other editors’ work. However, a short bout of reflection and a thorough check of the text re-confirmed that I set high standards and ensure they are met.… read the rest >>
I am a huge advocate of comprehensive and well-organised style sheets. When copy-editing and proofreading, they help me to clearly summarise the style decisions I’ve made and communicate them to my client. And, in my project management work, they are indispensable tools for corralling copy-editors on multi-editor projects and for keeping styles consistent throughout copy-editing, typesetting, proofreading, collating and indexing. I’ve previously written about how editors should never fail to provide a proper style sheet (see point 4).
I’ve recently been experimenting with a new technique in my own style sheets: the use of the combo box (also known as a dropdown list). These allow inputting of a set of pre-defined options, one of which is later chosen by clicking on the list and selecting an item.
So how can combo boxes be used in style sheets? Well, I find that the process of compiling a style sheet can be quite time consuming.… read the rest >>
But, however good your editorial skills, they may not be able to save you from losing a client to certain common etiquette pitfalls. I’ve collected seven of these below. These examples particularly apply to relationships with traditional project managers (PMs) or production editors. However, they can apply to relationships with business or self-publisher clients too.
Avoid these ‘sins’ to lessen your chances of irritating your client into dropping you as a supplier.
1. Bad filing
Unhelpfully named documentation can be a hindrance and gives a poor impression of your professionalism. When communicating with your PM or other members of the project team, try to pick email subjects and file names that will be helpful to everyone. For example:
- Never title an email ‘Index’, ‘Queries’, ‘Complete’, ‘Help please!’ or any other unspecific term.