# What is Floxar? Bits, flows, trails, and references

> Floxar is a platform for turning your team's processes into interactive, step-by-step workflows. Instead of writing a procedure into a static document that people read once and set aside, you build it as a guided experience: a person follows the process one step at a time, records their answers and decisions as they go, and Floxar keeps a complete record of every run.

Floxar is a platform for turning your team's processes into interactive, step-by-step workflows. Instead of writing a procedure into a static document that people read once and set aside, you build it as a guided experience: a person follows the process one step at a time, records their answers and decisions as they go, and Floxar keeps a complete record of every run. Four concepts make this work: bits, flows, trails, and references.

## Bits: the building blocks

A bit is the smallest unit of process content in Floxar — a single, focused step. Each bit holds rich content such as text, headings, lists, images, and video, together with interactive elements like checklists, dropdowns, text fields, and date pickers. These elements are what make a step actionable rather than just readable: when someone works through the step, what they select or type is captured automatically. Bits are independent building blocks — a bit is authored and maintained on its own, and the same bit can be connected into more than one flow, so a shared step only needs to be written once.

## Flows: steps connected into a process

A flow is a navigable sequence of connected bits — in other words, a workflow or process template. Every flow begins at a designated start bit. From each bit, connections point to the possible next steps; when a bit has several outgoing connections, the person running the flow chooses which path to take. This is how a single flow can handle branching situations, such as different handling for different case types. Flows can also be tagged with categories, which makes them easier to organize, filter, and find.

## Trails: a record of every run

A trail is the record of one person's journey through a flow — a single run of the process. When you start a flow, Floxar creates a trail for you. As you move from step to step, the trail captures each bit you visited, the answers and inputs you provided, and the time you spent. Trails are flexible about how work actually happens: you can pause a trail and resume it later, hand it over to a colleague, or leave it in a shared queue for someone else to pick up. A trail ends when it is completed or abandoned, and its full history remains available afterwards so the work can always be reviewed.

## References: supporting knowledge

References are read-only supporting documents that back up your process content — policies, guides, FAQs, definitions, and similar material. They are written with the same rich-text tools as bits, but they contain no interactive elements and are never steps themselves. Instead, references are linked to bits, and while running a flow you can open a linked reference in an overlay to check the details without losing your place. References are also searchable alongside bits and flows, so supporting knowledge stays easy to find.

## Putting it together

Teams use Floxar to document their processes as executable workflows and then actually run them. Authors create bits and connect them into flows; people execute those flows, producing trails; references supply the background knowledge each step relies on. Because every run is recorded as a trail, you get consistency while the work happens and a reliable execution history afterwards — who did what, which path they took, what they entered, and how long it took.

*Last reviewed: 2026-07-28*