TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Need hints & tips on writing a proposal From:Chris Morton <salt -dot- morton -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 29 Nov 2012 09:44:08 -0800
All good stuff.
To this I might suggest that your proposal begin with an *executive
summary* (so-labelled)
that can be quickly skimmed. It should hit on the benefit/cost/risk
analysis, but not in detail—that's what the remaining RFP is all about. I'm
pretty confident you can find all sorts of examples online by Googling
(Binging?).
> Chris
On Thu, Nov 29, 2012 at 9:27 AM, Gregory P Sweet
<gps03 -at- health -dot- state -dot- ny -dot- us>wrote:
>
> Very clearly define the problem this will solve up front. You don't want
> it to be perceived a solution without a problem. So of course it is not
> that we can save $x, or gain and additional $x, it's we will lose $x.
> Simply generating extra, better efficiency, or savings are often a nice to
> haves, where losing is to be avoided at all costs.
>
> -Greg
>
> techwr-l-bounces+gps03=health -dot- state -dot- ny -dot- us -at- lists -dot- techwr-l -dot- com wrote on
> 11/29/2012 07:38:52 AM:
>
> > From: Craig Cardimon <craig -dot- cardimon -at- gmail -dot- com>
> > To: techwrl <techwr-l -at- lists -dot- techwr-l -dot- com>
> > Date: 11/29/2012 07:38 AM
> > Subject: Need hints & tips on writing a proposal
> > Sent by: techwr-l-bounces+gps03=health -dot- state -dot- ny -dot- us -at- lists -dot- techwr-l -dot- com
> >
> > Morning, Whirlers,
> >
> > I offered to help a computer person with a proposal for equipment. They
> > need help simplifying the language. The document does seem kind of
> > "jargony."
> >
> > This document will be seen by the president of the company and probably
> > the board of directors.
> >
> > Any suggestions would be appreciated.
> >
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Writer Tip: Create 10 different outputs with Doc-To-Help -- including
> Mobile and EPUB.
>
> Read all about them: http://bit.ly/doc-to-help-10-outputs
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as salt -dot- morton -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Writer Tip: Create 10 different outputs with Doc-To-Help -- including Mobile and EPUB.