How to Evaluate and Select a Workday Implementation Partner

Choosing your Workday implementation partner is the single highest-stakes decision you'll make before the programme begins. It determines the team that will configure your system, the methodology that will govern your delivery, the commercial relationship that will shape every negotiation for the next twelve to twenty-four months, and the quality of the foundation your organisation will operate on for a decade.

Most organisations approach this decision with rigour. They issue an RFP. They evaluate responses. They conduct orals. They score against criteria. They negotiate commercial terms. They select a partner.

And most organisations still get it wrong. Not because they chose a bad SI. The major Workday implementation partners are all capable firms with experienced consultants. They get it wrong because the evaluation process focuses on the wrong things, asks the wrong questions, and underweights the factors that actually determine whether the engagement will succeed.

After 25 years on both sides of this relationship, first running SI delivery teams and now advising clients on partner selection and governance, I've seen what predicts a successful SI engagement and what doesn't. The answer is rarely what the evaluation scorecard measures.

What most evaluations focus on (and why it's insufficient)

The standard SI evaluation process measures things that are easy to compare: proposed team qualifications, methodology overview, reference clients, timeline estimates, and price. These are all relevant. None of them are predictive.

Team qualifications look good on paper. Every SI responding to your RFP will present a team of experienced consultants with impressive CVs. What the CV doesn't tell you is whether those specific consultants will actually be assigned to your project. SI proposals routinely feature senior resources during the sales process who are replaced by more junior consultants once the contract is signed. The experienced architect who presented during orals may be leading three other projects simultaneously. The project manager whose CV listed fifteen Workday deployments may have been a workstream lead on twelve of them, not the programme-level PM your project requires.

Methodology descriptions are nearly identical. Every major Workday SI uses some variation of the same implementation methodology. The phases are the same. The deliverables are similar. The governance structures look comparable on paper. Methodology is not a differentiator. Execution is. And execution quality is determined by the specific people on your project, the SI's internal resource management decisions, and the commercial pressures on the engagement, none of which are visible in a methodology document.

Reference clients tell you the best-case story. No SI provides references from projects that went badly. The references you receive are curated to present the SI in the best possible light. They're useful for validating that the SI can deliver a successful project. They're not useful for understanding how the SI behaves when things go wrong, which is the scenario that actually matters for your risk assessment.

Timeline estimates are optimistic by design. In a competitive bid, the SI that proposes the shortest timeline has a structural advantage. Buyers want to go live sooner. A sixteen-month proposal looks better than an eighteen-month proposal, even when the eighteen-month estimate is more realistic. Most SIs know this and calibrate their estimates accordingly. The timeline you're comparing across proposals is the timeline the SI believes you want to hear, not necessarily the timeline the programme will actually need.

Price comparisons are misleading. The lowest bid is almost never the cheapest outcome. A lower initial price often reflects a tighter scope definition, which generates change orders when requirements inevitably expand. It may reflect a more junior team composition, which reduces the day rate but increases the total hours required. It may exclude items that other SIs included, such as data migration support, integration development, or post-go-live hypercare. Comparing SI proposals on price without normalising scope, team composition, and assumptions is comparing numbers that measure different things.

What actually predicts a successful engagement

The factors that determine whether an SI engagement succeeds are harder to evaluate than CVs and pricing schedules. But they're the factors that matter.

The specific project manager and functional leads who will be assigned to your project. Not the team presented during orals. The team that will actually show up on day one. Ask the SI to contractually commit to named individuals for key roles for a defined period. If they can't or won't, that tells you something important about how they manage resource allocation. The difference between a strong and a weak Workday PM on your project is easily worth several hundred thousand pounds in avoided change orders, rework, and timeline extension. Investing evaluation time in assessing the actual PM is more valuable than any other element of the process.

How the SI handles situations when the project is in trouble. Every Workday programme encounters difficulties. Design decisions get contested. Testing reveals defects. Timelines slip. The question is not whether problems will occur but how the SI responds when they do. During orals, ask the SI to describe a project that went badly. Not one that had a few bumps and then succeeded. One that genuinely struggled. Ask what went wrong, what they did about it, and what they learned. The quality of that answer tells you more about the SI than any case study of a successful deployment. An SI that can discuss failure honestly and specifically is an SI that has a learning culture. An SI that deflects, minimises, or can't provide an example is an SI that either hasn't reflected on its failures or won't be honest with you about them.

The SI's approach to scope boundaries and change orders. Before you sign the contract, you need to understand how the SI defines and manages scope. Ask to see examples of change orders from previous projects, with client details removed. Ask how they determine whether a requirement falls inside or outside the SOW. Ask what their process is when the client and the SI disagree about whether something is in scope. The answers reveal the SI's commercial culture. Some SIs manage scope tightly and generate change orders aggressively. Others absorb more ambiguity and negotiate collaboratively. Neither approach is inherently wrong, but you need to know which model you're buying into because it will shape every commercial conversation for the life of the engagement.

The SI's resource management practices and utilisation targets. This is the question most clients don't think to ask, and it's one of the most important. SIs are businesses. They manage their consultants against utilisation targets, typically 75-85% billable time. When utilisation pressure is high, consultants get spread across multiple projects. Quality on your project suffers not because the consultant isn't capable but because they're splitting their attention. Ask the SI what their current utilisation rate is. Ask how many other projects your proposed team members are currently assigned to. Ask what happens to your resourcing if the SI wins another large deal during your programme. These questions make SIs uncomfortable, which is exactly why they're worth asking.

The SI's relationship with Workday. Not all Workday implementation partners have the same relationship with Workday. Some are launch partners with deep platform access and influence. Others are smaller firms with strong niche expertise but less platform leverage. The SI's relationship with Workday affects their access to product roadmap information, their ability to escalate platform issues, and their influence on feature prioritisation. For complex implementations, this access can be meaningful. Ask the SI to describe their relationship with Workday specifically, not generically.

What changes when you are selecting an SI in the UK

UK organisations selecting a Workday SI face a market shaped by four conditions the standard global guidance does not address.

The UK SI pool is concentrated. A relatively small number of partners deliver the majority of UK Workday programmes. That concentration affects your evaluation in two practical ways. First, the partners on your shortlist almost certainly know each other's pricing, methodology, and bench because consultants move between them. The "competitive tension" the procurement team is hoping to engineer is more limited than it looks on paper. Second, references in a small market are reciprocal. The reference client you call has worked with the consultants on other partners' benches and may be cautious about saying anything that gets back to them. Treat references as one input, not the deciding one, and rely more heavily on direct interrogation of the proposed team.

Public sector buyers operate inside a framework. If you are central government, an arm's length body, NHS, a local authority, or higher education, you are most likely buying through a Crown Commercial Service framework, typically the current G-Cloud or Digital Outcomes and Specialists agreement, or through a sector-specific vehicle. The framework defines who you can call off, what you can negotiate, and how the evaluation is run. The framework does not, however, define the depth of your due diligence. Public sector buyers regularly treat framework procurement as a lighter-touch process than open competition. That is a mistake. The call-off stage is where you set scope, named resources, and acceptance criteria, and it carries the same long-term consequences as a private sector signature.

Offshore delivery is the norm, and it sits inside UK GDPR. Most large UK Workday programmes are delivered with a blended model: a UK-fronted account team supported by configuration, integration, and AMS work performed in India or another offshore centre. That model is not inherently a quality problem and is often a commercial requirement to hit a viable price point. It is a UK GDPR problem if you have not addressed it in the contract. The SI is a processor under UK GDPR for any employee data they touch in your tenant. The Data Processing Agreement needs to name subprocessors, identify the lawful transfer mechanism (the UK IDTA or the UK Addendum to the EU SCCs), and define breach notification timelines that let you meet your 72-hour ICO obligation. Ask for a copy of the standard DPA before contract negotiations begin so you have time to negotiate the specifics rather than accepting the template under signature pressure.

The UK Payroll bench is the smallest part of every SI. If your scope includes UK Payroll, this is the single most important SI capability to interrogate. The pool of consultants in the UK who have configured Workday Payroll for a complete UK pay run, including PAYE, RTI, pension auto-enrolment, statutory leave, P11D processing, and a clean March year-end, is small at every SI in the market. Bench depth is not the same as overall headcount. Ask each SI for the named UK Payroll consultants they will assign, their actual UK Payroll project history, and what their plan is if one of them moves on mid-programme. A strong UK HCM SI can be a thin UK Payroll SI. The two evaluations need to happen separately.

How to read a SOW Critically

The Statement of Work is the document that defines what you're buying. It's also the document that generates the most disputes during implementation, because ambiguity in the SOW is the primary source of preventable change orders.

Look for specificity in scope boundaries. A well-written SOW defines not just what's included but what's explicitly excluded. "Payroll implementation" without specifying which countries, which pay groups, and which downstream integrations is an ambiguity that will generate a change order. Every major deliverable should have a clear definition of done that both parties agree on before signature.

Examine the assumptions section carefully. Every SOW contains assumptions about client readiness, data quality, resource availability, and decision-making timelines. These assumptions are the SI's risk transfer mechanism. If an assumption proves false, the SI has grounds for a change order. Read every assumption and assess whether your organisation can realistically meet it. Challenge assumptions that feel optimistic. If the SOW assumes "client will provide clean data extracts within two weeks of request," ask whether your organisation has ever delivered a clean data extract within two weeks of anything.

Understand the change order process before you sign. The SOW should define how change orders are raised, evaluated, priced, and approved. It should specify what happens when the client and SI disagree about whether a requirement is in scope. It should define the escalation path for commercial disputes. If the change order process is vague or absent, you're entering the engagement without a mechanism for managing the commercial conversations that will inevitably arise.

Check the resource commitment. Does the SOW commit specific named resources for specific periods, or does it commit "appropriately qualified resources"? The difference matters. If the SOW allows the SI to substitute resources freely, your project team can change mid-programme based on the SI's internal resource management priorities rather than your project's needs.

Review the acceptance criteria for each phase. How does the SOW define successful completion of design? Of build? Of testing? If phase completion is based on the SI delivering documentation rather than the client confirming that deliverables meet requirements, the SI can declare phases complete before the client is genuinely satisfied. This creates downstream rework that the SI may argue falls outside the original scope.

The questions most organisations forget to ask

Beyond the standard evaluation criteria and SOW review, there are questions that reveal the SI's operating culture in ways that formal proposals don't.

"What will you tell us that we don't want to hear?" A good SI will challenge your assumptions during the engagement. They'll tell you when your requirements are overcomplicated, when your timeline is unrealistic, and when your executive sponsor's expectations don't match the programme's trajectory. Ask them during the evaluation what they'd push back on based on what they've seen so far. If they have nothing critical to say, they're either not paying attention or they're telling you what you want to hear. Neither is a good sign.

"How do you handle it when your team disagrees with the client's decision?" This reveals the SI's approach to client management. Some SIs are genuinely consultative: they'll present their recommendation, explain the trade-offs, and respect the client's decision even if they disagree. Others defer to the client on everything, which sounds accommodating but means you're not getting the expert guidance you're paying for. And others push their preferred approach regardless of client input, which creates conflict. You want the first model.

"What does your team do when they're blocked by a client decision?" On every Workday programme, there are moments when the client team can't make a decision quickly enough to keep the SI's work moving. The SI's response to this situation reveals their delivery culture. Do they escalate immediately? Do they proceed with assumptions? Do they pause and wait? Do they log it as a risk and continue with other work? Each approach has different implications for how the programme flows, and you should understand which approach your SI takes before you're in the situation.

"What would you do differently on this project compared to a project of similar scope you delivered last year?" This tests whether the SI learns and adapts or runs the same playbook regardless of context. A thoughtful answer that references specific lessons from recent projects indicates a firm that reflects on its delivery. A generic answer about "continuous improvement" indicates a firm that markets learning without practising it.

The value of independent support during selection

Most organisations conduct SI selection with their internal team, sometimes supplemented by a procurement advisor. The internal team brings organisational knowledge but typically lacks the experience to evaluate an SI's proposal with the depth required.

Having someone on your side who has worked inside SI organisations, who understands how proposals are constructed, how teams are assembled, how scope is defined, and how commercial levers work, fundamentally changes the quality of the evaluation. They can read between the lines of a proposal because they've written proposals. They can assess whether a team composition is realistic because they've staffed projects. They can identify SOW ambiguities because they've seen those ambiguities generate change orders on previous programmes.

This is the focus of our independent SI selection advisory. We support clients through the SI selection process, providing the independent expertise that ensures the evaluation focuses on the factors that actually predict success rather than the factors that are easiest to measure. We help structure the evaluation criteria, participate in orals, review SOWs line by line, and negotiate commercial terms with an understanding of what's standard, what's favourable, and what's a red flag.

After signature, our COMPaaS service continues that work to hold the partner accountable through delivery. The same independence model carries from procurement into governance.

If you'd like a structured first pass at scoring SI responses yourself, our free SI Vendor Scorecard covers the criteria most often missing from internal evaluations.

The cost of getting SI selection wrong is measured in millions and years. The investment in getting it right is measured in weeks. The asymmetry is significant.

Where to Start

If you're approaching SI selection for a Workday programme and want independent support to ensure the evaluation is rigorous, or if you've already selected an SI and want an independent review of the SOW before signature, start with a conversation.

Our free programme risk review can be conducted at any stage, including pre-selection. It's a focused 30-minute discussion about your programme's current position and the decisions ahead. Within 24 hours, you'll receive a written findings summary and our top three recommendations.

Book Your Free Programme Risk Review →