JobFrame / Long Term Care

healthcare_delivery

Long Term Care

Long Term Care is a job family — a stable cluster of work with shared purpose, outputs, responsibilities, and labor-market identity. On the frame it spans 17 canonical roles across 3 tracks (M, P, S), 17 levels in all.

The job family matrix

Every level of the family, side by side — what genuinely changes as the work scales, and what it pays. Open any level for its full profile.

M1
Long Term Care Nursing Supervisor
3–6 yrs
open profile ›
P1
Long Term Care Nurse
0–2 yrs
open profile ›
S1
Certified Nursing Assistant
0–1 yrs
open profile ›
M2
Senior Nursing Supervisor, Long Term Care
5–8 yrs
open profile ›
P2
Long Term Care Nurse
1–3 yrs
open profile ›
S2
Nursing Assistant
1–3 yrs
open profile ›
M3
Long Term Care Nursing Manager
8–12 yrs
open profile ›
P3
Long Term Care Nurse
3–5 yrs
open profile ›
S3
Senior Certified Nursing Assistant
3–5 yrs
open profile ›
M4
Senior Manager of Long Term Care
10–15 yrs
open profile ›
P4
Senior Long-Term Care Nurse
5–8 yrs
open profile ›
S4
Advanced Long-Term Care Nursing Assistant
5–8 yrs
open profile ›
M5
Director of Long Term Care Nursing
12–18 yrs
open profile ›
P5
Expert Long Term Care Nurse
8–12 yrs
open profile ›
S5
Lead Long Term Care Nurse Specialist
8–12 yrs
open profile ›
M6
Senior Director of Long Term Care Services
15–25 yrs
open profile ›
P6
Principal Long Term Care Nurse
12–18 yrs
open profile ›
ScopeA single teamOwn tasks within a defined componentA single task type or queueAn established team or sub-functionDefined deliverables / small featuresA defined queue or customer setMultiple teams or a sub-functionFeatures or a sub-system end-to-endEscalated / complex casesA function or departmentA system or set of related featuresTeam process and qualityMultiple functions or a large departmentMultiple systems or a technical domainFunction-wide support practiceA major function or divisionOrganization-wide architecture and the hardest problems
AutonomyManages within established goalsClose supervision; work reviewed frequentlyClose supervision; follows defined proceduresOwns planning for the groupGeneral supervision; reviewed at milestonesGeneral supervision; handles standard cases independentlySets goals within functional strategyWorks independently on standard work; reviewed on the non-standardLimited supervisionOwns area strategy and budgetSelf-directed; reviewed at critical decision pointsWorks independently; owns improvementsOwns multi-year strategy for the areaSets direction within the domainSets direction for the support disciplineAccountable for division strategy and outcomesDefines direction; minimal oversight
ComplexityDay-to-day delivery and people issuesRoutine problems with known solutionsRoutine, well-defined requestsCross-project coordination and prioritiesSome non-routine problems; applies established patternsStandard issues within known proceduresMulti-team execution and resourcing trade-offsDiverse problems; adapts existing approachesComplex or non-standard casesStrategic priorities and cross-functional alignmentComplex, ambiguous problems; devises new approachesCross-case patterns and process gapsOrg-level trade-offs and investmentNovel, high-ambiguity problems; establishes the approachProgram-level and systemic support problemsEnterprise priorities and external factorsStrategic, open-ended problems shaping the technical future
ImpactTeam output and healthOwn deliverablesIndividual transactionsGroup delivery and developmentOwn and immediate-team deliverablesCustomer satisfaction for own queueSub-function outcomesProject / team outcomesResolution quality on the team's hardest casesFunction-level resultsMulti-team / function outcomesTeam-level quality and efficiencyMulti-function resultsOrg / multi-team outcomesSupport strategy across the functionDivision-wide / organization-wideOrganization-wide
Decision rightsOwns team execution, hiring input, performanceFew independent decisions; escalates the restActs within scripts; escalates exceptionsOwns staffing, priorities, performance for the groupRoutine technical choices within guidanceResolves standard cases; escalates complexOwns goals, budget input, and people decisions across teamsOwns implementation decisions for own scopeOwns escalation resolution within policyOwns strategy, budget, and org design for the areaOwns technical decisions for a system; influences adjacent designOwns process and quality decisions for the teamOwns investment and org design across functionsAuthority over a technical domainAuthority over support practice and standardsOwns strategy, budget, and org for a divisionSets technical strategy for a major area
LeadershipDirect people management of one teamNone — building the craftNoneManages a team; sometimes manages leadsMay guide internsNoneManages managers and/or several teamsMentors juniors informallyGuides junior support informallyLeads managers; sets direction for the functionTechnical lead for focused efforts; mentors severalMentors and coordinates the support teamLeads directors and managersLeads cross-team technical initiativesSubject-matter authority; shapes the practiceLeads the leadership of a divisionRecognized authority; multiplies many teams

Adjacent families

The work that sits closest to Long Term Care on the frame — by coordinate distance, not by hand.

Map your org's Long Term Care roles → Upload your job list and get every role mapped to the frame — with leveling, market pay, and an architecture-quality report.