When Was This Cable Ready for Service? A 7-Step RFS Coax Verification Checklist

I'm a quality compliance manager at an RF communications company. I review coax installations before they're accepted—roughly 200 cable runs and terminations per year, going back more than four years now. In 2024, I rejected about 12% of first deliveries. Most of those were for connector mismatches, failed VSWR tests, or missing paperwork, in that order.

When someone asks, "when was this cable ready for service (RFS)?" they're usually not asking me for a calendar date. They're asking a harder question: was it actually verified? By whom? With what equipment? A cable run is not ready for service on the day it's pulled through the trays. It's ready on the day it passes a specific set of checks.

If you're deploying a base station, upgrading a distributed antenna system, or installing radiating cable for in-building cordless phone systems (DECT in hospitals, office towers, and warehouses—still coax, still RF), this is the checklist I work through before I put my name on the acceptance form. Seven steps. No shortcuts.

First, understand what "RFS" means on your project

RFS is one of those acronyms that shows up twice at the same job site. Worth sorting out before you go further:

• Radio Frequency Systems—the manufacturer. If your purchase order says "RFS coax," that's the brand. RFS makes a wide range of coaxial cables, connectors, and RF components, and their stuff is common on base station builds.
• Ready for Service—the acceptance milestone. A cable is "RFS" when it has been verified and cleared to carry RF power.

The install date and the RFS date are rarely the same. I've seen cables installed and terminated two weeks before anyone tested them. Under contract terms, the RFS date is the one that starts warranty clocks and triggers payments. If you don't know which date is on record, that's a problem worth fixing before cutover.

The 7-step ready-for-service checklist

I use this order deliberately: it catches the cheapest, fastest failures first, so you're not paying for expensive instrument time on a run that's already physically damaged.

Step 1: Review the design and the test plan

Before touching the cable, know what "pass" looks like. Which frequency band? What return loss threshold? What insertion loss budget? Which connector types at each end? What weatherproofing level is specified?

This sounds obvious, but in our Q1 2024 quality audit, three of 22 rejected runs had perfect test numbers—tested perfectly, against the wrong frequency band. The physical work was fine. The data was useless. That was a pure communication failure: the technician was told "run the standard test," and the test plan in the project spec said something different. Both sides used the same word ("standard") and meant different things. We didn't catch it until the acceptance review.

Step 2: Walk the entire cable path

Get out of the equipment room. Physically walk from one end of the run to the other. Look at bend radius at every transition. Look for kinks, crushed jackets, sharp edges, and cable ties tightened like they're clamping a fire hose.

Mechanical damage is the most common reason a brand-new coax run fails before it ever carries power. And it's usually not visible from the front of the rack—you have to walk the aisle, check the overhead trays, and look behind the cabinet.

I knew I should walk the full path before accepting one particular install, but I thought "what are the odds?" The odds caught up with me when a cable crushed against a rack edge started showing intermittent VSWR at 2.4 GHz. Front looked perfect. The damage was around the back. That little oversight turned into a site revisit and a replacement run.

Step 3: Verify the connectors (and know what they are in the first place)

In case part of your team is newer to this: connectors are the components that terminate the coax and join it to a radio, an antenna, or another cable. They're not just plumbing fittings. They are part of the transmission line, and the transition between cable and connector is where a huge chunk of RF energy gets reflected if it's done wrong.

Common base station connector types:

• 7-16 DIN—the old workhorse. Big, reliable, excellent PIM performance.
• 4.3-10—smaller and lighter than 7-16, increasingly common on new radios.
• Type N—often used on indoor systems and smaller equipment.

They all look similar from a few feet away. They are absolutely not interchangeable. I've seen this exact failure mode more times than I'd like to count: the install crew said "standard connector," the equipment side said "standard connector," and nobody discovered they were on different pages until the jumper would not mate with the radio port. One missing adapter and the whole sector stays dark on launch night.

Check the connector type on both ends against the project datasheet, and check the center pin before you mate anything. If a connector looks even slightly damaged, replace it. I know it's more cost up front, but a bad connector will fail a VSWR test and cost you a truck roll and a tower crew later. Trust me on this one.

Step 4: Check torque—hand-tight is not a torque value

Connector coupling nuts have specified torque ranges. The datasheet lists them for a reason: the connection needs enough pressure to seat the inner contact and fully engage the outer conductor. Too loose and you get arcing and PIM. Too tight and you deform the center pin or strip the threads.

If you're choosing between torque wrenches, look past the sticker price. I've been through this. A crew "saved" a few hundred dollars buying an uncalibrated torque tool, over-torqued a series of 7-16 DIN connectors, cracked the insulators, and the repair bill came out to $22,000 plus a two-week launch delay. The cheap tool wasn't the savings. The rework was the cost.

Step 5: Seal it like water is actively looking for a way in

Weatherproofing comes after the connection is mechanically verified, not before. Check every connector, every cable entry point, and every grounding termination. Use the correct cleaning sequence and the right self-amalgamating tape. An IP rating (per IEC 60529) only holds up when the installation actually follows the method that the rating assumes.

Water ingress is the slow killer. It raises VSWR gradually, creates intermittent faults, and corrodes connectors from the inside, where you can't see it until it's too late. I can't count how many "ready for service" cables came back with moisture in the connector within 90 days. (Ugh.) The fix is always more expensive than doing the weatherproofing once, properly, at installation time.

Step 6: Run the electrical tests and keep the numbers

This is the step that actually answers the question. A cable is ready for service when the measured values say so. Run a cable analyzer or VNA sweep and compare against the design plan:

• Return loss / VSWR across the operating band
• Insertion loss against the calculated loss budget for that cable length
• Continuity and grounding, if that's part of the system design

Keep the trace files. Don't just store "PASS" in a ticket. If there's ever a question about whether a cable was actually tested, the trace is the evidence. I once had a vendor claim a cable was "within industry standard" when the trace clearly showed a resonance dip in the operating band. The vendor's spec sheet said one thing; measured reality said another. The vendor rebuilt it at their cost, and now every contract we write includes a trace requirement in the acceptance criteria.

Step 7: Put the RFS date in writing

The ready-for-service date is the date the verification report is signed—not the install date, and not the date someone verbally says it "should be fine." So glad I made this step formal in 2022. Almost accepted a verbal handover once, which would have started the warranty clock early and made us responsible for a reinspection that wasn't ours. The written RFS date protects both sides. It says: on this day, this cable passed these tests, measured by this equipment, witnessed by these people.

Common mistakes that delay RFS

These are the ones I see most often when a project is trying to close out a site.

Skipping the final review out of routine

"It's basically the same cable configuration as the last site." Those are famous last words. In one case, we skipped the final check because the crew was rushing—and it wasn't the same. The connector was a 4.3-10 variant instead of the specified 7-16. $400 mistake multiplied across twelve sectors. The review exists exactly for the cases where everything feels the same.

Picking the cheapest component without counting time

I'll say it plainly, because this is where field experience changes your view: the lowest quote is rarely the lowest cost. I've seen a $200 savings on cable and connectors turn into a $1,500 problem when the cheaper connector caused a VSWR failure and a return visit. Count the truck roll, the labor hour inside a confined tower, the downtime—and the "savings" vaporize completely. In my experience reviewing 200+ runs a year, the lowest-price option has ended up costing more in about 60% of cases. Total cost of ownership is the number that matters.

Bottom line: a coax run is ready for service when it has been walked, measured, and documented. The install date is just the beginning. The RFS date is the proof.