Crisphive

Built for electrical contractors

Deterministic scheduling for electrical contractors, embedded in the software your crews already use.

Crisphive sits behind your existing dispatch board, CRM, or AI assistant. When a journeyman calls in sick at 6:30 or a commercial power-loss call lands mid-route, it re-cascades panel upgrades, EV-charger installs and inspection appointments across licensed, nearby electricians in under 3 seconds — without missing an inspector window, and without anyone learning a new tool.

Try the sandbox
cascade re-schedule on a call-in
< 3 s
MCP tools for Claude & ChatGPT
43
new screens for dispatchers
0

Every job inside its window

The day Crisphive protects

  • Electrical contractor van with a ladder rack and open rear doors, conduit and wire spools inside, parked at a construction site

    The route

    6–9 jobs a day per van: service calls, panel work, rough-ins timed to other trades. One absent electrician strands the inspection schedule.

  • Gloved hands landing conductors in a commercial electrical panel, multimeter leads clipped to the bus, cover plate leaning against the wall

    The inspection window

    Rough-in and final inspections are booked days ahead with the AHJ. Miss the slot and the GC's whole schedule slides.

  • Electrical drawings spread on a plywood table in an unfinished building, a red pencil and a torque screwdriver holding the pages flat

    The licence

    Master, journeyman and apprentice ratios are law. The solver treats licence tier and supervision as hard constraints.

The problem is statistical, not occasional

Every week, roughly 1 in 30 of your field crew won't show up as scheduled.

Across installation, maintenance and repair occupations, 3.2% of full-time workers miss part of any given week — and 1.7% of all scheduled hours are simply lost. Illness and injury, not vacations, drive most of it.

3.2%
of U.S. full-time workers absent in any given week (2025), up from 3.1% in 2023
BLS, CPS Table 47
4+ days
lost per full-time employee per year — 1.7% of scheduled hours, before vacation and holidays
BLS, CPS Table 47
US$3,600
cost of unscheduled absence per hourly worker per year — about US$36K for a 10-tech crew
Circadian
US$150–300
direct disruption from a single field-tech no-show, before any missed-appointment revenue
U.S. field-ops stat sheet

Weekly absence by field segment

% of full-time workers who worked under 35 h in the reference week for illness, injury or personal reasons · all-worker benchmark 3.2%

  1. Installation, maintenance & repair3.2%
  2. Last-mile delivery & transport3.4%
  3. Facilities / grounds maintenance3.4%
  4. Production / plant3.4%
  5. Skilled trades / construction2.7%
  6. Construction industry overall2.3%

U.S. Bureau of Labor Statistics, Current Population Survey Table 47, 2025 annual averages (11-month average, excluding Oct 2025). Construction reads low partly because unpaid hourly absences go unrecorded.

Planning rule of thumb

1 absent tech per 30, every week

At a 2.7–3.4% weekly absence rate and 1.5–1.9% of hours lost, plan for about one absent technician per 30 in any week and 4–5 lost days per technician per year. The CDC puts absenteeism-linked productivity losses at US$225.8B a year — US$1,685 per employee.

In an electrical shop each no-show is a manual re-plan: the office phones around, licence tiers get guessed, an inspector window slips, a GC's drywall day moves, and the homeowner finds out last. That's the work Crisphive removes — inside the tools you already run.

Sources: BLS CPS Table 47 (2025 annual averages); CDC Foundation, "Worker Illness and Injury Costs U.S. Employers $225.8 Billion Annually"; Circadian, "Absenteeism: The Bottom-Line Killer"; Integrated Benefits Institute ($530B total illness-related lost productivity).

Three ways in — انسخ رابط هذا القسمتم نسخ الرابط

Pick the surface. The same deterministic solver answers behind all three.

Call the solver from your own backend.

Your dispatch system already owns jobs, techs and contracts. Send Crisphive the delta — "tech 04 is out" or "new urgent stop" — and get back a complete, SLA-valid plan to write wherever you keep schedules. Idempotent, deterministic, versioned.

  • Event in, plan out. One call returns reassignments, new start times and a plain-language reason per move.
  • Webhooks for drift. Traffic, overruns and no-shows trigger re-solves you can accept automatically or review.
  • Nothing to host. Constraints and territories live in your tenant; we never see customer data you don't send.

FitsExisting FSM platformsIn-house dispatch toolsVoice agents (Twilio, Vapi, Retell)

POST /v1/solvedeterministic
POST https://api.crisphive.com/v1/solve
{
  "schedule": "2026-10-06/portland-metro",
  "event": { "type": "tech.unavailable",
             "tech": "T-04", "from": "06:30" },
  "constraints": ["certifications",
                  "sla_windows", "drive_time",
                  "daily_capacity"]
}

200 OK  · solved_in: 2.41s · sla_breaches: 0
{ "moves": [
  { "job": "ACME-7781", "to": "T-07",
    "start": "11:30", "shift_min": 240,
    "why": "nearest certified tech
            with window slack" },
  … 3 more ] }

Electrical work, modelled properly — انسخ رابط هذا القسمتم نسخ الرابط

Every service type carries its own credential, duration and window. The solver knows the difference.

  • New 200-amp residential panel mid-install, breakers partly seated, neatly bundled conductors fanning into the enclosure

    Panel upgrade / service change

    Utility disconnect coordination, inspection same day. Anchors a route and needs a journeyman or master.

    Credential
    Journeyman / Master
    Duration
    5–7 h
    Window
    Utility slot
  • Level-2 EV charger mounted on a garage wall with fresh conduit run to it, cable coiled on its holster

    EV charger install

    Permit-driven residential volume with a load calc. Flexible by a day, so the solver uses it as slack.

    Credential
    Journeyman
    Duration
    3–4 h
    Window
    ± 1 day
  • Open commercial breaker panel in a utility room with a clamp meter reading one feeder, flashlight lying on the floor

    Commercial service call

    Tenant-improvement and property-management accounts with contract response times.

    Credential
    Commercial licence
    Duration
    1–2 h
    Window
    4 h SLA
  • Romex cable pulled through drilled studs in open framing, boxes nailed to the studs, sawdust on the subfloor

    Rough-in (new construction)

    Sequenced behind framing and ahead of drywall. A missed day costs the GC, not just you.

    Credential
    Journeyman + apprentice
    Duration
    Full day
    Window
    GC schedule
  • Standby generator on a fresh concrete pad beside a house, transfer switch conduit entering the wall, gravel still raked

    Standby generator

    Gas-fitter coordination, utility interlock, inspection. Two-visit chain with fixed sequencing.

    Credential
    Master + gas cert
    Duration
    6–8 h
    Window
    Fixed date
  • Clipboard with an inspection checklist resting on an open electrical panel, green approval sticker beside it

    Inspection / final

    AHJ inspector arrives in a window. Someone licensed must be on site, nothing else can move it.

    Credential
    Licence holder on site
    Duration
    30–60 min
    Window
    Hard window

What happens in those 3 seconds — انسخ رابط هذا القسمتم نسخ الرابط

Deterministic means the same inputs always give the same plan — auditable, explainable, no surprises at 6:30 AM.

  1. 010.0 s

    Event arrives

    A call-in, an overrun, a commercial power-loss call — from your app, a webhook, a voice agent, or a sentence typed to Claude.

  2. 020.1 s

    Constraints load

    Certifications, SLA contract windows, live drive-time matrix, remaining daily capacity and territory rules for the affected day.

  3. 03< 3 s

    Deterministic cascade

    The engine re-sequences the whole connected day, not just the broken slot, and returns one reproducible plan with a reason per move — zero SLA breaches or it says so.

  4. 04you decide

    Preview, approve, write back

    Humans see every move before it lands. On approve, your system of record is updated and technicians and customers are notified.

Hard constraints the solver carries

  • Licence tier master / journeyman / apprentice ratio
  • Inspection windows AHJ-booked, hard
  • Drive time live traffic matrix
  • Capacity hours, jobs, breaks
  • Trade sequencing GC and utility dependencies
Field electricians40
Jobs per electrician per day7
Average ticketUS$420
Jobs recovered same-day with cascade rescheduling85%

Your assumption, not a benchmark — depends on cert coverage and territory density.

Techs out in a typical week
1.3
3.2% weekly absence rate
Tech-days lost per year
172
4.3 days per tech, illness & personal only
Jobs on absent routes / yr
1,204
7 jobs × lost tech-days
Unscheduled-absence cost / yr
US$144K
Circadian: about US$3,600 per hourly worker per year

Revenue kept on the calendar per year

US$430K

1,204 jobs a year sit on an absent tech's route. At 85% same-day recovery, Crisphive re-sequences 1,023 of them onto certified colleagues instead of a callback queue — plus 129 dispatcher hours not spent phoning around.

Illustrative. Lost tech-days and weekly rates are U.S. benchmarks from the sources above; dispatcher time assumes 45 min of manual re-planning per absent tech-day; recovery rate and ticket size are your inputs. Excludes overtime, backfill and SLA penalties.

Shipping it — انسخ رابط هذا القسمتم نسخ الرابط

Runs in shadow mode next to your current planner until you trust it.

Crisphive reads your jobs, techs, certifications and SLA contracts through the connector you choose, proposes plans beside the ones your team makes by hand, and only writes back once you flip it live. Your system of record stays the system of record.

  1. 1

    Connect days

    Point a connector at your jobs, techs, certs and contracts. Read-only.

  2. 2

    Shadow mode weeks

    Crisphive proposes a plan for every real disruption beside the one your dispatchers make by hand. Compare SLA breaches, drive time and wrench time.

  3. 3

    Go live your call

    Flip write scope on for the surfaces you chose — API, embedded components, MCP, or all three.

More embedded use cases

The same solver, your vertical's constraints