Components and Purposes of Client Project Documents

Memorandum

To: English 427 Class, Winter '06
From: Professor Benninghoff
Date: 11 April 2006

Re: Components and Purposes of Client Project Documents

Overview: Parts and Purposes of the Client Project and the
This memo lays out the pieces that need to be turned in with the project, and then goes into more depth from class discussion about what should be in your reflective report about the project.

The Components

Client Project Write-up and Reflective Report
Original documents from the client
Design editing feedback documents
Substantive editing feedback documents
Copy-editing feedback documents

About the Write-up and Reflective Report
First off, here's a list of aspects of editing the Reflective Report ought to cover:

How to work with someone
not just telling, but teaching
know (investigate?) their business
ask what they want to do
how to do html
style issues -- consistency -- pre-suppositions
Aspect1

Here I'll record whatever the class discussion turns up about what aspects of editing ought to be covered in the report.

Evaluation: Evidence of "Good Editing"
The client project is all about realizing the complexity of real editing work. It's one thing for a sentence to be wrong on the test on in class, a whole 'nother thing to have to teach the concepts while maintaining a relationship with the client. It puts you in the position of explaining "why" for rules in a constructive way. So what counts as good editing will be not just effective feedback, but awareness of the process while you are doing so. When giving feedback, you will have to make the case for what you recommend from awareness of the audience and its needs. Editing by rote rule will be evaluated poorly.