Reading plans, answering redlines, and producing sheets — the design and CAD shelf.

Worked ★: Speed Limits in Florida · SPM Plan Review Checklist · OpenRoads and MicroStation File Review Workflows: Redline Response Workflow · Quantities and Pay Items How-To · spawn CAD-workflow notes per task (sheet setup, plotting, references…)

  • TTC-MOT Plan Review Checklist — what to check on temporary traffic control sheets: 102-series match, tapers/buffers, ped route through the zone, closure windows, signal conflicts. Design checks to spawn as design-standard notes: lane/shoulder widths · SSD/ISD · tapers (MUTCD/Std Plans) · turn lane lengths (Turn Lane and Queue Checks) · median openings · superelevation & curve basics · ADA slopes (PROWAG and ADA) · sign spacing · signal/ped head placement · lighting spacing basics · MOT lane-closure checks (Std Plans 102) · stall/aisle dimensions.
  • Intersection Sight Distance — ISD vs SSD, the departure sight triangle cases, field measurement, and the landscaping/monument-sign review comment. Plan sheet literacy list (make a one-page “how to read” note per type as you meet them): S&PM · signalization · lighting · ITS · MOT/TTC · typical sections · roadway plans · intersection layouts · driveway connections · ped/bike · school zones · curb ramp details · parking layout/garage circulation/loading/ADA plans. Discipline coordination: what traffic OWES others (design vehicle turns, signal/ITS needs, MOT phasing input, S&PM) and NEEDS from them (drainage inlets vs curb ramps/bulb-outs, utility conflicts w/ poles & loops, structures clearances, lighting circuits, roadway geometry files). One coordination-note per project saves three meetings. References: FDOT Design Manual (FDM) · FDOT Standard Plans · FDOT CADD Manual and FDOTConnect · Florida Greenbook · AASHTO Roadside Design Guide · FDOT Basis of Estimates and Pay Items Firm-choice note: Florida DOT work = MicroStation/OpenRoads under FDOTConnect; land development side often AutoCAD/Civil 3D — know which pipeline each client uses (log it in your software notes).