Care runs around the clock. Does your IT contract?

Start with the care tasks the contract supports

Care Circle recommends mapping a small number of essential tasks before comparing packages: opening the current care plan, recording a visit, checking authorised medication information, contacting the on-call lead and retrieving the documents needed for a transfer. For each task, name the people affected by delay and the safe alternative agreed by the service. This is a decision tool, not a new regulatory checklist.

An equipment list rarely explains those relationships. A tablet can be functioning while staff cannot log in; a records platform can be available while the local network fails. Ask who owns diagnosis across those boundaries. The useful supplier conversation follows the whole task, including staff devices and access, rather than ending at the component the supplier happens to sell.

Separate acknowledgement from restoration

A quick reply may reassure a manager without returning a service to use. Set out what the supplier promises to acknowledge, investigate, escalate and restore. The promises need to match the actual agreement, including exclusions and dependencies. Care Circle suggests using one realistic example, such as loss of authorised records access during an evening shift, to test everyone’s understanding before signature.

Do not invent a universal restoration target for every care setting. The provider should determine tolerable disruption through its own risk assessment and care arrangements, then compare that need with available support. Record any gap explicitly. A cheaper package can still be appropriate where a tested alternative exists; a premium package can still leave an important third-party dependency unowned.

Price the service the team will actually use

Build an illustrative annual comparison using the provider’s own expected support demand. Include routine fees, onboarding, device changes, additional visits, after-hours work and the staff time required to raise and follow tickets. Label assumptions clearly. This calculation does not predict incidents or promise savings; it shows which commercial choices would materially change the bill.

Ask finance and operational colleagues to review the same comparison. Finance may notice an automatic renewal while the registered manager notices a weekend escalation gap. Neither issue is solved by a supplier brochure. Preserve the agreed answer alongside the contract, and name the person who will check usage and charges after the first billing period. Unclear inclusions should become written questions before purchase.

Make access and responsibility visible

NHS England’s supplier charter identifies supported systems, MFA, monitoring and tested recovery among its expectations. Its list is based on declarations, not certification. For a care provider, those themes can inform questions without implying that charter participation is compulsory for every supplier or that listing proves the provider’s own configuration is secure.

Care Circle’s proposed access register records the business purpose, approving manager, method of access and review date for privileged supplier access. Ask for a demonstration of how access is granted and withdrawn, using a test account where possible. The contract owner needs to know who is responsible when a technician leaves the supplier, when the provider changes systems and when emergency support is requested.

Use the first quarter to establish evidence

Agree a short review after onboarding, then compare actual tickets with the expectations used to select the service. Examine repeated causes, hand-offs, communication quality and unresolved risks. A rising ticket count is not automatically poor performance: staff may have found an easier reporting route. The question is whether essential work is becoming more dependable and colleagues understand how to obtain help.

NHS England and DHSC’s January 2026 supply-chain letter describes proportionate engagement with suppliers, rather than a pass/fail audit. A provider can use the same practical principle: request evidence relevant to the service, avoid repetitive generic questionnaires, record the gaps and agree named remediation. The goal is a dependable relationship that can be reviewed, challenged and changed without losing care continuity.

The ticket record can reveal a contractual gap without requiring a technical audit. Follow one resolved ticket and ask who first received it, how many teams handled it and whether the agreed communication reached the shift lead. Compare that sequence with the support arrangement. Where the provider itself caused a delay, include that openly in the review. A fair account helps both parties improve the hand-off and prevents a service credit from becoming the only measure of success.