F-Tags vs K-Tags: Understanding the Two Surveys Every Nursing Home Faces

Most administrators know what an F-Tag is. Fewer understand that the K-Tag findings sitting on their desk come from a completely different survey, governed by a different code, evaluated by a different surveyor, and carrying different requirements for the Plan of Correction.

This guide walks through what F-Tags and K-Tags actually are, why they exist as separate compliance frameworks, and what facility leaders should know about handling each.

The two-survey reality

A skilled nursing facility actually undergoes two distinct survey processes from the state agency contracting with CMS. The Health Survey looks at resident care, quality of life, governance, and clinical operations — basically, how the facility cares for the people inside it. The Life Safety Code Survey looks at the building itself — the physical environment, fire safety systems, egress paths, and how the structure protects residents during an emergency.

The Health Survey produces findings cataloged as F-Tags. The Life Safety Code Survey produces findings cataloged as K-Tags. Most facilities receive both surveys during the same cycle (typically annually), but they're conducted by different surveyors trained in different bodies of regulation, and the findings come out as separate Statement of Deficiencies documents on separate CMS Form 2567s.

F-Tags — federal resident-care requirements

F-Tags catalog deficiencies against 42 CFR Part 483, the federal regulations governing skilled nursing facilities participating in Medicare and Medicaid. The tag number identifies a specific regulatory requirement, and surveyors evaluate compliance using CMS Appendix PP, the State Operations Manual interpretive guidance.

Examples you've probably seen:

• F600 — Free from Abuse and Neglect — covers any failure to protect residents from physical, verbal, or sexual abuse, mistreatment, or neglect.
• F689 — Free of Accident Hazards / Supervision / Devices — covers fall prevention, hazard supervision, and the use of devices like bed alarms or assistive equipment.
• F684 — Quality of Care — a broad category covering treatment for pressure ulcers, range-of-motion issues, vision and hearing care, and other clinical quality concerns.
• F880 — Infection Prevention and Control — covers infection control program implementation, surveillance, antibiotic stewardship, and outbreak response.

The Plan of Correction for an F-Tag has to address the affected residents, identify others potentially at risk, describe systemic changes (typically policy revisions and staff training), establish monitoring (audits, quality assurance reviews), and commit to a completion date.

The clinical staff own most F-Tag responses. The Director of Nursing typically leads on care-related F-Tags. The Administrator owns the systemic and governance components. The MDS Coordinator may be involved for care planning citations. Training records, in-service documentation, and clinical audits are the standard evidence.

K-Tags — Life Safety Code requirements

K-Tags catalog deficiencies against NFPA 101, the National Fire Protection Association's Life Safety Code, as adopted by CMS under 42 CFR §483.90(a). The "K" doesn't stand for anything mnemonic — it's just the prefix CMS uses to distinguish Life Safety Code citations from F-Tag (health) citations.

Examples that appear frequently — see our top 10 K-Tags listicle for the broader landscape:

• K0223 — Doors with Self-Closing Devices — covers the function of self-closing devices on corridor and smoke barrier doors.
• K0353 — Sprinkler System Maintenance — covers the maintenance, inspection, and testing of automatic sprinkler systems.
• K0761 — Fire Door Inspection — covers the annual inspection and condition of fire-rated door assemblies under NFPA 80.
• K0291 — Emergency Lighting — covers the installation, testing, and maintenance of emergency lighting systems.

K-Tags are evaluated against the specific NFPA chapter and section referenced in the citation. NFPA 101 covers the broad Life Safety Code, but specific systems are governed by adjacent NFPA codes — fire doors by NFPA 80, sprinklers by NFPA 13 and 25, fire alarm systems by NFPA 72, and so on. A surveyor citing a K-Tag will name both the NFPA 101 section that applies and the specific NFPA reference code where the technical requirement lives.

The Plan of Correction for a K-Tag has the same five-component structure as an F-Tag POC, but the content is meaningfully different. Corrective action means physical repair or replacement, not policy revision. Identification of others affected means inspecting comparable equipment building-wide, not auditing other residents' records. Systemic changes mean inspection and maintenance schedules, vendor coordination, and capital planning, not staff training and care plans. Monitoring means periodic walk-throughs and annual NFPA-required inspections, not clinical audits.

The Maintenance Director typically owns most K-Tag responses. The Administrator owns the budget and vendor coordination. Outside contractors — fire door inspectors, sprinkler companies, electrical contractors — are often essential partners. The complete K-Tag Plans of Correction guide walks through the regulatory framework and POC structure in detail.

Side-by-side: F vs K at a glance

Why the POC approach differs

The structure of a Plan of Correction — five components, signature lines, completion date — is the same for F-Tags and K-Tags. The substance is different because the underlying compliance question is different.

An F-Tag POC asks: how will you change how you care for residents to prevent this from happening again? The answer involves people — staff training, supervision, policy enforcement, care plan revision.

A K-Tag POC asks: how will you maintain the physical building to comply with code? The answer involves systems — inspection schedules, work order processes, contractor relationships, capital planning.

Surveyors expect a K-Tag POC to feel grounded in the physical reality of the building. A clinical-sounding K-Tag POC ("staff were re-educated on the importance of fire safety") will get rejected. A K-Tag POC needs verbs like inspected, replaced, repaired, tested, documented, scheduled. It needs vendor names and dates. It needs NFPA references where the F-Tag POC would cite 42 CFR.

The reverse is true for F-Tag POCs. A facilities-sounding F-Tag response ("the door alarm was replaced") doesn't address the clinical practice issue that generated the citation. F-Tag POCs need verbs like assessed, revised, trained, monitored, audited. They need clinical references.

Common pitfalls

The most common mistake facilities make is treating K-Tags as a Maintenance afterthought. A K-Tag citation is just as much a CMS compliance matter as an F-Tag, with the same formal POC requirements, the same revisit process, and the same potential for enforcement remedies if the corrective action is unsatisfactory.

The second most common mistake is using F-Tag clinical framing in a K-Tag POC. Staff training is rarely the right answer to a fire door deficiency. The right answer is fixing the door, scheduling the inspection, and documenting both.

The third common pitfall is missing the timing implications of K-Tag deadlines. Some K-Tag corrective actions require vendor coordination (a fire door inspector, an alarm panel technician) that may have lead times. Facilities that wait until after receiving a citation to call the vendor sometimes can't complete the physical repair within the timeframe the POC commits to.

A practical pattern that works: when a Life Safety Code survey is announced or expected, the Maintenance Director should already have a current annual inspection cycle running, with vendor contracts in place and recent inspection reports on file. The K-Tag findings that do come in are then narrow, specific, and addressable within standard POC timeframes.

Getting both right

The facilities that handle survey season well are the ones that recognize F-Tags and K-Tags as two parallel compliance tracks requiring different people, different documentation, and different POC framing. Treating them as one problem produces weak responses on both sides.

If you're dealing with a fresh Statement of Deficiencies and need a starting point that gets the framing right — whether it's an F-Tag POC grounded in Appendix PP or a K-Tag POC grounded in NFPA 101 — EasyPOC routes your citation to the right framework automatically based on the tag prefix.

Paul Richards, RN, MSHI

Founder, EasyPOC

Paul Richards is a registered nurse and healthcare informatics leader who oversees quality and compliance across a network of six skilled nursing facilities in New York City. He holds a Master of Science in Health Informatics and built EasyPOC to solve the compliance documentation challenges he witnessed firsthand every day.