What a Pre-Flight Check for Your Estimate Actually Looks Like

Why a Pre-Flight, Not a Quote

Most estimating problems don't come from bad math. They come from bad inputs. The page that didn't get read. The note in the email that nobody saw. The spec on page 14 that contradicts the spec on page 4. The bid goes out, the customer signs, and three weeks in you find out the job needs something nobody priced for.

A pre-flight check isn't a quote. It's the step before the quote. You take everything the customer sent you — the PDF, the photo, the spreadsheet, the rambling email — and you run it through a checklist that catches the stuff humans miss when they're tired, busy, or confident.

Pilots have been doing this for a hundred years. Surgeons started doing it in the 2000s and cut complications by a third. Estimators are the next ones to figure it out.

The Five Things a Pre-Flight Check Looks For

A good pre-flight on an estimate covers five things. Each one is the kind of thing that, when missed, eats your margin.

1. What's actually being asked

Sounds obvious. It isn't. A 50-page quote request might describe the same part three different ways across three different sections. A remodel scope might say "kitchen renovation" in the email and "full gut to studs" in the attached PDF. A panel schedule might list 48 circuits while the riser diagram shows 52.

The pre-flight pulls every described item, every quantity, every spec, and lays them out side by side. Your job becomes spotting the difference between what the customer wrote in three places, not reading 50 pages of dense PDF and trying to remember what page 12 said by the time you get to page 40.

2. What's missing

This is where bids die. Not the wrong number — the missing question. Did anyone confirm the finish? The tolerance? The substrate? Is there an inspection requirement nobody mentioned? Is the wall load-bearing? Does the customer have the permits or do you need to pull them?

A pre-flight produces a list of things you don't know yet. That list is more valuable than the bid itself. Send the questions back to the customer before you send the price. Half the time they don't have answers either, which tells you everything you need to know about how the job will actually go.

3. Where the contradictions are

The drawing says 0.250-inch wall thickness. The cut sheet attached to the same email says 0.190. The spec sheet referenced in the drawing says "minimum 0.250 unless otherwise specified." Which one is right?

You don't know. The customer probably doesn't either. But if you bid 0.190 and the inspector measures 0.250 in the field, that's a rework charge nobody planned for.

A pre-flight flags every place where two documents disagree. You don't have to resolve them — you just have to know they exist before you commit to a number.

4. The risk flags

Tight delivery date. Unusual material. Custom finish. New customer with no payment history. A spec that requires equipment you don't own. A scope that mentions "or equal" without saying what the equal is. Code references with no version number. A site address in a region you've never worked in.

None of these kill a job by themselves. But each one adds a percent or two to your real cost that doesn't show up in a clean line-item estimate. Pre-flight surfaces them so you can either price the risk in or walk away from it.

5. The work breakdown

Once the inputs are clean, you need to turn them into operations: what gets done, how many hours, what equipment, in what order. This is the part that actually drives the dollar number. But it's only as good as the four checks before it.

If you skip the first four and jump straight to building the work breakdown, you're estimating against assumptions instead of facts. Half your variance comes from there.

What This Looks Like in Practice

You get an email Friday afternoon. PDF attached, 38 pages. The customer wants a number by Tuesday. You're already booked solid through next week.

Old way: you skim the PDF, copy the parts that look quotable into a spreadsheet, fill in numbers from gut feel and last quarter's job rates, and send it Tuesday morning. The bid is fine. Maybe you win, maybe you don't. If you win, you find out what you missed when the work hits the floor.

New way: you upload the PDF to a pre-flight tool. Extraction reads the document and pulls every described item, quantity, spec, and reference into a structured list. Readiness Check runs over that list and tells you which items are ambiguous, which contradict each other, and what's missing. Work Breakdown builds the operations and hours from what's actually there.

You spend twenty minutes reviewing the output instead of three hours reading the PDF. The questions you send the customer Friday afternoon get answered over the weekend. By Monday morning you have clean inputs, and your Tuesday bid is built on facts instead of guesses.

The Numbers People Don't Talk About

Shop owners, contractors, and estimators we've talked to all say roughly the same thing: 60-80% of the time it takes to produce a quote is spent on the inputs — reading the package, hunting for specs, asking the customer questions, reconciling drawings with descriptions. The actual pricing math takes 15 minutes.

If you cut the input phase from three hours to thirty minutes, two things happen. You can quote more jobs. And the quotes you do send are based on better information, which means tighter margins and fewer surprises.

This is the entire pitch for a pre-flight check. It doesn't price the job for you. It doesn't replace your estimator. It cleans the inputs before they get to the part where dollars get attached. Cleaner inputs, better bids.

Who Needs This

Anyone who quotes from documents. A machine shop owner pricing a fabrication run. A remodel contractor scoping a bathroom gut. A handyman quoting from a customer's photos and a paragraph of texted requirements. An electrician reading a panel schedule. A precast plant taking off a structural drawing. A roofer pricing from a satellite image and a pitch report.

Different industries, same problem. The customer hands you a stack of stuff. You have a few hours to turn that stack into a number that's right enough to win the job and high enough to make money on it. The pre-flight is the part nobody had a tool for — until now.

How to Start

Pick your next quote request. Before you start pricing it, do this:

• List every described item. If two documents describe the same thing differently, write down both versions.
• List every quantity. Note any place where the same item shows up with different quantities in different places.
• List every spec or reference. Material, tolerance, finish, code, standard, deadline, location.
• List the questions you can't answer from the package. Send those to the customer before you send the bid.
• Then build the work breakdown and price it.

You can do this with a spreadsheet and a yellow pad. It takes maybe two hours per quote, and you'll catch things you would have missed. Do it on a few jobs and you'll see the pattern: the items that show up on the "questions" list are the ones that bite you in the field if you ignore them.

Once the habit is there, the tool is just an accelerant. ForgeAI Workshop runs the same checklist in a few minutes instead of two hours. Same checklist. Faster.