Tools and Features

Decision Studio: Feature-by-Feature Guide

Use every documented Decision Studio feature with sample input and expected output.

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 · Technical Reference

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 is the complete documented feature inventory for Decision Studio version 2.0.0. Every feature includes sample data, a seven-step use pattern, expected output, and a verification rule. Reverify this article whenever the product release changes.

Prerequisites

  • A clean demonstration workspace
  • The downloadable all-feature CSV or JSON
  • Current product release notes
  • Permission to use each tested feature
  • A reviewer familiar with the product

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.

Feature-by-feature procedure

1. Decision Packet

Purpose: Use Decision Packet within the governed Decision Studio workflow.

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

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a versioned packet containing all decision artifacts.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

2. Problem Framing

Purpose: Use Problem Framing within the governed Decision Studio workflow.

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

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a bounded decision statement.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

3. Evidence Ledger

Purpose: Use Evidence Ledger within the governed Decision Studio workflow.

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

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: traceable evidence records.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

4. Scenario Studio

Purpose: Use Scenario Studio within the governed Decision Studio workflow.

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

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a scenario table with aligned measures.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

5. Impact Records

Purpose: Use Impact Records within the governed Decision Studio workflow.

Sample action: record cost, emissions, comfort, disruption, and equity effects.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: structured impact entries.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

6. Claim Review

Purpose: Use Claim Review within the governed Decision Studio workflow.

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

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

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

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

7. Finance Tradeoffs

Purpose: Use Finance Tradeoffs within the governed Decision Studio workflow.

Sample action: compare capital, operating, lifecycle, and uncertainty considerations.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a transparent tradeoff record.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

8. Risk and Recovery

Purpose: Use Risk and Recovery within the governed Decision Studio workflow.

Sample action: record contractor delay, budget overrun, rollback, and recovery.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a risk register with owners and mitigations.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

9. Assumption Register

Purpose: Use Assumption Register within the governed Decision Studio workflow.

Sample action: record 3% annual tariff growth with source and confidence.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a versioned assumption.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

10. Workbench Handoffs

Purpose: Use Workbench Handoffs within the governed Decision Studio workflow.

Sample action: request lifecycle-cost and emissions calculations.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a returned calculation artifact and receipt.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

11. Readiness Review

Purpose: Use Readiness Review within the governed Decision Studio workflow.

Sample action: check evidence, privacy, unresolved issues, and approval requirements.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: an advisory readiness report.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

12. Briefing Studio

Purpose: Use Briefing Studio within the governed Decision Studio workflow.

Sample action: assemble a board briefing from reviewed packet sections.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: an executive brief.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

13. Publication Studio

Purpose: Use Publication Studio within the governed Decision Studio workflow.

Sample action: prepare a redacted public decision summary.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a controlled publication artifact.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

14. Outcomes Monitoring

Purpose: Use Outcomes Monitoring within the governed Decision Studio workflow.

Sample action: track six months of post-retrofit energy and comfort data.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: outcome records and variance explanations.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

15. Reassessment

Purpose: Use Reassessment within the governed Decision Studio workflow.

Sample action: reopen the decision after grant or outcome changes.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a new review cycle preserving history.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior state.

16. API and Embeds

Purpose: Use API and Embeds within the governed Decision Studio workflow.

Sample action: expose an approved public packet summary.

Steps

  1. Open or create the synthetic retrofit workspace.
  2. Select or navigate to this feature.
  3. Enter the matching row from the CSV or JSON sample.
  4. Review required fields, sources, units, permissions, assumptions, and warnings.
  5. Run or save the feature operation.
  6. Compare the result with the expected result below.
  7. Add a review note and preserve the feature state.

Expected result: a scoped privacy-aware JSON or embed.

Verification: The result must preserve the sample feature ID, product version, lifecycle state, provenance, and any domain-specific unit or classification. Failure must return an actionable error without destroying prior 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 transparent tradeoff record
  • a risk register with owners and mitigations
  • a versioned assumption
  • a returned calculation artifact and receipt
  • an advisory readiness report
  • an executive brief
  • a controlled publication artifact
  • outcome records and variance explanations
  • a new review cycle preserving history
  • a scoped privacy-aware JSON or embed

Whole-product verification

  • All 16 documented features are present or intentionally permission-restricted.
  • Every feature accepts its synthetic row or explains why it does not apply.
  • Errors preserve saved state and provide a recovery path.
  • Exports and handoffs retain provenance and version identity.
  • No private, confidential, or secret information appears in public output.

Responsible use

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

Scroll to Top