Use the claims workspace
Work inside the claim detail surface so evidence, next actions, communications, and operational context stay together instead of being reconstructed across separate screens.
Guide
Create your first claim
Create your first live claim in claimOS so the team can move from setup into real execution without getting stuck in unnecessary data entry or unowned records.
Outcome
What this helps you do
Get one claim into the system with enough structure for the team to assign work, review evidence, and act on it immediately without treating intake like a paperwork exercise.
This guide is written for all teams and uses real claimOS screenshots so the instructions map cleanly to the product surface.
Prerequisites
Before you start
- An active workspace.
- Basic claim details or intake information.
- A clear owner for the first real follow-up action.
- At least one piece of supporting context or evidence if you want to validate downstream workflows.
Steps
How to do it
1Start from the guided claim path
Start from onboarding or the standard intake path so the first claim enters the system through the same creation flow your team will use later.
2Choose the owner and claim context before you overfill the form
Decide who should own the next real action and what kind of claim is being opened before you spend time enriching fields that do not affect immediate execution.
3Capture the minimum viable claim details
Add only the fields that unblock downstream work first. The record can become richer after the first pass once the team has ownership and context.
4Attach the first useful evidence or intake context
If you already have notes, photos, or communication context, attach the first high-value items now so the record starts with something the next operator can trust.
5Assign the next action immediately
Once the claim exists, create or route the first task so the new record does not sit as unowned inventory.
6Verify the record in the claims workspace
Open the claim detail view and make sure files, communications, and follow-up actions have a clear place to land.
7Run a readiness check before you leave the record
Before you move on, confirm the claim has an owner, a next action, a due expectation, and enough context that another teammate could pick it up without a hallway explanation.
If the first claim feels like a shell record with no obvious next step, fix that immediately. Early trust in claimOS comes from seeing real work move, not just seeing a record created.
Screenshots
See the workflow
Watch the paired walkthrough
Walkthrough0:48
See the same workflow in motion
A short buyer-facing walkthrough of how claimOS turns launch readiness into the first live claim without losing momentum, context, or team trust.
See how claimOS points the team from launch readiness straight into the first live workflow instead of leaving them to figure out the handoff manually.
Watch related walkthroughFAQ
Common questions
What if I do not have every claim detail yet?
Create the record with the minimum viable details that let the team own the work and collect the rest in the next step. The first claim should unlock execution, not wait for perfect intake.
Should I upload evidence during the first claim pass or later?
Add the first high-value evidence as soon as it exists so the claim has context right away, then continue filling out the file as the work develops.
Who should own the first live claim?
Choose the person or role that will take the next real action. A claim without a clear owner usually turns into hidden inventory instead of useful operating work.
Keep Going