Everything a senior engineer would bring to the bench.

The Irregular Terrain Model the professionals use, at the reliability level you specify, with the terrain roughness measured from USGS elevation data around your actual site instead of guessed from a menu. Plus Hata, COST-231, and Egli for quick estimates.

Give it two coordinates and it pulls the actual USGS elevation profile between them, runs Longley-Rice point-to-point, and tells you line of sight or obstructed, the loss, and the margin.

A full fixed-microwave link budget between two sites: free space and gaseous loss, antenna gains, EIRP, receive signal, and fade margin, with Vigants-Barnett multipath and ITU-R P.530 rain availability worked out to the worst-month and annual percentages, and a side-view profile showing the direct ray, first Fresnel zone, and earth bulge.

The propagation map runs a Longley-Rice radial sweep over real USGS ground profiles, up to 360 radials, and draws the actual irregular coverage polygon: shorter into the ridge, longer down the valley, with forest and built-up clutter from land cover data figured in at the receive end.

A contour answers how far. This answers how good, and where: signal levels over real USGS ground profiles, painted bin by bin into usage classes from a portable inside a building to a mobile on a roof antenna, with the square miles each covers. No class floor is invented. Each is your receiver threshold plus the antenna correction the TIA standard tabulates for that band plus the loss you enter, and the page shows that arithmetic.

Upload a pattern file (MSI Planet or NSMA) or give a beamwidth, point the boresight, set the tilt, and the contours and tile studies follow the pattern instead of assuming omni. Patterns live in a shared library for the whole operation.

The public-safety coverage-acceptance method: a uniform tile grid, a real Longley-Rice median for every tile, and predicted area reliability against your target, using the channel performance criterion you enter from the TSB-88 revision you design against. Bound the study to the area you actually serve, traced on the map or uploaded as GeoJSON or a shapefile, and reliability averages over those tiles instead of a circle. Interferers, co-channel or adjacent, apply the receiver's own rejection.

Every propagation study, channel search, and TOWAIR screen prints or downloads as a PDF under your operation's name: parameters, results, the map, and the planning-study disclaimers, kept in a report history and ready to hand a customer or attach to a coordination request.

Third and fifth order products against your site frequency list, so interference turns up on paper rather than in a complaint. The list builds itself: click a tower and every licensed land mobile frequency loads from FCC data, along with the FM and TV stations on the site, because a 100 kW FM carrier is usually the strongest mixer on the tower and ULS cannot see it. Receive inputs are derived by band offset and labeled as convention, never guessed, and the report shows which frequencies came from where.

Zone radius, the 60% clearance rule, earth bulge, and the diffraction cost of that ridge or tree line near the path.

Ground rod resistance from soil and rod dimensions, and antenna-to-antenna isolation from vertical or horizontal separation for repeater planning.

Fade margin to edge and area coverage percentages, receiver noise floor, sensitivity conversions, RF exposure per OET-65, VSWR, and ERP.

Two pre-construction screens apply before a tower goes up, and the second is the one shops miss. FAA screening answers whether the FAA needs notice. AM protection answers whether a nearby broadcast station does: within a wavelength of a nondirectional station and over 60 electrical degrees tall, or within the lesser of ten wavelengths or three kilometers of a directional one and over 36. Notice is due 30 days before construction, and both screens run off the same coordinates against live FCC data.

Two things a co-located site needs that one transmitter at a time will never tell you. RF exposure summed across every emitter on the tower, each against its own frequency limit, because sources that pass alone can be over the line together. And a desense budget: transmitter noise landing in the receive channel, front-end blocking, the receiver's thermal floor, and how many dB of isolation the site is short. Both work from your measured numbers.

Coax loss by cable type and run length, dBm/watts/microvolt conversions, PL and DPL tone tables, emission designator decoding, audio line levels, DC voltage-drop, and battery runtime.

Put your licenses, and your customers', on a watch list by callsign or FRN, one at a time or imported straight from a spreadsheet. Sentinel RF checks every one against each weekly FCC data refresh.

Automatic expiration alerts at 180, 90, and 30 days out, delivered in the app and by email, the way a diligent office manager would catch them.

Construction notification deadlines sit right beside the renewal dates: the earliest unfiled deadline on each license, the days left, and alerts at 90 days, 30 days, and overdue. An unfiled buildout can cost the license, so it gets the same attention an expiration does.

Add a structure by its ASR number, or add your owner FRN and pick up every tower registered to you at once, with newly registered ones joining on their own. Name each site the way your crew does, not by its registration number.

Alerts when a watched structure changes owner, changes status, or changes height, and when an application is filed against its registration. That last one is the earliest warning there is, because a filing lands before the registration itself changes. It matters whether you own the tower and lease space out or just have gear on someone else's: a site going up for dismantlement is not something to learn from a field visit.

Every license whose transmit site is that structure, listed against it. This is the FCC's own record of who is on the tower, not a guess from nearby coordinates, so it is worth trusting for a tenant audit or a co-location question.

Define an area and stay aware of new antenna-structure applications and grants inside it. A simple, weekly heads-up on what is being proposed or built nearby, useful for planning, coordination, and local awareness.

Set an area and a frequency band, and get notified when a new license is granted or applied for nearby: the coordination and interference check a system operator actually needs.

Define the area as a simple radius, a polygon you trace on the map, or a boundary you upload as GeoJSON or a shapefile, reprojected for you automatically.

Renewal windows, expirations, status changes, and new-activity alerts collect in one place, so nothing depends on one person remembering to check.

Hold the mic button in the chat bar and talk. It works in every browser, so a tech with a probe in one hand can still ask a question.

For general or background questions, an optional open-web fallback can be turned on. It is clearly labeled and never used to answer a spec or a procedure.

Upload your logo once and it prints at the top of every study report, so what you hand a customer looks like it came from you. If the logo already carries your name, tell Sentinel RF and it leaves the printed name off rather than saying it twice.

Owner, admin, and member roles keep control where it belongs. Each person signs in with their own seat; credentials are never shared.

Add or remove seats from the admin console with prorated changes previewed before you confirm, and manage billing from a self-serve portal.

See usage by seat and an audit log of who did what, so an owner can run the operation instead of running the software.

Your documents stay isolated to your operation and are never used to answer another operation's questions. Export your data any time from the admin console.

The platform is actively monitored for health and reliability, with automated offsite backups, so your library and history stay safe.