Documentation / Docs

Overview

The shortest useful explanation of what TrialStack is, how the product is organized, and how to read the docs.

Keep important work reviewable

flowchart LR
    Files[Disconnected files and notes] --> TrialStack[TrialStack]
    TrialStack --> Governed[Governed workflow]

TrialStack helps teams run trial-facing work in a system where records, relationships, history, and review boundaries stay visible. It is designed for work that becomes risky when it lives only in files, messages, and ad hoc approvals.

Understand more than one page

mindmap
  root((Why teams use it))
    Governed records
    Connected context
    Reviewable workflows

That gives teams a practical advantage:

  • the important records stay in one governed model
  • related context remains connected instead of reconstructed later
  • review, approval, history, and AI-assisted work can be understood in the same workflow language

Read the product as a system

flowchart LR
    TrialStack[TrialStack] --> Assets[Assets]
    TrialStack --> Connections[Connections]
    TrialStack --> Tools[Tools]
    TrialStack --> Workflows[Workflows]
    TrialStack --> General[General]

The product is easiest to read in six buckets:

  • Start for orientation and rollout
  • Assets for governed records such as trials, documents, and evidence packs
  • Connections for organizations, sites, people, systems, and their relationships
  • Tools for actions, runs, knowledge, rules, and templates
  • Workflows for the cross-cutting operating ideas behind the product
  • General for workspace-level oversight and administration

Start with one real workflow

flowchart TD
    Team[New team] --> Overview[Overview]
    Overview --> Quickstart[Quickstart]
    Quickstart --> FirstRecord[First record or workflow]

Most teams should read this page, then move straight to Quickstart and the first asset pages they will actually maintain. TrialStack becomes much easier to understand once the team reads one real record flow end to end.