Skip to main content
Cases are the fundamental building blocks of FTS. Each case documents a specific operational problem, solution, or best practice in your technical operations with structured evidence and review workflows.

​
What is a Case?

A case is a self-contained knowledge record containing:
  • Title: A clear, descriptive headline
  • Body: Detailed narrative explaining the problem, solution, or process
  • Evidence: Supporting files (photos, logs, PDFs, measurements)
  • Tags: Custom labels for organization and discovery
  • State: Tracks the case through its lifecycle

​
Case Lifecycle

Cases progress through five distinct states:

Draft

Initial creation. Only visible to creators and their team. Edit freely.

In Review

Submitted for review. Assigned reviewers examine and provide feedback.

Verified

Approved by reviewers. Considered reliable knowledge ready for publication.

Published

Active in your knowledge base. Discoverable via search and browsing.

Deprecated

Marked as outdated. Archived for historical reference, not recommended for new use.
You can move cases backward through the lifecycle to fix issues. For example, move Published → Draft to revise based on new findings.

​
Creating a Case

Click New Case in the dashboard. You’ll enter:
  1. Case Title – Be specific and descriptive
  2. Body – Use markdown for formatting. Include context, steps, outcomes, and lessons learned
  3. Tags – Assign custom tags for filtering and search
  4. Evidence – Attach supporting files (optional initially; add anytime)
Use templates if your workspace has them. Templates pre-populate sections like “Incident Description,” “Root Cause,” and “Resolution Steps” to standardize knowledge capture.

​
Editing Cases

Edit cases in Draft or In Review states by clicking the Edit button. Published cases require moving back to Draft first. All edits create an audit trail visible in the case’s activity log.
Once a case is Published, other team members may be relying on it. Always check the audit log before making significant changes.

​
Case Templates

If your workspace admin has created case templates, you’ll see template options when creating a new case. Templates are designed for specific scenarios (e.g., “Equipment Failure Analysis” or “Process Improvement”). Using a template:
  • Pre-fills common sections and structure
  • Ensures consistency across similar cases
  • Speeds up case creation

​
Audit Log

Every case maintains a complete history. Click Activity in the case view to see:
  • Creation and modification timestamps
  • Who made each change
  • State transitions (Draft → In Review, etc.)
  • Comments and reviewer feedback
This transparency ensures accountability and helps you trace how knowledge evolved.

​
Best Practices

Instead of “Equipment Issue,” use “Motor Bearing Failure: XYZ-2000 Unit, March 2026.”
Explain not only what happened but why it matters and what was learned.
Don’t wait until review. Attach photos, logs, and measurements as you document.

​
Next Steps

Evidence

Learn how to attach and organize supporting files.

Review Workflow

Understand how cases move through approval cycles.