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: White Paper Proposals From:"Bill Darnall" <darcom -at- sbcglobal -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 17 Jun 2004 16:34:24 -0700
It is for a solicited (aka advertised) grant. They are asked, along
with several other vendors, to answer the SOW, RFP and RFQ. It IS a
Seinfeld episode. Bill, any more questions I can answer w/out reading
a slew of doco on white papers???
- - - - - - - - - - - - - - -
In theory . . . . .
The only difference between a grant proposal and a "regular" proposal
is how funds are handled.
As far as I know, there is no difference between a white paper for a
non-grant project and a grant-funded project.
The proposal MUST address 100% of everything asked for in the Request
for Proposal (RFP). All requirements MUST be answered, item by item.
Ideally, you should be able to say you "comply" with each requirement
and why. If you have supporting white papers, the proposal item can
refer to specifics in that white paper.
The proposal MUST explain 100% of how you will accomplish the items
spelled out in the Statement of Work (SOW). If the company has
performed similar work, the SOW item can also refer to specifics in
the white paper.
The cost (quote) MUST explain funding requirements that are asked for
in the Request for Quotation (RFQ). If you wish, you may have cost
information (of some type) in a white paper, to which one can refer to
establish reasonableness of costs.
In general, your white paper(s) can / should be used to amplify any
claims made in your proposal. The white papers can be use in an
appendix or may be included as a SECTION in the proposal as supporting
My take on the requirement is your white papers need to be about
similar projects the company has performed on. Then, you can use these
white papers as reference material for different sections of the
If (they) don't want separate formal white papers, you can write
sections of the proposal that support the claims you are making. In
this case, they might be paragraphs or pages that would be directly
associated with a proposal item. Then, they would not be called white
papers, they would just have the same information that would appear in
a white paper.
One could call this final approach a proposal white paper! <g>
SEE THE ALL NEW ROBOHELP X5 IN ACTION: RoboHelp X5 is a giant leap forward
in Help authoring technology, featuring Word 2003 support, Content
Management, Multi-Author support, PDF and XML support and much more! http://www.macromedia.com/go/techwrldemo
COMPONENTONE DOC-TO-HELP 7 PROFESSIONAL: From a single set of Word documents, create online Help and printed documentation. New version offers yearly subscription service, Natural Search, Modular TOC Utility, Image Map Editor, Theme Designer, Context String Editor, plus more. http://www.componentone.com/doctohelp .
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.