Onboarding

Use this checklist every time you bring a new matter or teammate into TS360. Steps are intentionally generic so the same flow works for light cases and worst-case proof-of-concept reviews — details and evidence stay in your secure processes; here you only wire how you use the app.

Checklist version: v1 — extend lib/ts360-app/onboarding-checklist-v1.ts or add a new version file when the process grows.

• Step 1

• Confirm scope and roles

  Agree who is in scope (e.g. household, matter, counsel) and who may access the workspace. Keep sensitive narratives and identifiers in your secure systems — use TS360 for structured review, not long-form evidence storage in chat.

• Step 2

• Pick the identifiers you will use

  Decide the household id (and optional case id) you will pass into dashboard and Safety Review. Same pattern every time keeps demos and production reviews consistent.

  Open dashboard →
• Step 3

• Document inventory pattern

  For heavy matters, maintain an exhibit list elsewhere (page/Bates, short description). TS360 surfaces timeline and safety-oriented views when Azure procedures return rows — it does not replace your master index.

• Step 4

• Walk the Safety Review flow

  Use Safety Review to see critical signals, linked tasks, related timeline, optional BM party hints, and manual-only escalation actions. Nothing auto-notifies third parties.

  Open Safety Review →
• Step 5

• When ready: live four-database reads

  Turn on Azure connection strings and verify objects with the inspect script. The Case Reconstruction Engine™ (CRE™) checklist on Safety Review shows what is wired vs next.

  See CRE™ checklist →