Built for field pace

Five steps, each on a single key. Enter takes the next action, so a re-solve is a keystroke rather than a tour of the application.

1. 1Inputs

   Load the case or nudge the handful of parameters that change on site.

   clicks 6 → 2

2. 2QC

   Clear the ingest QC verdict for this revision before spending solver time.

   clicks 5 → 1

3. 3Run

   Solve the current revision — one key, no dialogs.

   clicks 3 → 1

4. 4Review

   Read the deltas against the last accepted run.

   clicks 4 → 1

5. 5Iterate

   Queue a tweak and re-solve without rebuilding the case.

   clicks 6 → 1

This is not a drawing. Every frame below is the real field-pace loop being driven one keystroke at a time — the step states, the gating and the recommended next action are read straight out of the code that runs in the app.

1. —
   Open the lane — nothing staged yet · rev 1
2. 1
   Stage the case inputs · rev 1
3. 2
   Clear ingest QC for this revision · rev 1
4. 3
   Solve the revision · rev 1
5. 4
   Read the deltas against the last accepted run · rev 1
6. 5
   Queue a tweak — Rate +10% · rev 1
7. 5
   Apply the tweak · rev 2

   QC clearance carries to the new revision — the parameter changed, the ingested data did not, so there is no second QC round trip.

8. 3
   Re-solve · rev 2

A classic multi-page loop costs 24 clicks per iteration; the fast lane costs 6 — 18 of them removed outright, step by step in the table above. This counts interface actions only — not solver time, which depends on your case.

4 wells, 50 stages each, 80 bpm at 2000 lb/ft — the same planning arithmetic the free calculator runs, not a slide. Change any of it there and these numbers move with you.

On that pad the pumps run 136.3 minutes and the full cycle is 181.3 minutes, leaving 45.0 minutes of wireline, pump-down and plug work. That is the whole decision window — and you are sharing it. At 6 iterations:

Interface minutes assume 3 seconds per action. That is a stated assumption, not something we measured on your crew — the click counts underneath it come from the shipped workflow. Solver time is separate and depends on your case.

Change any number and every figure below moves with it — the same planning arithmetic the free calculator runs, closed form, not a solved simulation. An input that cannot support the arithmetic is refused by name and the answers are pulled off the screen rather than rounded into range.

• Hydraulic horsepower is withheld: no treating pressure was entered, and it is not guessed from the rate.

What the rate does to the day

Where limited entry stops holding

Both tables re-plan your pad above, changing one knob at a time. Limited entry is called held only when perf friction reaches 500 psi — the rule of thumb, not a solved diversion result.