You’re a good editor. You can juggle serial commas and breathe fire at dangling modifiers. Your ninja coding skills can subdue even the most tortuous of manuscripts.

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:

1. Never title an email ‘Index’, ‘Queries’, ‘Complete’, ‘Help please!’