GUIDE · MANAGED SERVICES

Request for proposal (RFP) for IT services: how to write one

By the end of this guide you will know how to prepare a clear, comparable request for proposal for IT services. You will see what information to include, how to structure the document, how to define evaluation criteria, and how to stop suppliers' responses from being impossible to compare.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. What a request for proposal is and when you need one

RFP stands for request for proposal. It is the document with which a company describes its need and invites several suppliers to respond with a structured proposal. It is neither a contract nor a final specification: its purpose is to make proposals comparable that would otherwise be written in different languages. The main advantage is that the comparison takes place on the same elements, and not on each supplier's ability to present itself well.

It is worth writing one when the value of the service is significant, when the choice is difficult to reverse, or when you need to justify the decision internally. For a simple job, a short email request may be enough. For a managed service that touches systems and data, a structured document avoids many surprises at the point of signing. For the supplier too, a clear document reduces the time lost on later clarifications.

2. Before writing: clarify objectives and constraints

The most common mistake is to write the request before deciding what matters. Define the objectives: continuity, predictable cost, greater control, a single point of contact, stronger security, or a mix. Then list the non-negotiable constraints, such as data confidentiality, the sites served, working hours or the regulatory obligations you must meet. Also define who in the company approves the objectives, because the request must reflect a shared decision.

Try also to understand the current situation: which systems exist, which recurring problems there are, and which activities already carried out internally will remain in-house. This information belongs in the document, because without it suppliers respond with standard proposals that ignore your reality. A short description of the organisation, with the main roles, also helps the supplier understand the context.

3. Structure of the document

A good request has a predictable structure, so that every supplier responds in the same order. This is a structure that works in most cases and can be adapted to your company. Keep it lean: a longer document is not a clearer one. Every section should help the supplier respond precisely. It is worth doing the preparation calmly, because a clear structure saves everyone time.

Do not ask suppliers to fill in a generic form. Give them a response outline that indicates the order and the expected content, so the comparison becomes quick and fair. Explicitly ask them to flag the exclusions and assumptions they have made, because these are where offers differ most. Every declared exclusion is useful information, even when it is unwelcome.

  1. Presentation of the company and its context, in a few lines
  2. Objectives and the problems the service must solve
  3. Scope: systems, sites, users and activities covered
  4. Service requirements, with priorities and how they will be measured
  5. Security, confidentiality and data handling requirements
  6. Required commercial model and the format of the price proposal
  7. Evaluation criteria and their weighting
  8. Timetable, how questions may be submitted and deadlines for submitting offers

4. Requirements and scope: writing verifiable statements

Requirements must be verifiable. Phrases such as high-quality support or adequate security do not allow anyone to respond usefully. Instead, write what is needed in concrete terms: which systems to monitor, which backups to run, how often, which restores to test, and at what times the supplier must guarantee taking charge. Every requirement should have a simple way to verify compliance over time.

For scope, list what is included and ask suppliers to state explicitly what they exclude. A document that only asks them to confirm the scope produces responses that are identical in form and different in substance. Include the typical scenarios of your company as well, so the proposal shows how they would be handled in practice. Ask the proposal to explain how these scenarios would play out, step by step.

5. Evaluation criteria and weightings

Declare the evaluation criteria before receiving the offers, with the relative weight of each. This prevents choosing a preferred supplier after the fact and makes the decision explainable. Typical criteria are the quality of the technical proposal, experience with similar systems, the service model, contractual clarity and the total cost. You do not need a complex score: a simple scale, declared in advance, is enough.

  • Suitability of the technical proposal to your scenario
  • Experience with systems and sectors close to yours
  • Clarity of scope and exclusions
  • Governance model, reporting and contacts
  • Estimated total cost, with ancillary items made explicit
  • Exit conditions and return of data

6. Questions and communication during the tender

Provide a period during which suppliers can ask questions in writing. Answers should be sent to everyone, so that all start from the same information. Avoid private meetings with a single candidate about the content of the request: they distort the comparison and can create unfair advantages. If an answer changes the document, communicate it formally to all participants. This also applies to clarification requests that arrive late.

Set a deadline for questions and another for offers, with a single point of contact. This reduces the risk of misunderstanding and makes the process more orderly, even when little time is available. Keep track of communications, because the choice will need to be justified. A complete record protects both the company and the suppliers who took part in good faith.

7. How to compare the responses

Compare the offers on a grid that is the same for everyone: for each criterion, note what each supplier proposed, with any exclusions and assumptions. A comparison based on impressions or on memories of the presentation leads to decisions that are hard to justify. Evaluators should work independently before discussing together. Only then do the real differences emerge, rather than getting lost in collective discussion.

Verify the responses with targeted questions and, where possible, with a technical meeting. Ask to see an example report, to explain a managed incident, and to describe how the exit would work. Concrete answers are worth more than many pages of proposal. Only after this verification is it worth discussing cost in detail. At that point, the price becomes an element of comparison between proposals already assessed on their merits.

8. How to get started

The first step this week is to write a single page with the objectives, the systems involved, the constraints and the evaluation criteria you consider essential. You do not yet need the full document: what you need is to clarify what you want to achieve. Share it with the person in the company who is accountable for risk and with those who use the systems every day. A long meeting is not needed: a few short sessions are enough to align objectives and constraints.

Then use the structure of this guide to complete the request, and have an adviser review the contractual and data protection parts. Send it only once the first-page summary is agreed internally. A clear request shortens the comparison time and makes the choice safer. Remember to keep all the documentation produced during the process, as it will also be useful at renewal.

Frequently Asked Questions

Is an RFP mandatory for awarding an IT service?

Not in general. It depends on your organisation's internal rules, the type of body you are and the value of the award. Even where it is not mandatory, a structured request is good practice, because it makes the choice comparable and documented. For regulatory or tender questions, confirm with your adviser.

How many suppliers should I invite?

Enough to have a genuine comparison, but not so many that the evaluation becomes superficial. A small group of credible candidates is usually more useful than a long list of unsuitable suppliers. First check that each candidate can cover the scope you require.

Can I ask for a demo or a technical meeting?

Yes, and it is often useful. A technical meeting with the person who would handle your case shows more than any sales presentation. Arrange it on the same terms for all candidates, and prepare questions based on the scenario in your request, so that you can compare similar answers with each other.

What should I include on security and data protection?

Describe the data processed, the systems involved, the confidentiality requirements and the technical and organisational measures you require. Ask suppliers to state where data is held, which subprocessors handle it and how access is managed. Requests concerning regulatory obligations should be verified with an adviser, not taken for granted.

Can an offer be excluded if information is missing?

Yes, if the information requested is essential and the document clearly provides for it. In many cases, however, it is better to ask for clarification before excluding an offer, because missing information may stem from an unclear question. State in the request how incomplete proposals will be treated, so the criterion is known to everyone.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →