Sample — worked example, not a client engagement

Sample — worked example built on a hypothetical operation, not a client engagement.

Operations review · sample deliverable

This is what an operations review looks like.

Worked example — a hypothetical five-person landscaping operation, not a client engagement.

Before you spend a dollar, see the deliverable. This page is a worked example built on a hypothetical five-person landscaping operation — Patriot Landscape, the same modelled business as the job-costing example. The map, the findings, the fix list: this is the shape of what you'd receive.

See how work flows Email about a review

The setup

The engagement

Patriot Landscape is a modelled five-person operation: an owner who answers the phone, drives out to look at every job, and quotes on the spot, plus a four-person field crew that runs one truck. The work is good and the schedule is full — the question an operations review asks is what happens between the jobs: how a phone call becomes a quote, how a quote becomes a crew on a lawn, and how a finished lawn becomes money in the bank. A review like this runs on what already exists — a ride-along or two, the estimate book, the crew's text threads, the dates on last season's invoices — no new software, nothing installed, nobody's day interrupted for long.

The map

How work flows today

Every job at Patriot moves through the same three stretches. The gold markers are the friction points — the places where the model says work slows down, leaks scope, or waits on one person. Each marker links to its finding below.

  1. Getting the job

    1. Call comes in Always to the owner's cell — evenings included.
    2. Owner drives out and quotes on the spot No rate sheet in the truck; the number comes from experience and memory. Quoted from memory

  2. Doing the job

    1. Job lands on the whiteboard A name, an address, and a day — photographed each morning.
    2. Crew heads out What was promised at the quote never travels with them — scope arrives by text, mid-job. No handoff record
    3. Work gets done Hours and extras live in the foreman's head until Friday.

  3. Getting paid

    1. Invoice goes out — eventually Invoicing is the owner's Sunday-morning job, so finished work waits for the weekend. Waits for the weekend
    2. Payment arrives Checks, mostly — logged whenever the envelope gets opened.

Select a numbered friction point to jump to its finding — it will also light up the matching recommendation further down.

What the review surfaces

Findings

Findings 1–3 correspond to the marked friction points on the map. Nothing here comes from opinion — each one names the records an actual review would draw on to show it.

Sample findings — a modelled operation, not a client's records
Finding What the review would draw on Severity
Jobs are quoted from memory Last season's estimate book against the hours the crew actually texted in. In the model, near-identical jobs carry different prices depending on the day the owner stood on the lawn. High
No handoff record between estimate and crew The morning text threads. Scope promised at the quote — the extra bed, the haul-away — reaches the crew mid-job or not at all, and the model projects it as return trips and unbilled extras. High
Invoicing waits for the owner's weekend The dates on last season's invoices, which cluster on Sundays. Work finished early in the week sits unbilled until the weekend — and a busy weekend pushes it to the next one. High
The schedule is a whiteboard photo A week of those photos, laid side by side. Jobs get reshuffled by whoever writes last, and the truck criss-crosses town serving far-apart jobs on the same day. Medium
Materials are bought job-by-job The supplier receipts: repeated small runs to the yard for mulch, stone, and fuel — paying walk-in prices and burning crew time on every trip. Medium

What to do about it

Recommendations

Ordered by effort against impact, not by ambition. The first three are paper-and-habit changes a crew can absorb in the first two weeks; the rest can wait until those stick. Each one is tied to the finding it fixes.

The first two weeks

  1. Put a one-page rate sheet in the truck

    Standard prices for the jobs Patriot quotes most, worked out once from what the work really takes instead of recalled on a stranger's lawn. Quoting gets faster, and two similar jobs stop getting two different numbers.

    Effort: Low Impact: High Fixes finding 1

  2. Give every job a ticket that travels

    One sheet — paper is fine — written at the quote and handed to the crew: scope, price, and the extras that were promised. The morning text thread stops being the source of truth, and unbilled extras stop leaking.

    Effort: Low Impact: High Fixes finding 2

  3. Invoice the day the job closes

    A phone template the foreman can send from the truck before it leaves the curb, instead of a Sunday pile on the owner's desk. The job ticket from the previous fix already holds everything the invoice needs.

    Effort: Medium Impact: High Fixes finding 3

After that

  1. Plan the week by neighborhood, not by whiteboard

    A simple week plan that groups jobs by area, set once on Friday. The whiteboard survives as the day's view; it just stops being the plan. Less windshield time, fewer last-writer-wins surprises.

    Effort: Medium Impact: Medium Fixes finding 4

  2. Set up a standing supplier order for staples

    The materials every week uses — mulch, stone, fuel — ordered on a schedule at account terms instead of bought walk-in, job by job. Fewer yard runs, and the crew stays on the lawn it's billing for.

    Effort: Low Impact: Medium Fixes finding 5

The deliverable

What you get

  1. A written review in plain language — the findings and what each one rests on, like the table above, sized to your operation.
  2. A map of how your work flows today — from first call to money in the bank, with the friction points marked.
  3. A prioritized fix list — effort against impact, with a first-two-weeks plan your crew can actually absorb.
  4. The paper tools the plan calls for — whatever the first fixes need: a job ticket, a rate-sheet skeleton, an invoice template.
  5. A walkthrough call — we go through the whole thing together, and you keep every document.

An operations review is a structured look at how work gets scheduled, handed off, and tracked — and where jobs fall through the cracks. It runs on the records you already have and ends in the deliverable this page just walked you through.

$500–$1,500

Fixed price, quoted before work begins — typically two to three weeks from kickoff to walkthrough.

Email about a review See all services

Patriot Landscape is a hypothetical operation built as a worked example — not a client, and not a real business. Every finding on this page describes the model, every quantified claim is what the model projects, and no figure here is a client result. The one real number on the page is the price.