Sovereign cloud RFP template

Write an evidence-based sovereign cloud RFP with an editable scoring matrix, clear exclusion gates and practical supplier evaluation steps.

Last updated

In short

  • A location claim needs a data-flow register covering backups, logs and support access.
  • Mandatory requirements should be evaluated before weighted preferences.
  • Compare full service scope and exit evidence, not a country label alone.
On this page (6)

Procurement and evaluation · Part of Procurement

Mandatory gates, weights, supplier responses, evidence references and evaluation fields.

Download the sovereign-cloud RFP worksheet

Ask for an operating arrangement you can verify

A useful sovereign cloud RFP defines which organization controls the service, where each copy of data goes, who can administer it and how the buyer can leave. “Hosted in Switzerland” answers only one part of that decision. A supplier can provide a suitable infrastructure region while relying on other organizations for support, identity, monitoring or recovery.

Start with the workload: named applications, user groups, external integrations, data sensitivity, hours of operation and recovery needs. Then translate the consequences of failure into requirements. A departmental wiki and an emergency coordination service should not receive the same availability, staffing or recovery demands merely because both contain confidential information.

The downloadable matrix is a starting structure, not a legal specification or a record of an evaluated supplier. Its example rows describe evidence to request. They contain no invented supplier scores.

Separate exclusion gates from preferences

Decision Example buyer requirement Evidence to request Evaluation consequence
Mandatory location Listed data classes must remain in approved locations Contract schedule and service data-flow diagram Reject or obtain an approved exception if unresolved
Mandatory access Departing users must lose access through the chosen identity process Observed revocation exercise and residual session inventory Do not compensate for failure with a lower price
Recovery objective A named workflow must recover within the agreed time and data-loss limits Restore procedure and recorded exercise Evaluate against the workflow, not backup-job status
Preference Additional deployment regions may be useful later Available service scope and commercial terms Award weighted points only after mandatory gates pass
Exit Buyer can retrieve usable records and attachments Sample export with independent read-back Identify rebuild work and responsibilities

A useful scoring scale is zero for absent evidence, one for an unsupported assertion, two for incomplete evidence, three for evidence covering the requirement, and four for a demonstration against the buyer’s sample. These are proposed evaluation rules. Agree them internally before bids arrive and use the same rules for every supplier.

Build the evidence packet

Request five linked documents: service architecture, data-location register, responsibility matrix, recovery plan and exit plan. Each should identify its version and owner. A marketing statement should point to a contractual commitment where the buyer needs one; a technical diagram should point to the procedure that keeps it accurate after changes.

Pilae’s residency description is one supplier’s starting point. Use the same questions with a hyperscaler, a regional infrastructure provider, another managed operator or your internal platform team. Compare the actual offered service, because infrastructure alone does not include application administration.

For personal-data processing, relevant requirements may include processor terms and international transfers. The GDPR text, including Articles 28 and 44 onward, is a primary reference where that regulation applies. Have the buyer’s legal or privacy owner decide applicability and suitable wording. This worksheet neither certifies compliance nor turns a storage location into a legal conclusion.

A worked scoring example

Suppose recovery has weight 20 and receives score 3 out of 4 after the supplier provides the requested evidence. Its contribution is 20 × 3 / 4 = 15. A location gate with no signed answer remains unresolved even if the weighted total is high. Record the missing evidence, deadline and person empowered to accept an exception.

Do not award four points because a sales demonstration was smooth. The demonstration should use an agreed test: restore a restricted workspace, verify file counts, confirm an unauthorized account cannot enter, and obtain approval from the business owner. The example describes a proposed acceptance exercise; it is not a result achieved by any supplier.

Compare the whole cost and responsibility

Ask suppliers to separate onboarding, migration, recurring operations, infrastructure, application licences, support options and exit assistance. Include retained subscriptions and the buyer’s ongoing administration. Value staff time separately from cash invoices so a capacity benefit is not presented as a guaranteed budget reduction.

Pilae’s responsibility model helps identify which duties need explicit allocation. Your final agreement should name the owner of identity membership, plugin changes, retention, incident decisions and business acceptance. “Managed” without this allocation leaves gaps precisely when a change or outage crosses suppliers.

Run the evaluation in stages

Send written questions first, shortlist on mandatory evidence, then run the same focused workshop with remaining candidates. Give evaluators independent scores before discussing a group result. Preserve the version of each answer used for the award decision and log any later clarification.

Before signature, resolve exceptions into contract language, a dated implementation action or an explicit risk acceptance. After onboarding, repeat the critical demonstrations against the deployed service. The RFP is useful only if the requirements survive the handover into operations.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Review our requirements

Bring your mandatory requirements and supplier evidence gaps to a scoped procurement review.