Families call the front desk for two reasons: something is wrong, or they have not heard anything and are starting to wonder. A weekly update handles the second one. It takes one person about 40 minutes a week once the rhythm is set, and it answers the questions that would otherwise arrive as fifteen separate phone calls. Below are three fill-in templates (the standard weekly update, the short version for a chaotic week, and the new-family add-on), plus the one-page process that keeps them going when the person who writes them is out sick.
This is written for independent living and assisted living. Copy the templates into Google Docs or Word, drop in your logo, and keep last week’s version as the starting point for this week’s. You are editing, not writing.
What belongs in a weekly update, and what never does
The update is a community-wide message. It carries what happened this week, what is coming, what families need to do, and who to contact. It does not carry anything about an individual resident’s health, care plan, incident, behavior or billing. Those go in a direct call to the authorized contact.
The test before anything goes in: is this general, group or personal? General (event schedule, dining changes, visitor instructions, a repair, weather planning) goes in. Group (“several residents enjoyed the new chair yoga class”) goes in as long as it exposes nothing about anyone. Personal (a change in condition, a fall, a medication question, a care conference, a complaint) never goes in, even as a hint. Federal privacy rules allow sharing health information with a family member involved in a resident’s care when the resident agrees or does not object, and some assisted living communities are not covered by HIPAA at all, but every state has its own privacy rules for licensed care and none of them are satisfied by a group email. Keep it simple: if it is about one person, it is a phone call.
Photos need written consent on file for the resident, and “first name only” is the default in anything that goes to a group.
Template 1: The standard weekly update
Six sections, same order every week, so families learn where to look. Total length: one page, or one screen on a phone. The bracketed text is what you replace; the example lines show the tone.
| [Community name] Family Update – Week of [date] |
|---|
| Opening (3 sentences) “Hello families, [one highlight from the week]. [The one thing families need to act on this week, with the deadline]. Below you’ll find this week’s highlights, upcoming dates, and a few reminders to help visits go smoothly.” Example: “Hello families, the garden club planted the fall beds on Tuesday and the patio is looking good. Please note that Friday’s family lunch needs an RSVP by Wednesday at 3 p.m. Below are this week’s highlights, upcoming dates and a couple of reminders.” |
| This week’s highlights (3–4 lines) “[Activity], [day]: [one specific, dignified sentence].” Example: “Music hour on Wednesday had strong turnout, especially for the Sinatra set residents picked themselves.” “The dining team’s pie tasting on Thursday ended in a tie between apple and pecan; both are on the menu next week.” |
| Family action needed (1–3 items, each with what / who / by when / contact) “[Action]. This applies to [who]. Please [do it] by [date/time]. Questions: [role, phone or email].” Example: “Please label new sweaters, jackets and blankets before bringing them in so housekeeping can return them to the right apartment. Questions: front desk, (555) 555-0100.” |
| What’s changing (only if something is) “[What is changing], [when], [why], [what to do instead].” Example: “The front entrance will be closed Monday from 9 a.m. to noon for door repair. Please use the side entrance off the north lot; there will be signs, and the front desk phone stays open.” |
| Upcoming dates (next 2 weeks) “[Day, date, time] – [event] – [open to families? RSVP?]” |
| Who to contact Care questions: [Wellness Director, phone]. Visits, transportation, general questions: [front desk, phone]. Billing: [Business Office, phone, hours]. Activities and RSVPs: [Life Enrichment Director, email]. Optional one question for families: “Does your loved one have a favorite holiday recipe our dining team should know about? Reply to this email.” |
Tone rule, worth printing: residents are adults in their own home, not content. “Our sweet residents had the cutest craft day” becomes “Residents finished a set of pressed-flower cards this week; several are on display outside the activity room.” Warm, specific, and something a resident could read about themselves without wincing.
Template 2: The short version for a hard week
The weeks you are most tempted to skip (state survey, a holiday, a weather event, staffing trouble) are the weeks families most need to hear from you. Silence reads as a problem. Send this instead.
| [Community name] Family Update – Week of [date] (short version) |
|---|
| “This week’s update is a shorter one while the team [prepares for the holiday events / works through the storm cleanup]. Here is what families need to know:” |
| One operational update: “[What, when, what it means for visits].” |
| One action item: “[What, by when, contact].” |
| Upcoming dates: [next 7 days only] |
| Contact: “[Front desk phone] is the fastest way to reach us this week.” |
Template 3: The new-family add-on (first 30 to 60 days)
Families of new residents call more, because they have not learned the rhythm yet and because the move was hard. Add this block to the bottom of the standard update for households in their first month or two, or send it as a separate note on the same day.
| A note for our newer families |
|---|
| Who to call: “For anything about your loved one’s care, [Wellness Director, name, phone, hours]. For visits, meals, transportation or anything else, the front desk at [phone].” |
| What to expect: “The first few weeks are an adjustment for most residents. It is normal for appetite, sleep and social energy to move around before they settle. If you notice something that worries you, call [name]; that is what the number is for.” |
| What we’d like from you: “The more we know, the better. Favorite foods, music, a hobby or past profession, what time they like to get up, what helps on a rough day. Reply to this email or hand a note to the front desk.” |
| Your first check-in: “[Name] will call you around day [14 / 30] to see how things are going. You don’t have to wait for that call.” |
The process: one owner, one deadline, one review
The writing is the easy part. The hard part is gathering the right information on time and keeping the update going when the person who does it is out. That is the process below; it fits on one page and works as an SOP for a single community or a portfolio.
| Weekly family update – process sheet | Your community |
|---|---|
| Owner (accountable for it going out on time, in the approved format) | Role: __________ Name: __________ |
| Backup owner (knows where the template, photos and inputs live) | Role: __________ Name: __________ |
| Send day and time | Every __________ at __________ |
| Input deadline (two days before send) | __________ by __________ |
| Inputs, one or two lines each, by department | Life Enrichment: 2 highlights + next week’s dates Dining: 1 menu note or change Wellness: general reminders only, never resident-specific Maintenance / housekeeping: anything affecting visits or apartments Front desk: “What did families ask about more than once this week?” ED: 1 leadership note, when needed |
| Reviewer (can cut, rewrite or hold an item) | Role: __________ |
| Channel | Email (plain text + PDF attached) / printed copies at the front desk / portal: __________ |
| Reply inbox and who checks it | __________, checked at __________ and __________ daily |
| Photo consent verified by | Role: __________ |
Two details make this work. First, the front desk question (“what did families ask about more than once?”) is the most valuable input on the list; whatever five families called about this week is what next week’s update answers, which is how the update starts reducing calls. Second, the input deadline is midweek on purpose. Friday inputs for a Friday send produce a rushed update built from whatever people remember.
The five-minute review before sending
- Are all dates, times, names and phone numbers correct?
- Is every photo covered by consent on file, and first-name-only?
- Is anything resident-specific? If yes, cut it and make the call instead.
- Is there exactly one primary action item, with a deadline and a contact?
- Does it fit on one page or one phone screen?
- Would a resident be comfortable reading how they were described?
Handling replies
An update sent from an inbox nobody watches creates more frustration than no update at all. Replies fall into six buckets, and each has a home: RSVPs to Life Enrichment, transportation and visit questions to the front desk, care concerns to the Wellness Director the same day, billing to the Business Office, compliments to the ED (and to the staff member named), and anything that sounds urgent escalated immediately under your normal policy. The family should hear back within one business day even if the answer is “I’ve passed this to Maria, she’ll call you Thursday.”
How to know it is working
Three numbers, checked monthly, not weekly. Repeat family questions at the front desk (the same question from multiple families is a gap in the update). Engagement: open rate if you send by email, RSVPs, replies, and how often a family mentions the update during a visit. And front desk call volume on the topics the update covers, which should drop within two or three months of consistent sends. Once a quarter, cut any section families do not respond to. Updates grow; the good ones get pruned.
For multi-site operators
Standardize the six sections and the process sheet; leave the voice local. Families want to hear from the people who care for their parent, not from corporate. When one community writes an especially clear weather notice or holiday RSVP block, save it and share it as the model, so the library of good examples grows instead of every ED reinventing it. Reading the updates side by side each month is also a fast, cheap read on which communities are organized and which are improvising.
Even a good weekly update does not stop the phone. What it changes is what the calls are about, and the ones that remain are mostly routine: visiting hours, whether an event is open to families, transportation booking, who to call about billing. JoyLiving’s AI receptionist answers those, gives families the same information the update carried, and routes anything that needs a person to the right one, with every call logged so the front desk knows what families asked this week. You can see how it handles a real family call in the videos at joyliving.ai.
Ana Avila is a writer who covers the day-to-day operations of senior living communities: how calls get answered, how resident requests get handled, how families stay informed, and how small teams keep up with all of it.
Her work for the JoyLiving Operator Library focuses on the practical side of running a community. She writes about front desk workflows, after-hours coverage, request tracking, check-in programs, family communication, staffing, and the places where AI tools can take repetitive work off a caregiver’s plate. Most of her articles come from the same starting point: a real problem an executive director or front desk lead is dealing with this week, and what has actually worked for other communities facing it.
Ana writes for people who are busy. Her guides are meant to be read in one sitting, put to use the same day, and shared with staff without translation. She avoids jargon, explains technology in plain terms, and is careful not to oversell what any tool, including AI, can do.
A consistent theme in her writing is that technology should support the relationships at the heart of senior living rather than replace them. The measure of a good system, in her view, is simple: does a resident get help faster, does a family member get a clearer answer, and does a caregiver get more time with the people they care for.
