Sticking with Word and Acrobat is kind of essential. These documents go through many rounds of peer review, often with cantankerous and technology-averse professionals working in the developing world. Imagine working with your Great Aunt Edna. She’s completely clueless, but fortunately your cousin Steve spent last summer with her and got her up and running with Word and Acrobat. You’ve tried talking to her about things like Picasa and Google Docs, but she just doesn’t respond well to change.
Also, I’m a bit leery of porting between programs (see, I can learn!). I wouldn’t want to chance losing a comment, change or formatting element, even if the risk is relatively minimal. Word’s change tracking has a hard enough time dealing with deleted and moved footnotes. That said, any version of Word later than 2K would be fine and platform (PC/Mac) shouldn’t make a difference.
Come to think of it, I think an Acrobat substitute would be okay. If you have a program that opens a PDF without disturbing any graphics, can make visible in-text changes (e.g. cross-outs, insertions), anchors comment balloons (e.g. “adjust orphaned text,” “align with margin”), produces a check-offable (affable Chekhov?) list of all changes and comments and saves it so it opens seamlessly in Acrobat on a Mac, that’s fine.
Typical source materials are from agencies such as the United Nations Development Programme or UNICEF. Lengths typically vary from 10-page policy briefs to fifty- or sixty-page assessments. There are usually a handful of tables and figures, but documents rarely contain any significant data analysis.
There are a few (occasionally conflicting) style manuals to follow. UNDP (PDF) is the primary guide, along with a crapulent-but-improving UN editorial manual. UNTerm is the source for agency spelling, capitalization and acronyms. Chicago is the backup when in doubt (and the preferred style for formatting references).
We’re looking for someone with a modicum of professional experience, so I assume hopping across style manuals isn’t a big deal. Experience needn’t be extensive, but there is a bit more to proofing than keeping an eye on grammar and references (e.g. style consistency, heading numbering, table/reference correspondence, design elements).
Turnaround varies withy the project. Two to three days is typical, though we often find ourselves in situations where the client prints in the morning and then carries a box of books on the airplane as she heads to a meeting. Ideally it’ll be a situation where I write with a page/word count and ask if you can make it by a particular day. If so, great. If not, the sporadic nature of things means I can’t think of asking for a commitment to take things on. Given that, I’m thinking of eventually working with a couple people so there’ll be some backup if one can’t take on a project. That’s a bit up in the air though—there are also benefits of working familiarity and not spreading the work too thin.
And sporadic it is. We sometimes work back-to-back for months on end; sometimes we work part-time for months. It’s changing though (hence this post). We’re in a growth period where we occasionally find ourselves with more work than we have time for even with working through the night.
It’s a paid gig, freelance/1099-wise. Considering the primary client base, it’s not a * fantastically* paying gig.
Our heart-based cockles are warmed by the nature of the work (saving the world one comma at a time). And, well, it does pay.
I think that pretty much answers all the questions I’ve received here and in PM. Again, I’m sorry about the delay in moving this along.