A clear line drawn between two towers is not a microwave design; terrain can intrude into the working path. Trees can grow into a marginal clearance. A channel that looks available in an equipment table can conflict with a coordinated link; one incorrect antenna centerline can change both the path profile and the structural configuration. Geometry starts the work. Evidence finishes it.
This guide explains how we control a terrestrial point-to-point backhaul path from endpoint survey through licensing inputs and installation acceptance; it does not offer a universal availability promise. Climate data and selected equipment plus owner objectives and licensed parameters decide the actual design; we show where assumptions enter so another engineer can reproduce the result and challenge it.
What Microwave Backhaul Design Engineering Must Prove
Microwave backhaul design engineering must prove 2 linked conditions: the proposed radio path meets the owner's performance objective under documented propagation assumptions and the sites can support the licensed configuration. The package connects coordinates, antenna elevations and frequency inputs to a reproducible path profile plus link budget, interference record, structural interfaces and acceptance plan.
Endpoints are engineering objects, not labels; we verify datum and coordinate source plus ground elevation and proposed antenna centerline. Structure identity matters. So do mount position and azimuth feasibility. Indoor unit location or outdoor radio placement affects losses and cabling. Power and grounding interfaces follow the owner standard; a path calculation built on approximate pin locations may look precise while missing the actual support structure by enough to invalidate its geometry.
The design basis names capacity need and service role plus protection state and performance objective; a temporary construction link is not judged like an aggregation path supporting several sites. We define interface rate and traffic expectation without promising throughput from modulation labels alone. Equipment behavior can adapt under fading. The network layer can also affect delivered service; microwave engineering supplies the radio-path basis and exposes dependencies outside it.
Separate path proof from site feasibility
Path engineers control terrain and obstruction evidence plus propagation modeling and link calculations; frequency coordinators manage required interference and licensing steps. Structural engineers address antenna and mount demands under project criteria; site teams manage power and grounding plus access. Project managers connect those outputs. No one discipline should imply another's approval. A passing link budget does not prove structural capacity or license authority; a strong tower does not clear an obstructed path.
Our candid limitation is material: a desktop surface model cannot guarantee future clearance; vegetation heights can be stale. New buildings may be absent. Atmospheric behavior is statistical rather than certain. A field visit can miss seasonal tree canopy or proposed development; we record source dates and conservative treatments, then require targeted verification where the margin depends on uncertain obstruction height. We would not recommend construction from a path profile whose decisive surface source is unknown.
The Microwave Backhaul Evidence Gates
Each gate below closes a different failure path. Keeping them separate prevents a strong radio calculation from masking an unbuildable mount or unresolved coordination issue. The release trigger is evidence, not a scheduled percentage. Owner standards and jurisdictional requirements remain controlling. A project can add stricter gates when service consequence warrants them.
| Gate | Decision | Evidence | Release trigger |
|---|---|---|---|
| Service basis | What must the path carry? | Capacity; topology; availability objective; interfaces | Written design criteria |
| Endpoint control | Where are both antennas? | Coordinates; elevations; structure IDs; mount zones | Survey confidence accepted |
| Path feasibility | Can the path support the objective? | Profile; obstructions; propagation assumptions; alternatives | Margin basis documented |
| Radio configuration | Which equipment state is modeled? | Band; channel; gains; losses; modulation behavior | Link budget frozen |
| Coordination and site | Can it be authorized and installed? | Interference record; filings; structural and power interfaces | Required approvals matched |
| Acceptance | Does installed truth match the design? | Alignment; configuration; tests; redlines; license data | Operations accepts |
Control endpoint coordinates and elevations
We document coordinate reference and collection method; ground elevation comes from a named source and receives field reconciliation where practical. Antenna centerline is measured from the same vertical basis at both sites. Existing tower drawings can help, but the installed structure and proposed mount zone still need confirmation; a one-line note saying use tower height leaves open whether that means overall tip or platform or antenna centerline.
Azimuth feasibility gets equal attention; another tenant's sector or a climbing facility can block the theoretical bearing. The proposed dish may conflict with an existing mount. Cable route length can change when the only workable mount sits on the far face. We preserve candidate mount positions until structural and site reviews close; the path model then follows the approved centerline rather than the first convenient elevation.
Build a path profile that exposes uncertainty
The profile includes terrain and earth-curvature treatment plus known clutter and structures; it evaluates the relevant Fresnel region under the selected frequency and path geometry. We show the clearance criterion from the project basis rather than claiming that visible line of sight is enough. Optical visibility can coexist with poor radio clearance; conversely, a map that appears blocked may need better elevation or obstruction data before rejection.
The International Telecommunication Union's current ITU-R P.530 recommendation addresses propagation data and prediction methods needed for terrestrial line-of-sight systems. It provides recognized engineering methods, not a universal result for every project. The designer must select the applicable method and current supporting data plus local inputs. We preserve model version and parameter sources so the calculation can be reproduced.
Profile control: show the source and date for every decisive obstruction. A smooth terrain line should never hide an assumed tree height or an unmodeled building.
Model Propagation and the Full Link Budget
The link budget begins with licensed or proposed transmit parameters and selected antenna gains; it includes feeder or waveguide loss where used plus connector and branching losses. Receiver threshold is tied to the modeled modulation state and equipment release. We calculate fade margin from those controlled inputs; then we connect margin to the performance method rather than presenting one large number as proof of availability.
Free-space loss is only one term; multipath behavior and atmospheric effects can dominate long terrestrial paths. Rain attenuation becomes more significant in certain bands and climates. Terrain reflections can create another exposure. Adaptive modulation changes how service degrades. We model the selected configuration and make the design objective explicit. A vendor calculator can support the work; it should not be the only record when its assumptions are hidden.
Treat fade mechanisms separately
Rain and multipath are not interchangeable fade labels; their relevance changes with frequency and path length plus climate and geometry. The engineering file identifies which prediction methods were used and what data edition supported them. Where space diversity or another mitigation is proposed, the package models the actual separation and equipment behavior; we avoid universal claims such as one antenna size guarantees five nines because no single size closes every path.
Performance results should include sensitivity to uncertain inputs; if a small height change materially alters clearance or predicted reliability, that is a design warning. We run alternatives at practical mount elevations and compare the consequence. Sometimes raising a dish improves obstruction clearance but worsens structural demand or cable loss; sometimes a shorter path to another site wins. The recommendation states the cross-discipline trade-off rather than optimizing the radio model alone.
Fiber can be the better transport choice where a buildable corridor exists. The small cell fiber backhaul guide describes route and pathway considerations for distributed sites. Microwave avoids continuous physical pathway construction, but it adds spectrum coordination and line-of-sight dependency. We compare lifecycle constraints. We do not frame either medium as universally cheaper or faster.
Coordinate Frequency and Licensing Inputs
A technically strong path still needs the correct regulatory route; FCC 47 CFR Part 101 contains rules for fixed microwave services. Section 101.103 addresses frequency coordination procedures under its stated scope. The coordinator and licensee must apply current rules to the actual service and band; this guide does not replace legal or licensing review.
Coordination inputs must match the design baseline: coordinates and antenna heights plus make and model and polarization plus azimuth and emission parameters; a late antenna substitution can affect interference behavior and structural demand at once. We therefore link coordination records to revision-controlled equipment IDs. Proposed data and licensed data remain separate until authorization; the construction package identifies which state is approved for installation and operation.
Preserve the interference record
Interference analysis is not a one-time screenshot; the file retains input data and coordination notices plus responses and final parameters. Exceptions or conditional resolutions need owners. The network inventory should record the authorized channel and polarization plus antenna characteristics. That history matters when another path is proposed nearby or equipment is replaced; a future engineer should not have to reverse-engineer the licensed configuration from a radio label.
Unlicensed or lightly licensed options require their own technical and regulatory analysis. They are not shortcuts around interference risk. Band rules and power limits plus equipment authorization conditions matter. We avoid recommending a band solely because hardware is available. The service objective and local interference environment plus authorization path must align. The design file names which assumptions remain provisional.
Procurement stays tied to that baseline. Draftech's vendor engagement route can support sourcing coordination, but product selection still follows approved technical parameters. Alternate radios or antennas return to engineering and coordination review as needed. A same-band product is not necessarily interchangeable. Antenna pattern and connector arrangement plus software capability can change the installed result.
Self-critical weakness: a highly detailed model can create false confidence when one endpoint elevation or clutter input is weak. We prefer a plainly labeled uncertainty to a precise result built on an undocumented assumption.
Connect Site Design to Installation and Acceptance
The site package identifies antenna centerline and azimuth plus mount and radio configuration; cable or waveguide routes and indoor interfaces are shown. Grounding and power follow owner standards and qualified review. Structural approval must match the actual dish and mount arrangement. Installation crews receive alignment targets and hold points; the package avoids prescribing rigging means unless those documents come from the accountable qualified party.
Alignment evidence should be more than an installer statement; the acceptance plan identifies instrument and configuration plus recorded values and responsible reviewer. It also captures radio software state and configured channel. Test thresholds come from the approved design and owner procedures; we do not invent universal receive-level tolerances. The final result must reconcile to the licensed or otherwise authorized parameters for the path.
Commissioning verifies the radio link and its network interfaces. A strong received level does not prove correct VLAN or timing behavior. Conversely, traffic passing during clear weather does not prove the path meets its fade objective. We keep radio alignment evidence and network service tests as separate records. Operations accepts both under the approved criteria. Failed checks remain traceable through correction and retest.
Draftech performs engineering in-house; when construction is included, Draftech provides full turnkey delivery through Draftech-managed subcontract crews under our QA/QC and safety oversight. Our delivery model keeps engineering authority distinct from contractor means and methods; field deviations that affect path geometry or licensed parameters return to the accountable reviewer before acceptance.
Closeout updates coordinates and antenna elevations plus equipment IDs and authorized parameters. It attaches path tests and alignment records plus redlines. Structural and licensing references remain linked. The small cell explainer provides context for distributed access nodes that may feed into this transport layer. Draftech's service-area approach supports delivery across markets while current local and federal controls remain project-specific.
Microwave Backhaul Recommendation by Decision Trigger
Rural ISP network planner: choose microwave when both sites have supported geometry and the modeled path closes the written objective with an achievable authorization route. Keep fiber as the alternative when future vegetation or one uncertain obstruction consumes the path's practical margin. Do not let trench avoidance decide before path proof.
Carrier transport engineer: make reproducibility the release trigger. Require controlled endpoints and equipment parameters plus current propagation inputs and a retained interference record. Reject a result that cannot be recreated outside the vendor portal. The design should show which assumption changes would force reanalysis.
Site acquisition or tower team: hold the final mount position until path and structural reviews agree on one centerline. A higher dish may solve clearance while creating a different structural problem. A lower dish may reduce demand but lose margin. One coordinated location must drive the path model and installation package.
Our recommendation trigger is direct: if endpoint elevation or decisive obstruction data remains unsupported, do not release procurement as though the path were proved. Investigate first. Draftech's wireless backhaul design team can develop the controlled record. For a path feasibility review, email our microwave engineering team.
