The sample workspace is a single complete real-world workflow pre-loaded into your tenant — one sample customer with users, fee schedule, customer representatives, default claim settings, financial defaults, and 2–3 fully completed sample claims. Each sample claim has every field populated: status history, time logs, documents, photos, invoices, payment records, audit trail. The idea is that your team has a real working example to look at and copy when they're configuring their own first client and running their own first claims. It's a template, not a sandbox separate from your live data.
What's actually in the sample workspace
A single complete client workflow, fully populated:
A sample customer (client company) — the carrier or program manager whose work the sample represents.
Sample users — adjusters, supervisors, reviewers, claims reps with role-based access pre-configured so your team can see how the access controls play out.
A sample fee schedule — the billing structure for the sample client's claims, with adjuster payouts wired in.
Customer representatives — sample contacts at the client side, with the customer-portal access pre-set so your team can see what the client sees.
Default claim settings — claim status types, color coding, alert rules, document categories, template letters all configured for the sample client.
Financial defaults — invoice templates, AR aging behavior, fee mapping all set up.
2–3 fully completed sample claims — each one walked all the way through the lifecycle from intake to close. Every photo uploaded. Every diary entry logged. Every status change recorded. Every invoice generated. Every payment posted. Every report runnable. The tracking, documents, logs, and audit trails are all there.
The point is to give you a real-world reference. When your team is configuring your first actual client, they can open the sample to see exactly how a complete client should look in the system. When they're running their first real claims, they can open one of the sample claims to see how a finished file should be populated, what a clean fee schedule application looks like, how a properly tagged document set is organized, what a complete invoice and payment chain looks like.
How it relates to your real data
The sample lives in your tenant alongside your real client and claim records. It is clearly labeled as sample data — not hidden, not in a separate environment, just identifiable as the example template it is. Your real claims, real clients, real users, and real billing live alongside the sample without overlap.
Some operations leave the sample in place permanently as a reference for new staff training. Others delete or hide it once the team is comfortable with the workflow. Either approach is fine; the sample is yours to use as long as it's useful.
Why this approach instead of a pure sandbox
A separate sandbox environment that's totally isolated from your live tenant has two problems: it requires double the configuration to be useful, and the team treats it as "the trial" rather than "how the real system works." A pre-loaded sample inside your live tenant gives your team something concrete to copy from while they're working their actual first claims, so the lessons transfer directly into the real workflow.
It also means the sample is the same shape as your live data — same workflows, same field structure, same integration touchpoints. If you have a question about how a specific field should be populated on a real claim, you go look at the sample claim and see exactly how it was done.
Training new staff later
The sample workspace stays available as a reference for new hires. Onboard a new adjuster, supervisor, or claims rep against the sample data first — they walk through a fully completed workflow before they touch a live claim. New staff training doesn't require building artificial test cases; the example is already there.
Related questions
What does the onboarding process actually look like?
How long does setup take from sign-up to working real claims?
Can I migrate my existing claim data into FileTrac, and how?
What does training look like for adjusters who aren't tech-savvy?
What kind of support do I get, and how fast do you respond?