John Boyd’s observe, orient, decide, act (OODA) cycle can guide a shop routine: rules for repeat calls in the field, alerts for work that cannot wait, and a weekly slot for decisions that can.
Start with what the crew may decide without calling you. Then decide which events deserve an alert and which questions belong in a scheduled review. The goal is to make routine calls consistent while leaving room to change a rule that fails in practice.
Two Loops, One Business
Use two working rhythms. A technician facing a customer needs a clear boundary now. The owner can review pricing, service radius, and lead sources on a schedule.
In the field, a tech may need to choose between a repair and a replacement or answer a discount request. Write the conditions for an escalation before the call. Leave safety, diagnosis, consent, and the customer’s actual needs to the qualified person on site.
Office decisions can wait for a regular review: dispatch fees, service radius, and lead sources, for example. Compare the same definitions each week, ask what changed, and assign the next check. A schedule is useful because it gives these decisions a place outside the rush of a call.
Set field boundaries in advance; reserve time to revisit them when the record suggests they need work.
Element One: Write the Standing Rules
A standing rule states what a person may do, when to escalate, and who owns the next step. Marine Corps guidance calls for simple, flexible plans, standing procedures, and initiative among subordinates when uncertainty cannot be eliminated. [1]
Start with recurring calls that cause delay or inconsistent answers. Write each rule in language a new dispatcher or technician can use.
Lead response
Choose a response target the office can staff during stated business hours. Assign one person to answer, record the request, and hand it off if unavailable. A five-minute target can be a shop goal, but it is not a universal cutoff that guarantees a booking. Tactical 4 covers lead response.
Pricing floors and discount authority
Give technicians a written range of approved offers and a route to ask for approval outside it. Check the actual job scope before using a price floor. Record discounts so the office can see what was offered and why.
When to walk a job
Write service-area, licensing, capacity, safety, and payment boundaries. If a request falls outside them, explain the reason and route the caller to a person who can review an exception. Do not let a checklist replace a job-specific judgment.
Callbacks and warranty
Set an owner for a warranty or callback request, a first-response target the shop can meet, and a way to document the finding. The appropriate remedy depends on the warranty, the problem, and the facts of the job.
Keep each rule short enough to use on a busy day, but include an escalation path. For estimates, record when the visit leaves the scope ready for pricing and when the written estimate reaches the customer. Assign an owner for the handoff; note waits for approval or supplier prices and tell the customer when a complex estimate will arrive. Review both delivery time and estimate accuracy against actual outcomes before changing the rule. Put the current rules where dispatch and field staff can reach them. Review exceptions rather than judging a technician for following an unclear rule.
Element Two: Wire the Observe Layer
Observation is the first part of the OODA model. For a shop, that means collecting a few actionable signals and naming who receives each one. [2]
Start with four alert categories. Add safety, emergency service, or contractual alerts where your work requires them. Route alerts to an available person rather than assuming the owner can answer while driving or working on site.
New lead: notify the person on intake when a form, call, or chat request arrives. Test delivery and a backup route; do not count a platform notification as a reply to the customer.
New review: check the listing and assign a person to respond. Thank customers where appropriate; investigate complaints before posting a calm public reply. Do not disclose private job details or promise that reply speed changes the rating.
Missed call: log the number and have the intake owner decide whether a text or call back is appropriate. Confirm that automated messages respect consent, opt-outs, and local requirements before switching them on. A missed call is a contact attempt, not a confirmed lost job.
Money out of bounds: flag a job that exceeds its approved estimate, an invoice that reaches the shop’s aging threshold, or a declined payment. Give the office a way to verify the record and choose the next action.
Keep routine updates in a queue for the weekly review. Test whether critical messages reach the right person and restore any notification needed for safety or service. A short alert list helps only when someone actually watches it.
Element Three: Set the Orient Block
Orientation means interpreting what was observed before choosing an action. The weekly review below is an office routine for that work. [2]
Book a recurring block that the owner and dispatcher can keep. Thirty minutes is a starting slot. Reschedule a missed review rather than letting open issues wait indefinitely.
Use the definitions in your Tactical 6 dashboard: incoming leads, answered calls, booked requests, completed tickets, reviews, and receivables. Compare like periods and check the underlying records before treating a change as a trend.
End with a decision log: what changed, which record supports the next step, who owns it, and when to check again. Check the time from scope-ready visit to written estimate, any approval or supplier wait, and whether faster delivery held up against estimate accuracy and booked outcomes. Sometimes the right decision is to collect a missing piece of information. Do not turn one noisy week into a permanent rule.
Element Four: Automate, Systematize, or Rule
Sort recurring work by how much judgment it needs. Software can send a routine notice; a person should handle a diagnosis or a complaint. The categories below help assign responsibility.
Automate a repeatable step after testing its trigger, wording, owner, and opt-out path. An invoice reminder can be scheduled against a verified due date. A missed-call acknowledgment needs suitable consent handling and a monitored reply route. A review request must comply with the review platform’s policies.
Use a checklist for repeatable steps that still need a person: a job walkthrough, closeout, or warranty callback. The checklist should record the finding and make room for exceptions, not force a diagnosis into a script.
Use a standing rule where a person must judge a case inside approved boundaries. Specify price authority, stop-work conditions, and who can approve an exception. Review the rule when field experience shows it misses a common case.
Try one recurring decision in each category, then ask the crew where the handoff breaks. New, high-risk, or disputed calls still need an owner.
Five Moves You Run This Week
Move one: draft a short set of standing rules. Start with lead ownership, discount authority, work boundaries, and callbacks. Name the approver for exceptions and ask the crew to test the wording on recent cases.
Move two: route new leads, reviews, missed calls, and financial exceptions to named owners. Test each alert and its backup. Keep any additional safety or emergency notifications your work requires.
Move three: reserve a weekly review on the calendar. Start with a thirty-minute slot, keep the same dashboard definitions, and move the appointment if a job interrupts it.
Move four: choose one low-risk, repeatable step and test it before enabling it. Confirm the trigger, consent where needed, reply handling, and who fixes a failed run.
Move five: hold the review, record one decision or evidence request, assign an owner and a check date, then revisit it next week. Check that decision against the next week’s records before you change the rule.
Key Takeaways
- Use fast field boundaries and a scheduled office review for different kinds of decisions.
- Write a rule for recurring calls, with an owner and an escalation path.
- Check pricing authority, work boundaries, and callback ownership with the crew.
- Route leads, reviews, missed calls, and financial exceptions; keep safety alerts as needed.
- Log the weekly decision, its owner, and the date for checking the result.
- Automate a tested routine step; use checklists for repeated work with judgment; set rules for field authority.
Write the routine boundary before the next busy day.
Let the crew flag cases the rule does not cover.
Handle urgent work promptly. Give larger changes a scheduled review.
Next in the Series
This guide puts the field and office decision loops into a repeatable routine.
For a recurring competitor file, see Competitor Analysis for Contractors.
Three Ways to Apply the Laws
Free contractor website and competitor audit, with business, market and evidence scope confirmed before acceptance
Competitive intelligence applied during website strategy
Managed Websites built on the intelligence: see current plans and pricing
Start with one rule, one alert test, and one review you can keep.
Commercial disclosure: KKS sells website services for contractors. KKS previously used affiliate links in its articles. This page has no affiliate purchase links.
Frequently Asked Questions
What is a contractor decision framework, in plain terms?
It is a written set of field boundaries, alert owners, and a regular office review. It helps a crew know which calls they can handle and which need an escalation. The owner can adjust the rules as actual cases come in.
How is the field loop different from the office loop?
The field needs clear boundaries for a decision on site or by phone. The office can review pricing, radius, and lead sources on a schedule.
Which notifications should a contractor actually keep on?
Start with new leads, reviews, missed calls, and financial exceptions. Route each to an available owner and test the backup. Keep safety and emergency alerts when required.
How long should the weekly review take, and when should I do it?
Start with a weekly slot that your team can keep. Thirty minutes may be enough for a short dashboard review; longer issues can get their own meeting. Log the decision, owner, and next check date.
How do I decide whether to automate a task or just write a rule for it?
Automate a tested routine step with a monitored reply and proper consent. Use a checklist for repeated work that needs a person. Write a standing rule for judgment calls inside approved boundaries, with an escalation route.
What if I set all this up and still make a bad call?
Review the case at the next office session. Check whether the rule was unclear, the facts were missing, or an exception was needed. Correct the rule or training and check whether the change holds up on later jobs.
Sources
- U.S. Marine Corps, MCDP 1 Warfighting, section on uncertainty. The military guidance informs the analogy, not a claim of contractor results.
- John R. Boyd, A Discourse on Winning and Losing, Air University Press, 2018, discussion of the observation-orientation-decision-action cycle.