Looking for CSM BRD template & Requirement gathering Template

[Naresh_5120]

Dear Community

I am going to start working on CSM implementation project as Business Analyst. I am looking for ServiceNow CSM BRD template & requirement gathering template. Can someone help me where can i find the BRD template & Requirement gathering template.
#CSM, #BRD, #Requirementsgathering #implementation 

[Vikram Reddy · Accepted solution]

Hi @Naresh_5120 ,

Welcome to the CSM world. Starting as a BA on a CSM rollout is one of the best ways to learn the platform end to end, since you will touch the data model, channels, knowledge, the agent workspace, and reporting all on the same project.

I have put together a small starter pack you can use right away. Two templates and two decks, all built around how a real CSM implementation actually runs (not a generic ITSM BRD rebadged for CSM).

1. CSM Business Requirements Document (Word) Structured the way a CSM BRD should be: executive summary, scope (in / out / phased), current and future state, then functional requirements grouped by CSM capability, Account & Contact, Case Management, Omnichannel intake, Advanced Work Assignment, Knowledge, Customer Portal, Service Contracts & Entitlements, SLAs, Major Issue Management, Field Service integration, Surveys, CSM Configurable Workspace, and Notifications. Plus non-functional, roles, integrations, data migration, reporting, RAID, glossary, and sign-off.

2. Requirements Gathering Workbook (Excel) 17 discovery sheets, one per CSM topic. Each question has a "Why it matters / OOB notes" prompt so you are not just collecting answers, you are guiding the customer toward the right design. Columns for Customer Response, your Recommendation, MoSCoW priority, and an OOB / Config / Custom tag. There is also a Workshop Plan tab, Stakeholder Matrix, RAID Log, Decision Log, and a Summary Dashboard with built-in charts.

A few things I tell every first time CSM BA, in case it saves you some pain later:

1. Get the Account, Contact, Consumer, Sold Product, and Install Base model right before anything else. Almost every downstream feature reads from it, and going back to fix it after build hurts.
2. Keep your case types tight. Four to six is plenty for most B2B implementations. More than that and your form, playbook, and routing maintenance becomes painful very quickly.
3. Drive SLAs from service contracts and entitlements, not just from case priority. CSM is designed for entitlement-driven service, and the engine does the heavy lifting if you set it up right.
4. Default to OOB first, configure second, customize last. Document any custom work with the business reason behind it, so a future you (or a future architect) knows why it exists.
5. Bookmark Now Create. The Case Management Process Guide, Case Types Implementation Guide, and Playbooks for CSM are gold. Cross-check your BRD against them as you write it.

Worth reading on the community as you ramp up:

• Getting Started with CSM Case Management by @PriyamvadhaM 
• Core Case Management Features
• Advanced Work Assignment in CSM Omnichannel

Hope this gives you a strong start

Thank you,

Vikram Karety

ServiceNow Architect
Octigo Solutions INC