Why Government IT Ops Is Different
Government IT operations is not the same as private sector IT operations. The fundamentals overlap - incident management, change management, service desk, monitoring - but the operating context creates constraints that most commercial consultants have never dealt with.
Federal departments and Crown corporations operate under the Treasury Board Secretariat (TBS) Policy on Service and Digital, which sets expectations for service management, digital standards, and IT governance. Shared Services Canada (SSC) controls significant infrastructure, which means your IT operations team often does not own the full stack. You are managing services that depend on infrastructure someone else operates.
Security classification adds another layer. Protected B environments require consultants with appropriate personnel security screening - Reliability Status at minimum, Secret clearance for many engagements. This alone eliminates most commercial consultants who have never gone through the process.
Then there is procurement. You cannot just hire a consultant. You need to go through an established procurement vehicle - ProServices, TBIPS, or a standing offer - which means the firm you want to work with must already be qualified. Understanding how government procurement works is not optional knowledge for an IT operations consultant working in this space. It is table stakes.
Finally, there is the bilingual requirement. Official Languages Act obligations mean that IT services, documentation, and communications often need to be delivered in both English and French. A consultant who cannot work in a bilingual environment will struggle in most federal departments.
What to Look For
When evaluating an IT operations consultant for a government engagement, these are the criteria that matter most. Use this as a screening checklist - any firm you are considering should meet at least seven of these ten.
Common Mistakes Departments Make
After years of working inside government IT operations, these are the patterns that come up again and again when departments bring in outside help.
Hiring for certification, not capability
ITIL certification tells you someone passed an exam. It does not tell you they can walk into your department and improve your incident management process. The most effective IT operations consultants have a mix of certification and practical experience - they have built processes, configured ServiceNow workflows, and run service desks. Certification without implementation experience is theory without practice.
Buying bodies instead of outcomes
Staff augmentation has its place, but if you need your IT operations improved, you need a consultant who will own a deliverable - not someone who fills a seat. The difference is accountability. A staff augmentation resource does what they are told. A consulting engagement should produce specific, measurable improvements to your service management maturity.
Underestimating the SSC complexity
Departments often bring in consultants who have great private sector experience but have never worked in a shared services model. When your consultant writes a beautiful incident management process and then discovers that half the escalation path goes through SSC, the whole thing needs to be redesigned. Hire someone who understands this from day one.
Choosing the biggest name instead of the best fit
Large integrators win government IT operations work because they are safe choices, not because they deliver the best outcomes. The partner who sold you the engagement will not be the person on-site. You will get a team of junior consultants following a methodology playbook. For process improvement work, a boutique firm with senior practitioners who stay for the full engagement will almost always deliver better results.
How Procurement Works
Understanding procurement is essential because it determines which firms you can actually hire. Government technology consulting typically flows through one of these vehicles.
ProServices
ProServices (Professional Services) is PSPC's supply arrangement for management consulting, IT consulting, and other professional services. It is the most commonly used vehicle for IT operations consulting. Firms must be pre-qualified under specific categories and stream values. For IT operations work, you are typically looking at Stream 2 (IT Business Solutions) or Stream 3 (IT Services).
TBIPS
Task-Based Informatics Professional Services (TBIPS) is designed for task-based IT work with defined deliverables and timelines. If your engagement has a clear scope and end date - like an ITSM maturity assessment or a ServiceNow configuration project - TBIPS is often the right vehicle. Requirements are typically more structured than ProServices.
SBIPS
Solution-Based Informatics Professional Services (SBIPS) is for solution-oriented engagements. If you need a firm to assess your current state and propose a solution - rather than execute a predefined task - SBIPS may be appropriate.
Before engaging any firm, verify their qualification on the procurement vehicle you plan to use. Check CanadaBuys or contact your departmental procurement team. Starting work with an unqualified firm creates legal and audit risks.
Red Flags When Evaluating Firms
Watch for these warning signs during the evaluation process. Any one of these should prompt deeper questioning before you proceed.
- The firm cannot name specific government clients or departments they have worked with. Confidentiality is reasonable, but they should be able to reference the type of department (central agency, line department, Crown corporation) and the nature of the work without naming the client.
- The proposal team is different from the delivery team. Ask point-blank: who will be on-site doing the work? If the answer is 'we will identify resources after award,' that is a staffing play, not a consulting engagement.
- They cannot explain how they work within the SSC model. If a firm claims government IT operations experience but cannot articulate how shared infrastructure affects service management, they are bluffing.
- Their ITSM approach is tool-first rather than process-first. A firm that leads with 'we will configure ServiceNow' before understanding your processes is selling technology, not improvement.
- They promise a maturity level jump without assessing your current state. Any firm that guarantees you will go from Level 1 to Level 3 in six months without first understanding where you are today is selling a fantasy.
- No references from government clients. This is the simplest test. If they cannot produce a single reference from a federal department or Crown corporation, they have not done this work.
- They do not ask about your procurement timeline. An experienced government consultant knows that procurement takes time and will factor this into their approach. A firm that ignores procurement logistics has not done much government work.
Questions to Ask Before Signing
These questions cut through marketing material and get to the substance of what you are actually buying.
- Who specifically will be doing the work, and what is their background in government IT operations?
- How many ITSM improvement engagements have you completed in federal departments in the last three years?
- What ServiceNow modules have your team configured in a government environment?
- How do you handle the SSC dependency in your service management process designs?
- What is your approach to knowledge transfer? Will our internal team be able to sustain the improvements after you leave?
- Can you show us a sample deliverable from a similar engagement (with client details redacted)?
- What metrics do you use to measure the success of an IT operations improvement engagement?
- Are your proposed resources currently holding valid security clearances?
- What procurement vehicle are you qualified on, and what is your stream and category?
- How do you handle situations where the assessment reveals that the problem is not process but people or organisational structure?
Frequently Asked Questions
How do I improve IT service management in a government department?
Start with a maturity assessment across your core ITSM processes - incident, problem, change, and service request management. Score each against ITIL 4 practices and identify the biggest gaps. Then prioritize ruthlessly. Most departments try to improve everything at once and end up improving nothing. Pick one or two process areas, get them working properly, and build from there. The biggest lever is usually incident management - fixing how you detect, categorize, and resolve incidents produces visible improvements fast.
Can a small or boutique firm handle a large department's IT operations improvement?
Yes, and often better than a large firm. IT operations improvement is not about how many bodies you throw at the problem - it is about the quality of the assessment, the relevance of the recommendations, and the ability to implement changes that stick. A boutique firm with three senior practitioners who each have 15+ years of government IT operations experience will typically outperform a large integrator's team of eight junior consultants. The key question is not firm size but practitioner experience.
How long does a typical ITSM improvement engagement take in government?
A focused ITSM maturity assessment can be completed in 4-6 weeks. Implementing the recommended improvements typically takes 3-6 months per process area, depending on complexity and organisational readiness. The biggest variable is not the technical work - it is change management. Getting a department to adopt new processes requires stakeholder alignment, training, and sustained executive sponsorship. Plan for 6-12 months from assessment to steady-state for a meaningful improvement program.
Should we pick a firm that specialises in our specific ITSM tool (ServiceNow, BMC, etc.)?
Tool expertise matters, but process expertise matters more. The best IT operations consultants understand ITSM principles independent of any platform - and then know how to implement those principles on your specific tool. That said, ServiceNow dominates in the Government of Canada, so any firm you are considering should have deep ServiceNow experience. If your department runs BMC Helix or another platform, make sure the firm has real implementation experience on that platform, not just certification.
What is the difference between staff augmentation and IT operations consulting?
Staff augmentation puts a person at a desk to do work you direct. Consulting delivers a defined outcome - an assessment, an improved process, a configured platform - with the consultant owning the methodology and quality of the deliverable. Both have their place. If you know exactly what needs to be done and just need skilled hands, staff augmentation works. If you need someone to assess your current state, recommend improvements, and help implement them, you need consulting. The pricing model is different too - staff augmentation is typically a day rate, while consulting should be tied to deliverables.
How do we evaluate IT operations consultants when we are not IT operations experts ourselves?
Focus on outcomes, not methodology. Ask the firm to describe three specific improvements they delivered in government departments - with metrics. Ask to speak with a previous government client. Ask them to explain your department's biggest IT operations challenge and how they would approach it. If they cannot give you a coherent, jargon-free answer, they are not the right fit. Also, pay attention to how they listen. A good consultant asks more questions than they answer in the first meeting.
Related Services
About the Author
Corey Derouin is the founder and principal consultant at Codeview Digital. With extensive experience in federal government IT operations, ServiceNow platform delivery, and digital transformation, Corey brings a practitioner's perspective to every engagement - not a slide deck, but hands-on delivery from someone who has done the work inside government.
Learn more about our team