4.4 Permits, Encroachments & Landowner Requirements
Key Takeaways
- Front-end construction touches a web of permits — road crossings, road access, railroads, encroachments, and wetland/waterbody crossings — each with its own issuing authority and conditions
- The inspector verifies that the correct, current permit is on site (physically or electronically accessible) before work at a permitted location begins; no permit on site means stop-work
- The line list is the per-station record of landowner and tenant requirements (gates, fencing, crop restrictions, timber, avoidance areas, access, work-hour limits, irrigation/drainage)
- Line-list items are tracked through construction to closeout; incomplete items become punch-list/restoration carry-overs
- API 1169 requires written or electronic daily reports capturing daily progress, staking verification, one-call ticket numbers, utility exposures, and clearing/grading acceptance
Permits, Encroachments & Landowner Requirements
Quick Answer: Front-end construction touches a web of permits — road crossings, road access, railroads, encroachments, and wetland/waterbody crossings — and a parallel set of landowner requirements captured on the line list. The API 1169 inspector verifies that the correct permit is on site before work at each crossing begins, that permit conditions are followed, and that line-list and landowner requirements are tracked to closeout. All of this is documented in the inspector's written or electronic daily report.
Permit Types Encountered During Front-End Construction
Pipeline construction crosses roads, railroads, waterbodies, and other facilities, each of which requires its own permit. The inspector does not obtain permits — that is the operator's and contractor's responsibility — but must verify the correct permit is on site and being followed before work at that location begins.
Permit-Type Field Reference
| Permit Type | Issuing Authority | Typical Conditions the Inspector Verifies |
|---|---|---|
| Road crossing (open cut) | State DOT / county road authority / municipality | Crossing method, casing or uncased, traffic control, paving restoration, working hours |
| Road crossing (bore / HDD) | Same road authority | Bore pit location, casing spec, depth of cover, settlement monitoring |
| Road access (approach) | Road authority | Approach grade, sight distance, culverts, gravel surface, removal at closeout |
| Railroad crossing | Railroad company / FRA | Bore or HDD required (no open cut on active main line), casing, depth, inspector of record, flagging |
| Encroachment | Adjacent landowner / facility owner / utility | Setback, hand exposure of existing facilities, protection of structures |
| Wetland / waterbody crossing | USACE (Section 404) / state water authority | Timing window, equipment restrictions, spoil management, refueling restrictions, restoration |
| Cultural / archaeological | SHPO / tribal authority | Monitoring, avoidance, stop-work if resources found |
| Threatened & endangered species | USFWS / state wildlife agency | Timing windows, tree-clearing restrictions, habitat avoidance |
Permit-on-Site Verification
A core API 1169 inspector responsibility is verifying that the applicable permit is on site — physically or electronically accessible — before work at a permitted location begins. "On site" means the crew and inspector can produce the permit document, including all conditions and drawings, at the work location.
What the Inspector Verifies for Each Permit
- The permit is the correct one for the location (station matches)
- The permit is current (not expired)
- The permit's conditions are being followed
- Required notifications (for example, 24-hour notice to the road authority) have been made
- Required third-party inspectors or monitors (environmental, archaeological, railroad flagger) are present
- Permit closeout conditions are recorded for tracking
Inspector checkpoint: Work at a permitted crossing without the permit on site is a stop-work condition. The permit must be produced before excavation at that station.
Special Landowner Requirements: the Line List
The line list is the project's per-station record of landowner and tenant requirements. It is the mechanism that translates landowner easement terms, crop agreements, fence requirements, timber disposition, and special conditions into field actions.
Typical Line-List Entries
| Line-List Entry | Field Action |
|---|---|
| Gate installation | Temporary gate installed at fence cut; gate type and location per line list |
| Fencing restrictions | Specific fence types, heights, or setbacks required |
| Crop restrictions | No-stubble burning, crop timing windows, compaction limits, noxious-weed control |
| Timber disposition | Salvaged to landowner, chipped, or removed; stump handling per agreement |
| Avoidance areas | Structures, wells, septic systems, landscaped areas to be avoided |
| Access restrictions | Only agreed access roads; no off-road travel outside ROW |
| Work-hour limits | No work outside agreed hours (for example, near residences) |
| Irrigation / drainage | Existing irrigation lines and drainage tile preserved or repaired |
Inspector checkpoint: The line list is not a suggestion — it is the enforceable record of landowner requirements. The inspector cross-checks field activity at each station against the line-list entry and records compliance.
Connecting the Line List to Closeout
Many line-list items are closeout items: gates remain, fences are restored, crops are compensated, drainage tile is repaired. The inspector tracks open line-list items throughout construction so that closeout can be certified. A line-list item that is not completed at construction completion becomes a punch-list or restoration carry-over.
Written / Electronic Reporting
API 1169 requires the inspector to maintain written or electronic reports of daily activities. During front-end construction, the inspector's daily report captures, at minimum:
Front-End Daily Report Contents
| Report Item | Source |
|---|---|
| Daily progress | Stations advanced by activity (staked, cleared, graded, trenched) |
| Staking verification | Survey and staking checks performed and results |
| One-call ticket numbers | Active tickets, expiration, renotices (Section 4.2) |
| Utility exposures | Stations where existing utilities were hand-exposed and verified |
| Clearing / grading acceptance | Stations accepted for next activity |
| Permit-on-site verification | Permits checked at each active crossing |
| Line-list compliance | Landowner requirements checked at each active station |
| Nonconformances | Any deviation from spec, permit, or line list |
Note: API 1169 treats the inspector's daily report as a primary project record. Reports must be timely, factual, and complete — written or electronic, but consistently maintained.
Coordinating Permits, Line List, and Alignment Sheets
The three documents work together at every station:
- Alignment sheet — what is to be built (route, pipe, crossings, special conditions)
- Permit — what is authorized at each crossing (conditions, notifications, monitors)
- Line list — what the landowner requires at that station (gates, crops, timber, access)
The inspector cross-checks all three at every active station. A crossing that appears on the alignment sheet but has no permit on site is a stop-work. A fence cut that is not on the line list is a nonconformance. A permit condition that is not being followed is a nonconformance.
Key Takeaways
- Front-end construction requires road, road-access, railroad, encroachment, and wetland/waterbody permits, each with its own authority and conditions.
- The inspector verifies the correct, current permit is on site before work at each permitted location; no permit on site means stop-work.
- The line list is the per-station record of landowner requirements and is enforceable; the inspector cross-checks field activity against it.
- Open line-list items are tracked to closeout; incomplete items become punch-list or restoration carry-overs.
- API 1169 requires written or electronic daily reports covering progress, staking verification, one-call tickets, utility exposures, and clearing/grading acceptance.
A crew is about to begin a bore under a county road. The API 1169 inspector asks to see the road-crossing permit, and the supervisor says it is in the project office 30 miles away. The inspector should:
The line list shows that at station 8+50 a temporary gate must be installed in an existing fence before the fence is cut. The crew cuts the fence without installing the gate. The inspector should:
Which document is the per-station record of landowner and tenant requirements such as gates, fencing, crop restrictions, and timber disposition?
Under API 1169, the inspector's daily report during front-end construction must include, at minimum: