Assessment
Radio cluster quality walkthrough
A scheduled reading of one live cluster: dropped-call samples, neighbour-list friction, complaint geography, and a written quality note the operations desk can keep.
- Who it is for
- Radio operations supervisors, quality engineers, and regional NOC leads who already own the counters and tickets
- What is left with the desk
- A dated walkthrough note covering the cluster’s weakest sectors, the complaints that map to them, and the outage windows that still lack a closed cause
- Duration
- Two consecutive working days on the named cluster, plus a half-day write-up
- Where it happens
- On-site at the operator’s radio operations room, or remote if counter extracts and ticket text can be shared on a screen
- How it is priced
- Quoted per cluster; typical starting figure listed on the rates page — see rates.
Included
- Agreement on the cluster boundary (sites, technologies, and the hours that count as busy)
- Joint reading of CSSR, drop, PRB, and HO failure extracts the desk already stores
- Mapping of open quality tickets to sectors, not to generic city names
- A written chronology for any outage in the look-back window that still has an open cause code
- A close-out conversation with the person who will own the next week of checks
Left out
- Live probe installation, packet capture, or access to private keys of any system
- Crew dispatch, spare-part orders, or landlord negotiation
- Holding or processing of subscriber funds or cryptocurrency assets
- Investment, trading, or wallet advice of any kind
How the days run
- Day 0: you name the cluster, the look-back window, and who will sit with us.
- Day 1 morning: we sit with the extracts and mark sectors that moved, not averages that hid them.
- Day 1 afternoon: complaint text is read against those sectors; mismatches are listed.
- Day 2: outage tickets in the window are lined up with generator logs, fibre tickets, and weather notes you already have.
- Close: a single walkthrough note is left with the desk; we do not retain a live feed.
Preparation
Have two weeks of hourly counters for the cluster, the ticket export, and a printed or PDF neighbour list. Name one person who can explain local naming (site codes vs. marketing names).
Constraints
We do not accept work that requires us to bypass access controls. If extracts cannot be shown, the walkthrough is postponed rather than guessed.
Next step
Write to contact@releasegridpath.digital with the cluster name and the look-back dates. There is no inquiry form on this site. Correspondence details are on the correspondence page.