> For the complete documentation index, see [llms.txt](https://build-it-the-right-way.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://build-it-the-right-way.gitbook.io/home/design-artifacts/servicenow-architects-checklist.md). # ServiceNow Architect's Checklist ### Introduction In the **Build It The Right Way Framework for ServiceNow**, the architect is accountable for producing solution designs that leverage the full capabilities of the ServiceNow platform while addressing operational, security, and business objectives. The ServiceNow architect transforms functional and non-functional requirements into platform-aligned design patterns and components that are scalable, secure, resilient, and maintainable over the solution’s lifecycle. A ServiceNow architect’s responsibility extends beyond technical design. The architect ensures the solution is ready for real-world operations, covering observability, automation, exception handling, and disaster recovery. All architecture outputs must align with governance standards, regulatory requirements, cost considerations, and organizational priorities. The **Build It The Right Way Framework** provides ServiceNow architects with principles, patterns, and guidance designed specifically for the platform. These artifacts should be combined with decision records, reference designs, and assessments to make well-informed, sustainable architecture decisions. **Prefer a visual walkthrough?**\ Watch the full video breakdown of the checklist here: {% embed url="" %} It’s a practical, step-by-step explanation of each task in the checklist, aligned with the Build It The Right Way Framework. ### Checklist **Key ServiceNow architecture tasks:** * [ ] Develop a ServiceNow solution design package including architecture specifications and diagrams that meet functional and non-functional requirements and support routine, exception, and recovery operations. * [ ] Create architecture diagrams that show the full solution landscape, from high-level structure to detailed components such as integration points, data models, security layers, and workflow automation. * [ ] Maintain a ServiceNow architecture decision record (ADR) that documents the reasoning behind key design choices made during the architecture process. * [ ] Work closely with platform teams and stakeholders during build and deployment, providing guidance to ensure implementation stays aligned with the architecture vision and BRY principles. * [ ] Support modeling of platform costs, performance, risk, and operational health to provide a clear understanding of solution impact. * [ ] Offer optimization recommendations based on evolving platform usage, business needs, and changes within the ServiceNow ecosystem. * [ ] Participate in platform governance and compliance reviews, ensuring architectural decisions meet required standards and external obligations. * [ ] Advise on change management activities by providing insights into the feasibility, cost, and architectural fit of proposed changes. ### Next steps Begin by exploring the pillars of the **Build It The Right Way Framework**, and apply its design principles to build ServiceNow solutions that are scalable, secure, and future-ready. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://build-it-the-right-way.gitbook.io/home/design-artifacts/servicenow-architects-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.