Before signing a contract
This checklist is for the contract manager and project manager of a public body after the award and before signature. Each item is something that is hard to add later.
Note This page describes features and common practice; it is not legal advice. Have the contract reviewed by your legal counsel.
Contents
- Scope and versions
- Ownership and source
- Service and support
- Security, privacy and accessibility
- People and knowledge
- Exit
Scope and versions
- To do: The deliverables match the tender requirements, each with an acceptance test.
- To do: The Exponential version to be delivered is named (a 6.0.x release tag), with the extensions and their versions (Release policy and version numbers).
- To do: The supplier keeps the site on a supported version for the term (Supported versions).
- To do: Platform responsibilities (PHP, database, operating system) assigned (PHP and platform support).
Ownership and source
- To do: Custom extensions, designs and settings are delivered as source into a repository you control (Develop with Git).
- To do: Custom code that extends Exponential is under the GPL version 2 or later when it is distributed to you, and you receive its source (Licensing questions).
- To do: No changes to kernel files; customization in extensions and overrides, so upgrades stay possible (The upgrade check).
- To do: Third-party components and their licenses listed.
Service and support
- To do: Service levels with your own figures: availability, response per severity, RPO and RTO, maintenance windows (SLA options for Exponential hosting). The project publishes no SLA.
- To do: How service levels are measured and reported.
- To do: Time to apply released security fixes (Security updates and patching cadence).
- To do: Routine updates included, or priced (Planning upgrades in the budget).
- To do: Escalation path and named contacts.
Security, privacy and accessibility
- To do: Processing agreement signed with each processor; data location stated.
- To do: Hardening baseline agreed (Security checklist).
- To do: Incident notification duty and time agreed (Incident readiness).
- To do: Accessibility target for the public site, with who tests and who fixes (Accessibility checklist).
- To do: No production personal data in development or training copies.
People and knowledge
- To do: Training sessions, participants and material rights defined (Buying training from a partner).
- To do: Documentation to be delivered: content model, roles, settings, deployment, runbooks.
- To do: Administrator accounts for named staff of your organization from day one.
Exit
- To do: Exit plan annexed: export formats, handover period, cooperation with a successor (Exit plans).
- To do: Keys and secrets handed over at exit: audit signing keys, mail preferences secret, TLS keys (Backups: keys and secrets).
- To do: Return and deletion of data by the supplier at the end, with confirmation.
- To do: Exit readiness checklist added to the contract file.
Related pages
- Government checklists
- Before a tender
- Tender templates
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.