An American Editor

February 28, 2018

On the Basics: Making the Best Use of Interaction with Colleagues

Ruth E. Thaler-Carter

Networking and Etiquette

It seems to occur almost every day — someone in a Facebook group or on an e-mail discussion list says they’re available for projects and asks colleagues in the group to send work to them. They might ask for referrals or recommendations or say they’re available for overflow or projects, that they’re starting out and need work, that they’re having a slow period or just lost a major client; some even ask group members to share contact information for clients. It doesn’t matter exactly how they phrase the request, but the basic message is “Please give me work.”

These messages invariably are from people who have never been seen or heard from before. They haven’t introduced themselves, haven’t asked any questions, haven’t contributed anything useful in response to other group members’ questions. Some are new to editing or freelancing, with little or even no training or experience; some have been working for a while, but have hit a dry spell.

Just this past week, a new member of a professional association showed up at its discussion list with the fast-becoming-classic “Hi, I’m new here, please give me your contacts or overflow work and recommend me to your clients and colleagues” message as his first post to the list. He did present his credentials, but still — he posted the same information about his background (essentially his résumé, which is not considered de rigueur on a list) — six times in an hour or so. This did him little, if any, good in terms of respect or interest from listmates.

As with most online communities, it is important to understand that people we “meet” in these collegial environments can be generous with advice and insights into our craft — both editing and freelancing — but that there is a certain etiquette for becoming part of these communities. It is becoming clear that we can’t say it too often: Not only is networking a two-way street, but newcomers should listen, read, and contribute before asking to be referred, recommended, hired, or subcontracted with.

Perhaps even more important, newcomers should remember that established colleagues, both freelancers and in-house workers, are invested in their contacts and clients, and in their reputations. We have put many years into building up our relationships and reputations by providing skilled, high-quality work and respecting the privacy of those we work with. Most of us are more than glad to offer advice and resources, but are not going to risk our reputations, and our relationships with clients or employers, by handing off contact information to strangers.

Keep in mind that there’s a difference between saying “I have openings in my schedule,” “I’m looking for new clients,” “Expected payments are running late and I could use some new projects” versus “Give me your contacts” and “Send me your overflow work when you don’t know anything about me.”

Some editors (and freelancers in other aspects of publishing) may list our clients and projects at our websites. That is not an invitation for others to contact those clients to offer their services, although we have no control over whether someone might do so. We can only hope that anyone who does take advantage of that information doesn’t pretend to know us in the process, or suggest that we’ve referred or recommended them.

With this as a basis, how do we make the best of getting to know each other either in person at meetings and conferences or online in discussion lists and groups without ruffling feathers and crossing lines?

Newcomers to a group can (some would say should) sit back and observe — “lurk” — after joining to develop a sense of what is appropriate for discussion, the tone of the community, and more. Once that is clear, ask questions about the profession, the skills needed, worthwhile resources for enhancing one’s skills, how to break in (most of us love recalling and recounting our early years in the field or in business).

Look for opportunities to establish a professional image and be helpful. Answer colleagues’ questions (if you can). Suggest new resources that haven’t been mentioned or vetted. Relate experiences that demonstrate skills in doing editorial work or dealing with difficult clients. Announce good news about new training you’ve taken, clients and projects you’ve snared, even kudos from clients who are happy with your work. Dial down any boasting, but let colleagues know how your work and business are progressing.

It takes time to gain the trust, confidence, and respect of colleagues. Once you’ve done so, it might be appropriate to ask for referrals and recommendations. Before doing that, though, stop and think about how you would feel if someone you don’t know anything about were to ask you for the contacts and clients you have worked so hard to build up. Use that insight to influence how you word your requests, whether one-on-one or in a group setting.

On the Other Side of the Fence

For colleagues who have established successful editing careers and businesses, today’s culture can be annoying, but it can’t hurt to provide some kind of response to pleas for help.

I try to live by the good ol’ Golden Rule “Do unto others as you would have them do unto you” — and “What goes around, comes around” (or, as Billy Preston sang it, “Nothing from nothing leaves nothing”). When I was ready to start freelancing, I figured out most of what I needed to know on my own, but I also had some very generous colleagues. I tried not to take advantage of their time and knowledge, but it was so reassuring to know that they were available if I needed them.

Nowadays, even established, experienced editors and freelancers need help with the occasional sticky language, client, or technological matter, or even with financial dry spells. No one is immune. It makes sense to give back when possible, because we never know when we may have to ask for help ourselves.

I keep a list of useful resources to offer when someone asks for help in finding work. I also have a boilerplate response for people who ask — whether privately or in a group of some sort — for my client contact information, and for referrals, recommendations, “overflow work,” and other elements of my editorial business.

Helping colleagues feels good — and is an investment in karma: It might seem selfish, but you never know when helping someone out, even with just a list of resources, will come back to help you out in the future. I aim to enhance that karma through avenues like the An American Editor blog (both my own posts and those of our wonderful contributors), participating in lists and groups of colleagues, hosting the Communication Central “Be a Better Freelancer”® conference, referring colleagues whom I know for projects outside my wheelhouse for any reason, and even hiring or subcontracting to colleagues I know and trust.

The operative phrase, of course, is “colleagues I know and trust.” I might not have met some of them in person, but I’ve learned enough about them to feel comfortable with referrals or projects.

How do you respond to people who make what you feel are unreasonable or inappropriate requests for client contacts or business leads?

January 17, 2018

What Not to Do as a Newcomer to Freelance Editing

Ruth E. Thaler-Carter

Over the years, I’ve noticed that many people inadvertently make gaffes when they’re just starting out as freelance editors (or writers, proofreaders, indexers, graphic artists, layout and design providers, etc.). As you start out, or as you look for opportunities in new areas of skills, topics, or services, you don’t want to be the person remembered for a clumsy entry into a community of colleagues.

Keep in mind that most colleagues are more than generous about sharing advice and even fixing problematic sentences — essentially doing your work for you. Be careful not to take advantage of that generosity.

With that in mind, here are a few things not to do when you’re starting out. Or even if you’ve been in the profession for a while!

  • Jump into a discussion group or list to ask how to get started. It might seem like a logical thing to do, but there are so many resources to check out that it shouldn’t be necessary to ask such a general question. Most established freelancers are more than willing to share information, but get tired of the same old “how do I get started” questions that could easily be answered by doing a little research yourself — looking through group archives, doing online searches, consulting bookstores, etc. Once you’ve done some of that basic research, ask something specific.
  • Make your first comment in a discussion list or group a request (or what looks like a demand) that people send you their “overflow” work or refer you for projects. Wait until you have contributed something — preferably several things — useful to the group before you expect people to consider you as someone to refer, recommend, or subcontract to. At least let members of the community know what your background, training, and experience are. Established colleagues are not going to recommend, refer, or subcontract to someone we don’t know and whose skills and experience aren’t evident.
  • Have typos and clunky language in your first — or any — posts to groups of colleagues. Yes, many online environments are considered virtual water coolers or almost family gatherings, and some communities are more forgiving of errors in posts among colleagues than others. And yes, we all make mistakes. But our online presence is often the only way colleagues meet us. If we want people to think well of us as professionals, we have to make our posts as clean, error-free, and coherent as possible. You don’t want to be remembered for error-filled posts when an opportunity arises to be referred, recommended, or hired by a colleague.
  • Ignore the rules of a group. Editorial professionals, especially editors and proofreaders, are supposed to be detail-oriented (perhaps to an extreme extent). If you join a discussion list that calls for tags or labels on messages, use ’em. If the group discourages personal or off-topic posts, pay attention.
  • Complain — to a client or to colleagues — about late payment before it’s been 30 days after you billed for a project, unless the client has clearly agreed to pay sooner than that. Payment by 30 days after invoice date is a standard in the business world. Some clients use 30 business days, and others are using 45 or 60 days. Some will cut and mail that check on day 30, so it won’t reach you for another couple of days. We have a right to be paid on time, but “on time” could mean day 31 or 32. Even if your agreement or contract is to be paid 10 or 15 days after the invoice date, give it a couple of days before checking on the payment if it doesn’t arrive by the agreed-upon date, and make the inquiry polite, not frantic or arrogant.
  • Tell clients you need to be paid because you can’t pay your rent or buy groceries until you receive their payments. Clients don’t care — at least, most of them don’t. They care about getting top-quality work back as scheduled. They also don’t need to get the sense that you can’t manage your finances, even if their lateness is causing the problem. If you have to chase late payments, state the matter in terms of being paid because you did the work as agreed, not because you need the money for essentials.
  • Accept a project deadline and/or fee without seeing the complete document or nature of the assignment first, or accept an editing or proofreading client’s description of the document’s number of pages and level of editing or proofreading needed. A client’s definition of a “page” and what the manuscript needs can be very deceptive. Until the you see the manuscript, you don’t know if the client’s page is single-spaced, in 8- or 9-point type, with next to no margins. Whether you use 250 words or 1,800 characters as your standard definition of a page, use it to determine the actual length of the manuscript.

Clients also tend to think their projects are better than they really are, and “only need a light edit/only need proofreading.” When you actually look at the document, it may need a heavy, intensive edit — one that is substantive or developmental — that will take two, three or 10 times longer than a light edit or proofread.

If you base your estimated fee or deadline on what the client says, you’re likely to cheat yourself — and work yourself to a frazzle for far less money than you should receive.

  • Accept a project when you don’t really know how to use the software program(s) it requires, unless you let the client know ahead of time that that’s the case. Clients don’t want to be your learning curve. Figuring out how to use a new program or application will slow down your editing speed, which could result in missing a deadline or earning less than you should.
  • Respond to a job listing when you aren’t qualified for the project. That only makes you look unprofessional, wastes the prospective client’s time (and yours), and makes the group sponsoring the listing service look bad. Focus on the opportunities that you really are qualified for and your results are likely to improve.
  • Answer questions that weren’t asked. If you can’t respond to what someone actually asked about in a forum, group or discussion list, don’t. If you have a related but different angle, start a new discussion rather than dilute the original one with information that isn’t helpful to the original poster.
  • Fail to look things up that are easily found online or in group/list archives. Most questions about starting out as an editor, a freelancer, or both have already been answered, either in the group you belong to or elsewhere, but so have many questions about usage, grammar, and other aspects of editing. Learn how to check the archives of the discussion lists, forums, and groups you belong to so you don’t ask questions that have been answered dozens of times.
  • Cry poor. This may seem harsh, but try not to use poverty to beg for work or as the reason you aren’t using current technology. Most of us have been there — short of cash, desperate for income, stuck with late-paying clients — and will be sympathetic, but would rather see someone make an effort to overcome these situations than play on that sympathy. Again, we deserve to be hired and paid for our professional services, not because we’re broke.
  • Bulk up your posts to a discussion list or forum with tons of repeated previous message content. As a colleague who manages a list said recently, when asking listmembers to trim their posts, “We’re editors here, so let’s edit.”

What “newbie” goofs did you make when starting out as an editor or freelancer? What would you advise colleagues not to do?

Ruth E. Thaler-Carter is an award-winning freelance writer, editor, proofreader, desktop publisher, and speaker whose motto is “I can write about anything!”® She is also the owner of Communication Central, which hosts an annual conference for colleagues (2018: September 21–22 in Rochester, NY), and the new editor-in-chief of An American Editor.

January 4, 2015

Worth Reading: Workers on Tap

As long-time readers of An American Editor know, I am a long-time subscriber to The Economist (my current subscription runs through 2022), a magazine I think all freelancers should read regularly. One reason why I believe this is demonstrated in these articles from the current issue: “The On-demand Economy: Workers on Tap” and “The Future of Work: There’s an App for That.”

“Workers on Tap” and “There’s an App for That” are must-read articles for all of us. They are not directly aimed at editors and publishing, but they could be without much stretch.

In my recent essay, “Business of Editing: Getting Ready for the New Year,” I mentioned the need for us to look for and evaluate trends that might or will affect our business in the coming and future years. One of the resources I use to identify trends that might affect my business is The Economist; articles like “Workers on Tap” and “There’s an App for That” is why. These articles have given me a great deal of food for thought; perhaps they will do the same for you.

Richard Adin, An American Editor

Blog at WordPress.com.

%d bloggers like this: