Before a fiber project moves to installation, agree what the network must connect, where the route can run, who controls access and which parties must prepare the infrastructure. Assign approval owners and define the evidence that will be required for acceptance. A route on a drawing is not yet an authorised, installation-ready route.
For project managers and consultants in Saudi Arabia, the planning output should be a coordinated package: approved requirements, a route and access register, a civil-work interface schedule, readiness milestones and an acceptance deliverables list. This guide explains how to build that package and includes an editable practical worksheet. It covers pre-installation planning; it does not prescribe excavation, cable-pulling, splicing or test procedures.
1. Write Requirements That Can Be Reviewed
Begin with the business purpose: which buildings or sites need to connect, which services depend on the link, and when the connection must be available. Identify the asset owner and future operator. A campus backbone, a carrier connection and fiber within one building can have different boundaries and approval parties.
Record the start and end points precisely: building, communication room, rack and intended termination location where known. State the required capacity and service availability objectives. Have the designer translate these into the fiber type, topology, core allocation, termination arrangement and active-equipment compatibility appropriate to the project.
Distinguish current requirements from expansion allowances. Ask who approves spare cores, reserve duct capacity and future termination space, and why each allowance is needed. Avoid selecting a generic fiber count or a universal growth percentage without a design basis.
Define what is included: survey, design, access coordination, civil infrastructure, cable supply, termination, testing, documentation or activation. Record exclusions and buyer-supplied work. Passive fiber acceptance and activation of a telecom service are different deliverables; assign responsibility for both if both are required.
Review nowa’s fiber-optic and telecom infrastructure overview when defining the requested project scope.
2. Build A Route And Access Register
Divide the proposed route into identifiable segments. Give each segment a route ID, start/end reference, drawing revision, route owner and access status. Separate surveyed information from assumptions. An existing duct shown on an old drawing should remain unverified until the agreed assessment confirms its location, condition and available capacity.
Check building risers, communication rooms, existing pathways, property boundaries and any proposed external crossings. For each segment, ask who can authorise entry, who can authorise work, and whether the approval covers the planned activity and dates. These may be different people or organisations.
Request the access conditions: permitted hours, occupied-area restrictions, escorts, keys, storage areas and coordination with other work. Identify third-party infrastructure and any required owner agreement. Existing physical space does not automatically establish a right to use it.
Where a route could affect public roads or municipal infrastructure, confirm the applicable process with the responsible authority and authorised applicant. The Ministry of Municipalities and Housing describes a Balady excavation-permit service for utility entities within city limits, involving route information and coordination. Do not treat that service as a universal permission route for every private-site fiber job.
Check the official request for a new excavation permit where the project falls within its scope.
Record the required approval, submission owner, reference number, current status and restrictions. Keep private-property consent, municipal coordination and infrastructure-owner approval as separate entries where applicable. A submitted request should be marked Pending, not Approved.
3. Compare Route Options Before Freezing The Design
Compare the preferred route with a viable alternative when access, congestion or service continuity makes that useful. Consider route length, available infrastructure, approval dependencies, maintenance access and civil-work requirements. Document unresolved survey items before committing to procurement quantities.
If diverse routes are required, ask the designer to show where the routes separate and where they share infrastructure. Two fibers within the same cable or two paths through one common duct do not establish independent physical routing. Record common sections and have the operational owner assess whether the proposal meets the resilience objective.
Illustrative scenario only: two buildings within a Saudi commercial campus need a connection. One route uses an existing pathway of unconfirmed capacity; another requires new civil works. The project manager should compare access evidence, survey findings and civil dependencies before recommending a route. This is not a verified nowa or Riyadh project case.
Record the route decision, approving person and conditions. If the route changes later, review its effects on quantities, access permissions, design, schedule and acceptance records. The approved drawing revision should follow the change decision.
4. Define Civil-Work Interfaces In Writing
An interface is the point where one party’s work must be ready for another party to proceed. Fiber planning should make these boundaries visible. “Civil works by others” is incomplete unless it identifies the responsible party, expected condition, evidence and required handover date.
| Interface |
Planning Decision |
Evidence / Owner To Agree |
| External pathway or duct |
Who designs, provides and releases the route for fiber work? |
Approved route and readiness record; civil lead and technical reviewer. |
| Chamber or access point |
Who provides access, identifies the asset and confirms suitability? |
Asset reference and inspection record; infrastructure owner. |
| Building entry and penetrations |
Who approves the entry and completes associated building works? |
Approved detail and agreed inspection responsibilities; building/design owner. |
| Riser, tray or containment |
Who confirms route availability and coordination with other services? |
Coordinated drawing and readiness release; relevant contractor and consultant. |
| Room, rack and termination space |
Who provides the location and operational access? |
Endpoint approval and room-readiness record; client IT/facilities. |
| Reinstatement and asset records |
Who closes civil defects and updates the route records? |
Agreed completion evidence and as-built responsibility; civil and project leads. |
Have qualified civil, building and safety specialists review the relevant interfaces. This guide does not specify excavation dimensions, utility clearance distances or firestopping details. Those belong in the approved project design and applicable specialist requirements.
Include the inspection or hold points that need witnessing before works are concealed or released. Agree who requests the inspection, the notice period and who may approve progression. Distinguish the civil handover from acceptance of the installed fiber system.
Use nowa’s design development overview when discussing coordinated drawings and specifications.
5. Assign Approval Owners And Keep Decisions Traceable
Name a delivery owner and an approval owner for every major output. The project manager coordinates decisions; the designer approves technical content within their authority; the client’s operator confirms operational requirements. Infrastructure owners and authorities retain their own approval roles where relevant.
Do not assume a consultant can approve third-party access or that a contractor’s drawing review replaces client acceptance. Record the authority of each approver and a deputy where necessary. For decisions affecting multiple parties, identify the sequence of reviews and the final release owner.
Maintain a decision log with the issue, document revision, decision, conditions, approver and date. Keep assumptions in a separate register with an owner and resolution deadline. The Fiber Optic Association’s project-paperwork guidance supports documenting scope, customer/contractor responsibilities and review or acceptance milestones before work proceeds.
See FOA guidance on fiber project paperwork and responsibilities.
6. Schedule Milestones Around Evidence Of Readiness
Build the programme around dependencies instead of assuming installation can begin once materials arrive. A useful milestone states what must be completed and what evidence releases the next activity. Assign dates after access and approval constraints have been checked.
| Pre-Installation Milestone |
Release Evidence |
Owner To Confirm |
| Requirements approved |
Signed brief, endpoints and scope boundary. |
Client technical/operational owner. |
| Survey and route review complete |
Survey findings, route alternatives and unresolved items. |
Designer and project manager. |
| Route/access conditions resolved |
Required permissions and access conditions recorded. |
Property/infrastructure owner; authorised applicant where relevant. |
| Design and interfaces approved |
Issued drawing revision, quantities and interface schedule. |
Design reviewer and relevant interface owners. |
| Civil/room readiness released |
Agreed inspection and handover records for the workfront. |
Civil/facilities owner and witness reviewer. |
| Acceptance plan agreed |
Test scope, criteria, deliverables, witnesses and sign-off process. |
Technical reviewer and asset operator. |
| Workfront released for installation |
Package reviewed; critical prerequisites closed for that workfront. |
Authorised project release owner. |
A project may release separate workfronts in stages if their dependencies are resolved and the authorised owner agrees. Mark unreleased areas clearly. Do not present a partial release as permission to proceed across the entire route.
Include procurement dependencies, restricted work windows and operator availability. If installation will connect into a live environment, agree cutover and rollback planning responsibilities before scheduling that activity. Avoid inventing permit lead times or standard completion durations.
7. Specify Acceptance Deliverables Before Installation
Acceptance planning defines what evidence will be produced later and who may accept it. Agree this before procurement and field work so suppliers price the same documentation and test scope. The FOA installation-deliverables guidance treats the scope, technical specifications and acceptance evidence as connected parts of the project.
Review the FOA guidance on fiber installation deliverables and acceptance.
Have the technical reviewer define the test methods, fibers covered, wavelengths, reference method, pass limits and recording format appropriate to the design. The optical loss budget is the planned allowance for signal loss along the link; its basis should match the selected components and intended service. Do not insert a universal loss threshold into every project.
Where optical time-domain reflectometer (OTDR) traces are required, specify their purpose and submission requirements. An OTDR provides information about events along a fiber; its inclusion should follow the technical acceptance plan. This article does not substitute a test procedure or imply that one instrument alone demonstrates every acceptance requirement.
| Deliverable To Agree Now |
Required Identification / Acceptance Detail |
| Approved design baseline |
Drawing revision, route IDs, endpoints and component schedule. |
| As-built route and termination records |
Final route, cable/fiber identifiers, connections and approved changes. |
| Test results and supporting files |
Link/fiber IDs, agreed methods and limits, equipment details, dates and result status. |
| Inspection and civil-interface records |
Readiness releases, witnessed checks and relevant reinstatement evidence. |
| Defect and corrective-action register |
Issue, owner, due date, retest evidence and closure decision. |
| Operations handover pack |
Asset register, warranties, maintenance contacts, spare allocation and agreed training. |
| Acceptance/sign-off records |
Authorised signatories, conditions, remaining items and handover date. |
Separate fiber-system acceptance from service activation and client application checks. State whether activation is included and who provides any carrier or active-equipment dependencies. Define how conditional acceptance differs from final acceptance, and which defects prevent either decision.
Practical Pre-Installation Planning Worksheet
Complete this worksheet with the client, designer and relevant infrastructure/civil owners. Use one row per route segment, requirement or interface; duplicate rows as needed. Reference the actual evidence, including its revision. Use Open, Pending Approval or Closed as status labels. Closed means the named approver has accepted the evidence, not merely that a document has been submitted.
| Project Baseline |
Complete Before Route Release |
| Project / site / planning revision |
________________________________________ |
| Client asset owner / future operator |
________________________________________ |
| Project manager / design reviewer |
________________________________________ |
| Endpoints and services to connect |
________________________________________ |
| Capacity / availability / growth basis |
________________________________________ |
| Included work / exclusions / active-service boundary |
________________________________________ |
| Drawing and specification references |
________________________________________ |
Worksheet A. Project baseline — editable fields.
| Item / Route ID |
Requirement Or Evidence |
Delivery / Approval Owner |
Due Date / Status |
| Route/access permission |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
| Survey uncertainty |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
| Civil-work interface |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
| Endpoint/room readiness |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
| Design/quantities approval |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
| Acceptance deliverables |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
| Workfront release |
____________________ ____________________ |
____________________ ____________________ |
____________________ ____________________ |
Worksheet B. Coordination register — add rows per segment or issue.
For each row, record the relevant document or approval reference, unresolved conditions and the next action. If an approval expires or applies only to a specific window, record that restriction. Keep the current register with the issued planning package so site teams can see which prerequisites remain open.
| Pre-Installation Review Question |
Status / Evidence Reference |
| Are requirements and endpoints approved? |
________________________________ |
| Is each route segment surveyed or its uncertainty controlled? |
________________________________ |
| Are applicable access permissions recorded? |
________________________________ |
| Are civil and building interfaces assigned? |
________________________________ |
| Are milestones tied to readiness evidence? |
________________________________ |
| Are acceptance records and signatories agreed? |
________________________________ |
| Are critical open items resolved for the released workfront? |
________________________________ |
Worksheet C. Readiness review — record the release owner and date below.
Release owner: ____________________ Date: __________ Released workfront: ____________________
A decision to hold installation should identify the blocking item, owner and next review date. A decision to release should identify the specific workfront and any approved conditions. This keeps the worksheet useful as a planning control rather than a checklist completed for its own sake.
Prepare A Clear Planning Brief For nowa
Planning a fiber project in Saudi Arabia? Share your endpoints, service requirements, route information and known approval constraints with nowa through its consultancy enquiry form. Request a written planning scope that identifies survey outputs, route/interface coordination, approval responsibilities and acceptance deliverables. Confirm which tasks are included and which remain with the client, civil contractor or infrastructure owner.
Discuss the planning brief through nowa’s consultancy enquiry form.
Frequently Asked Questions
Can We Order Cable Before The Route Is Approved?
Only if the authorised project team understands and accepts the procurement risk. Unresolved routes can change lengths, construction assumptions and component requirements. Record provisional quantities and which items depend on final approval. Do not treat early purchasing as evidence that route permissions or installation readiness have been resolved.
Does An Existing Duct Mean We Can Use It?
No. Verify its location, condition, available capacity and ownership, then obtain the applicable permission to use it. Record access restrictions and handover requirements. Existing drawings or a visible access point can support the survey, but they do not by themselves establish the right to enter or install infrastructure.
Who Should Approve The Fiber Acceptance Plan?
Assign approval to the authorised technical reviewer and the asset owner or future operator, with other parties involved where the contract requires them. The installer should understand the agreed scope before work starts. Identify witness roles and final signatories so test results are not submitted into an undefined review process.
Is A Second Fiber Automatically A Diverse Route?
No. Separate fibers may share the same cable, duct, access chamber or building entry. Ask the designer to identify common sections and explain how the routing meets the required resilience objective. The operational owner should assess those shared dependencies rather than inferring route independence from the number of fibers.
What Should Happen If A Route Changes After Approval?
Raise a documented change that identifies the new route and its effects on access, civil interfaces, quantities, schedule and acceptance records. Obtain the relevant approvals before releasing the affected workfront. Issue the updated drawing and coordination register, and identify superseded documents so teams do not work from conflicting instructions.