Creytix Field

Dispatch, routing and work orders for people who are not at a desk.

A field-service package: work orders with a guarded status machine, scheduling that refuses to double-book, job assignment, route ordering from real distances, and estimates that become invoice drafts.

The day's route is built from where the crew actually is.

What it does for you

  1. Routes from real geography

    Ordering uses great-circle distance with a nearest-neighbour pass and a 2-opt improvement, and the cost function is a seam — swap in drive time when a traffic source is wired, without touching the routing.

  2. A stale position is not a position

    Latest-known locations carry their age and drop out past a staleness threshold. A dispatcher routing to where somebody was two hours ago is worse off than one who knows they do not know.

  3. The status machine refuses the impossible

    A work order cannot jump from scheduled to invoiced. Illegal transitions are rejected rather than recorded, which is the difference between a history and a wish.

  4. Estimate to invoice without retyping

    A price-book estimate converts to an invoice draft whose lines still balance to the total.

Capabilities

Hover or focus a capability to see why it matters.

  • Work orders with a guarded status machine

    Ordering uses great-circle distance with a nearest-neighbour pass and a 2-opt improvement, and the cost function is a seam — swap in drive time when a traffic source is wired, without touching the routing.

  • Conflict-checked scheduling and slot finding

    Latest-known locations carry their age and drop out past a staleness threshold. A dispatcher routing to where somebody was two hours ago is worse off than one who knows they do not know.

  • Job assignment across a crew

    A work order cannot jump from scheduled to invoiced. Illegal transitions are rejected rather than recorded, which is the difference between a history and a wish.

  • Distance-based route ordering (NN + 2-opt)

    A price-book estimate converts to an invoice draft whose lines still balance to the total.

  • Staleness-aware last-known positions

    Ordering uses great-circle distance with a nearest-neighbour pass and a 2-opt improvement, and the cost function is a seam — swap in drive time when a traffic source is wired, without touching the routing.

  • Price-book estimates that become invoice drafts

    Latest-known locations carry their age and drop out past a staleness threshold. A dispatcher routing to where somebody was two hours ago is worse off than one who knows they do not know.

Proof, not adjectives

Package ships and is tested
packages/creytix-field — route, dispatch, schedule, workorder, estimate and pricebook, each with its own test suite.
Conflict detection is real
Scheduling finds overlaps and available slots rather than trusting the caller, so two jobs cannot be booked onto one technician at one time.

Built with Creytix, on Creytix

This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.

Have a code from email or QR?