Analysis Phase

Hi,

The main official sources are below.

1. No-Code Toolkit (closest to an official analysis checklist)
The No-Code Toolkit is the most practical resource for the analysis phase. It is the online companion to The No-Code Playbook and offers guidance for every stage of the no-code methodology, with 150+ pages of step-by-step instructions, real-world examples and checklists. Its Design phase covers analysis in four stages: Creatio

• Business Use Case. It gives example checklists and questions for defining the application's business requirements and outcomes, and points to supporting material on Roles and Responsibilities (Chapter 4) and the Application Matrix (Chapter 5). This stage covers requirements gathering and business process scoping. Creatio
• Options Analysis. This stage determines whether to use out-of-the-box functionality, Marketplace apps, or custom development. Its inputs include pre-built app templates and AI skills already identified, and third-party packaged applications reviewed for their fit in the overall architecture. Integration and architecture decisions start here. Creatio
• Design and Prototyping. Business requirements are translated into functional design, with prototypes, UIs, workflows, and data structures validated with key stakeholders. This is where object and data analysis happen. creatio
• Project Assignment. It provides checklists for narrowing the first-release scope, decomposing the Business Use Case into smaller elements, and choosing the team and delivery model. Creatio

Later phases, such as Governance Checks, include security, data governance, and compliance, which feed back into the roles and permissions analysis.

2. The No-Code Playbook
The Playbook explains the methodology behind the Toolkit. The Business Use Case chapter is useful for structuring requirements. It describes a pyramid of requirement levels, with non-functional and system requirements at the base. Creatio

3. Creatio implementation methodology (Professional Services)
For a traditional delivery approach, see the Creatio implementation methodology. It is based on PRINCE2, with Elaboration, Execution, Transition, and Operation stages. The analysis-phase deliverables are: Creatio

• Project Charter. It defines agreements and project goals. Creatio
• Project Concept. It is built from the customer's business cases and describes the whole user experience, including workflows outside the system. Creatio
• Requirements documentation. Each requirement is documented, including system logic, integrations, pre-built reports, and the test cases needed for customization. Creatio

4. Creatio Academy, for topic-specific analysis

• The Getting started section helps you create an implementation plan based on business goals and requirements and includes a short quiz to determine the best way to configure Creatio. Creatio
• For roles and permissions, the access rights documentation covers organizational and functional roles, operation permissions, and object, record, and column permissions. It is a good checklist for a permissions matrix.
• For integrations, the developer documentation covers OData, DataService, web services, and integration with external systems. It helps you classify each integration by direction, protocol, and volume during analysis.
• For data and objects, the object and data import documentation, together with the base object model of the relevant product (Sales, Marketing, or Service), supports gap analysis before adding custom objects.

5. Creatio Marketplace
The Marketplace is worth checking during Options Analysis for ready-made apps, connectors, and templates.

Many teams combine the Toolkit's Design-phase checklists with their own BRD or FSD template, adding a few Creatio-specific sections. Typical ones are an object/field mapping against the base data model, a role and permission matrix, an integration catalog, and a process list with no-code or custom-code classification.