request for proposal (rfp) guidance notes

RFP Guidance Notes – CIPS Australia of 20

Request for Proposal (RFP)

Guidance Notes


1 Contents Overview ................................................................................................................................................. 4

Use of the template and guidance notes ................................................................................................ 5

Discussion and explanation of RFP sections and clauses ........................................................................ 5

1. Instructions to proposers and proposal conditions ........................................................................ 6

1. 1 Definitions ............................................................................................................................... 6

1. 2 Summary of the Requirement ................................................................................................ 6

1. 3 Structure of this document ..................................................................................................... 7

1. 4 RFP key dates .......................................................................................................................... 7

1. 5 Company contact .................................................................................................................... 8

1. 6 Queries and questions during the RFP period ........................................................................ 9

1. 7 Proposal briefing and site visit ................................................................................................ 9

1. 8 Amendments to RFP documents ............................................................................................ 9

1. 9 Proposal lodgement methods and requirements ................................................................. 10

1. 10 Late Proposals ................................................................................................................... 10

1. 11 Acceptance of Proposals ................................................................................................... 11

1. 12 Alternative Proposals ........................................................................................................ 11

1. 13 Validity of Proposals .......................................................................................................... 11

1. 14 Evaluation of Proposals ..................................................................................................... 12

1. 15 Withdrawals ...................................................................................................................... 12

1. 16 Proposers to inform themselves ....................................................................................... 12

1. 17 Costs of preparing Proposals ............................................................................................ 13

1. 18 Confidentiality ................................................................................................................... 13

1. 19 Inconsistencies and omissions .......................................................................................... 13

1. 20 Proposal acknowledgement .............................................................................................. 14


1. 21 Return of RFP documents ................................................................................................. 14

2. The Requirement .......................................................................................................................... 15

3. Information to be provided by Proposers .................................................................................... 17

3.1 Pricing Information ..................................................................................................................... 17

Prices include all costs ...................................................................................................................... 17

Goods and Services Tax (GST) ........................................................................................................... 18

Currency of proposed rates and prices ............................................................................................. 18

3.2 Non-Price Commercial Information ............................................................................................ 18

3.3 Technical Information ................................................................................................................. 19

4. Proposed Contract ........................................................................................................................ 20


Overview A Request for Proposal (RFP) is issued by an organisation to obtain proposals (also known as bids or offers) for the supply of inputs to the organisation (usually goods or services). An RFP is almost always prepared in writing. The RFP sets out details of what is required to be supplied, but it also includes what other information the buying organisation needs to select a winning bid and to provide sufficient information to form a valid contract for the supply. Typically more than one supplier is invited to respond to an RFP and, by doing this, the buying organisation seeks to use ordinary market forces to ensure invited suppliers provide their most competitive offers.

A Request for Tender (RFT) (alternatively called an Invitation to Tender (ITT)) or Invitation to Bid (ITB)) is also used by organisations to seek offers for the supply of inputs to the organisation. In practice RFP and RFT/ITT/ITB terminology tends to be used interchangeably. This is understandable, as they do similar things. However the primary difference between an RFP and RFT is that an RFP is used where the requirement is less prescriptive or defined. This means that suppliers preparing bids or offers may be allowed more freedom and latitude in their responses and the response requirements may be less extensive or onerous than an RFT. In contrast, the RFT/ITT/ITB will be used for more exacting requirements, with tender latitude correspondingly reduced. Assessing whether an RFP or RFT is more appropriate can be quite subjective.

Often RFTs (more so than RFPs) are preceded by a short listing or pre-qualification process. The short listing is sometimes initiated by a more “open” document again - known as Request for Information (RFI) or a call for Expressions of Interest (EOI). The information sought in RFI’s is less onerous again that in an RFP and there will usually not be sufficient information sought from prospective suppliers to allow a valid supply contract to be formed. The idea is that a buying organisation will use the information provided in RFI responses/EOIs to shortlist prospective suppliers. Only shortlisted suppliers then receive RFPs or RFTs. This staged procurement approach is useful for ensuring that the cost and time buyers and sellers invest in tendering is optimised because only companies deemed capable of submitting genuinely competitive offers are invited to participate in the much more involved RFP or RFT processes.

To support the concept of this staged procurement, CIPS Australia has prepared two template documents – an RFP and RFI. This guidance note sets out the basic elements of the RFP and describes the reasons why the various clauses are included in the RFP.


Use of the template and guidance notes The RFP template and these related guidance notes, have been prepared by CIPS Australia with procurement practitioner input. The content has been subject to CIPS professional practice review and is considered a reliable framework to ensure primary risks and commercial issues are addressed for a typical sourcing transaction.

But, like any template of a general nature, the RFP cannot accommodate all purchasing circumstances or suit the specific needs of buying organisations. CIPS Australia does not warrant or represent that these documents will meet the exact needs of any one requirement. The RFP template is intended to be a launch pad or thought-jogging device and CIPS Australia expects that users will customise the template to suit their needs. Individuals should therefore not rely on the contained information and are encouraged to use their own judgement as to the applicability of any of the provided materials and when independent professional advice should be sought.

Discussion and explanation of RFP sections and clauses The RFP is a document in four parts:

1. Instructions to proposers and proposal conditions – Sets out the expectations, obligations andrequirements for buyer and proposer while the RFP is active.

2. The requirement - Describes what the buyer seeks to purchase; including specifications,standards, quality requirements, timelines and the like.

3. Information to be supplied by proposers - Sets what information is to be provided by proposers(including pricing of course) to allow the buyer to adequately consider proposals, identify thesuccessful bid and obtain all the information needed to form a valid contract for the supply.

4. Proposed contract - Sets out the terms and conditions for a contract expected to be formed as aresult of the RFP.

Each of the four RFP sections is discussed in more detail below.

Sometimes the RFP may also include an introductory cover letter or email. The purpose of this letter, apart from individually inviting a response, is to provide reinforcement of particular issues or additional context or emphasis for the RFP.


1. Instructions to proposers and proposal conditionsReproduced below is each of the “Instructions to proposers and proposal conditions” clauses in the CIPS Australia template RFP document. Located next to each clause is a dialogue box that describes the intent of the clause and, where appropriate, offers additional help or suggestions. Text highlighted in yellow is meant to be replaced or over typed.

1. 1 DefinitionsFor the purposes of this Request for Proposal (RFP) and any subsequent contract the following definitions, unless otherwise noted, apply.

Company (may in lieu or in addition use a shortened version or acronym of the Company name)

Means [name of Company, including ABN]

Contract Means any contract that results from this Request for Proposal

Contractor Means the entity that forms a Contract with the Company for provision of the requirement.

Proposal Means a written offer submitted in response to this Request for Proposal

Proposer Means an entity that submits, or is invited to submit, a Proposal in response to this Request for Proposal

Requirement Means the supply to be made by the Contractor to the Company in accordance with Part 2 of the RFP.

1. 2 Summary of the RequirementCompany invites you to submit a Proposal for the [summary of requirement]. Further details of the requirement are described in Part 2 of this RFP.

1. It is good practice to define the keywords and phrases used in commercial documentation. This list is not exhaustive – feel free to add as you see fit.

2. Use at least a couple of sentences tosummarise the requirement. Proposers should be able to get a good handle on what is required just by reading this.


1. 3 Structure of this documentThis RFP comprises of four parts as described below:

Part Title Description 1 Instructions to Proposers and

Proposal Conditions Sets out rules and requirements for

participation in the RFP. 2 The Requirement Sets out details of the

requirement, including scope of works.

3 Information to be provided by Proposers

Sets out the minimum RFP response requirements to allow due consideration by

the Company. 4 Proposed Contract Sets out the applicable terms

and conditions that will apply to any contract arising from

this RFP.

1. 4 RFP key datesThe following key dates apply to this RFP:

RFP Issue Date As stated on the RFP Cover Page

Date for lodgement of Proposal Acknowledgement

[Insert]

Date of Proposer briefing/site visit [Insert]

RFP Closing Date and Time As stated on the RFP Cover Page

Estimated Contract Award Date [Insert]

3. Including this structure helps demystifythe document.

4. Clear RFP dates are essential. Good drafting practice dictates that the dates are only includedonce (so there is no chance of confusion). Another way of doing this is to use the “Field” function in MS Word to only update information once but have it reflected in multiple places - eg if you want to show the dates here as well as on the front page of the RFP.

Delete the briefing/site visit requirement if not needed.

Sometimes buyers like to issue a cut-off date for proposal clarification questions. If so, include it here.

Remember to include your time zone (eg EST, WST) when including the closing time.


1. 5 Company contactThe following individual is the nominated Company contact for this RFP.

Name [Insert]

Title/Position [Insert]

Telephone [Insert]

Facsimile [Insert]

Email address [Insert]

Postal address [Insert]

5. Having a single focal point is essentialto manage all Proposal correspondence. Include a back up person if needed. Note that there will also need to be a company representative in the Contract – it may not be the same person as for the RFP.


1. 6 Queries and questions during the RFP periodProposers are to direct any queries and questions regarding the RFP content or process to the Company contact. No other Company personnel are to be contacted in relation to this RFP unless directed to do so by the Company contact. Company reserves the right to disqualify and reject Proposals that do not comply with this requirement. All questions should be submitted in writing either by post, facsimile or to the nominated email address.

Company may choose to convey responses to submitted questions and queries to all Proposers so that each is equally informed.

1. 7 Proposal briefing and site visitCompany will hold an RFP briefing session to further familiarise Proposers with the Requirement. This briefing will also include a visit to the Company site. A maximum of two representatives from each Proposer is permitted to attend the RFP briefing session and site visit. Further details regarding the RFP briefing session and site visit will be provided to Proposers.

1. 8 Amendments to RFP documentsCompany may amend the RFP documents by issuing notices, by way of formal [variation/addenda], to that effect to all Proposers and may extend the RFP closing date and time if deemed appropriate.

6. RFP processes are highly susceptible toconcerns over probity and fairness. One way to minimise this risk is to ensure clear communication channels between Company and Proposer and to ensure everything is in writing and directed to the one person. Depending on what the question or query is, you may wish to share the answer with all Proposers to ensure the “playing field stays level”. This clause permits you to do this.

7. For more complex requirements it isnormal to have these information sessions. They are usually held a little way into the RFP open period once Proposers have had a chance to read and reflect upon the RFP documents. Delete this clause if you are not having a briefing or site visit.

8. Issuing RFP variations/addenda isquite normal during an RFP open period. This clause acknowledges that this may happen. Update the clause to reflect whatever naming convention (eg Variation/ Addendum etc) applies to your company and make sure you stick to it. Addenda are to be sequentially numbered, should be subject to individual receipt acknowledgement, and you should keep a register of these as part of your RFP process documentation.


1. 9 Proposal lodgement methods and requirementsProposers must submit [number] copies of their Proposal to the Company in any of the following methods:

a) By post to: [insert postal address].

b) By email to: [insert email address]. The subjectheading of the email shall be [RFP [insertreference number] – Proposal - [Proposer Name]].Electronic copies are to be submitted in PDF andnative (eg MS Word) format and proposers maysubmit multiple emails (suitably annotated – egEmail 1 of 3) if attached files are deemed toolarge to suit a single email transmission.

c) By hand to: [insert details of drop off location – egtender box]

Proposals must be prepared in English and in the format requested in Part 3 of this RFP. As a minimum, a Proposal is to also contain a cover letter [and executive summary].

Hard copy Proposals must be:

d) contained in a sealed envelope or package, clearly labelled with the RFP reference number; and

e) loose bound so that pages can be readily separated by the Company.

1. 10 Late ProposalsProposers are responsible for submitting their Proposals prior to the RFP closing date and time in accordance with the acceptable lodgement requirements described in Clause 1. 9. There will be no allowance made by the Company for any delays in transmission of the Proposal from Proposer to Company. Any Proposal received by the Company later than the stipulated RFP closing date and time may be removed from further consideration by the Company.

9. Most organisations have their ownrules about how proposals and tenders are to be submitted. There are myriads of combinations – eg sometimes you might want price and non-price information to be submitted separately, and depending on how the evaluation is to proceed you might need varying hard and electronic copies.

Note that usually email attachments of >5MB would be considered “too large”.

Consider whether an additional executive summary from Proposers would be useful and amend the text accordingly.

TAILOR THIS CLAUSE TO SUIT YOUR OWN NEED, POLICY OR PRACTICE.

10. Modify this clause to suit your ownlate proposal/tender policy – eg some organisations outright reject late tenders. The clause as drafted gives you the right to keep late proposals in the process but does not let Proposers claim the Proposal should be accepted because it was “lost in the mail”.


1. 11 Acceptance of ProposalsProposal may be for all or part of the Requirement and may be accepted by Company either wholly or in part. A Proposal will not be accepted by Company unless and until Company has signed a Contract or sent a 'Notice of Award' in writing to the successful Proposer.

Company is under no obligation to accept the lowest priced Proposal or any Proposal and reserves the right to reject any Proposal which is incomplete, conditional or not complying with the RFP documents.

1. 12 Alternative ProposalsProposers may submit alternative Proposals it they feel it may offer the Company additional benefits whilst still complying with the Requirement. Company reserves the right to accept or reject any proposed alternative either wholly or in part.

1. 13 Validity of ProposalsProposals submitted in response to this RFP are to remain valid for a period of [insert number of days] from the RFP closing date.

11. This clause is necessary to retain yourflexibility during the evaluation process and to make sure no actions or activities undertaken by you can be reasonably interpreted at acceptance of any offer. Remove this clause at your peril!

12. Including this clause allows aninnovative idea to be proposed. However sometimes separating an alternative proposal from a non-compliant one is difficult. You need to retain the flexibility to deal with alternatives as you see fit.

13. Set a reasonable validity date –usually the amount of time between RFP close and estimated contract award is a good yardstick. Asking for a validity period of greater than 90 days will often cause Proposer concern. In some instances it may not be permissible by law. If in doubt, seek advice.


1. 14 Evaluation of ProposalsThe minimum selection criteria to be used in the evaluation of Proposals include, but are not limited to, the following:

[insert evaluation criteria]

These criteria are not in any particular order nor do they necessarily carry equal weight.

Company may request additional information from Proposers to assist further evaluation of Proposals.

1. 15 WithdrawalsProposals may be withdrawn at any time prior to the RFP closing date and time by written notice to the Company.

1. 16 Proposers to inform themselvesCompany has taken all reasonable care to ensure that the RFP is accurate, however the Company gives no representation or warranty as to the accuracy or sufficiency of the contained information and that all Proposers will receive the same information. Proposers are required to inform themselves fully of all conditions, risks and other circumstances relating to the proposed contract prior to submitting a Proposal. Proposed prices shall be deemed to cover the cost of complying with all the conditions of the RFP and of all things necessary for the due and proper performance and completion of the Requirement.

14. This is an extremely important clauseand how much or little you include will depend on your company policies and procedures. In general terms the more prescriptive you are in defining evaluation criteria and weightings the higher the burden you face in demonstrating that you evaluated the proposals as stated. There is case law in Australia that has deemed that the RFP/RFT document can represent a process contract and you could be held in breach if you do not do what you said you were going to do – especially in regards to the evaluation. You should obtain legal advice on this matter if you are at all unsure.

15. This clause is self-evident but therequirement to withdraw in writing is necessary given potential process contract issues outlined above. Buyers should be very wary of letting proposers withdraw after the closing date, given potential impacts during the evaluation and award processes. It is for this reason that proposers are required to fully inform themselves so they can’t back out later because they “didn’t know” about something.

16. It is absolutely necessary to keep thisclause to ensure there are no opportunities for proposers to rescind their Proposals. The efficacy of evaluation and award processes depend on robust Proposals.


1. 17 Costs of preparing ProposalsAll costs relating to the preparation and submission of a Proposal are the sole responsibility of the Proposer. Company shall not pay any Proposer, wholly or in part, for its Proposal.

1. 18 ConfidentialityExcept as required for the preparation of a Proposal, Proposers must not, without Company’s prior written consent, disclose to any third party any of the contents of the RFP documents. Proposers must ensure that their employees, consultants and agents also are bound and comply with this condition of confidentiality.

1. 19 Inconsistencies and omissionsProposers must promptly advise Company in writing of any inconsistencies and omissions they discover in the RFP.

17. Sometimes buying organisationsmight reimburse proposers for participating in large RFP/RFTs. Usually however the cost of submitting proposals is borne by the proposer and this clause creates this clarity.

18. Observing confidentiality during aRFP is essential. Depending on the level of security and confidentiality required, a separate confidentiality agreement with proposers may be required before issuing an RFP. You should obtain advice on this matter if unsure.

19. This clause is needed to ensureProposers can’t profit or gain from obvious errors and problems they encounter in RFP documents. The RFP process allows for due consideration of these problems and, if needed, addenda to be issued and extra time provided to respond.


1. 20 Proposal acknowledgementBy participating in this RFP Proposers are indicating their acceptance to be bound by conditions set out in this Part. Proposers’ are to acknowledge this acceptance, and furnish details of their representative that will be the sole point of contact for all matters relating to the RFP, in writing, to the Company prior to the proposal acknowledgement due date set out in Clause 1. 4.

Any Proposer choosing to not submit a Proposal is required to acknowledge this intent, in writing, to the Company and return all RFP documentation to the Company prior to the proposal acknowledgement due date.

1. 21 Return of RFP documentsProposers must return to the Company all issued hard copies of the RFP documents within seven (7) days of being notified that their Proposal was unsuccessful. Unsuccessful Proposers are to also permanently delete any electronic copies of RFP documents (either issued by the Company or created by the Proposer).

20. Proposers receiving RFP documentsmust make a positive election as to whether they intend to submit a proposal or not. If they do then they are required to agree with these proposal conditions. Sometimes buying organisations create separate forms that Proposers are required to submit in this regard.

Like the Company representative role, good practice requires that Proposers also nominate a focal point for all correspondence/queries.

21. This is good housekeeping andconsistent with confidentiality obligations.


2. The RequirementThis part of the RFP is really the engine of the whole document. The purpose of this section is for the buying organisation to describe what is required. There is no one way to do this, but a well described requirement (sometimes also referred to as a scope of work or specification) is essential to receive quality proposals and form effective contracts. The last thing the buying organisation needs is potential suppliers having to make many assumptions or guess what is required when they put proposals together. When requirements are vague suppliers may not bid or, if they do, their prices may also increase to reflect the additional risk they may perceive is present. Invariably contracts formed on the basis of poor requirements end up with extensive revision, renegotiation and difficulty.

So how do you describe what you want? When drafting requirements the following concepts are usually addressed:

a) Background and context for the requirement

b)

. It is very useful for the potential supplier tounderstand the need or reason for the requirement. Any issues, unique attributes and othermatters you think a potential supplier would need to know about the organisational climate,culture etc to perform the requirement should be included.

Organisation overview, including contact details

c)

. Who is involved in the requirement? Whospecifically are the customers of the requirement? Who will be the principle point of contact inthe buying organisation?

Detailed description of the requirement

d) Detailing a requirement can be quite involved and may also need additional informationappended to the RFP to properly identify all requirement details (drawings, schedules, etc).

. There are a number of recognised ways of describingwhat is required. Sometimes the requirement needs to be very technical and prescriptive –setting out exact obligations like weights, sizes, colours and distances. In other situations(usually the case for an RFP rather than RFT) the requirement can be more functional orperformance-based and describe the expected outcomes or the problem that needs to besolved. Another way of thinking about a functional or performance requirement is that itdescribes outputs and expectations (eg flow rates, durability, reliability, target speeds, permittedvariability) rather than inputs. Another type of requirement is to reference a known acceptableexample - perhaps an existing product or service.

e) Irrespective of the form a requirement statement takes, it needs to very clearly set out thedeliverables (quantities, due dates/duration etc). The supplier must be in no doubt as to what itmust provide; this clarity is especially important as payment will usually to be connected to thedeliverables.

f) Quality Requirements/Performance Standards. This section is included to demonstrate theminimum acceptable standard and basic acceptance criteria for supplying the required


goods/services. This may therefore include references to applicable AS/NZ/ISO standards and any applicable internal standards, policies or procedures of the buying organisation (that may then need to be appended to the RFP). Perhaps there are industry association standards or guidelines that may apply as well. This section might also include proposed performance measures or Key Performance Indicators and targets, although these are sometimes reflected in the commercial terms rather than the Requirement part of the RFP.

g) Approvals

h)

. Are there any internal or external approvals or permits required before the requirement can be undertaken? If so, they should be described, along with clarity about whether the supplier, the buying organisation or a third party is responsible for obtaining the approval.

Boundaries and Exclusions. It is really important to also describe what the requirement boundaries are and, in particular, what items are not

i)

included in the scope. Sometimes it is useful to delineate in a tabular form what the buying organisation (or other third parties) will do and what the supplier is expected to do to illustrate these limits.

Buying Organisation inputs.

This Part of the Proposal document is intended to form part of the final Contract.

Will the buying organisation be providing any services or materials in support of the requirement (eg office space, materials, computers, etc)? This helps the supplier better identify what will be available and therefore does need not be provided and priced.


3. Information to be provided by ProposersThis section of the RFP sets out what information the buying organisation wants to receive from potential suppliers. Much of the information provided in response to this section will form part of the final contact -so ordinarily the information requirements are prepared at the same time as the requirement. An excellent RFP drafting principle is to keep all the “response” obligations in the one place – this way the potential supplier does not need to search through the whole RFP to work out what questions need to be answered or information is to be provided. The buying organisation can also be more directive in how it wants to receive the information (eg in particular formats to help comparisons). Both of these factors help reduce the overall time and cost burden of issuing and responding to RFPs.

Information to be provided by potential suppliers tends to fall into three basic groups:

(1) Pricing information.

(2) Other non-price commercial information.

(3) Technical information.

3.1 Pricing Information This section is used to collect rates and prices from the Proposers. Exactly how the buying organisation chooses to receive prices will be a function of the Requirement, the way in which rates and prices for goods and services are usually expressed by potential suppliers and how the buying organisation chooses to present the pricing information for evaluation purposes.

As outlined in the RFP template, the following clauses should also be included in this section to help inform the submission of pricing details:

Prices include all costs Submitted rates and prices are to deemed include all costs, insurances, taxes, fees, expenses, liabilities, obligations risk and other things necessary for the performance of the requirement. Any charge not stated in the Proposal as being additional, will not be allowed as a charge against any transaction under any resultant Contract.

You need confidence that, as part of informing itself, the Proposer has factored everything it reasonably should have into its rates and prices. This is very important because the proposed rates and prices of the winning Proposal are transferred to the final Contract and, as such, need to be robust or you will be constantly challenged for price variations!


Goods and Services Tax (GST) Proposal rates and prices shall be exclusive of Australian GST.

Currency of proposed rates and prices Unless otherwise indicated, all rates and prices submitted by Proposers shall be in Australian currency.

3.2 Non-Price Commercial Information There are usually a number of commercial inputs from the Proposers that need to be assessed and, as required, incorporated into any final Contract. Exact information requested from Proposers will be tailored to suit the specifics of the requirement, but may include:

a) Form of Proposal – Company details, contact information etc (sometimes the requiredinformation can pre-formatted by the buying organisation).

b) Financial Information – to demonstrate robust organisational performance and stability.

c) History and previous job performance, including details of reference clients.

d) Details of held insurances.

e) Compliance with proposed Contract T&Cs (often presented in a standard clarification register).

Lots of confusion can prevail unless the GST status of pricing is made clear. The Contract will typically describe how GST, payments, invoicing etc is to be treated so the primary aim here is to make sure all Proposers price on the same basis.

This clause is self evident but needed for clarity purposes. Obviously you can change the currency or allow multiple currencies if required, but remember to be very clear about this in the rates and prices tables where numbers are collected!


3.3 Technical Information Technical information to be provided by the potential suppliers should directly reflect the nature of the requirement and provide information necessary to satisfy the buying organisation that the potential suppliers can deliver the intended Requirement. Typical technical information sought in Proposals includes:

a) Execution Plans and key dates (ie how is the Requirement going to be performed, and by when).You may need to consider things like proposed facilities, systems / IT, planning and reportingprocesses.

b) Details of resources and key personnel performing the requirement (ie the quality and

c) Proposed sub-contractors or outsourcing of any part of the Requirement.

quantity of resourcing to perform the requirement – people, materials, equipment). This may includeposition descriptions, CVs, organisation diagrams.

d) Quality management plans.

e) Health and Safety management plans.

f) Environment and Sustainability management plans.

g) Employee Relations/Industrial Relations management plans.

h) Other management plans and administrative arrangements.

i) Risk Management plans and mitigation approaches.

j) Transition/Implementation plans.

k) Any proposed Alternatives.


4. Proposed ContractRather than restating the proposed commercial terms in the body of the RFP, a good practice is to append a blank proposed contract to the RFP. In this way the potential suppliers can see what the contract will look like and be better placed to comment on the proposed terms and conditions. CIPS Australia has prepared a generic contract that could be used for this purpose.

request for proposal (rfp) guidance notes

Documents