I have to create the ServiceNow requirement gathering document for the client.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 07:19 AM
I have to create the ServiceNow requirement gathering document for the client. Can anyone please suggest what it should include?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 09:00 AM
@Community Alums
It depends on what type of requirements you are gathering.
But here is something for you to keep in hand
-
Project Overview – Purpose, objectives, stakeholders.
-
Scope Definition – In-scope & out-of-scope modules.
-
Current Process & Pain Points – Existing challenges.
-
Functional Requirements – Forms, workflows, SLAs.
-
Integrations – Systems to be connected.
-
User Roles & Access – Visibility, approvals.
-
Reporting Needs – KPIs, dashboards.
-
Data Migration – Import requirements.
-
Non-Functional Requirements – Security, performance.
-
Timelines & Assumptions – High-level milestones.
Accept the solution and mark as helpful if it does, to benefit future readers.
Regards,
Sumanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 09:34 AM
Hi @Community Alums
I am a BA and BPC, and conducting workshops and requirement gathering is part of my daily job. To clarify, there is no specific document provided by ServiceNow for me to use. In our workshops, we first present the OOTB functionality of the modules. If there are any differences, we capture the 'why' behind them in user stories. You can also refer to the OOTB stories. All these documents are easily available on Now Create. In the current scenario, we did not create any specific requirement documents; everything gets captured as part of the story, which is quick and easy to get signed off.
https://youtu.be/QyvYXRFdXEg?si=iEBZw5-AEHNkUJ7Z
I am happy, if you need to connect 1-1 .
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2025 09:58 AM
ServiceNow Requirement Gathering Template
1. General Information
Field | Description |
Request Title |
|
Requested By |
|
Business Unit / Department |
|
Date Submitted |
|
Priority |
|
Due Date / Target Completion |
|
2. Business Requirement
Field | Description |
Business Objective |
|
Problem Statement |
|
Expected Outcome |
|
Stakeholders |
|
3. Functional Requirements
Field | Description |
Use Case / User Story |
|
Modules / Applications Involved |
|
Form Fields Required |
|
Business Rules / Workflow Logic |
|
Notifications / Alerts |
|
UI Requirements |
|
4. Technical Requirements
Field | Description |
Integrations Needed |
|
Data Sources |
|
Security / Role Access |
|
SLAs / Performance Expectations |
|
Audit / Logging Requirements |
|
5. Reporting & Metrics
Field | Description |
Reports or Dashboards Needed |
|
KPIs or Metrics |
|
6. Dependencies and Constraints
Field | Description |
Upstream / Downstream Dependencies |
|
Known Constraints / Risks |
|
7. Sign-Off
Field | Description |
Prepared By |
|
Date Prepared |
|
Approved By |
|
Approval Date |
|
Hope that helps!