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: Request for Proposal forms From:Rowena Hart <rhart -at- XCERT -dot- COM> Date:Fri, 5 Mar 1999 10:11:54 -0800
Richard,
Here are some pointers on creating an RFP:
- Always remember that an RFP is a legally binding
contractual agreement. It isn't the contract itself,
but it is considered (under the law) to be the
foundation of a contract, and is therefore part of a
legal agreement between two parties.
- Second, always clearly define what IS and IS NOT
expected in terms of:
(a) DELIVERABLES. paper or disk delivery?
how many chapters? binding preferences for
print documents? technical appendices? maps
and charts? file format (Word, FrameMaker,
or something else)? delivery at the end of the
project, or at points in between?
(b) COPYRIGHT OWNERSHIP. who owns the
contractors work? if it isn't clearly stated that your
company owns the work, ownership defaults to
the contractor.
(c) HOW YOU WILL EVALUATE THE PROPOSALS
you receive? if you do not have a clearly defined
evaluation process (point system is preferred) you
are opening yourself to legal challenges from the
losers.
(d) QUALIFICATIONS OF APPLICANTS. what
are the minimum qualifications you will accept?
(e) TIMELINE !! create a hard and fast timeline
for the project. make it clear that failure to meet
the timeline (tied to deliverables) constitutes
failure to meet the requirements of the contract,
i.e. the contract becomes invalid.
(f) RESOURCES AND DELIVERABLES OF
YOUR COMPANY AND EMPLOYEES in the
service of the contract. make it clear what your
company will provide to the contractor, and at
what time you deliver it. make it clear that any
delays in YOUR delivery will mean that the
timeline the contractor is following will be
re-evaluated.
(g) DEADLINE FOR DELIVERY OF PROPOSALS.
always define the exact date and hour after
which proposals will not be accepted.
(h) SCOPE OF PROPOSAL. outline what you
expect to see in the proposal itself -- table of
contents, management proposal, technical
proposal, appendices, resumes, price proposal
(sometimes delivered in a separate package
and evaluated separately from the technical
and management proposals).
There are other items as well, but this should get
you started. Best of luck,