Sector pursuit field 26 · Technology and digital
Our basic working position: This is the first position we would test—not the final bid position. It changes with every buyer organisation, procurement or commercial team, evaluator group, operational user, budget owner and other stakeholder. The live opportunity, people, documents, conversations and clarifications determine the final pursuit.
Public and private contract pursuit
Same capability. Different buying system.
A it managed services pitch cannot be carried unchanged from a published public competition into a private sourcing decision. The solution may be similar, but authority, visibility, negotiation, risk appetite and the people shaping the decision can be very different.
Follow the declared route—and the decision behind it.
Buyer settings evidenced in the sector dossier: central government departments and arm’s-length bodies; local authorities, regulators and public corporations; schools, academies, colleges and universities.
Start with the live notice, conditions, evaluation model, timetable, clarification rules and contract.
- Separate continuous service operation from projects, licences, consumption and product supply.
- Define the retained authority before assigning supplier responsibility.
Find the real buying group and approval path.
Enterprises use managed-service RFPs, outsourcing renewals, co-sourcing, service towers and transition agreements.
- Establish who initiated the purchase, who owns the budget, who can veto it and how procurement, legal and finance will shape the agreement.
- Test incumbent relationships, negotiation room, approval gates, commercial risk and the evidence each decision-maker needs.
- Use conversations lawfully available in the process to refine the proposition; do not assume a private RFP reveals every deciding factor.
The “buyer” is rarely one person.
Map the CIO, service owners, architecture, cyber, procurement, finance, users and incumbent suppliers.
Sector roles to test: users and accessibility representatives; business service and product owners; retained technology and security leaders; service desk, engineering and architecture teams; incumbent, platform and application suppliers.
The bidder is ready; the response needs precision.
Use focused writing when the it managed services offer, price, delivery model, responsibilities and approved evidence already withstand challenge. We then align them to the question, stakeholder, evaluation logic and response architecture without pretending prose can repair the underlying business.
Strengthen the bidder, then build the bid.
Use end-to-end management when qualification, solution design, process, team, partners, evidence, commercial logic or mobilisation still needs work. The pursuit becomes a project: gaps are exposed, capability is implemented, owners decide and the written answer grows from a stronger operating position.
Candidate lifecycle movements: Shape → Design → Prove → Deliver. Useful operating lenses to test include Zanshin (sustained operational attention), independent review and handover readiness. They are selected proportionately; they are not certification claims or a substitute for the live contract.
Explore Achmed Esser's Assurance & Delivery Lattice →Relevant practice here can include capture strategy, compliance matrices, solution and pricing alignment, colour-team reviews and implementation transition. We apply the parts that fit the pursuit rather than forcing every competition through one template.
See APMP's winning-business lifecycle →Managed IT scope ranges from partner role to infrastructure operation
Evidence-linked insight · What this changes Alpha Academies Trust described a provider acting as its primary ICT partner because it has no internal ICT resource, including service desk, onsite support, networks, cyber, licensing, assets and strategy. Co-Ownership sought managed IaaS, backup and disaster recovery around the clock. Pool Re and CQC records show further award and pipeline shapes. [ 010, 011, 012, 013 ]
Where we would start first Disaggregate the requirement into services, sites, users, assets, hours, retained buyer functions, suppliers and outcomes. Confirm which party owns architecture, policy, operational decisions, budgets and risk acceptance. Do not use the phrase fully managed as a substitute for a responsibility matrix or assume one buyer's service tower applies elsewhere. [ 010, 011, 012, 013 ]
Government technology guidance has stated scope
Evidence-linked insight · What this changes The Technology Code of Practice, Service Standard and Digital, Data and Technology Playbook provide useful public-sector context. The Playbook is mandatory on a comply-or-explain basis for central government departments and arm's-length bodies and is to be considered by the wider public sector. That distinction prevents indiscriminate claims of universal mandate. [ 003, 004, 007 ]
Where we would start first Identify which policies the target authority says apply and at what approval stage. Convert relevant principles into traceable solution decisions such as interoperability, sustainability, security, reuse, lifecycle and exit. Record deviations and buyer approvals. Do not insert government language that the bidder's architecture or service model cannot evidence. [ 003, 004, 007 ]
Route-to-market evidence needs current verification
Evidence-linked insight · What this changes The Procurement Act and Regulations frame covered procurements, while Technology Services 4 provides an official technology-services agreement with its own lots and call-off mechanics. A pipeline notice signals potential future activity; a framework position only enables routes stated in the agreement. Neither guarantees work or revenue. [ 001, 002, 008, 013 ]
Where we would start first Confirm authority, jurisdiction, estimated value, procedure, lot, eligibility, call-off method, timetable and latest notice. Separate open opportunity from pipeline and award. Check that the contracting entity, subcontractors and proposed services satisfy every participation condition. Model pursuit cost without treating ceilings or pipeline values as forecast sales. [ 001, 002, 008, 013 ]
Outsourcing does not remove the buyer's need to govern technology
Evidence-linked insight · What this changes Even a supplier acting as primary ICT partner cannot responsibly own the authority's statutory accountability, business priorities or every risk decision. Alpha's no-internal-resource context increases the need to define informed buyer authority. Co-Ownership's provider is described as an extension of an internal team, demonstrating a different retained model. [ 011, 012 ]
Where we would start first Create a RACI covering policy, architecture, security risk, budget, change approval, incident decisions, suppliers, data, continuity and acceptance. Identify minimum retained capability and meeting cadence. State which recommendations need buyer approval. Avoid designs that make the authority unable to challenge performance, transition supplier or exercise contractual rights. [ 003, 004, 007, 011, 012 ]
A bid needs an evidence-backed starting estate
Evidence-linked insight · What this changes Service levels, staffing and price depend on users, devices, applications, networks, infrastructure, sites, tickets, support hours, technical debt, contracts and asset condition. Tender summaries rarely provide a complete baseline. Unrecorded shadow systems and aged hardware commonly emerge only after award, turning assumptions into transition disputes. [ 011, 012 ]
Where we would start first Build a baseline register with source, date, confidence and owner for every sizing driver. Reconcile asset and configuration data with ticket history, monitoring and stakeholder interviews where allowed. Make discovery deliverables, materiality thresholds and change-control consequences explicit. Do not convert missing buyer data into a precise fixed-volume promise. [ 003, 004, 007, 011, 012 ]
Service desk design requires demand and user context
Evidence-linked insight · What this changes Alpha specified minimum operating hours and tiered technical support, but another authority may need twenty-four-hour critical cover, multilingual service or different channels. Ticket counts alone do not show complexity, avoidable demand, user impact or the proportion resolved at first contact. Onsite and remote support interact with geography and digital confidence. [ 011 ]
Where we would start first Model contacts by time, channel, priority, location and skill, then translate demand into shifts, queues, escalation and field coverage. Define identity checks, accessibility, major-incident routing and user communication. State automation boundaries and human fallback. Evidence resolution quality rather than promising a headline answer speed unsupported by capacity. [ 003, 004, 011 ]
A service level must define the clock and consequence
Evidence-linked insight · What this changes Availability, response and resolution figures are meaningless without service hours, start event, pause rules, priority definition, exclusions, measurement source and dependency treatment. Composite monthly percentages can hide severe user harm. Service credits are a contractual remedy, not evidence that service outcomes or resilience have been achieved. [ 005, 006, 011, 012 ]
Where we would start first Create a service-measure dictionary and scenario-test it against the architecture and staffing model. Balance operational indicators with user experience, recurrence and business impact. Define root-cause and improvement routes. Reconcile all targets to the pricing case and resist unqualified commitments to components controlled by the buyer or another supplier. [ 005, 006, 007, 011, 012 ]
Incident management needs authority before urgency
Evidence-linked insight · What this changes Managed providers detect, triage, communicate and coordinate incidents, but decisions about business continuity, data disclosure, shutdown, recovery priorities or public communication may remain with named buyer roles. Multi-supplier environments introduce hand-off risk. Fast response language cannot replace a tested incident-command model. [ 009, 011, 012 ]
Where we would start first Define severity by business consequence, then specify detection source, commander, technical leads, buyer authority, communications, evidence capture, escalation, recovery acceptance and post-incident learning. Test the plan with credible scenarios. Distinguish service incidents, security incidents, problems and requests so reporting and contractual clocks remain coherent. [ 005, 009, 011, 012 ]
Problem and change control protect long-term service quality
Evidence-linked insight · What this changes Clearing tickets quickly can mask recurring faults, while unmanaged change creates instability. Managed services often span buyer projects, vendor releases, emergency fixes and strategic transformation. Without one change calendar and configuration source, different suppliers can each meet local targets while degrading the end-to-end service. [ 003, 004, 007, 011 ]
Where we would start first Specify problem thresholds, root-cause ownership, known-error control, change categories, approval levels, testing, rollback and review. Connect authorised change to configuration and knowledge records. Price routine and project change distinctly. Show how urgent action remains governed and how benefits or adverse effects are measured after implementation. [ 005, 006, 007 ]
Asset management joins finance, security and support
Evidence-linked insight · What this changes Alpha's notice includes hardware refresh, software licences and asset management. Accurate lifecycle records determine supportability, vulnerability, warranty, cost and disposal. A device inventory without ownership, location, user, configuration, purchase, support and disposal status cannot underpin refresh forecasts or secure service. [ 003, 011 ]
Where we would start first Define the authoritative asset and configuration model, discovery method, reconciliation frequency, custody events and evidence for disposal. Allocate responsibility for buyer, supplier and third-party assets. Link refresh plans to business criticality, supported life and budget. Avoid promising inventory accuracy before initial discovery and acceptance have been completed. [ 003, 004, 011 ]
Licence management must follow use and contract rights
Evidence-linked insight · What this changes Subscriptions and software licences can be user-, device-, capacity- or consumption-based, with complex transfer and audit conditions. Overbuying wastes money; under-licensing creates legal and operational exposure. A managed-service fee may or may not include licences, cloud consumption, vendor support and price changes. [ 011, 012 ]
Where we would start first Build a licence entitlement and consumption register with renewal dates, metrics, owners and contractual constraints. Separate pass-through costs from managed effort, define optimisation authority and preserve buyer visibility. State currency, indexation and vendor-change assumptions. Never imply that technical access gives a supplier the right to reallocate every licence. [ 005, 006, 007, 011 ]
Managed infrastructure needs a shared-responsibility design
Evidence-linked insight · What this changes Co-Ownership's requirement includes hosting, operating, securing, monitoring and supporting IaaS with backup and disaster recovery. Even where a managed provider operates these layers, platform vendors, connectivity providers and the customer retain specific responsibilities. Marketing labels do not describe who configures identity, encryption, recovery or monitoring. [ 012 ]
Where we would start first Map responsibility by service and control, including tenant, platform, operating system, network, data, keys, logging, patching, backup and recovery. Verify vendor dependencies and support routes. Design monitoring around business services, not only resource health. Reconcile capacity and consumption assumptions to the cost model. [ 003, 004, 007, 009, 012 ]
Backup is not demonstrated recovery
Evidence-linked insight · What this changes A successful backup job confirms only a limited technical event. Resilience depends on scope, immutability, separation, retention, encryption, monitoring, restore procedures, dependencies, recovery order and business acceptance. Disaster-recovery service wording cannot establish achievable recovery time or recovery point without architecture and testing evidence. [ 009, 012 ]
Where we would start first Inventory protected services and data, map business priorities, set proposed recovery objectives with assumptions, and show technical feasibility. Define restore tests, full exercises, evidence, exceptions and improvement. Identify buyer decisions during invocation and recovery. Price capacity, data movement, environments and testing rather than treating recovery as an included label. [ 005, 009, 012 ]
Security remains shared across the managed boundary
Evidence-linked insight · What this changes Managed-service scopes can include cyber management, secure operations and privileged access, yet no supplier can guarantee prevention. Buyer policies, users, applications, data owners, other vendors and platform controls affect exposure. Government security guidance offers contracting material, but the authority's classification and live schedule determine applicable obligations. [ 009, 011, 012 ]
Where we would start first Create a control responsibility matrix and privileged-access model. Define personnel screening, secure administration, logging, vulnerability, patching, incident support, subcontractors and assurance. Record control exceptions and buyer risk acceptance. Keep security outcomes distinct from response-time promises and refer specialist cyber questions to competent reviewers. [ 003, 009, 011, 012 ]
Third-party service integration needs enforceable seams
Evidence-linked insight · What this changes Alpha expects its provider to act as a front door to associated systems, while managed infrastructure also relies on connectivity, platform and software vendors. The lead supplier may coordinate without holding contractual authority over every third party. Blurred responsibility causes stalled incidents and unpriced management effort. [ 011, 012 ]
Where we would start first List each supplier, contract owner, service boundary, escalation, support entitlement, data exchange and change dependency. Define operational-level agreements where possible and buyer escalation where not. Test end-to-end incidents during mobilisation. Avoid accepting outcome liability for a third party unless the contract, access and price support that risk. [ 005, 006, 011, 012 ]
People transfer and service transition must be integrated
Evidence-linked insight · What this changes Alpha states a TUPE requirement and a short handover period. Employee transfer questions require specialist legal advice and verified information. Service readiness also depends on knowledge, access, assets, supplier relationships and user communication. Treating TUPE as a separate HR appendix can miss operational capacity and cost consequences. [ 011 ]
Where we would start first Maintain a legally reviewed transfer workstream alongside service discovery. Validate employee information, roles, location, terms, consultation, pensions, vacancies, training and measures subject to lawful access. Connect people assumptions to shifts and price. Create fallbacks for information delay while respecting confidentiality and avoiding invented workforce facts. [ 005, 006, 011 ]
Transition must prove control before service acceptance
Evidence-linked insight · What this changes A provider may inherit incomplete documentation, expiring contracts and production risks while the incumbent continues delivery. Big-bang transfer can jeopardise users; an indefinite shadow period can duplicate cost and obscure accountability. The correct phasing depends on service criticality, data quality, access and the buyer's deadline. [ 007, 011, 012 ]
Where we would start first Sequence discovery, access, knowledge, assets, tools, integrations, security, people, pilot, cutover and stabilisation. Give each gate entry criteria, test evidence, accepting owner and rollback. Track incumbent and buyer dependencies. Define when contractual service levels begin and how inherited defects are baselined rather than silently accepted. [ 005, 006, 007, 011, 012 ]
Exit design is part of the initial service
Evidence-linked insight · What this changes The DDaT Playbook addresses resolution and exit because technology contracts can create knowledge, tooling, data and supplier dependencies. An apparently efficient proprietary operating model may make later transition slow or expensive. Contract expiry is not the only trigger; partial termination, supplier failure and service redesign also matter. [ 005, 007 ]
Where we would start first Specify an exit information set, asset and configuration exports, knowledge, credentials, data return, licence position, cooperation, charges, timing and deletion evidence. Maintain the plan throughout delivery and test export where proportionate. Separate buyer-owned artefacts from supplier tools while ensuring operational continuity and security. [ 005, 006, 007, 009 ]
Price must follow service demand and risk allocation
Evidence-linked insight · What this changes Managed IT can use fixed fees, per-user or per-device charges, consumption, catalogues, projects and pass-through costs. Each mechanism creates incentives and boundary disputes. A fixed price based on an unreliable baseline either embeds contingency or invites change claims, while uncapped consumption transfers budget risk to the buyer. [ 005, 006, 007, 011, 012 ]
Where we would start first Develop a driver-based should-cost view and reconcile it to roles, shifts, tools, licences, vendors, assets, transition and exit. Define inclusions, bands, indexation, volume change and benchmarking. Run demand, wage, vendor, currency and incident scenarios. Explain gainshare or credits without presenting them as guaranteed savings. [ 005, 006, 007 ]
Solution design must connect to measurable operation
Evidence-linked insight · What this changes Alpha published a 75 per cent solution and 25 per cent cost weighting at its initial stage, but another buyer may score differently. Imported weightings and generic best-practice claims weaken alignment. Evaluators need to see how proposed people, process, technology, controls, evidence and price solve their identified risks. [ 011 ]
Where we would start first Reconstruct the live evaluation model and distinguish pass/fail, selection and award questions. Build a compliance matrix down to attachment and word-limit level. For each claim cite approved evidence and explain comparability. Run technical, service, security, commercial and user reviews against the same baseline and assumption register. [ 001, 002, 011 ]
Case-study equivalence requires service-level comparison
Evidence-linked insight · What this changes A large contract value or recognisable client does not prove capability for the target environment. A school trust with no internal ICT team, a housing body needing managed infrastructure and a regulator planning workplace and operations services demand different evidence. Contract award is also not evidence of successful delivery. [ 010, 011, 012, 013 ]
Where we would start first Choose examples by users, sites, hours, service towers, criticality, retained model and transition challenge. State period, scope, role, baseline, result, denominator and attribution. Obtain client permission. Identify gaps honestly and support them with named specialists, tested methods or partners rather than stretching adjacent experience. [ 010, 011, 012, 013 ]
Capacity needs skill, shift and location evidence
Evidence-linked insight · What this changes A blended service may require service desk, field engineers, infrastructure, cloud, network, security, applications, service management and architecture. Total headcount hides availability, on-call burden, travel and single points of failure. Named senior experts do not guarantee everyday queue coverage. [ 011, 012 ]
Where we would start first Translate demand into a role-and-shift model, including leave, training, escalation, surge and succession. Map certifications only where the requirement makes them relevant, and verify expiry. Show how local and remote resources interact. Reconcile all named allocations across concurrent bids and existing contracts before commitment. [ 007, 009, 011, 012 ]
Automation should improve service without hiding accountability
Evidence-linked insight · What this changes Self-service, monitoring, orchestration and assisted support can reduce delay and repetitive effort, but poor automation creates lockouts, noisy alerts and inaccessible journeys. A forecast efficiency is not a realised saving. Users need human escalation and the buyer needs visibility into rules affecting service outcomes. [ 003, 004, 007 ]
Where we would start first Select automation from evidenced demand, pilot it, define approval and rollback, and measure quality as well as volume. State where humans review or intervene. Protect access and security. Keep projected benefits conditional until baseline and adoption are verified, and show how efficiency changes staffing rather than double-counting savings. [ 003, 004, 007, 009 ]
Strengthening starts at responsibility and baseline
Evidence-linked insight · What this changes Managed-service bids usually fail structurally when service boundaries, retained authority, volumes, incumbent information, third-party seams, recovery objectives or price assumptions conflict. More polished prose cannot close those gaps. The current notice set demonstrates why the same MSP label can conceal fundamentally different accountability. [ 010, 011, 012, 013 ]
Where we would start first First confirm route, scope and baseline; then close eligibility, security, workforce and evidence barriers. Reconcile service levels, architecture, people, suppliers, transition, exit and commercial model. Challenge every performance and saving statement. Keep unknowns in the clarification, assumption and decision logs until resolved by evidence. [ 001, 002, 003, 007 ]
Public procurement records are not delivery endorsements
Evidence-linked insight · What this changes The Pool Re award shows an award decision, Alpha and Co-Ownership show tender requirements, and CQC shows pipeline intent. None proves Bid Champions participation, successful operation, savings or service outcomes. Official guidance likewise provides context rather than evidence of a bidder's compliance. [ 003, 004, 007, 010, 011, 012, 013 ]
Where we would start first Use these sources as dated market evidence only. Any public client, award, metric or testimonial claim needs an approved record with exact words, files, consent, period, denominator, attribution, permitted routes and review date. Until available, describe what can be implemented or coordinated without implying prior results. [ 010, 011, 012, 013 ]
Risk acceptance and contract commitment stay with the client
Evidence-linked insight · What this changes Bid support can analyse the pack, coordinate architects and service leads, build traceability and challenge assumptions. It cannot accept security risk, approve architecture, determine TUPE liability, commit staffing, authorise contract departures or warrant recovery. Those are decisions for empowered client roles with appropriate specialist advice. [ 005, 006, 009, 011 ]
Where we would start first Maintain a decision register that names question, evidence, options, consequence, adviser, approver and deadline. Reflect approved choices consistently in solution, schedule and price. If authority or evidence is absent, narrow the commitment or raise clarification. Never fill a technical or legal gap with confident bid language. [ 001, 002, 005, 006, 009 ]
The pursuit should leave an operable service blueprint
Evidence-linked insight · What this changes Reusable outputs include a service catalogue, baseline schema, RACI, SLA dictionary, control matrix, asset model, transition gates, exit information set and assumptions-led price. These artefacts improve later procurements and contract mobilisation when they stay owned and current. [ 003, 004, 007 ]
Where we would start first Assign each artefact an operational owner, version, evidence links and review cycle. Remove buyer-specific constraints before reuse. Train service and commercial teams together, then test the blueprint against real incidents and changes after award. Capture lessons from evaluation without turning one authority's model into an industry rule. [ 003, 004, 007, 011 ]
Relevant anonymised case study
Securing an upper-six-figure public-sector award for managed ICT services for schools
An anonymised Bid Champions client was selected by City council to provide managed ICT services for schools. The public award record places the opportunity in the £500,000–£999,999 band.
- Buyer
- City council
- Published value band
- £500,000–£999,999
- Outcome
- Contract award recorded
The precise tender-support workstream is confidential. The full case separates Bid Champions’ recorded support, the client’s solution and commitments, and the buyer’s award decision.
Read the complete case studyLive-pursuit check
What we would verify before fixing the strategy.
For a live opportunity, we would recheck the applicable law and standards, the buyer's latest notice and documents, qualification route, amendments, commercial assumptions and delivery conditions. This keeps the analysis useful without treating a general market position as a substitute for the actual competition.
Priority public records to recheck: Government standard contracts for procurement; IT Managed Service Provider, contract award notice 2026/S 000-000023; ICT Managed Services Procurement, tender notice 2026/S 000-011578; T1051 Infrastructure as a Service Managed Service Provider, tender notice 2026/S 000-008564; Managed IT Services, pipeline notice 2026/S 000-015486.
Independent verification checks
The public references supporting the evidence points above remain available so a bidder, specialist or decision-maker can test the position against the original authority.
Open 13 public references used to test this sector position
- Procurement Act 2023 — UK Parliament / legislation.gov.uk
- Procurement Regulations 2024 — UK Parliament / legislation.gov.uk
- Technology Code of Practice — Government Digital Service
- Service Standard point 11: Choose the right tools and technology — Government Digital Service
- Model Services Contract — Cabinet Office
- Government standard contracts for procurement — Cabinet Office
- The Digital, Data and Technology Playbook — Cabinet Office
- Technology Services 4 agreement RM6190 — Government Commercial Agency
- Contracting securely — UK Government Security
- IT Managed Service Provider, contract award notice 2026/S 000-000023 — Pool Re Services Limited / Find a Tender
- ICT Managed Services Procurement, tender notice 2026/S 000-011578 — Alpha Academies Trust / Find a Tender
- T1051 Infrastructure as a Service Managed Service Provider, tender notice 2026/S 000-008564 — Northern Ireland Co-Ownership Housing Association / Find a Tender
- Managed IT Services, pipeline notice 2026/S 000-015486 — Care Quality Commission / Find a Tender
Additional value must not weaken the core service
Evidence-linked insight · What this changes Managed IT can support apprenticeships, accessible careers, SME supply chains, reuse, energy efficiency and responsible disposal. These actions require resource and measurement. Hardware refresh and cloud optimisation may affect environmental impact, but a single proxy such as devices recycled cannot establish whole-service carbon reduction. [ 003, 007, 011 ]
Where we would start first Separate contractual delivery from additional commitments. For each action define baseline, quantity, participant or asset, period, owner, evidence and cost. Avoid counting the same apprenticeship or disposal across contracts. Use a stated environmental boundary and obtain data-quality review before publishing reduction claims. [ 003, 007, 011, 012 ]