RFP Design step 1 – The Background

Over the next few weeks I will provide a breakdown on the process to drafting an RFP,  this first blog will cover “Background”, after I have gone through the RFP documentation I will continue through the submissions, up to contract administration.
The Background section puts the whole project in context.  It helps the Tenderers  (parties tendering their proposals) to get a “handle” on what the company does, how it does it and why this RFP was drafted.

Some points normally covered under Background include:

1.    Company – the size of the company, the products/services it provides and how it provides these products services to the market and possibly who its customers are.  It may also be relevant to include whether the company operates from multiple sites.  Think of this as a “marketing spiel”.

2.    Department – which department, Branch, division,  the winning Tenderer will be working with.

3.    Explain what product/service will be required from the Tenderer at a high level – more detail will be given further into the document.

4.    Describe how this process fits in with the overall goal of the company/Department, this can also be considered as the reason the RFP has been drafted.  This will give the Tenderer a reason why THEY are important to the process.

5.    Access to public information also allows the Tenderer to source further information that may help with their proposal.  Providing the company’s URL or others pertaining to your particular industry is an obvious option and gives them an opportunity to provide further information/services that were not requested but just might add value to the arrangement.

6.    Provide information on other aspects you consider important but not critical, for example: by stating that you are an environmentally and humanitarian conscious company may solicit comparative information from the Tenderers.

7.    Other items as you deem appropriate.

Good Procedures – a business requirement.

Procedures can be formal or informal, simple or complex but whichever you use they are there to minimise the guesswork and irregularity in the business.  The format of which should be standard throughout the company as far as possible (there are many templates on the web to build from), they should also be effective and efficient! I have worked with companies that are overburdened with procedures and those that literally rely on the information and experience of individuals.

Overburdensome procedures take away the ability to move quickly, to adapt to change before competitors.  This scenario is usually found in larger organisations (& Government) and colloquially called “bureaucracy”.

Whereas a lack of documented procedures can often facilitate a faster response, the problem that lies herein is that the improvements and changes are again not documented.  Thus there is confusion over the “correct” procedure to follow.  Plus, as is often the case without procedures, results and KPIs are not accurate and may even be guesses, if they are presented at all.

Either way, change is required with benefits found in both scenarios. Redesigning procedures can be seen as being easier due to the fact that they have already been written and only need “tweaking”, while in other situations documenting procedures from scratch can also be seen as being easier as there is a clean slate to work with.

The issue here is often not the need to redesign or design procedures; it is the perception of change. There are companies that state they are looking for change, to make the improvements they know they need to take their company to the next level. I just wonder how many people have found a company’s statements on change are not always congruent with their actions.

Some companies I have worked with see change as part of their business, continual improvement itself being a process that happens everyday. These are the companies that have realised change can bring a level of uncertainty or a period of moving backwards before improvement (but careful planning and testing will reduce any negative effect).  Yet there are others that talk about change but can only manage partial implementation, sometimes abandoning improvements that have been made. I have found there is also a correlation to particular industries as well.

I would welcome comments on companies that have good procedures and how they design/change them.

Next instalment – Failure to change