CSS-Transit study materials
CSS-Transit study resources

CSS-Transit study plan

CSS-Transit · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Public Transit Operations and Systems & Safety and Security Management

  • Map the five exam domains to your own job tasks and rate your current confidence in each on a 1-5 scale

  • Sketch a typical fixed-route service day end to end: vehicle pull-out, operator sign-in, dispatch, headway management, pull-in, and revenue reconciliation

  • Define the core scheduling vocabulary (headway, cycle time, recovery time, peak vehicle requirement) and compute a simple peak vehicle requirement from a sample timetable

  • List the safety-relevant handoffs between operations control and the safety function during a service disruption

Your checkpoint

A one-page domain self-assessment with confidence ratings plus a worked peak vehicle requirement calculation for a 12-bus sample schedule

Week 2

Public Transit Operations and Systems

  • Calculate headway, cycle time, and required fleet size for three scenarios: a 10-minute peak, a 15-minute off-peak, and a 20-minute evening service

  • Explain how running time, dwell time, and layover interact and identify which one you would adjust first when on-time performance degrades

  • Describe how service planning decisions (route spacing, stop spacing, span of service) affect ridership and operating cost

  • Compare demand-response and fixed-route models on cost per trip and eligibility constraints

Your checkpoint

A spreadsheet with three timetable scenarios showing headway, cycle time, peak vehicle requirement, and daily platform hours

Week 3

Safety and Security Management

  • Build a hazard register with at least 15 transit-specific hazards drawn from vehicle operations, stations, maintenance yards, and customer interactions

  • Apply a risk matrix to score each hazard by likelihood and severity and rank the top five

  • Identify the control hierarchy level (elimination, engineering, administrative, PPE) for each of your top five hazards

  • Outline the sequence of a post-incident review: scene control, data collection, causal analysis, corrective action, and follow-up verification

Your checkpoint

A scored hazard register with the top five risks, assigned control types, and a named owner for each corrective action

Week 4

Safety and Security Management & Standards, Compliance, and Procurement

  • Draft a security threat and vulnerability assessment outline covering stations, vehicles, and fare-collection areas

  • Explain the difference between safety management system components (policy, risk management, assurance, promotion) and where security fits

  • Identify which regulatory and oversight bodies set requirements for your transit mode and what each one actually enforces

  • Trace one procurement from specification to acceptance and note where safety and security requirements enter the document set

Your checkpoint

A four-page threat and vulnerability outline plus a one-page map of oversight bodies and the requirements each imposes

Week 5

Standards, Compliance, and Procurement

  • Explain the purpose and structure of a specification, and distinguish a performance specification from a prescriptive one with an example of each

  • Describe the procurement lifecycle stages and the approval gate at each stage

  • Identify the compliance obligations that attach to federally funded transit procurements and when a sole-source justification is defensible

  • Draft acceptance criteria and a defect-liability clause for a bus procurement

Your checkpoint

A two-page procurement package excerpt containing a performance specification, evaluation criteria, acceptance criteria, and a defect-liability clause

Week 6

Technology for Transit Systems

  • Describe the data flow from an automatic vehicle location unit through the back office to a public arrival prediction

  • Compare fare-collection technologies (closed-loop card, open-loop contactless payment, mobile ticketing) on cost, data ownership, and equity impact

  • Explain how condition monitoring and telematics data feed preventive maintenance scheduling

  • Identify the cybersecurity risks in connected transit systems and the controls that reduce them

Your checkpoint

A system architecture diagram of one technology chain (AVL to arrival prediction, or fare collection to reconciliation) annotated with data owners and failure points

Week 7

Workforce, Leadership, and Professional Development & Technology for Transit Systems

  • Build a training needs analysis for one operator or maintenance role, mapping tasks to required competencies

  • Describe how to structure a practical, scenario-based refresher training session and how to measure whether it worked

  • Outline a change-management approach for rolling out a new technology to frontline staff

  • Draft three behavioral interview questions for a frontline supervisor role and the indicators you would listen for

Your checkpoint

A one-page training needs analysis for a chosen role with competencies, assessment method, and a success metric

Week 8

Public Transit Operations and Systems & Safety and Security Management & Standards, Compliance, and Procurement & Technology for Transit Systems & Workforce, Leadership, and Professional Development

  • Re-rate your confidence on all five domains and compare against your week 1 baseline

  • Write and answer 60 practice questions distributed across the domains in proportion to their exam weight

  • Review every missed question and record the underlying concept gap rather than the answer

  • Assemble a one-page formula and definitions sheet for last-week review

Your checkpoint

A scored 60-question practice set with a written concept-gap log and a final one-page formula and definitions sheet

Milestones

Week 2: You can compute headway, cycle time, and peak vehicle requirement without notes and explain the operational trade-offs behind each number

Week 4: Your hazard register is scored and ranked, and you can name the oversight body behind at least three specific compliance requirements

Week 6: You can draw the technology chain from memory and explain where data ownership and failure risk sit at each step

Week 8: Practice score at or above 75 percent with every missed question traced to a named concept gap, and all five domains re-rated at 4 or higher