Make Reporting Lines, Field Supervision and Escalation Work at Three in the Morning
Telecom organisations are built on two axes at once, geography and function, and the junction between them is where decisions stall. We help you draw the structure both ways, set supervision spans that suit scattered sites, and derive the escalation matrix from the live structure, so an outage call reaches someone who holds the role today.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsThe starting point
Does Your Structure Hold Up When the Network Does Not?
Circle heads and functional heads each own part of the picture, and the rules for who allocates an engineer, who approves a night call-out and who may authorise a site shutdown are usually unwritten. On ordinary days the goodwill of senior people covers the gap. During an outage, the gap shows.
We help you replace assumed authority with written authority.
You may be experiencing:
- Field engineers claimed by both the circle head and the functional head, with conflicts settled by seniority.
- Supervisors responsible for many scattered sites, who cannot see the work and rely on trust.
- An escalation list that still carries the names of people who have moved on to other roles.
- Doubt over who may approve an emergency purchase, an access change or a night call-out.
- Partner supervisors working beside your staff with authority that nobody has defined.
- Informal deputies for operations centre shift leads and on-call roles, never written down.
- Head office functions that add layers between a circle and the decision it needs.
What we can help with
Our Organisation Design Services for Telecom
Structure Review by Circle and Function
Chart how the business is arranged today along both axes, with the real reporting lines and not the ones on the old chart. Mark where two leaders believe they own the same person or decision.
Matrix Rules
Settle which line owns the person day to day and which owns the standard, for allocation, approvals, appraisal and discipline. Write the rule so conflicts are resolved by role, not by rank.
Field Supervision Design
Set the number of sites or crews per supervisor from travel time, risk and fault load. Decide who visits, how often, and what a supervisor sees when the crew is on a remote tower.
Operations Centre Structure and Shift Leadership
Define shift lead, analyst and escalation roles for a floor that runs through the night, including who is in charge when the shift lead steps away and how handover between shifts is owned.
Escalation Matrix from the Live Structure
Build the escalation ladder from current roles, with deputies, and update it whenever someone moves, instead of maintaining it as a separate document.
Delegation of Authority
Write limits by role for emergency spend, overtime, access approval, customer credits and site shutdowns, with a named deputy for each, so a decision at night does not wait for a phone call to head office.
Contractor Supervisor Placement
Show on the chart where partner supervisors stand: who directs their work, who sets the safety standard on your sites and who handles employment matters at the partner.
Transition Planning
Plan the move from today's arrangement to the new one: which roles change, who is told what and when, and the points at which you will check that it is working.
The deliverables
What You Receive
Depending on the work you choose, deliverables include:
- A circle-wise and a function-wise chart of the current structure.
- Written matrix rules for allocation, approval, appraisal and discipline.
- Recommended supervision spans for each field and operations role.
- An operations centre role and shift-leadership structure.
- An escalation matrix with deputies, kept consistent with the structure.
- A delegation of authority table with limits by role.
- Role accountability definitions for key positions.
- A transition plan with owners and review points.
Step by step
How We Work
Listen to the Floor and the Field
We speak with circle heads, functional heads, shift leads, area supervisors and field engineers, and with night staff, to hear who they actually go to.
Map Decisions, Not Just Boxes
We trace a handful of real decisions, such as an emergency purchase or a site shutdown, from the first call to the approval, and note where they wait.
Draft Options
We set out one or two structures with their effects on supervision, cost and clarity, and discuss them with your leadership.
Write the Rules
We put the chosen structure, matrix rules, approval limits and escalation ladder into short documents that can be read at a desk or on a phone.
Review After the Change
Before work starts we record where you stand today. After the new arrangement has run for a while we review it against that record with you.
The difference
Give Every Role a Clear Place and a Clear Limit
A clearer structure helps you:
We do not promise outcomes. We record a baseline before work starts, covering how often decisions are escalated beyond their limit, how current the escalation matrix is and the number of sites per supervisor, and report against it, so you can see what changed and what did not.
- Know who owns a field engineer, a decision or a site at any hour.
- Keep the escalation ladder true as people move.
- Give supervisors spans they can actually supervise.
- Let deputies decide within limits when senior people are unreachable.
- Show partner supervisors where they stand in your chain.
- Prepare the structure for new circles and new technology.
Find your fit
Who This Service Is For
Operators with Several Circles
Settle how circle heads and functional heads share authority over the same teams.
Providers Setting Up a New Region
Design the structure for a new territory before habits form.
Tower and Infrastructure Companies
Define supervision for large numbers of remote, unmanned sites.
Growing Broadband Providers
Move from founder-held decisions to written authority as installation and care teams grow.
Companies After a Merger or Acquisition
Reconcile two structures and two escalation ladders into one.
How it usually shows up in telecom
Telecom organisations are shaped by geography and function at the same time. A circle or region head owns the territory, while network, field engineering, quality and commercial functions have their own reporting lines into a head office. Matrix arrangements are common, and the boundary is often unwritten: who allocates a field engineer, who approves overtime, who may authorise a site shutdown. Field supervisors manage wide spans over scattered sites. Escalation contacts are kept in a document that drifts out of date when people move. Contractor supervisors sit beside own staff with unclear authority, and deputy arrangements for the operations centre and for on-call roles are frequently informal.
Common challenges
Where it goes wrong in telecom
The matrix is real but unwritten
Circle heads and functional heads each assume the field engineer is theirs, and conflicts get settled by seniority.
Field spans are too wide to supervise
A supervisor responsible for many scattered sites cannot see the work, so quality and safety rely on trust.
The escalation matrix is out of date
Names and numbers on the ladder belong to people who have moved, and the gap shows up during an outage.
Decision limits are vague
Nobody is sure who may approve emergency spend, site access changes or a night call-out.
A better process
What a working version looks like
- 01
Draw the structure both ways
One chart by circle and one by function, with a plain rule for who decides what where the two meet. The organisation design work produces both.
- 02
Set supervision spans from the work
Base the number of sites or crews per supervisor on travel time, risk and fault load, not on convenience.
- 03
Generate the escalation matrix from the structure
Build it from current roles and update it when anyone moves, so it is never maintained separately.
- 04
Write a delegation of authority
Limits for emergency purchases, overtime, access approvals and customer credits, with a named deputy for each.
- 05
Place contractor supervisors on the chart
Show who they report to for work, who for safety, and who at the contractor for employment.
What to check this week
- Pull the escalation matrix and phone the first three names to see whether they still hold the role.
- Ask two field engineers who their line manager is and who allocates their jobs.
- Count the sites each field supervisor covers.
- Find who may approve emergency spend at night, and who stands in for that person.
- Check whether contractor supervisors appear on any chart.
What this looks like in telecom
The parts of organisation design that are specific to this sector, rather than general.
Structuring Across Circles and Functions
Geography, technology and operations at once.
What this coversHide
Structuring Across Circles and Functions
Geography, technology and operations at once.
What this coversHideTelecom organisations are structured along at least two axes - geography and function - and staff frequently report into both, which has to be designed rather than allowed to happen.
Operations and field
- Circle and regional operations
- Field engineering and maintenance
- Network Operations Centre and monitoring
- Site acquisition and rollout
Technical and support
- Planning, design and optimisation
- Core network and technology functions
- Vendor and contractor management
- Quality, safety and compliance
- Matrix reporting between circle and function defined explicitly
- Escalation matrix derived from the structure, maintained live
- Authority limits for network and commercial decisions
- Contractor workforce position in the structure
- Shift structure for continuous operations
- Succession for circle, NOC and engineering leadership
Deriving the escalation matrix from the organisation structure, and maintaining it as the structure changes, prevents the outage call that reaches nobody.
Questions on this, in telecom
Decide which line owns the person day to day and which owns the technical or commercial standard, then write the rule for allocation, approvals, appraisal and discipline. Conflicts are then settled by the rule instead of by seniority.
That depends on distances, risk and how much of the work needs direct oversight. We work it out from travel time and fault load for your zones, and the answer is usually lower for remote tower crews than for city teams.
Because it is kept as a separate document that nobody owns. If it is built from current roles and reviewed whenever a role changes hands, the named contacts remain the people who hold the position.
Yes. We help you write limits by role and name a deputy for each, so a decision at night has someone entitled to take it. The amounts and who holds them are your decisions.
No. Often it means clarifying who decides, changing a reporting line or adding a supervisory role. Where a change affects an employee's terms, confirm the position with a qualified professional. GullyHR does not give legal advice.
It depends on distance, risk and how much of the work needs direct oversight. Remote tower crews need smaller spans than office-based roles, and the answer should come from travel time and fault load.
Because it is kept as a separate document. If it is derived from the live structure and reviewed when anyone changes role, it stays current.
Named roles, with a deputy for each, written into one matrix. Limits tied to people rather than roles break when someone moves or is on leave.
They are outside your reporting line for employment but inside your control for safety and work quality. Show both relationships on the chart so authority is not guessed.
Give Your Network a Structure That Works Out of Hours
If authority is clear only when the right senior person answers the phone, the structure needs writing down. Tell us how your circles and functions are arranged today.
Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.
Book an Organisation Design Consultation
Tell us about your circles, functions and where decisions get stuck.
The general method — what organisation design covers, the questions it answers and what an engagement produces — is the same whatever the sector, and is set out on the organisation design page. What is above is the part that differs for telecom.
Other HR topics for telecom
Where to start
Most engagements begin with a review of how this runs in your business today, then a written process and the sequence to implement it.