Re: Writing technical reports?

Subject: Re: Writing technical reports?
From: Peter Neilson <neilson -at- windstream -dot- net>
To: TECHWR-L List <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 13 Nov 2008 10:12:08 -0500

Geoff Hart correctly wrote:
> First place to go is the people you're writing for. There is no such
> thing as a single definition of a "technical report" -- there are
> dozens, and possibly hundreds, of different kinds of manuscripts that
> bear this name, all with different purposes and contents.

Ask them to show you a sample of a report that they think typifies what
they want. Even a negative sample ("Not like *ugh* this one!") can be a

ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals.

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

Writing technical reports: From: Cardimon, Craig
Writing technical reports?: From: Geoff Hart

Previous by Author: Re: Windows 3.1 to Windows 95
Next by Author: Re: Trademark placement . . . again
Previous by Thread: RE: Writing technical reports?
Next by Thread: Trademark placement . . . again

What this post helpful? Share it with friends and colleagues:

Sponsored Ads