Operational command software Built from 40 years of field discipline
Call (714) 476-6485

Product capabilities

Field Muster is a fully integrated operational command system — not a single-point app. Every module feeds the Cockpit and closes the loop from detection to recovery.

3-Stage Dispatch

Men & equipment

Assign and reassign with full visibility into who is on site now, who is scheduled in, and who is leaving — for both manpower and equipment.

  • Manpower search by skill, trade, and title (e.g. skid-steer operator, own vehicle, English-speaking)
  • Personnel profiles: contact data, tools, licenses & expirations, discipline/awards, photos
  • Equipment: utilization, costs, repair history, rental hourly cost, return-date alerts, transport specs
  • Automatic move lists with notes and instructions for each transfer
  • Filter large rosters by static vs. in-motion assignments

PACE Production

Core IP

Track projects by task using hours per unit or units per hour. Catch issues in the single-digit percent complete stage — when recovery still works. See the Recovery Impact Curve for why that early window matters.

  • Required speed and recovery rate when behind
  • Heading: projected dollars under or over budget
  • Production Value (PV): what an estimated labor dollar is actually costing
  • Automatic threat flagging across active tasks
  • Estimating feedback loop from real field performance

Job Site Walk

OODA loop

Job Site Walk is Field Muster’s OODA loop in the field — Observe, Orient, Decide, Act. A finite set of conditions impact production. JSW lists active tasks by speed, surfaces red flags, and forces a complete decision cycle before the recovery window closes.

  1. O Observe See the job as it is: tasks ranked by speed, red flags on the surface.
  2. O Orient Name the production-impacting condition from the editable library.
  3. D Decide Decide an action, allocate accountability. Person in charge (PIC) and a drop-dead date — here all threats are captured.
  4. A Act Execute the recovery. Overdue items escalate to the HIT LIST.
  • Editable library of production-impacting conditions
  • Assign cause, required action, PIC, and drop-dead date
  • Example: other-trade interference → draft GC letter → PIC–PM → drop-dead date
  • Overdue items escalate automatically to the HIT LIST — and the next Observe cycle restarts the loop
  • Three-day recon — a superintendent / foreman checklist for the next three days: what to expect and what to prepare for. Because typically the dust of production is three days thick.
  • Job site meeting agenda template for meetings with the GC or other contractors on site

HIT LIST

Production agenda

The company’s living production agenda — the backbone of weekly production meetings.

  • Tracks overdue actions from Job Site Walk and direct HIT LIST items
  • Shows best-guess % complete on recovery actions in progress
  • Surfaces on the Cockpit when drop-dead dates pass
  • Completes the OODA loop: loss ID → required speed → action → owner → follow-up

Cockpit (Home Page)

Executive view

The operational arm of the company at a glance — built for control, not passive reporting.

  • Men and equipment in motion between jobs
  • Per job: onsite / incoming / outgoing crew counts
  • Rental count vs. owned equipment count
  • Heading (projected dollars over or under budget in thousands), % complete, % of labor spent, Production Value
  • Broke date, liquidated-damages drop-dead date, crew day balance
  • Dispatched wage vs. estimated wage
  • HIT LIST actions and equipment return alerts

Contract Progress Log

Pre-job discipline

Static pre-job preparation checklist (~19 actions) — schedule complete, move-on dates, shop drawings, and more — tying project management readiness to field operations.

Utilities & Order of Production

System foundation

Cost codes, roll-up codes, skills/trades/titles, equipment categories, and a graphic Order of Production showing % complete, % spent, and schedule progress — with Production Value (PV) on each project for portfolio-level command.

Trends & Production Value

Core IP · Claims

The Trends chart documents the cost of an estimated labor dollar based on Production Value (PV), allowing a quick assessment of production loss and its impact. From there, that timeline is proprietary operational advantage — and the backbone for production-impact claims.

  • Baseline at one dollar (1.00): the estimated intended cost of each labor dollar spent to that point
  • Strong PV below 1.00 (more production per dollar) vs. loss above 1.00
  • Hover audit dates on trend points to open Job Site Walk conditions for that day
  • Builds a dated record of interference, recovery, and production impact for claims support — and displays for the operations staff the production flow of the project
A day in the life

Fourteen command tasks. Ten minutes, fifteen seconds.

The same modules above are what a general superintendent of a self-performing specialty contractor actually runs every day — timed with a stopwatch on Field Muster. Simulation: 100+ men in the field, 15 active projects.

00:00:20

Move five men and post the dispatch.

00:00:09

Name the worst labor-dollar loss — project and task.

00:00:41

Place the bilingual operator with a car for Tuesday.

00:10:15

The full command day, timed end to end.

Without Field Muster, most of these answers live in other people’s heads, other people’s spreadsheets, or a briefcase that is not in the truck. On Field Muster they are already on the superintendent’s screen.

# Typical superintendent task On Field Muster Watch
1 Relocate 5 men from one job to another and update the dispatch posting 00:00:20
2 Rent a piece of equipment, edit the dispatch, and post estimated return date and rental rate 00:01:13
3 Review all 8 outside rentals and evaluate total rental charges per unit 00:00:35
4 Trucking company on hold: pull transport specs for the excavator being moved 00:00:26
5 Reference all down equipment and review expected “up” dates 00:00:30
6 Dispatch 4 pieces of equipment off a shut-down project and generate the move list 00:00:20
7 Document 6 projects too muddy to work due to rain 00:00:22
8 Compare dispatched wage to budgeted estimated wage on every dispatched project and find the busts 00:00:26
9a Identify the project projecting the worst labor-dollar loss 00:00:06
9b Identify what part of that project is projecting the worst dollar loss 00:00:03
9c Communicate required actions to support staff to resolve or minimize those losses 00:01:36
10 Update percent complete by telephone interview with the foreman in charge 00:00:54
11 Review the contract with a foreman who has questions on scope 00:00:26
12 Review all outstanding back orders and contact the staff member handling each 00:01:32
13 Review an employee file for past discipline and confirm probation or further action 00:00:37
14 Locate and assign an employee with a specific trade who is bilingual, owns a car, and can operate a specific machine next Tuesday — then post the move 00:00:41
Stopwatch total — office or field 00:10:15

Timed by the builder of Field Muster on the live platform. Individual task times are as recorded; the 10:15 figure is the end-to-end stopwatch for the full set. How valuable is your superintendent’s time?

Inside the platform

Command views from the live system

Representative screens from Field Muster — not print-final polish, but the real operational surfaces buyers and partners evaluate. Demo project sets can be reloaded for acquisition walkthroughs.

Cockpit · Home Executive command grid Per-job onsite / incoming / outgoing crew, equipment, Heading, % complete, % spent, PV, broke and LD dates, crew day balance, dispatched wage vs. estimated wage, plus manpower/equipment moves and HIT LIST recovery actions. Click to enlarge.
Order of Production Portfolio production graph Projects ranked with PV, % spent, quantity % complete, and % to schedule — the graphic Order of Production view for portfolio health and acquisition demos (full project reload available for walkthroughs). Click to enlarge.

Click any screenshot to expand. Framework reference only — final print/web marketing assets can be recaptured after demo data refresh and UI polish.

Why early detection wins

Recovery Impact Curve — nip it in the bud

When a task is already 20% off plan, the remaining work must run faster to finish on budget. Catch that loss early, and recovery is realistic. Catch it late, and the math becomes impossible.

PACE does not wait for mid-task surprises. It surfaces required recovery rate while the task is still in single-digit percent complete — the window where a small pace change still fixes the loss.

@ 10% complete

Only ~2% faster than plan

A 20% loss found early needs just 2.3% more speed than the original estimate — or about 23% faster than the current (slow) pace. Recovery is still attainable.

@ 50% complete

Now 25% faster than plan

The same 20% loss at halfway requires 25% faster than estimate (50% faster than current pace). Recovery is still attainable — but you’ll need to pull a rabbit out of your hat.

@ 80% complete

400%+ — effectively lost

Late discovery demands 400% faster than estimate (about 500% faster than current pace). Your time is up. That is not a recovery plan. That is damage control.

Required recovery speed vs. when the loss is found

Scenario: 20% production loss on a task. Y-axis shows how much faster than the original estimate the remaining work must run to recover.

Chart scale caps at 100% for readability. At 80% complete the true required rate is ~400% faster than estimate — shown as the red off-scale marker.

Recovery rates required when a 20% production loss is recognized at different percent-complete stages
Loss recognized at Faster than estimate Faster than current pace Practical meaning
10% complete 2.3% 23% Nip it — small adjustment still works
20% complete 5.3% 26% Still highly recoverable
30% complete 9.4% 31% Manageable with focused action
50% complete 25% 50% Hard — needs real recovery plan
60% complete 42.9% 71% Severe — few crews can sustain this
70% complete 87.5% 125% Nearly impossible in the field
80% complete 400% 500% Loss is locked in

Illustrative recovery math for a fixed 20% production loss on a single task. Field Muster’s PACE engine calculates required speed and recovery rate from live field performance so superintendents act while the early window is still open.

Cross-category replacement

One platform instead of a tool stack

Field Muster consolidates capabilities that companies often buy as separate products.

Category Typical tools Field Muster
Workforce / dispatch Assigner-class tools, spreadsheets 3-stage dispatch + skill search + move lists
Production tracking HeavyJob / B2W-class, custom sheets PACE + Heading + Production Value
Field documentation Daily report apps Job Site Walk OODA loop + conditions + actions
Executive dashboards BI + PM suite dashboards Cockpit + HIT LIST agenda
Equipment control Fleet tools + rentals trackers Utilization, rentals, repair, return alerts

Walk the Cockpit with us

We’ll demo dispatch, PACE, Job Site Walk, and HIT LIST using scenarios that match how you run work.

Call Request demo