Technical Editing Client Project

Editing, Not Writing
This has to be a collaborative project. You are helping someone along to their goals, not trying to do it for them. That said, it will, hopefully, be part of your job to be advising/consulting with them on what those goals, and the means to them, ought to be. This requires you to be able to sell yourself as "one of them" -- i.e., you have to show them you know their, as well your, "business" -- that you belong, care, share their larger goals, etc. In some common editing situations, where the editor is the "gateway" to something the writer wants--publication--this is not as much of an issue. The editor will already be established as someone with "stake" in the project. But that is not at all likely to be your position in this project. You are soliciting to help someone. So it is likely you will have to provide evidence you know the genre or form, but also the audience being targeted and how they will respond.

Components

• Proposal and Plan
• Editing Documents: Evidence of Copyediting and Substantive Editing
• Final Report and Presentation of Areas of Improvement, Key Lessons

Key Issues, Problems

Editing on the Whole Spectrum of Writing and Design before knowing It:

Credibility and Ethos
Building Relationships
Design Skills and Concepts
Audience Analysis and User Testing

Limiting the Scope and Defining Deliverables

(the possibility of low-fidelity testing of designs and information)