Start Here

Decision Studio: Getting Started

Start using Decision Studio with a controlled example.

ProductDecision StudioVerified version2.0.0ComponentAPI and Embeds, Assumption Register, Briefing Studio, Claim Review, Decision Packet, Evidence Ledger, Finance Tradeoffs, Impact Records, Outcomes Monitoring, Problem Framing, Publication Studio, Readiness Review, Reassessment, Risk and Recovery, Scenario Studio, Workbench HandoffsUpdatedJuly 17, 2026Reading time18 minutes
← Back to product guides

Decision Studio · Getting Started

Auditable decision packets, evidence, scenarios, tradeoffs, risk, briefing, publication, monitoring, and reassessment.

Audience: product users, administrators, reviewers, and integrators.

Last verified version: 2.0.0

Reading time: 18–30 minutes

Status: Published support documentation.

Purpose

This guide provides a safe first run of Decision Studio. It explains the product role, the main feature surface, the synthetic demonstration dataset, how to recognize a valid result, and when human or expert review is required.

Capability overview

  • Decision Packet
  • Problem Framing
  • Evidence Ledger
  • Scenario Studio
  • Impact Records
  • Claim Review
  • Finance Tradeoffs
  • Risk and Recovery
  • Assumption Register
  • Workbench Handoffs
  • Readiness Review
  • Briefing Studio
  • Publication Studio
  • Outcomes Monitoring
  • Reassessment
  • API and Embeds

Prerequisites

  • A modern supported browser or runtime
  • The current installed product and service version
  • A new demonstration workspace
  • No confidential, personal, credential, or production information
  • A named reviewer for consequential output

Sample data

This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.

Download CSV feature examples · Download JSON workspace example

Preview

# Feature Sample action Expected result Classification
1 Decision Packet create DS-RETROFIT-001 for a community-center retrofit choice a versioned packet containing all decision artifacts synthetic-demo
2 Problem Framing define the decision, scope, objectives, constraints, stakeholders, and deadline a bounded decision statement synthetic-demo
3 Evidence Ledger add utility bills and an engineering assessment with relevance and confidence traceable evidence records synthetic-demo
4 Scenario Studio compare no action, controls-only, and whole-building retrofit a scenario table with aligned measures synthetic-demo
5 Impact Records record cost, emissions, comfort, disruption, and equity effects structured impact entries synthetic-demo

The downloadable files include all 16 feature rows.

Procedure

  1. Open the product from its canonical Sustainable Catalyst page or administrative route.
  2. Confirm the product and backend version before creating data.
  3. Create a synthetic workspace named DECISION-STUDIO-RETROFIT-001.
  4. Download the CSV and JSON examples supplied below.
  5. Use the feature matrix to complete the first six feature checkpoints.
  6. Save, close, and reopen the workspace to verify persistence.
  7. Inspect warnings, sources, units, permissions, and lifecycle state.
  8. Export or hand off only after completing the verification checklist.

1. Decision Packet

Action: create DS-RETROFIT-001 for a community-center retrofit choice.

Expected result: a versioned packet containing all decision artifacts.

2. Problem Framing

Action: define the decision, scope, objectives, constraints, stakeholders, and deadline.

Expected result: a bounded decision statement.

3. Evidence Ledger

Action: add utility bills and an engineering assessment with relevance and confidence.

Expected result: traceable evidence records.

4. Scenario Studio

Action: compare no action, controls-only, and whole-building retrofit.

Expected result: a scenario table with aligned measures.

5. Impact Records

Action: record cost, emissions, comfort, disruption, and equity effects.

Expected result: structured impact entries.

6. Claim Review

Action: review the claim that the project pays back in five years.

Expected result: a supported, contested, or unresolved claim state.

Expected output

  • a versioned packet containing all decision artifacts
  • a bounded decision statement
  • traceable evidence records
  • a scenario table with aligned measures
  • structured impact entries
  • a supported, contested, or unresolved claim state
  • A saved record that reopens without data loss
  • An export or handoff that identifies product, version, artifact, source, and review state

Verification

  • Every sample value remains attached to its identifier and classification.
  • Warnings remain visible and are not silently treated as approval.
  • The saved workspace reopens in a clean session.
  • The product and version shown in output match the installed release.
  • Another reviewer can understand how the output was produced.

Responsible use

The product organizes evidence and reasoning; accountable decision owners, due process, experts, and institutional approvals remain necessary.

Scroll to Top