Here's an uncomfortable truth: most of the pain in a Traffic Impact Analysis review isn't decided when the report gets submitted. It's decided weeks earlier, in a 30-to-60-minute scoping meeting that a lot of teams walk into half-prepared.
Show up with a vague site plan and a "we'll figure it out as we go" attitude, and you'll walk out with a scope that's too loose, too narrow, or just plain wrong for what staff actually wants to see. Then you spend the next two months building a study around it — and find out in review that it was never going to fly.
Show up prepared, and the scoping meeting becomes the cheapest insurance you'll buy on the whole project. Here's how to walk in ready.
Know which meeting you're actually walking into
City scoping and TxDOT scoping are not the same conversation, and conflating them is a fast way to leave with half a scope. City staff care about local thresholds, the comprehensive/thoroughfare plan, and municipal review checklists. TxDOT cares about state-maintained facilities, access permitting, and their own spacing and warrant criteria. If your site touches both, you may need two separate conversations — and the earlier you figure out which agencies actually have jurisdiction, the less you're improvising later.
Bring a real site plan, not a sketch
Reviewers can't scope a study around a concept. Come in with a conceptual site plan that shows building footprints, proposed access points, and how the site connects to the surrounding street network. If the project is phased, show that too. A vague plan gets a vague scope, and a vague scope is exactly what turns into review comments six weeks later.
Have your trip generation numbers ready to discuss
You don't need a finished trip generation table walking in, but you should have a strong first pass: proposed land uses, the ITE land use codes you're planning to use (or a plan for what to do if there isn't a good fit), and a rough estimate of peak-hour trips. This is often the moment staff will tell you whether a TIA is even required, or whether your estimated trip count needs a different level of study altogether. Walking in without this means the whole meeting stalls out on math that could've been done in advance.
Propose a study area — don't just wait to be told one
It's tempting to let staff draw the study area for you. Don't. Come in with a proposed boundary and a list of intersections you think matter, based on where you expect site traffic to actually go. You'll usually end up negotiating from there, but proposing something specific gives staff a concrete thing to react to, rather than starting from a blank page. It also signals that you've actually thought about how traffic moves through the area, not just around your site.
Ask about other projects in the pipeline
One of the most common review comments later on is "you didn't account for the other approved development nearby." The scoping meeting is your best chance to head that off. Ask staff directly what else is in the pipeline near the site — other TIAs under review, recently approved projects, roadway improvements already funded or under construction. Staff usually know this off the top of their head, and it can change your study area or your background growth assumptions significantly.
Nail down the horizon year and peak hours up front
Don't leave the meeting without explicit agreement on the analysis horizon year and which peak periods you're studying — typically weekday AM and PM, but retail, school, and event-driven uses often need something different, like a Saturday midday peak. These sound like small details, but they're exactly the kind of thing that turns into a comment if the report doesn't match what was discussed.
Bring up internal capture and pass-by trips before you assume them
If your project is mixed-use or has a retail component, don't wait until the draft report to introduce internal capture or pass-by trip reductions. Raise it at scoping, name the methodology you intend to use — ITE guidance, NCHRP Report 684, or whatever the city typically accepts — and get a read on whether staff is comfortable with that approach. It's a much easier conversation before you've built numbers around it than after.
Ask for the checklist and template by name
Every city that requires TIAs has some version of a checklist or format guide, and TxDOT districts have their own submittal expectations. Don't assume you already have the current version. Ask directly in the meeting, and get a copy or a link before you leave. Building your report around last year's template — or a different city's template — is an entirely avoidable source of comments.
Clarify who reviews what, and how long it takes
If the project touches both a city and TxDOT, ask how those two reviews relate to each other. Are they sequential or parallel? Does one depend on the other being finished first? Also ask about typical review timelines and how many rounds of comments are normal for a project like yours. This won't change your traffic analysis, but it will save you from blowing a project schedule because you assumed one review process when it was actually two.
Write it all down — and send it back to staff
The single easiest way to avoid "you deviated from scoping" as a review comment later is to leave the meeting with a written record of what was agreed, and send a short summary email to staff confirming it. Study area, intersections, horizon year, peak hours, trip generation approach, methodology for any reductions — get it in writing while it's fresh. If anything changes later in the process, you'll have something concrete to point back to, and a record that shows you flagged the change instead of burying it.
The Short Version — What to Leave the Meeting With
If you take one thing into the room, take this list. Every item on it is something that turns into a review comment when it's left unsettled:
- Which agencies actually have jurisdiction
- Conceptual site plan, with access points and phasing
- First-pass land uses, ITE codes, and peak-hour trips
- A proposed study area and intersection list
- Other approved or pending projects nearby
- Horizon year and the peak periods to be studied
- Internal capture / pass-by methodology, if any
- The current agency checklist and report template
- Who reviews what, in what order, and how long it takes
- A written summary of the agreement, sent back to staff
None of this replaces doing good traffic engineering. But a strong scoping meeting means the study you spend the next two months building is actually the study the reviewer wanted to see — which is the cheapest way there is to avoid a comment matrix.
Want to go deeper?
Before you scope anything, check whether a TIA is required for your project in Texas and which deliverable the agency actually expects. Then read how big a traffic study area should really be for how to arrive at the boundary you'll propose, and Beyond the ITE Manual for when standard trip rates won't hold up.