PTP common mistakes
PTP · Understand the traps and how to avoid them.
Answering 'what happens next in the planning process' from general intuition rather than from the formal sequence of the rational planning model (vision/goals and objectives → problem identification → data collection and analysis → plan and alternative development → evaluation and selection → implementation → monitoring and feedback), and omitting where public participation and performance measurement are embedded.
Candidates with strong practitioner experience often work inside one stage of the process and treat the exam's process-ordering items as common sense, so they skip the canonical steps and the federally required planning factors that anchor them.
What to do instead
Write out the step sequence once, from memory, and annotate each step with its key product (e.g., goals and objectives, needs assessment, fiscally constrained project list, monitoring report). Memorize the federal planning factors and note that public involvement is continuous, not a single step near the end.
Attributing a product or action to the wrong institution in the planning and decision chain - for example, saying the MPO alone adopts the STIP, expecting the MPO to hold the federal-aid obligation authority, or expecting a transit agency to adopt the metropolitan transportation plan.
Roles overlap heavily in practice and are often described loosely in workplace shorthand ('the MPO approves the program'), so the exam's precise institutional questions catch candidates using informal usage.
What to do instead
Build a one-page responsibility matrix with rows for MPO, state DOT, transit agency, local government, and FHWA/FTA, and columns for MTP adoption, TIP adoption, STIP adoption, project selection, NEPA lead agency, and obligation of funds. Rehearse it until each cell is automatic.
Computing a design-year or horizon-year volume by applying a growth factor to the wrong base year, or by mismatching the horizon of a growth rate with the horizon of the project (e.g., extrapolating 20 years of growth to an opening year five years out, or applying an annual rate as if it were a cumulative factor).
Forecast arithmetic looks trivial, so candidates rush it; the exam deliberately supplies base year, horizon year, and rate so that a single sign or year error produces a plausible wrong answer.
What to do instead
Before computing, write down three labelled quantities: base year, target year, and elapsed years. Use the compounding form explicitly, keep units attached, and check the answer against the direction and rough magnitude you expect before selecting an option.
Transferring published trip generation rates directly to a site whose context differs from the source data - applying suburban, single-occupancy, free-parking rates to an urban mixed-use infill site, or ignoring internal capture, pass-by, and diverted-link trips when summing a multi-use development.
The rates are easy to look up and feel authoritative, and candidates rarely see the adjustment steps applied in day-to-day work, so the need to adjust is invisible under exam time pressure.
What to do instead
Internalize the adjustment hierarchy: start with gross rates, then apply independent-variable corrections (size, setting, density), then internal capture for mixed use, then pass-by and diverted-link shares, and only then convert to driveway and directional volumes. Practice identifying which adjustment a question is testing before calculating.
Reading model and statistical output as a single 'goodness' number - declaring a variable important because R-squared is high, calling a coefficient 'significant' without checking its standard error or t-statistic, confusing correlation with causation, or choosing the mean when the data are skewed and the median is the appropriate measure.
Software output presents many numbers at once and practitioners typically read only the summary line; exam items isolate the statistic that actually answers the question.
What to do instead
For each statistic, memorize the one-sentence question it answers: R-squared answers 'how much variance is explained', a t-statistic answers 'is this coefficient distinguishable from zero', a p-value answers 'how surprising is this result under the null'. Drill a small set of items where two statistics point in opposite directions so the distinction becomes concrete.
Treating the long-range transportation plan and the short-range program as interchangeable - expecting a vision or scenario plan to be fiscally constrained, or expecting the TIP/STIP to contain only fully funded projects while the MTP may include an illustrative category.
Both documents list projects, and the fiscal-constraint rules differ by document and by whether the list is 'illustrative', so candidates collapse them into one mental object.
What to do instead
Memorize a two-column contrast: MTP (20+ year horizon, fiscally constrained in the adopted version, may carry an illustrative unfunded list) versus TIP/STIP (4-year, must be fiscally constrained, must conform to the MTP, updated on a defined cycle). Test yourself by sorting sample project statements into the correct document.
Mixing up plan, program, and policy instruments - describing a zoning overlay, a TDM ordinance, or a complete-streets policy as if it were a capital program item, or assuming a policy change requires the same adoption and funding steps as a construction project.
Planning vocabulary is used loosely in practice, and candidates answer based on what the measure 'does' rather than on which instrument category the question is probing.
What to do instead
Sort interventions into three bins and note the implementation lever for each: regulatory/policy (adoption by ordinance or resolution), programmatic (annual funding and prioritization cycle), and capital (design, NEPA, right-of-way, construction). When a question names an intervention, name its bin first, then answer.
Assigning federal funding to the wrong program or assuming uniform match requirements - placing a congestion-relief or air-quality project in a general surface transportation block when it belongs in CMAQ, assuming every FHWA program carries the same non-federal share, or assuming a transit capital project can use the urbanized area formula program without regard to apportionment.
Program names, eligibilities, and match ratios are numerous and rarely memorized in full; candidates substitute the program they use locally for the one the question describes.
What to do instead
Build a compact table of the major programs with three columns only: eligible activities, typical federal share, and fundable phase. Keep it to the handful of programs the exam is likely to test, and review suballocation and match rules separately, since those are the most frequently inverted facts.
Confusing performance measure, target, and report - treating a national performance measure as a target that every MPO must meet, assuming all MPOs must set their own targets rather than being permitted to support the state's, or mixing up which measures are reported on a two-year cycle versus a four-year cycle.
The performance framework layers federal measures, state targets, MPO target choices, and reporting cycles, and practitioners usually see only the local slice of that framework.
What to do instead
Draw the hierarchy explicitly: national measure → state target → MPO option (adopt the state target or set its own) → reporting obligation. Attach each measure family to its reporting cycle on the same diagram, and review it until you can state who sets what and who reports it.
Evaluating outcomes with a naive before-and-after comparison - crediting a project with a crash or volume reduction without a comparison group or trend control, or treating a published crash reduction factor as a guaranteed outcome rather than an expected average effect.
Before-and-after data are easy to obtain and politically satisfying, and the counterfactual is invisible unless the evaluator deliberately constructs it.
What to do instead
For any evaluation item, name the counterfactual first: comparison site, statewide trend, or empirical-Bayes expected value. Then interpret effect estimates as expected average effects with uncertainty, not as deterministic forecasts. Practice framing an evaluation design before looking at the answer choices.