Coverage planning
RF coverage prediction software: from site parameters to a client-ready report
A coverage prediction is useful when it helps an engineer decide what to build, set expectations before a visit, and explain the result afterwards. This workflow keeps the inputs, map and assumptions together.
What RF coverage prediction software does
RF coverage prediction software estimates the received signal level around one or more transmitters. It turns a radio design into a map: site location, antenna height, azimuth, tilt, frequency, power and a propagation model become a predicted signal-strength layer.
That is different from a mobile operator coverage map. An operator map describes a public network as it is advertised. A planning tool starts with your site and your antenna parameters, so it is used before deployment, before an antenna adjustment, or before a field visit.
For a field engineer, the valuable output is not just a colored heatmap. It is a repeatable record of what was assumed: the coordinates, EIRP, antenna orientation, model, terrain option and coverage threshold. That makes a result discussable with a client and comparable with drive-test measurements later.
The minimum inputs for a useful prediction
A fast first-pass study does not require a GIS project. Start with the information that normally exists in a design file or site survey:
- Site position: latitude and longitude of the antenna location.
- Antenna geometry: height above ground, azimuth, beamwidth, mechanical and electrical tilt.
- RF chain: frequency, transmitter power, feeder loss and antenna gain, expressed as EIRP where possible.
- Environment: the propagation model and whether terrain or clutter should be considered.
- Receiver assumptions: receiver height and the signal level that marks usable coverage.
When data is uncertain, write it down instead of hiding it. A report that labels an antenna gain as assumed is more useful than a precise-looking map based on an unknown input.
A practical coverage-planning workflow
1. Build the site and its sectors
Add the physical site once, then add its sectors at the same location. Give every sector the correct azimuth and band. This keeps a three-sector macro site understandable on the map and prevents a report from looking like three unrelated transmitters.
2. Choose an appropriate model, then calculate
Empirical models are appropriate for a first planning view, but every model has a validity range. For example, ITU-R P.1546 describes point-to-area predictions for terrestrial services; a simple free-space calculation does not represent terrain shadowing or local clutter. Use a model that fits the band, terrain and scale of the study, then state it in the result.
3. Read the map as a prediction, not a measurement
Strong, usable and weak areas are decision zones. They are not a guarantee that a handset will see the exact same level at every point. Building penetration, traffic load, antenna pattern accuracy and local obstructions can move the field result by several decibels. The useful question is: where should the engineer verify first?
4. Export the evidence
A client report should include the map and legend, but also the parameters and model. That makes the design review faster and creates a baseline for a later optimisation visit.
What separates a map from an engineering deliverable
| Map-only output | Useful RF planning deliverable |
|---|---|
| Color layer with no source parameters | Coverage map plus site, sector and RF-chain inputs |
| Unknown model | Named propagation model and terrain/clutter assumptions |
| One-off screenshot | PDF that can be shared, reviewed and repeated |
| No validation path | Drive-test comparison after the intervention |
This is why the workflow matters more than a long feature list. On a small project, the fastest tool is the one that lets you enter the actual design values, review the map with the client and keep the assumptions beside it.
How to validate a coverage prediction in the field
Use the prediction to plan a measurement route: sample the center of the main lobe, both sector edges, a marginal area and any terrain shadow indicated by the map. Record signal level and quality, then compare the trend rather than one isolated reading.
When prediction and measurement diverge, check the basics before changing the model: antenna orientation, total tilt, feeder loss, actual output power and the band that was measured. The propagation-model guide explains how the model choice affects the result; the Network Drive Test companion helps collect a field trace.
Use the Coverage Planner for your next study
GSM Field Suite's Cell Coverage Planner is made for this first-pass workflow: place sites and sectors on a map, adjust the antenna and radio parameters, run the prediction and create a report containing the map and assumptions. The free plan is suited to trying a study; the Pro plan adds report exports for client work.
Sources and further reading
- ITU-R P.1546: Method for point-to-area predictions for terrestrial services
- ITU-R P.525: Calculation of free-space attenuation
- GSM Link Budget: A Practical Field Guide
- Antenna Height and GSM Coverage: A Planning Guide
Predictions are planning estimates. Confirm deployment and acceptance criteria against the operator's procedures and field measurements.