Largest Coworking Companies
It's Monday morning. A member can't connect to the meeting-room screen, your next tour arrives in ten minutes, and a colleague asks whether that overdue invoice has been paid.
Somewhere on your to-do list is “check the numbers.” Again.
Reporting is easy to postpone when it feels like a separate job: download a file, tidy the columns, work out what changed, and then decide whether any of it matters.
But you probably don't need another spreadsheet. You need answers to the questions already on your mind: What needs attention this week? Why is that meeting room always empty? Who should we speak to before their membership ends?
Start there. Then use AI and scheduled reports to help with the preparation, not to make every decision for you.
Now imagine a different start to Monday. Before you arrive, a short report is waiting in your inbox. It might flag:
That's enough to give your team catch-up a useful starting point. You don't need a chart to tell you that someone still waiting for help with door access deserves a call.
Your first recurring report could answer one question: what needs our attention today?
Suppose a member's invoice was €1,200, but they have already paid €900. The useful number is the €300 remaining, not the original invoice total.
Ask for overdue balances grouped by company, with due dates and a way to open the original records. Keep payments still processing separate so you can check them before sending a reminder.
A support summary should show what is unresolved, how long it has been waiting, and who owns it. Look for repeated problems, too.
Three complaints about a meeting-room screen might be three separate incidents. Or they might be a reason to replace a cable. The report gives you somewhere to look; your team works out what is happening.
An approaching membership end date is a reason to talk, not proof that someone is leaving.
A weekly list of upcoming end dates helps you ask useful questions early: Does the team need more desks? Has their working pattern changed? Are they already discussing another plan with your colleague?
The outcome of Monday's review should be a few names beside a few actions. Not another spreadsheet saved for later.
The small meeting room looks quiet whenever you walk past. Should you lower the price?
Before changing anything, look at its bookings by day and time. Perhaps it is busy every morning and empty after lunch. Perhaps members book it regularly, while outside customers rarely do. Those patterns suggest different next steps.
Here is a simple example. Two rooms are each available for eight hours a day, five days a week. That gives you 80 available room-hours. If they were booked for 36 hours, 45% of that time was reserved.
Useful,but not the whole story.
One room might account for nearly all those bookings. One might have been closed for repairs. And a reservation does not prove someone actually arrived.
For a practical room review, ask:
Then choose a small experiment. Improve the quieter room's photos. Check whether its equipment meets members' needs. Mention available afternoon slots to teams that regularly struggle to find space.
Review the same figures after the change. That is more useful than cutting every room's price because one looked empty on Tuesday.
Weekly reports help you handle the immediate work. Monthly reports help you spot a change in direction. A total alone won't do that: 120 room bookings could be an excellent result or a quiet month.
Ask for comparisons, not just totals. Compare the last complete month with the one before it, then look at three to six months together. Where comparable records exist, check the same month last year for seasonal context.
Keep it focused on three areas:
Money collected. Did more money come in than last month? Was it from memberships, meeting rooms, or something else? Show refunds separately, and don't mix invoices you've sent with payments you've received. A good month for collections isn't necessarily a profitable month.
Membership mix. Are more subscriptions starting? Which plans are people choosing? Compare monthly starts, and save a month-end snapshot of active plans to track the mix over time. Count customers separately from subscriptions, one customer may have several.
Room bookings. Compare booking counts and hours by room. Has that quiet afternoon been quiet for three months? Are more bookings coming from outside your membership?
Imagine a room's booked hours rose from 40 to 50, then 60 over three months. That's ten more hours than last month (a 20% increase) and a steady rise across the period. Worth a closer look.
Before drawing conclusions, check what else changed. Were there more working days? Did you extend opening hours or add a room? Keep locations, currencies, and counting methods consistent. If the earlier figure was zero, show the increase without a percentage.
Then pick one change to investigate. More room payments might mean more bookings, longer meetings, or a different customer mix. The numbers tell you where to look; they don't explain everything on their own.
Once you've found a report you actually use, you shouldn't have to remember to request it every week.
For spaces using agents in Spacebring Intelligence, that could mean giving an agent a regular job: gather unresolved support requests, put the oldest first, and email a short summary to the person responsible. You choose the schedule and instructions, then check that the report contains what your team needs.
Work backward from when you want to read it. If you arrive at 9 a.m., you want the report waiting in your inbox, not an agent just starting to gather the data. Try a run, see how long preparation and delivery take, and schedule it early enough to leave a buffer.
Start small:
When | What to receive | Why then? |
|---|---|---|
Before you arrive on Monday | Overdue balances, unresolved requests, upcoming membership end dates | Start the week with priorities already in your inbox |
Before Friday's team catch-up | Support requests still open or unassigned | Agree on ownership before the weekend |
Before your first monthly review | Payments, membership measures, and room bookings compared with earlier periods | Spot trends, not just read last month's totals |
You don't need all three on day one. Start with the report you'd otherwise have to pull together yourself, and check that your tool can access the records it needs.
If you're following up on payments every day, a daily summary may earn its place. Otherwise, weekly might be plenty. Choose a rhythm that fits your work. Another unread email isn't an improvement.
Think of the instructions you'd give a colleague covering for you. Which location? What should they look for? Who needs the result? A support-report brief could be as simple as:
Choose the recipient and timezone when you set it up, and confirm the first scheduled delivery arrives before you need it. If it's too long or misses something important, adjust the brief, just as you would with a colleague.
For the monthly review, be just as clear. “Last month” should mean a complete calendar month, not whichever 30 days happen to precede the run. Ask for the comparison explicitly:
Add one rule to every brief: say when information is unavailable. Missing data is not zero. If a historical figure wasn't saved and can't be retrieved, leave the comparison blank rather than guessing.
You might also want an occasional answer to “Has anything changed down the road?” If your chosen agent supports scheduled web access, a pricing digest could help. Check that capability separately from its access to your own records.
Choose a handful of nearby spaces and review their public offers monthly, or weekly while you are reviewing your own positioning.
Compare like with like. A hot desk available during business hours is not the same offer as a dedicated desk with 24/7 access. Include meeting-room allowances, minimum commitments, stated taxes, and promotional conditions.
A short brief could be:
Save the first report as your baseline for future checks. Use the findings to understand your market, not automatically match the cheapest offer.
You know things a report won't: the member who's already spoken to your colleague, the room that was closed for painting, the company whose payment is being sorted out.
Bring that context to the review. Before relying on a new report, check an important total and a few records, including the dates and location. Keep customer information within tools your team has approved.
Keep reporting separate from taking action. Preparing a list of overdue invoices should not also authorize an agent to email every customer on it.
Most importantly, give each recurring report an owner. If nobody reads it or does anything differently because of it, simplify it, or stop sending it.
For your first report, choose something you've already had to chase this week. Get that answer right, arrange for it to arrive when you need it, and see whether it makes the next team conversation easier.
You can always add another report later. For now, the goal is to know what needs your attention before the next tour walks through the door.
Save your community manager 41 hours each week—learn how The Yard did it with cloud-based access control.
Read the Case StudyFree access to our best guides, industry insights and more.