Project Management for OSP Work
Core concepts
OSP projects succeed on scope, schedule, cost, and risk control. Candidates should understand work breakdown structures, critical path basics, permits and right-of-way lead times, material procurement, and change control. Know the difference between a change order and a field directive, and how punch lists and closeout documentation affect acceptance. Stakeholder communication with utilities, municipalities, and property owners is a recurring theme.
Traps to watch
Questions often test whether a delay is excusable or compensable; weather may excuse time but not always cost. Another trap is treating permit approval as a construction activity rather than a predecessor. Watch for confusion between quality assurance and quality control, and between a punch list item and a warranty item. Also expect questions where the correct action is to document and escalate rather than to absorb a change silently.
Worked rule of thumb
Build a simple precedence list. Example: permit approval (30 days) precedes pole attachment application (45 days), which precedes strand installation. If the customer needs service in 90 days, the critical path is 30 + 45 + installation. If installation needs 20 days, total is 95 days, so the project is 5 days late before work starts. Flag the risk early and propose mitigation such as expedited review.
Codes, Standards, and Compliance
Core concepts
Compliance work ties design and construction to adopted codes, standards, and utility requirements. Candidates should understand the roles of national electrical and safety codes, consensus standards for optical fiber and telecommunications infrastructure, and local permitting authority. Key topics include clearance requirements, grounding and bonding, marking and locating, and worker safety practices such as confined space and trench safety.
Traps to watch
The most frequent trap is assuming a national standard overrides a local requirement; the more stringent applicable requirement generally governs. Another is confusing recommended practices with mandatory requirements. Questions may test whether a standard applies to customer-owned inside wiring versus outside plant. Watch for scenarios where a code minimum is met but the utility's own specification is stricter.
Worked rule of thumb
When requirements conflict, rank them: law and adopted code first, then utility or owner specification, then consensus standard as guidance. Example: a code gives a minimum clearance, but the utility requires more; design to the utility value and note the code minimum in the drawing notes. This documented hierarchy answers most compliance questions and protects the designer during review.