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: [2] Request for Proposal forms From:Richard Elsberry <richard -dot- elsberry -at- SCORECAST -dot- COM> Date:Fri, 5 Mar 1999 12:58:14 -0600
Rowena,
This is exactly what I was looking for. It would have taken me hours to
work down to this level of clarity-and I wouldn't have thought of some
of these topics. You will make me look like a genius!
I'm closing my eyes right now and sending you "have a wonderful weekend"
vibes...can you feel them?
-----Original Message-----
From: Rowena Hart [mailto:rhart -at- XCERT -dot- COM]
Sent: Friday, March 05, 1999 12:41 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Re: [2] Request for Proposal forms
A few more thoughts about what should be in
an RFP:
>- Second, always clearly define what IS and IS NOT
>expected in terms of:
(i) CONTACT PERSON at the company who
will be responsible for answering questions of
proposal applicants. this is typically the project
manager, i.e. the person who will oversee the
contract. include contact info such as address,
phone/fax number, e-mail address.
(j) LOCATION OF WORK. will the contractor
be expected to work in your office, or can they
work at home or even in another city? if you do
not specify, you will have to answer this question
later.
(k) SUBSTITUTIONS. will you accept substitution
of personnel? under what circumstances? do
these people have to meet the minimum
qualifications listed in the RFP, or can they have
less experience?
(l) DESCRIPTION OF WORK. (D'uh!) yes, some-
times the people who write RFPs forget to include
a complete description of the work required. this
can REALLY cause problems, because the
contractor can legally argue that the task(s) that
needed to be performed were not clearly defined
and therefore the deliverables and timelines were
inappropriate. in these cases, the law is behind
the contractor, not the company.
(m) PAYMENT TERMS. if a number of companies
are bidding for a large contract, a "deposit" of
n-dollars may be required against the work to be
completed (paid by the contractor bidding for the
contract). this money is held until the work is
deemed to be completed, at which time it is
refunded and interest is paid to the contractor.
similarly, you may specify in the RFP that payment
will be made only upon completion of the contract.
(n) DECISION DATE AND NOTIFICATION DETAILS.
specify the day on which the award decision will
be available, and how the proposal applicants
will be notified of a win/loss.
If I can think of any more sections/items, I'll pass them
on at a later date.
