Question 1

What is a daily operations huddle and why does it need software?

Accepted Answer

It is the short stand-up your community already runs most mornings, where census, staffing, admissions and yesterday's problems get covered. It does not need software to happen. It needs software so that what was reported, who owns it, and whether it got resolved still exists tomorrow, next month, and when a surveyor asks.

Question 2

How long does the huddle take with Marthen-Huddle?

Accepted Answer

The same length it takes now, usually ten to fifteen minutes. Department heads submit their update in under a minute before the huddle, so the room is reviewing information rather than collecting it. Meeting mode keeps the order fixed so the huddle does not drift into problem-solving.

Question 3

Do department heads need training to use it?

Accepted Answer

A department update is a short form on a phone. Most people are submitting them the same day they get access. We walk your administrators and department heads through it during rollout, and the huddle itself stays the huddle they already know.

Question 4

How is this different from our EHR, like PointClickCare?

Accepted Answer

Your EHR is the clinical record for each resident. This is the operational record for the building: who reported what this morning, which concern has an owner, what the front desk is expecting today, whether you were short on the floor. They answer different questions and we do not ask you to move clinical documentation out of your EHR.

Question 5

How is this different from Teams, Slack, or a group text?

Accepted Answer

A message thread is a stream. It has no owner, no due date, and no way to show a surveyor that a family concern from six weeks ago was addressed and signed off. Messaging is included here for quick coordination, but the huddle, the issues and the front desk boards are structured records, not chat history.

Question 6

Can staff see other communities in our portfolio?

Accepted Answer

No. Staff and administrators see only the communities they are assigned to. Access is enforced on each record, not in the interface, so a member of one building cannot reach another building's data.

Question 7

What can a regional director see that an administrator cannot?

Accepted Answer

A regional director sees every community in the organization on one dashboard and can move between them without being assigned building by building. An administrator sees their own community in full. Both see the same underlying record for the buildings they reach.

Question 8

Is our data secure, and how do you handle PHI?

Accepted Answer

Access is enforced with row-level security on every record, scoped by role and community assignment, with audit logging of admin and access activity. The data model is built for operational coordination rather than clinical charting, so resident detail stays in your EHR. We do not hold HIPAA certification or a SOC 2 report and we will not tell you otherwise.

Question 9

How long are messages and huddle records kept?

Accepted Answer

Direct messages are deleted after 30 days, and the retention notice is visible inside the conversation so nobody is surprised. Huddle records, department updates, issues and front desk history are retained so you can open any past day and export a month at a time.

Question 10

Does this help with state survey preparation?

Accepted Answer

It helps because the documentation is captured as the day happens rather than rebuilt afterward. Grievance sign-off with how it was addressed, who was contacted, root cause and preventive action, PPD against budget by day, and a dated history of what was raised and resolved are all there when you need to produce them.

Question 11

How does pricing work?

Accepted Answer

Per unit, per day, billed monthly, with no per-seat charge. Every CNA, housekeeper and front desk person can use it without changing the bill. To see the number for your community, book a demo and we will walk through your unit count with you.

Question 12

How long does it take to get a community live?

Accepted Answer

Setting up an organization, a community, departments and the team is a short configuration, not an implementation project. The realistic timeline depends on how many buildings you are starting with and how your departments are structured. Book a demo and we will give you a specific date rather than a range.

Question 13

What happens if our executive director leaves?

Accepted Answer

The record stays with the community, not with the person. The incoming director opens the last several months of huddles, open issues with owners and due dates, and the front desk history on their first morning. That is the main argument for getting this out of one manager's spreadsheet.

Question 14

Can we start with one building before rolling out the portfolio?

Accepted Answer

Yes, and most operators should. Run one community for a few weeks, keep the huddle you already have, then add the rest of the portfolio under the same organization when you are satisfied. Nothing has to be rebuilt when you expand.

Question 15

Do you integrate with our EHR or HR system?

Accepted Answer

Personal calendar connections for Google and Outlook are supported today. EHR and HR integrations are handled case by case rather than promised generically, because the answer depends on which systems you run and what your vendor exposes. Bring your stack to a demo and we will tell you plainly what is possible now.

Questions and answers

Still have a question we did not answer?