Home / Product / State tracking

Guide work through a lifecycle

Make the next valid step clear—and preserve how the work got there.

Define the stages an important record may move through, prevent impossible jumps, and keep transition history connected to the subject.

See what it changes Technical guide ↗

State tracking in a product

Start from a known stageDraft, submitted, approved, fulfilled

Choose an allowed eventSubmit, approve, reopen, cancel

Record the new state and historyThe product can explain the path

Important work follows a visible lifecycle

01Prevent impossible transitionsOnly accept movements declared for the current state.

02Create a shared languageGive product and operations the same names for progress.

03Keep transition evidenceConnect the state history to the record it describes.

Why it matters

A status field can say where work is. It rarely says what is allowed next.

A request should not jump from draft straight to completed. A cancelled order should not be fulfilled. When state is just free-form text, every screen and automation must remember the same transition rules.

Daptin lets a resource use a declared state model with an initial state and named events that move it between allowed stages. A transition updates the record's state context and leaves history.

Actions and permissions can then build on that lifecycle: the right people see the right next operation, reports can summarize where work is, and investigations can follow the path.

Make progress understandable

Use meaningful stages that product and operations can discuss.

Stop invalid jumps

Validate the requested event against the record's current state.

Turn history into context

See not only where the record is, but how it moved.

How it fits

Part of one connected backend.

State tracking does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Declare

Name the stages and allowed events between them.

Step 2Start

Create the record in its initial state.

Step 3Transition

A permitted request applies a valid event.

Step 4Remember

Store the new state and its transition evidence.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Approval process

Move a submission through draft, review, approval, and rejection.

Service request

Track received, assigned, in progress, waiting, and resolved.

Content lifecycle

Guide an article from draft to review, scheduled, published, or archived.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes state tracking more useful.

Know the boundary

What Daptin leaves in your hands.

State tracking validates finite transitions; it is not a full business-process engine. Complex branching, timers, compensation, parallel work, and human assignment may require actions or a specialized workflow system.

Understand the operating responsibility →

Build from one foundation

Make state tracking part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities