Competitive ATP applications aren't written in three months. The agencies that score 90+ have been working the project for the better part of a year: coordinating with Caltrans Districts, refining DAC qualification, building the engagement record, and locking down match commitments long before the narrative is drafted. Skip the early phases and you arrive at deadline week with gaps the rubric will punish.
Why 9–12 months
The constraints aren't writing time: they're external lead times: Caltrans District concurrence (4–8 weeks), governing body resolution adoption (3–6 weeks given typical agendas), DLAE encroachment permit pre-coordination (4–6 weeks), and RTP/RTIP amendments if needed (often a regular cycle adoption). Stack those serially and you've burned 4+ months before you've written a paragraph of narrative.
Five external coordination tracks run in parallel. Treat each as having its own owner, deliverable, and lead time. The biggest application-killing surprises come from underestimating Caltrans District responsiveness or assuming RTP/RTIP consistency is automatic.
Caltrans District Coordination PDT · Concurrence
What it is:Engaging the Caltrans District through the Project Development Team (PDT) process to confirm scope, design approach, and concurrence on the proposed approach: particularly important for any project on or adjacent to the State Highway System (SHS).
- Initial meeting with District Local Assistance Engineer (DLAE) within first 30 days of pursuit decision
- PDT scoping memo documenting agreed scope and lead Division/Functional Unit assignments
- Design concurrence on geometric layout if any work touches state right-of-way
- Caltrans review of preliminary engineer's estimate for SHS work elements
Typical lead time: 6–10 weeks for first concurrence touch; longer if District workload is high.
SHS Coordination Forms If SHS Touched
When required:Any project element within state right-of-way, on a state-owned facility, or affecting a state intersection. Required before submission, not after award.
- Caltrans concurrence letteron project scope, signed by District Director or designee
- DLAE sign-offon engineer's checklist (Attachment B) for any SHS components
- Encroachment permit pre-coordination: early discussions on permit requirements, not the permit itself; reduces post-award delivery risk and signals deliverability to evaluators
- State-only vs. federal-aid funding designationrequest, if applicable
Common failure mode:Discovering at month 8 that a curb extension touches the SHS and the District hasn't been engaged. Re-scoping mid-application is a score-killer in Q7 (scope consistency).
CTC Coordination & Submittable Portal
What it is:Direct engagement with California Transportation Commission staff for technical assistance, debrief calls (post-cycle), and portal mechanics.
- Workshop attendance: CTC holds three regional workshops (Northern, Central, Southern) plus central workshops; attendance is informal but signals serious pursuit
- Submittable training: typically 8–10 weeks before deadline; covers application form mechanics, attachment limits, file formats
- PSR-equivalent trainingfor projects requiring Project Study Report content
- Debrief requestfrom the prior cycle if you submitted before: contact the assigned ATP coordinator with Application ID and cycle number
Submission portal:All applications go through Submittable. Account creation, file size limits, and required metadata are non-trivial; do not leave portal mechanics for the last week.
MPO / RTPA Coordination
What it is:Engagement with the regional planning agency on regional ranking, supplemental application requirements, and Regional Transportation Plan / Regional Transportation Improvement Program consistency.
- Regional ranking process: large MPOs run their own regional component; some require supplemental questions in addition to the statewide application
- RTP consistency letter or excerptshowing the project is reflected in the adopted Regional Transportation Plan / Sustainable Communities Strategy
- RTIP programming check: confirm the project is programmed (or amendable) in the regional improvement program; some regions require RTIP amendment before allocation
- Regional DAC definition: some MPOs have CTC-approved alternate DAC definitions (e.g., "Equity Priority Communities") that may better fit the project area than statewide tools
Common failure mode:Submitting a regional supplemental application late and being deemed "unresponsive": projects have been rejected for this in past cycles even with strong statewide scores.
Local Assistance Procedures Manual (LAPM) Alignment
What it is:Confirming the agency can deliver an ATP project under the federal-aid framework documented in the Caltrans LAPM. ATP projects with $1M+ in capital construction must be federal-aid eligible unless state-only is granted.
- Master Agreementin place between agency and State (LAPM Chapter 4); if not, partner with an agency that has one
- Baseline Agreementrequired for projects $25M+ total or $10M+ ATP funds (LAPM §28)
- Federal-aid project funding chapterreview; certain elements are not federal-aid eligible and must be stripped or state-only
- Allocation timing: the proposed CTC allocation dates must fall within the cycle's available fund years; this drives schedule design
- NEPA scope: federal-aid triggers NEPA in addition to CEQA; build the time in
Reference:LAPM Chapters 4, 5, 22, 23, and Appendix L of the ATP Guidelines.
Internal Agency Coordination
What it is:The internal lift: getting the elected body, finance, legal, and operations on board. This is where most agencies under-budget time, then scramble at the end.
- Council/board briefing #1: informational, ~6–8 months before deadline, securing pursuit authorization
- CIP alignment: confirming the project is programmed in the Capital Improvement Program with placeholder match funds
- Match funding identification: finance department confirms source, amount, fiscal year availability
- Council/board briefing #2 + resolution: formal authorization to apply, typically 4–8 weeks before deadline depending on agenda cadence
- Executive sign-offs: Public Works Director, City/County Manager, Risk/Legal as applicable
- Communications/PIO loop: for engagement materials, public meeting flyers, social posts
Click each item to mark complete. Progress is tracked locally for the session. The checklist consolidates required and strongly-recommended attachments across the 2027 ATP application packet, supplemental MPO requirements, and internal-agency artifacts.
Application Attachments (Required)
Strongly-Recommended & Internal
DAC Qualification Tools: 2027 Cycle Change
For Cycle 8 (2027 ATP), the accepted DAC qualifying tools are: CalEnviroScreen 4.0 (score ≥ 40.05), Median Household Income (< 80% statewide; statewide MHI for 2020–24 ACS = $99,122, threshold = $79,297.60), Healthy Places Index 3.0 (≤ 25th percentile), National School Lunch Program (≥ 75% FRPM eligibility, project within 2 mi of school), Federally Recognized Tribal Lands, and Other (regional definitions, requires CTC pre-approval). The Climate and Economic Justice Screening Tool (CEJST)and USDOT Equitable Transportation Community Explorerwere removed from the Cycle 8 rubric: applications using only these tools will not qualify.
Patterns that recur across cycles. Most are procedural: they don't reflect a bad project, they reflect missed mechanics. Each is paired with the prevention.
Regional supplemental application not submitted (or submitted late)
MTC and several other large MPOs require a supplemental application in addition to the statewide application. Projects that miss the supplemental are deemed "unresponsive" and disqualified from the regional component: even with high statewide scores. Two Bay Area projects were dropped for exactly this reason in Cycle 7.
Prevention:Identify your MPO's supplemental requirements within the first 30 days. Treat supplemental and statewide as a single application package.DAC qualification using a removed or non-accepted tool
Applications relying solely on CEJST or USDOT ETC for DAC qualification will lose all 10 DAC points in Cycle 8. The Cycle 8 rubric removed both tools. Projects that previously qualified under those frameworks need to re-qualify under one of the accepted alternatives.
Prevention:Run the DAC worksheet against all five accepted tools (CES 4.0, MHI, HPI 3.0, NSLP, Tribal Lands) and pick the one with the strongest severity sub-score.Influence area defined too broadly relative to project scope
Q3 (Reduce Collisions) requires the project's "influence area" to be reasonable: defined by the rubric as ~250 feet for a new traffic signal, the corridor itself for road diets, etc. Applicants who claim a 1-mile influence area for a single intersection improvement lose substantial points. Evaluators are explicitly instructed to test reasonableness.
Prevention:Use the TIMS ATP Tool's default influence area suggestions or document why your defined area is appropriate based on the countermeasure type.Pro-forma public engagement that doesn't change the project
Q4 evaluators look for evidence that engagement actually shaped the project. A handful of social media posts and a single open house typically scores 3–5 out of 10. Evidence of multi-channel outreach, language access, and design changes driven by community input scores 8–10.
Prevention:Document at least three rounds of engagement, multiple channels (in-person, online, intercept surveys), and a "what we heard / what we changed" matrix.Generic "walking and biking are healthy" need statement
Q2 (Statement of Need) explicitly warns evaluators against accepting generic claims. The rubric requires localpublic health data tied to specific community concerns: state or national data is "not sufficient." Applications that lean on generic mode-shift benefits cap out around 12–15 of 38 points.
Prevention:Pull project-area data: HPI 3.0 sub-indicators, county health rankings, school FRPM rates, locally-collected walk/bike counts.Engineer's checklist (Attachment B) missing DLAE signature for SHS work
Any project element on or affecting the State Highway System requires DLAE sign-off on the engineer's checklist. Submissions arriving without this signature are flagged in evaluation. Some are rejected outright; others have points deducted in Q7.
Prevention:Schedule the DLAE walk-through 8 weeks before deadline; pad 2 weeks for revisions.Match commitment is verbal or "in the CIP" without a resolution
Cash match must be documented. A line item in the CIP is necessary but not sufficient for full leveraging points. Evaluators want a board/council resolution committing the funds, or in lieu of that, an executive letter signed by the agency CFO.
Prevention:Sequence the council resolution to address both authorization to applyand match commitmentin a single agenda item.NEPA / CEQA posture unclear or under-described
Project readiness is increasingly important as a tiebreaker. Applications that describe environmental status as "to be initiated" or leave the section ambiguous lose readiness points and trigger evaluator concerns about deliverability within the cycle's allocation window.
Prevention:Have a written environmental approach (categorical exemption rationale, expected NEPA class, anticipated technical studies) before submission, even if clearance isn't yet obtained.Cost estimate inconsistencies between Attachments F, H, and narrative
The project estimate (Att. F), plans/SOW (Att. H), and narrative cost references must reconcile. Evaluators flag mismatches: even small ones: as scope consistency failures. Q7 points are lost not because the estimate is wrong, but because three documents disagree.
Prevention:Designate one estimate as canonical (Attachment F) and force-reconcile every other document against it 2 weeks before submission.Combined I/NI projects without distinct NI workplan
Combined Infrastructure + Non-Infrastructure projects must include a credible NI workplan (Attachment G or equivalent) showing the NI program is new (not a continuation), tied to the infrastructure benefits, and includes evaluation/sustainability plans. Weak NI workplans drag down otherwise strong infrastructure applications.
Prevention:Have NI partner identified by month 4 and workplan drafted by month 7.Submittable portal upload failures in the final 48 hours
File size limits, attachment count caps, and naming conventions cause last-minute failures. The Submittable portal does not accept submissions after the deadline timestamp: there is no grace period, and "system was slow" is not a recognized excuse.
Prevention:Run a full upload rehearsal 7 days before deadline. Confirm file naming matches the application's required convention. Submit at least 24 hours early.Past ATP project delivery failures not acknowledged
The CTC may deduct points for failure to deliver any phase of an ATP project programmed in a prior cycle. Applications that ignore this risk a downward adjustment. Acknowledging the issue: and explaining what's changed: is more credible than silence.
Prevention:Audit prior ATP awards before submission. If delivery slipped, address it directly in Q7 (or wherever fits the rubric category) with corrective actions.Enter your start date, the submission deadline, your project's complexity flags, and your agency's typical governance cadence. The tool back-schedules every critical task by dependency, classifies each task's status, and renders a top-level readiness verdict. Tweak any input and the schedule recalculates instantly. Export the full task list as an .ics calendar file for your team.
Schedule Anchors
Project Complexity Flags
Agency Governance Cadence
Export Calendar
Compatible with Outlook, Google Calendar, and Apple Calendar. Each task becomes an event with start date, deadline, owner, and deliverable in the description.
Week-by-week visualization. Each bar shows when the task should start and complete. The vertical gold marker is the submission deadline; the cyan marker is "today."
A mock evaluator. Walks through the 2027 ATP rubric question by question, scores your application section by section, and surfaces the weak spots. Calibrated against Cycle 7 awards (top score 96, statewide cutoff 96, Small Urban & Rural cutoff 95) so a known awarded project should land within ±3 points of its actual evaluator score. Subjective by design: the goal is rapid self-assessment, not a substitute for the formal evaluator process.
How calibration works
Each rubric sub-element is mapped to a small set of inputs that aggregate to the published point bands. Where the rubric awards 4 points for "clearly and convincingly" and 3 points for "addresses at least three of the following," the inputs reflect the underlying evidence requirements. Calibration was anchored to four Cycle 7 awarded large-infrastructure projects (Visalia Beyond the Lanes ≈ 96; Stanislaus Church Street ≈ 96; Covelo/Round Valley SRTS = 95; Tecopa Bike/Ped = 95) and the published rubrics for 2027.
Pre-Flight Check 5 questions, 30 seconds
Project Category
Q1.Disadvantaged Communities
Q2.Potential to Increase Walking, Biking & Rolling
Q3.Potential to Reduce Fatalities & Injuries
Q4.Public Participation & Planning
Q5.Context-Sensitive & Innovation
Q6.Transformative Project Large only
Q7.Scope, Plan Consistency & Cost-Effectiveness
Q8.Leveraging Funds
Readiness Gates
Section Breakdown
Threshold Tracker
Min funded score by cycle. Cyan marker = your mock score. Calibrated to CTC-published cutoffs.
Readiness Gates
Based on your inputs, the highest-leverage areas to lift your score. Each recommendation links to a relevant lesson in the Lessons-Learned Bank where applicable.
Complete the form sections above to see recommendations.
Patterns of failure observed across recent ATP cycles, drawn from CTC staff reports, debrief commentary, and post-cycle analyses. Each lesson is tagged by the rubric question it most affects, so the Mock Scoring Tool can surface the relevant cautionary examples when it flags a weak section. Filter below to focus on a specific scoring area.