Planning a Rail Corridor Survey: What to Confirm Before Site Access

A rail corridor survey can slip before a surveyor takes one observation. Access authority, safeworking, control, features, and data formats often depend on the infrastructure owner and the site. Leave those until mobilisation and the field team may be ready while the corridor is not.

Start with a written survey brief. It should connect six things: purpose, owner, access, control, features, and deliverables.

The short answer

Before a rail corridor survey, confirm:

1. Purpose: what design, construction, verification, or asset decision will use the survey?
2. Owner: which rail infrastructure manager, landholder, and project authority control the site and the requirements?
3. Access: what application, lead time, insurance, competence, induction, safeworking, and possession arrangements apply?
4. Control: what datum, project grid, height reference, and existing marks must be used and verified?
5. Features: what must be measured, with what codes, attributes, limits, and tolerances?
6. Deliverables: which CAD, GIS, model, drawing, report, and metadata formats will the recipient accept?

Do not lift an access or deliverable checklist from another network and assume it applies. The Public Transport Authority of Western Australia and the Australian Rail Track Corporation publish different access pathways. Project-specific requirements can sit below the public guidance.

1. Define the survey purpose before the method

“Survey the corridor” needs a defined scope. A design survey, a utilities investigation, a signalling site survey, construction set-out, a clearance check, a monitoring program, and an as-built survey each need different features and evidence.

Start with the next decision:

• Is a designer building a surface or alignment model?
• Is a contractor setting out works?
• Is the project recording existing assets before design?
• Is an engineer checking clearance, level, movement, or conformance?
• Is an asset team updating a drawing or GIS record?
• Is the result part of a handover or commissioning package?

The answer drives the observation method, survey limits, tolerance, coding, photographs, report, and reviewer. It also affects corridor access, because workgroup size, equipment, and proximity to operating rail may change.

2. Identify the infrastructure owner and exact site limits

A rail corridor can involve the rail infrastructure manager, a state transport authority, a landowner, a station operator, a freight operator, a project alliance, and adjoining-property owners. Work out who controls:

• permission to enter the land;
• access to the danger zone or track area;
• safeworking and protection;
• electrical or overhead-line risks;
• the survey standard and control;
• asset information and drawings;
• the accepted deliverable format; and
• final approval.

ARTC’s corridor access guidance states that access is highly regulated and needs the relevant application plus legal and safety arrangements. Its published process includes third-party works and specific corridor access protocols. PTA’s third-party access guidance states that work in or next to its rail corridor needs permission, and that access is allowed only after adequate safety precautions are accepted.

Both statements rest on the same safety principle. Each owner has its own process. Confirm the route, chainage, or map limits, then ask the relevant owner for the current requirements.

3. Obtain access requirements before fixing the field date

Access may need more than a property permit. Depending on the owner, project, and work location, the field plan may need:

• a third-party access or works application;
• evidence of insurance;
• worker competencies and rail-industry cards;
• owner or project inductions;
• a safe work method statement and site safety plan;
• corridor protection or a qualified safeworking person;
• a possession, isolation, or approved work window;
• electrical permits or an approach-distance plan;
• plant, equipment, or vehicle approvals;
• environmental or heritage controls;
• communications and emergency arrangements; and
• an approved entry, exit, and muster process.

The owner decides what applies. A public web page can show the pathway, but it is no substitute for the approved project access pack.

PTA’s public page also says drones are not permitted on or over PTA property. Treat that as an owner-specific constraint. Check any proposed aerial method with the relevant owner before it goes in the survey program.

4. Confirm survey control and coordinate systems

A corridor can cross control networks, mapping zones, historical project grids, and height references. Before fieldwork, obtain:

• the required horizontal datum and map projection;
• the vertical datum or project height reference;
• local-grid parameters or transformation files;
• existing control mark schedules, coordinates, and quality records;
• rules for establishing or replacing control;
• checks required before adopting supplied control; and
• naming, monumentation, and protection requirements.

Do not assume a supplied coordinate is ready to use. Confirm the mark exists, is stable, matches its description, and agrees with independent checks. Record discrepancies and get direction before mixing coordinate sources.

Control placement must also account for corridor operations. Marks need suitable geometry and stability without creating an access or maintenance hazard. If repeat work is expected, plan how the control can be reoccupied and checked over the project life.

5. Agree the feature list, coding and observation rules

Rail design teams need more than a generic topographic surface. Depending on the purpose, the feature list may include:

• track centrelines, rails, joints, turnouts, and crossings;
• platforms, coping edges, ramps, and access paths;
• signals, signs, equipment cases, and kilometre posts;
• overhead wiring structures and electrical assets;
• cable routes, pits, conduits, and service crossings;
• drainage, culverts, headwalls, and water paths;
• bridges, retaining walls, fences, and corridor boundaries;
• buildings, shelters, and station furniture;
• vegetation, batters, ground surface, and access tracks; and
• adjoining features needed for design tie-in.

For every feature group, confirm:

• the required point, line, or polygon representation;
• coding and mandatory attributes;
• whether levels are needed and at which physical point;
• the required tolerance and observation density;
• breaklines and model rules;
• hidden, unsafe, or inaccessible-feature treatment;
• photograph or sketch requirements; and
• how uncertainty or non-observation will be reported.

ARTC’s EGG-20-01 shows why this matters for signalling work. Its NSW/Queensland detailed site survey deliverable calls for fully dimensioned drawings that locate specified rail and lineside features relative to the running face of the nearest railway line. Drawing versions are managed through design, construction, and as-built stages. That is a specific ARTC deliverable example, not a template for every corridor survey.

6. Lock the deliverables before capture

Confirm the receiving team, software, and asset system. The deliverable schedule may include:

• survey report and methodology;
• control report and mark schedule;
• raw and reduced observations;
• CAD drawing and feature-code export;
• digital terrain model, breaklines, and contours;
• point cloud or imagery;
• cross-sections and chainage-offset schedules;
• as-built comparison or conformance table;
• GIS files with required attributes;
• drawing register, revision, and metadata; and
• limitations, exclusions, and inaccessible areas.

ARTC’s EGG-20-01 distinguishes designed, commissioned, and as-built detailed site survey drawings. It also requires readable CAD/PDF outputs and metadata for the relevant drawing system. The practical lesson is to confirm the deliverable state and revision pathway, rather than promising one undifferentiated “survey drawing”.

7. Design the field plan around rail operations

A field plan should connect each task to the approved access and protection arrangement. Include:

• work limits and access points;
• who authorises entry and handback;
• protection and communications roles;
• train movements, possessions, and other workgroups;
• electrical and plant hazards;
• safe equipment locations and sight lines;
• planned control setups and checks;
• inaccessible-feature fallback methods;
• weather and visibility constraints;
• daily data review and missing-data triggers; and
• contingency if access is shortened or cancelled.

Separate “nice to have” capture from features needed for the next design or construction hold point. If the access window closes early, the team needs a defensible priority order.

Illustrative pre-access worksheet

Illustrative example only. This fictional worksheet shows the level of detail needed before mobilisation. It is not an HR Surveyors project or a claim of experience.

Nothing in the worksheet authorises entry. Its purpose is to show missing decisions early, while the owner, project, and survey team can still resolve them.

Pre-access confirmation checklist

Purpose and responsibility

• named survey purpose and downstream decision;
• current drawings, specification, and revisions;
• infrastructure owner, landholder, and project contacts;
• party responsible for access, safeworking, control, and acceptance.

Access and safety

• approved access/works application;
• work limits, access points, and approved dates;
• competencies, inductions, insurance, and worker records;
• protection, possession, isolation, and electrical arrangements;
• plant/equipment approval and emergency plan;
• environmental, heritage, and adjacent-property controls.

Technical scope

• datum, projection, project grid, and height system;
• supplied control and verification procedure;
• feature list, coding, attributes, and tolerances;
• inaccessible and hidden-feature process;
• observation density, checks, and required field records.

Delivery and acceptance

• CAD, GIS, model, drawing, and report formats;
• file naming, metadata, version, and revision status;
• design/as-built state and certification requirements;
• receiving systems and named reviewer;
• acceptance criteria and resurvey trigger.

Common planning mistakes

Booking surveyors before the owner confirms access

A requested date remains unapproved until the owner confirms the work window. Link mobilisation to the owner’s approval pathway and protection arrangements.

Treating a previous project checklist as universal

Network rules, systems, and forms change. Verify the current owner documents for the exact corridor and project.

Asking for “all visible features”

This produces inconsistent interpretation and can miss the attributes designers need. Issue a feature schedule with physical measurement definitions.

Accepting supplied control without checks

An old or disturbed mark can propagate an error along the corridor. Specify verification and escalation before adoption.

Deciding file formats after fieldwork

Feature coding, attributes, observation density, and drawing requirements affect capture. Confirm them before access.

What to send with a rail corridor survey enquiry

Provide the owner and network, site limits or chainages, purpose, current drawings, access status, known work window, project control, survey standard, feature schedule, tolerances, required deliverables, and named acceptance contact. Identify unresolved items clearly. Do not present an access application as an approval.

HR Surveyors supports commercial, engineering, construction, and infrastructure survey briefs. Contact HR Surveyors to review the technical scope alongside the access information issued by the relevant rail infrastructure owner.

Sources

• Public Transport Authority of Western Australia, Access to PTA property, especially “Third-party access”, accessed 2 October 2026.
• Australian Rail Track Corporation, Accessing the Rail Corridor, including application forms and corridor-entry protocols, accessed 2 October 2026.
• Australian Rail Track Corporation, EGG-20-01 Project Management Data Deliverable Descriptions, section 2.7.5, version 1.0 reviewed 15 February 2024, accessed 2 October 2026.