Platform Map · How It All Connects

Everything in Transform, clearly connected.

A plain-language guide to how the Transform platform is structured, from the account all the way down to test cases.

Account
Organization
Project
Tasks & Requirements
Delivery
AI & Meetings
Analytics
Show All
Platform Structure: Top to Bottom
The company's root in Transform. Everything lives under here.
↓contains
Organization Typically represents a client or a distinct business unit. One account can have many orgs.
🏢
Organization
Represents a client, a company division, or a distinct work area. Each org holds its own projects, people, and shared resources.
Client container
🔄
Processes
Standard operating procedures and methodology, such as Record to Report or Order to Cash. Shared across all projects in the org.
Methodology
⚙️
Systems
The software platforms involved in the engagement. Link systems to requirements and test cases.
Tech landscape
🗂️
Segment Types
The classification schema for the organization's business dimensions, such as Department, Subsidiary, or Location. Define types once, then create Segments within each.
Classification schema
📌
Segments
The organization's core business dimensions, such as legal entity, department, or line of business. Used to structure how work is organized and reported.
Business Structure
↓holds many
Project The core unit of work. Everything below lives inside a project.
📁
Project
A specific engagement, phase, or workstream, such as an ERP Implementation or Evaluation. Projects hold all tasks, requirements, and deliverables.
Core container
📑
Project Sections
Break the project into phases or workstreams, such as Plan, Design, Build, Verify, or Deploy. Sections can nest inside each other and appear in the Gantt chart.
Structure
✅
RACI Matrix
Who is Responsible, Accountable, Consulted, and Informed for each activity. Can be set at the org or project level and published by role.
Accountability
⚠️
RAID Log
Track Risks, Assumptions, Issues, and Dependencies in one place. Visible at the org or project level depending on the configuration.
Risk management
↓work items created directly or via AI Ingest
AI & Meetings Optional source for auto-extracting requirements, tasks, and test cases.
🎙️
Meetings
Log every call, working session, or check-in. The AI notetaker bot joins the meeting, records it, and creates a full transcript and summary automatically.
Auto-capture
📎
Artifacts
Any document attached to the project, such as discovery questionnaires, BRDs, process flows, or SOWs. Connect to a document platform for living documents that stay in sync.
Documents
🤖
AI Ingest
Run Ingest on any meeting or artifact and the AI scans every word to pull out requirements, tasks, test cases, and action items. Review and approve before they are created.
AI extraction
↓tracked and managed as
Tasks & Requirements The day-to-day building blocks of the project.
📝
Requirements
What the customer needs the system to do. Each requirement is linked to a process area, a system, and can have child tasks and test cases hanging off it.
What's needed
✔️
Tasks
The actual work to be done. Tasks live inside project sections, can be assigned to teammates, have due dates, and can be broken into subtasks. Shown on the Gantt chart.
Work to do
🔗
Dependencies
Define the order that tasks must happen in. Supports four types: Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish. Optional lag days can be set between tasks.
Sequencing
↓tracked through
Delivery The technical and quality layer. Track what's being built and verify it works.
💡
Solutions
A complete piece of functionality being delivered, such as a system integration or a custom approval workflow. Solutions group together all the Build Items needed to make them work.
Functional scope
🔧
Build Items
The individual technical components inside a solution, such as scripts, workflows, saved searches, custom fields, or integrations. Track progress and % complete on each one.
Technical components
🧪
Test Cases
Verify that requirements and build items work as expected. Link test cases to specific systems and track Pass, Fail, or Not Yet Tested during UAT.
Quality assurance
↓surfaced in
Analytics & Visibility See everything, share the right view with the right people.
📊
Dashboards
Build custom views of project health, open items, and team progress. Publish dashboards by role so every PM, Consultant, or Executive sees what is relevant.
Role-based views
🔍
Saved Views
Save and share filtered lists of any object type, such as tasks by owner, open requirements by process area, or test cases by system. Publish to a role for team-wide access.
Filtered lists
📋
Pivot Tables
Slice and dice project data across multiple dimensions: requirements by status and process area, tasks by assignee and section, and more.
Data analysis
Key Relationships to Know
📝→✔️
Requirements → Tasks A requirement can have child tasks. When ready to action a requirement, create tasks directly underneath it to track the work.
📝→🧪
Requirements → Test Cases Test cases validate that requirements have been met. Link them during UAT to confirm sign-off against what was originally scoped.
📝→💡
Requirements → Solutions Link requirements to the solution that fulfills them. This provides full traceability from what was asked for to what was built.
💡→🔧
Solutions → Build Items A solution defines the functional outcome. A Build Item is the individual technical component. One solution can have many build items, each tracking a specific technical component.
🎙️→📝
Meetings → Requirements & Tasks Run AI Ingest on any meeting transcript and Transform will automatically surface requirements, tasks, and action items mentioned during the call.
🔄→📝🔧
Processes → Requirements & Build Items Link requirements and build items back to the process area they belong to, such as Record to Report or Order to Cash, for easy filtering and reporting.
⚙️→🔧🧪
Systems → Build Items & Test Cases Tag build items and test cases with the system they relate to, making it easy to view everything for a given system in one place.
📎→📝🧪
Artifacts → Requirements & Test Cases Upload a BRD or discovery doc as an artifact, run Ingest, and Transform will automatically extract requirements and test cases from the document.
🔑→📊
Roles → Dashboards & Views Publish dashboards and saved views to specific roles. The PM sees project health, consultants see their task list, and executive sponsors see the portfolio overview.
📌→✅
Segments → RACI Items RACI items can be scoped to a specific Segment, enabling accountability to be defined within a particular business dimension such as a department or subsidiary.
🗂️→📌
Segment Types → Segments Segment Types define the classification schema (e.g. Department, Subsidiary). Segments are the individual instances within each type (e.g. "Human Resources" within Department).
📑→📝✔️🧪
Project Sections → Requirements, Tasks & Test Cases Requirements, Tasks, and Test Cases can all be assigned to a Project Section, providing a structured phase-by-phase view of all work across object types.
✕