ServiceNow Implementation Brief

How to write a ServiceNow implementation brief

ServiceNow engagements arrive in shapes that share almost nothing: a greenfield platform build, an enhancement to a live instance, an ITAM rollout, an ITOM discovery project, a roadmap advisory. One brief covers all of them, and it does it by asking the shape first.

This is the ServiceNow implementation brief in Coligna — ten sections, forty-three questions. It's the longest template in the set, by design, and it's discovery rather than a form.

The ten sections, and what each one is for

Engagement Overview & Objectives. Organisation, engagement type, business drivers, definition of success, and stakeholders. The engagement type is the pivot the rest of the brief turns on — see below.

Current State & ServiceNow Estate. Whether an instance exists, the platform release, live modules, legacy tools, and technical debt. On an enhancement this is the most important section in the document.

Scope & Boundaries. Products in scope, processes in scope, explicit exclusions, and rollout approach. Exclusions are the field most briefs omit and most disputes come back to.

Functional & Process Requirements. Must-haves, current pain points, nice-to-haves, and the configuration-versus-customisation stance. That last one is a philosophy question with a price attached.

CMDB, Data Model & Asset Management. CMDB current state, CSDM alignment, discovery and data sources, asset-management needs. CMDB maturity is the quiet determinant of how much of the promised value is reachable.

Integrations & Data Migration. Systems, integration patterns, MID Server or on-prem considerations, migration scope.

Users, Roles & Licensing. Personas and volumes, the fulfiller-versus-requester split, assignment groups, licensing. The fulfiller split drives licence cost directly.

Experience, Service Management & AI. Catalogue and portal needs, SLAs and OLAs, reporting, and interest in platform AI capabilities.

Governance, Security & Compliance. Instance and environment strategy, security and access, compliance and residency, release governance.

Delivery, Timeline & Commercials. Timeline and milestones, hard constraints, organisational readiness and change management, budget, risks and dependencies.

Two questions clients answer badly — and two the brief doesn't ask

"What's in scope?" — then ask what's explicitly out. Scope stated positively always sounds agreed. The exclusions field is where the disagreement surfaces while it's still cheap, and clients leave it blank unless pushed.

"Configuration or customisation?" — and make it a real decision. Everyone says configuration-first until a requirement needs customisation. Establishing the stance at brief stage, in writing, turns a later argument into a change request with a rationale.

Two more worth asking in the kickoff call, even though the template doesn't ask them:

"Who owns the platform after go-live, and are they resourced?" Platform ownership is the difference between an implementation and an ongoing capability.

"What's the appetite for process change versus replicating what exists?" Lifting a broken process onto a new platform is a well-funded way to keep it.

From brief to project

A submitted brief arrives in your inbound queue, sectioned and typed. It becomes an estimate, and the accepted proposal becomes a live project carrying the scope and exclusions the client agreed — which on an engagement this size is the document everyone returns to. See how the full lifecycle works →

A PDF gets filled in once and filed. A brief-capture link needs no account from the client and starts the work at submission.

Frequently asked questions