Estimate request intake is how a job inquiry becomes either a scheduled site walk or a fast, honest no. Contractors lose more to the requests they should have declined than to the bids they lost on price. A system asks the qualifying questions at the moment of request, scores the answers against the work you actually want, and routes what passes to the estimator who bids that trade in that territory.
Requests that should never have reached an estimator
The form asks for a name and a message
A three-field contact form produces “need a quote on a remodel” and a phone number. Every one of those requires a call before anyone knows the trade, the address, the scope, or whether it is work you would take.
Requests route by whoever opens the inbox first
Everything lands in one place. The commercial estimator opens a residential fence request. The residential lead opens a tenant improvement package with a bid day in nine days. Both get forwarded, and the forwarding is the only work that happened.
Out-of-area work gets a site walk anyway
Nothing asks for the job address until someone reads the message body. By the time anyone checks, a walk has been scheduled ninety minutes outside the territory you can realistically staff with your own crews.
Bid deadlines are discovered late
A GC sends an invitation to bid with a due date and a plan set. It sits four days. The estimator now has a compressed takeoff on a job that needed a scope review, two addenda read, and quotes from three subs.
Nobody can say what happened to a request
It was answered or it was not. There is no state between received and won, so a request that got one voicemail and no follow-up looks identical to one that was declined on purpose after a real look.
Scoring an inbound request and where each score goes
Qualification is two operations running at once. Score the request on the things that predict whether it is worth an estimator’s day, and route it on what it actually is. Each row below does one or both.
| Intake input | Why it is asked | Score effect | Routing effect |
|---|---|---|---|
| Job address, or the nearest cross street | Territory and drive time | Inside the primary service area, plus two; secondary area, plus one | Outside both areas returns the referral response without an estimator seeing it |
| Trade or work type, from a fixed list | Which estimator bids it | None on its own | Sets the queue: concrete, framing, sitework, MEP, tenant improvement, service work |
| Budget band, selected rather than typed | Whether the job clears the trade minimum | Above the trade minimum, plus two; unstated, zero | Below minimum routes to a published price sheet or a decline with a reason |
| Requested start window | Whether you can staff it | Within the next two quarters, plus one | Inside two weeks routes to the operations lead, not the estimator |
| Bid due date, when it is an invitation to bid | Estimating capacity against the calendar | More than ten days out, plus one | Under five days flags for a go or no-go call before any takeoff starts |
| Plans, specs, or scope documents attached | Whether a takeoff is even possible | Drawings attached, plus two | No documents and no site access holds at qualification until one exists |
| Decision maker and their role | Whether you are talking to whoever signs | Owner or the GC’s project manager, plus one | A third party collecting prices routes to a lower-priority queue |
| Prevailing wage or public work | Whether certified payroll and bonding apply | Neutral | Public work routes to the estimator who carries that compliance load |
| How they found you | Source attribution only | None | Recorded, never used to route or decline |
How the intake and routing work
A form that asks the trade first
The first question sets the branch. A residential path asks about the property and the homeowner. A commercial path asks for the GC, the bid date, and the plan set. Nobody answers questions that do not apply to the work they are asking about.
Address validated during entry, not at scheduling
The job address is checked against your service polygons while the requester is still on the form. Out-of-area requests get an honest answer and a referral immediately instead of a walk you schedule and then cancel.
Documents collected on the request itself
Plans, specs, addenda, and site photos upload with the request. The estimator opens one record rather than reconstructing a bid package from an email thread that has been forwarded four times.
Routing rules held as data your team edits
Territories, trade owners, minimums, and coverage assignments live in a table your operations lead maintains. Adding an estimator or shifting a county is a row change, not a support ticket to us.
Every request carries a state and an owner
Received, qualified, walk scheduled, estimating, submitted, won, lost, declined. Each with a date and a name against it. A request cannot sit unattended in an inbox, because there is no inbox for it to sit in.
What runs after a request qualifies
- Cognito Forms build and configuration — The branching intake, address validation, and document uploads are built where your team can adjust the questions.
- custom application development — Territory tables, routing rules, and the request pipeline live in an application your operations lead maintains.
- workflow automation services — Qualified requests create site walk appointments and estimator tasks without anyone retyping the details.
Is this a fit for your business?
A good fit when
- More requests arrive than one person can qualify properly
- You bid more than one trade, or work across more than one territory
- Estimators spend days on requests that were never going to be jobs
- You want a defensible, recorded reason for declining work
Probably not a fit when
- All your work comes from two general contractors who call you directly
- You want lead generation; this is what happens after a lead arrives
- Your estimating is one person who wants to take every call themselves
What to have ready
- Your service area, however you define it: counties, ZIP codes, or drive time
- Trade minimums, below which a job is not worth a truck roll
- Who bids what, and who covers when that person is out
Questions we get asked
Will a longer form cost us requests?
Some, and mostly the ones you were going to decline. The trade-off is worth naming: a fourteen-field form filters harder than a three-field form. We build the first screen short and qualifying, with uploads and detail questions after the requester has committed.
What about invitations to bid that arrive by email?
Those never go through a form, because the GC sends what the GC sends. We parse the invitation into the same request record: GC name, project, bid date, plan link. It carries a state and an owner like everything else, even though it entered through a different door.
Can the system decline a request on its own?
It sends the out-of-area response automatically, because that answer does not change with judgment. Everything else lands on a person. Automatic declines on budget or scope go wrong in exactly the cases you would want to hear about, like a small job from a developer with four more behind it.
How does it handle requests for work we subcontract out?
It routes to whoever owns that relationship rather than to an estimator. A request falling mostly outside your self-performed scope is either a referral or a job you assemble from sub quotes, and those are different decisions made by different people.
Related
- change order approval workflow for contractors
- subcontractor onboarding and prequalification
- Cognito Forms consulting and build
- workflow automation for construction companies
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.