Notice out of the blue
A company in a six-person office gives notice. The community manager is surprised; they seemed happy. Looking back, the signs were there. Only two of the six had been coming in for months. They stopped booking meeting rooms. Their last two invoices were paid late. One of them had raised a complaint about noise that was never resolved.
None of this was hidden. It sat in the access system, the booking calendar, the accounts and the request log. Nobody was looking at it together.
Why leaving seems sudden
Community managers know their members, and good ones sense when something is off. But with dozens or hundreds of member companies across sites, intuition does not scale, and the quieter members are the ones who slip away unnoticed.
| Signal | Where it sits |
|---|---|
| Fewer people coming in | Door access logs |
| Fewer meeting room bookings | Booking system |
| Late or failed payments | Accounts and payment provider |
| Unresolved complaints | Request log or inbox |
| Downgrades or removed members | Membership platform |
| Agreement end approaching | Membership platform |
Each signal alone can have an innocent explanation. Several together, or a sharp change, are worth a conversation.
Members rarely complain before leaving, either. Many simply stop coming in, book less and quietly look elsewhere. The one conversation that might have kept them, about a smaller office or a different plan, never happens because nobody knew it was needed.
What surprise departures cost
An office that could have been kept by a change of plan, a smaller office or a fixed complaint becomes vacant. Replacing a member takes marketing, tours and sales time, and the office may sit empty while you do. And without understanding why members leave, the same reasons keep costing you members.
Some departures are unavoidable, when a company closes or relocates. The point is to know early which ones are not, while there is still a conversation to have.
The community team feels each unexpected departure as a personal failure, even when nothing could have been done. A clear view of which departures were preventable, and which were not, is fairer to them as well as more useful to the business.
The early warning view we build
- Data is brought together per member company from your access system, booking system, accounts, payment provider, request log and membership platform.
- Each company's normal pattern is established from its own history, so a drop is measured against how that company usually behaves.
- Changes are flagged: a fall in attendance, fewer bookings, late payments, open complaints, members removed, agreement end approaching.
- Companies with several flags appear on a watch list for the account owner or community manager, with the evidence behind each flag.
- The account owner records the conversation and outcome, such as a plan change, a fixed issue or a confirmed departure.
- Reasons for leaving are recorded from exit surveys and conversations, and reported by site and plan.
Data about members is used under your privacy notice. The view is for your team's conversations with members, not for automated decisions about them.
What the community team gets
A short list of members worth a conversation this week, with the reasons. Conversations happen while there is still time to help, whether that means a smaller office, a different plan or fixing a long-running complaint. And over time, a clear picture of why members leave, which guides what to change.
The same data works the other way too. Companies whose attendance and bookings are rising may be ready for a bigger office, which is a sales conversation rather than a retention one.
Does this sound familiar?
- Members give notice and it comes as a surprise.
- Nobody looks at attendance, bookings and payments together.
- Complaints go unresolved before members leave.
- You do not know the main reasons members leave.
- Growing members are not offered bigger space in time.