How Many Employees Should I Schedule Each Shift at My Assisted Living Front Desk?

Why the gross-profit division beats headcount rules of thumb

Most communities staff the front desk one of three ways, and only one of them survives contact with a budget review.

The first is the habit method: one person at the desk, always, because that's how it's been since the building opened. It is cheap to administer and impossible to defend. It under-staffs Saturday, when three families show up unannounced within forty minutes of each other and the one associate on duty is on the phone with a pharmacy while a prospective daughter-in-law stands in the lobby reading a brochure and deciding you're disorganized. It over-staffs Tuesday at 2 p.m., when the lobby is empty and you're paying a fully loaded hourly rate for someone to reorganize the visitor log.

The second is the ratio method borrowed from care staffing. Clinical ratios — caregiver-to-resident — are the right tool for the care floor and often the subject of state licensure requirements, so you cannot ignore them there. But they are the wrong tool for the desk, because desk demand does not scale with census the way care demand does. A 40-unit community and a 90-unit community can have nearly identical tour volume if their marketing spend and referral-source mix are similar. Census tells you how much care labor you need. It tells you very little about how many phones ring.

The third is the gross-profit division, and it is the one this page is about. You agree on a number — the attributable gross profit a single front-desk associate should support across a shift — then you divide. Say $240 a day. Pull the desk's trailing three-to-six-month attributable gross profit by day of week. Monday attributes $480, so Monday wants two. Saturday attributes $720, so Saturday wants three. Wednesday attributes $250, so Wednesday wants one and you accept that the second body is a floater on call.

The reason this method beats the other two is that it forces an argument you should be having anyway: *what is the front desk actually worth?* The habit method never asks. The ratio method answers a different question. The division method makes leadership put a dollar figure on the seat, and once that figure exists, every scheduling decision downstream becomes arithmetic instead of politics.

There's a fourth approach worth naming because it shows up in larger operators: queue-theory or demand-curve modeling, where you model arrivals per hour, average handle time, and target abandonment rate the way a contact center does. It's rigorous and it's genuinely better for phone-heavy desks with predictable volume. It also requires call data most single communities don't collect cleanly, and it optimizes for service level rather than margin. If you have a central intake line handling 200+ calls a day across a portfolio, borrow the queue math. If you're one building, the division method gets you 80% of the accuracy at 5% of the effort.

How to choose between them

Pick the method that matches your data quality and your span of control, not the one that sounds most sophisticated.

Use the habit method only as a bridge. If you genuinely have no attribution data — no tour log, no source-tagged move-ins, no phone records — you cannot run the division yet. Staff one associate, start logging, and revisit in ninety days. Do not pretend you're doing math when you're doing memory.

Use census ratios for the care floor and licensure compliance, never for the desk. Keep them separate in your head and separate in your scheduling tool. Conflating them is how communities end up with a fully staffed desk on a low-tour Tuesday because occupancy happened to be high that month.

Use the gross-profit division for any single community or small group. It needs three inputs you can assemble from records you probably already keep: a visitor/tour log, a move-in list with a source field, and a rough margin figure per occupied unit. Three to six months of trailing data is enough to see day-of-week shape.

Use demand-curve modeling when the desk is primarily a phone operation — a regional intake line, a central concierge hub, a multi-building campus routing all inbound to one point. At that volume the cost of a two-minute wait is measurable and the arrival data exists.

A note on the middle ground: plenty of communities run a hybrid, using the division method to set the daily headcount and a light arrival curve to place the hours. That's the recommended default. The division answers *how many*; the curve answers *when*. Neither answers the other, and trying to make one do both is where schedules go wrong.

One more selection factor people skip — who owns the schedule. If your executive director builds it personally every week, the method needs to be simple enough to run in twenty minutes. If you have a scheduling coordinator or a business office manager who owns it, you can afford a more granular approach with hour-by-hour placement. Match the method's complexity to the actual time budget of the person doing it, or the sophisticated version quietly reverts to the habit version within two months.

Costs, timelines, and expected impact

The method itself is free. What costs money is the labor you're scheduling and, optionally, the software that publishes it.

The labor math. Work in fully loaded cost, not base wage. A front-desk associate's fully loaded cost is base hourly plus payroll taxes, plus whatever your benefits load runs, plus paid time off accrual, plus the training and turnover cost amortized across their tenure. In most operators, fully loaded lands meaningfully above the posted hourly rate — often in the range of 1.25x to 1.4x, though yours will differ and you should pull the real number from your controller rather than trusting a rule of thumb. Use that figure when you decide whether an extra Saturday associate pays for itself. If a second Saturday body costs you an eight-hour fully loaded shift and prevents a single lost tour that would have converted at your historical rate against your average monthly margin per unit, the payback question answers itself quickly — one retained move-in typically covers many weekends of incremental desk labor.

The software cost. Scheduling tools price three ways, and the pricing model matters more than the feature list for a single community:

• Per-user monthly pricing — common among the widely used shift apps. Cheap per head, but a desk team with weekend floaters and part-timers inflates the headcount fast. Better fit when each building runs a lean, stable crew.
• Per-location monthly pricing — you pay one flat figure per building regardless of how many people are on the roster. Dramatically cheaper for a community running a mix of full-timers, part-timers, and PRN floaters. Several tools in this category offer a free tier for a single location.
• Flat per-team pricing — a single monthly figure for the whole roster, common among lightweight web schedulers. Attractive when the roster is small and stable and you need a clean grid and nothing else.

• Custom-quote enterprise pricing — relevant only for multi-campus operators with credential tracking, complex 24-hour coverage rules, and union or fair-workweek compliance obligations.

Confirm current pricing on each vendor's own pricing page before you budget; these tiers change and the free-tier terms in particular move around.

The timeline. Realistic sequence for a single community starting from scratch:

• Week 1 — leadership agrees on the per-associate daily target. This is a conversation, not a calculation, and it usually takes one meeting plus one follow-up. Write the number down and say it out loud to the desk team.
• Weeks 2–4 — assemble trailing data. Pull the visitor log, the tour calendar, the move-in list with source attribution, and the phone records if you have them. Build a day-of-week average. If your records are messy, this is where the time goes.
• Week 5 — run the division, build the first schedule, publish it.
• Weeks 6–12 — observe. Track missed calls, unattended-lobby incidents, and tour-to-deposit conversion by day. Adjust.
• Quarterly thereafter — re-run the division against fresh trailing data.

Expected impact. Be honest about what this does and doesn't deliver. It does not manufacture demand. What it does is redistribute labor you're already paying for toward the hours that generate margin, and it gives you a defensible answer when the regional asks why Saturday has three people. The two measurable effects to watch are: (1) reduction in unattended-lobby minutes during peak tour windows, and (2) a shift in labor cost from low-traffic to high-traffic hours at roughly flat total hours. If total desk hours go *up* after implementing this, either your target is set too low or you were genuinely under-staffed and now you know it.

The RevOps framing is worth stating plainly, because it's what makes this different from ordinary shift scheduling: you're treating the front desk as a revenue-generating function with attributable margin, not as an overhead cost center to be minimized. Overhead gets cut. Revenue functions get resourced against their contribution. Which of those two the desk is depends entirely on whether you can attribute margin to it — and the attribution work is the real project here, not the division.

Implementation and handoff details

The math is the easy part. The handoff — getting the number from a spreadsheet into a published schedule people actually work — is where implementations stall.

Step one: define attribution boundaries before you pull a single number. Decide explicitly what the desk gets credit for. A defensible starting set: tours the desk booked or greeted, move-ins whose first touch was a desk-handled inquiry, ancillary service sign-ups processed at the desk, and retention touches logged during resident or family check-ins. Decide what it does *not* get credit for — referral-agency move-ins that arrived fully qualified, for instance, where the desk's role was administrative. Write the boundaries down. Half the arguments about this method are actually arguments about attribution.

Step two: pull trailing data by day of week, not by month. Monthly averages hide the entire point. You need Monday's number separate from Saturday's. Three months is the minimum; six is better because it smooths seasonal tour patterns. If you have a marketing campaign that ran for six weeks inside your window, note it — that period's numbers will overstate steady-state demand.

Step three: set the target with leadership in the room. The number needs to be spoken by the executive director, not derived by a spreadsheet in isolation, because every associate at the desk is going to hear it. The framing that works: "If you greet families warmly, capture every inquiry cleanly, and run an average front desk, your seat should be covered by no less than $X a day in attributable gross profit." That's the floor, not the goal.

Step four: divide, then place. Division gives you a headcount per day. Placement gives you start and end times. Pull the arrival curve from your visitor log and phone records. Most communities see a late-morning cluster and an early-evening cluster on weekdays, with a heavy Saturday mid-day block. Staff two across the busy tour windows and one steady presence through the quiet afternoon rather than parking everyone at 9 a.m. because that's when the shift template starts.

Step five: define coverage floors that override the math. The division can output "one associate" for a slow Wednesday. That's fine until that associate takes a lunch break. Every schedule needs hard floors the math cannot violate: the lobby is never unattended during posted tour hours; someone can always reach the phone; there is a named backup — a business office manager, a life enrichment coordinator, a supervisor — who covers breaks. For 24-hour communities where the desk anchors overnight, the overnight floor is usually a body regardless of what attribution says, because the function there is safety and access control, not margin.

Step six: hand off the running of it. Name one owner. Give them the target number, the attribution boundaries, the trailing-data pull procedure, and the coverage floors, in writing. Set a quarterly calendar reminder to re-run the division. Without a named owner and a recurring date, the schedule reverts to last week's copy-forward within a quarter, every time.

A note on the handoff to payroll and compliance. Whatever tool publishes the schedule should be the same system that feeds time and attendance, or you will reconcile two sources of truth by hand every pay period. If you operate in a jurisdiction with predictive-scheduling or fair-workweek requirements, the posting-notice window constrains how late you can adjust — check your state and municipal rules, because they vary substantially and penalties attach to late changes. Overtime alerts matter here too: a three-person Saturday built by pulling a weekday associate into a sixth day can quietly convert your margin gain into premium pay.

Where this method travels — adjacent desks and neighboring roles

The division generalizes further than the front desk, and seeing where it does clarifies where it doesn't.

The concierge and dining crossover. In communities with a dining program, desk staff and front-of-house staff often overlap in the same people. If your desk associate covers the dining room at lunch, your attribution has to account for both roles or you'll systematically under-count the seat. Hospitality-focused scheduling tools handle meal-service demand curves well and can tie front-of-house labor to a labor-percentage target — a different but compatible framing to the gross-profit division.

The sales and marketing desk. Some communities separate the front desk from a dedicated senior living advisor or sales counselor. When that split exists, attribution gets cleaner: the advisor owns tour-to-deposit conversion, the desk owns first-touch capture and handoff quality. Run the division separately for each. Blending them produces a number that justifies neither role.

Multi-building campuses. Once you're routing inbound across several buildings, the question shifts from "how many at this desk" to "how many at the hub plus how many at each satellite." The division still works, but you run it twice — once for the centralized function, once per building — and the coverage floors dominate the math more than they do in a single community.

Adjacent industries with the same shape. The method transfers cleanly to any environment where a front-of-house seat drives attributable margin: multi-unit retail, single-store retail, restaurant front-of-house, furniture and mattress showroom floors. The mechanics are identical — set a per-employee target, divide the shift's attributable gross profit, place against the traffic curve. What changes is the attribution model and the coverage floors. Assisted living is unusual in that the coverage floors are partly a safety and licensure matter, not purely a service-quality one, which is why the overnight shift is the one place the math routinely loses to the floor.

Upstream and downstream effects. Upstream, this method creates pressure on your marketing team to source-tag leads properly, because attribution quality determines schedule quality. Downstream, it gives you a labor-cost line that moves with demand, which makes your monthly operating variance easier to explain. Both are good side effects, and both are reasons to do the attribution work carefully the first time rather than eyeballing it.

Related questions

What if my community only has 20–30 occupied units?

The formula scales down. Lower attributable daily gross profit means the division outputs one associate for most shifts. Consider lowering the per-associate target if your margins are thinner or the desk handles fewer high-value tasks — the ratio between the two numbers is what matters, not their absolute size.

Does the formula apply to overnight shifts?

Yes, with a lower target. Overnight attribution is genuinely smaller — emergency calls, security checks, late arrivals. But coverage floors usually override the math overnight, because the function is safety and access control rather than margin generation. Set the floor first, then check whether attribution justifies more.

How do I handle a desk that also does medication deliveries and resident check-ins?

Include those duties in the attribution if they carry margin, which raises the daily total and therefore the headcount. If they're purely administrative, exclude them from attribution but count their time against capacity — a seat that's busy but not margin-generating still can't take a second tour.

How often should I re-run the numbers?

Quarterly, plus after any material change: a new marketing campaign, an occupancy swing, a referral-source shift, or a change in the care mix. A 10–20% move in tour volume is usually enough to add or subtract a body on specific days.

Can I use one tool for both the desk schedule and the care floor?

Usually yes, but keep the underlying methods separate. Most scheduling platforms handle multiple departments with different rules. The mistake is letting the care floor's census-driven logic bleed into the desk's margin-driven logic inside the same template.

FAQ

How do I calculate the desk's attributable gross profit without specialized software?

Track the tours, move-ins, and ancillary sign-ups the desk directly supported over a month, multiply by your average monthly margin per occupied unit, and divide by the days in the month for a rough daily figure. A three-month average of handwritten tallies beats guessing by a wide margin, and it's enough to run the first division. Refine the attribution later — start with what you can count today.

Is it safe to schedule one person on slow days?

Only with a documented backup. On single-associate days, confirm a manager or supervisor can cover breaks and emergencies, the phone system forwards on no-answer, and the door has a buzzer or intercom. Many communities run one associate successfully on low-traffic weekdays. The failure mode isn't the slow hour — it's the unannounced tour that arrives during the lunch break nobody planned for.

What per-associate target should I start with?

There's no universal number — it depends on your margin per occupied unit, your fully loaded labor cost, and how much of your revenue the desk genuinely influences. Start by taking the desk's total attributable monthly gross profit, dividing by the number of desk shifts you currently run, and using that as a baseline. Then adjust up or down based on whether current staffing feels tight or slack.

Do I need scheduling software to do this at all?

No. The division is arithmetic and works in a spreadsheet. Software helps with the *execution* layer — publishing to phones, shift swaps, open-shift claiming, time-clock integration, overtime alerts. If your roster is five people and stable, a spreadsheet plus a printed grid is defensible. If you have floaters, callouts, and multiple buildings, the execution tooling earns its cost quickly.

What do I do when the math and the coverage floor disagree?

The floor wins, and you log the exception. If the division says one associate for a Wednesday overnight and your safety floor says a body has to be there, staff the body. Track how often floors override math — if it's most shifts, your target is set wrong or the desk's real function is coverage rather than revenue, and you should say so honestly rather than pretending the division is driving the schedule.

How does this interact with predictive-scheduling laws?

In jurisdictions with fair-workweek or predictive-scheduling rules, you typically must post schedules a set number of days in advance and may owe premium pay for late changes. That constrains how reactively you can apply the division — you're setting the pattern in advance from trailing data, not adjusting Saturday on Thursday. Check your specific state and municipal requirements; they vary considerably and penalties attach.

Sources

• https://www.bls.gov/ooh/office-and-administrative-support/receptionists.htm
• https://www.bls.gov/news.release/ecec.nr0.htm
• https://www.dol.gov/agencies/whd/flsa
• https://www.cdc.gov/nchs/npals/index.htm
• https://www.medicaid.gov/medicaid/long-term-services-supports/index.html
• https://www.ahcancal.org/Assisted-Living/Pages/default.aspx
• https://www.argentum.org/
• https://www.sba.gov/business-guide/manage-your-business/hire-manage-employees
• https://www.irs.gov/businesses/small-businesses-self-employed/understanding-employment-taxes

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)