Coworking Analytics: The 7 Numbers Every Operator Should Check Weekly

Monthly reporting is useful for owners and finance. Weekly reporting is useful for operators. By the time a monthly report shows a weak sales pipeline, poor room usage, or churn risk, the team has already lost time.

A weekly dashboard should be small enough to review in 20 minutes and specific enough to trigger action. The point is rhythm: look at the same numbers, ask the same questions, and assign follow-up before the pattern becomes a month-end surprise.

The CTW digital footprint model estimates that coworking software produces large volumes of daily interactions. Operators do not need all of that data every week. They need the seven numbers that point to action.

Occupancy sounds straightforward until the denominator changes. Physical capacity, contracted capacity, and available-for-sale capacity are different. A room held for events, a desk blocked for repairs, and a private office under negotiation should not all be treated the same way.

Track desk and office occupancy separately. Private offices need contracted occupancy and renewal risk. Hot desks need active plan count and actual usage. A space can look full on contracts and still feel quiet in the room if members attend less often.

Use occupancy to guide pricing, sales urgency, and expansion timing. High occupancy with a waitlist suggests pricing power. High occupancy with weak revenue per desk suggests discounting or plan design issues.

Net member movement is new joins minus cancellations and non-renewals. It is the weekly pulse of growth. Gross new members can look healthy while cancellations quietly erase progress.

Track individuals and accounts separately. Losing one company with ten seats is different from losing one individual hot desk. Also separate planned move-outs from avoidable churn. A member leaving the city tells a different story than a member leaving after unresolved Wi-Fi complaints.

If your platform does not show this directly, export joins and cancellations weekly. Even a simple spreadsheet with date, plan, source, reason, and owner is better than waiting for revenue to reveal the movement later.

Revenue per desk, or revenue per square meter, tells you how productive the space is. Include memberships, meeting rooms, day passes, services, lockers, mail, events, and other recurring add-ons. Exclude pass-through taxes and deposits.

This metric helps compare rooms, floors, locations, and plan types. A location with lower occupancy can still be healthier if revenue per desk is higher and churn is lower. A full room at discounted rates may look good in occupancy and weak in revenue.

Review the trend, not just the number. If revenue per desk falls while occupancy rises, the space may be filling with lower-yield plans.

Track available hours, booked hours, used hours, no-shows, cancellations, and revenue per room hour. Booking alone overstates demand when members hold rooms and do not show up.

This metric should feed pricing and layout. If small rooms are always used and large rooms are underused, the space may need room reconfiguration. If no-shows are common, add check-ins, release rules, or penalties. If external bookings produce high revenue but crowd members, adjust allocation.

For the detailed operating rules behind this metric, read the booking systems guide.

Lead-to-tour conversion shows whether demand is turning into real sales conversations. Track inbound leads, qualified leads, tours booked, tours completed, and source. If the ratio drops, the issue may be speed-to-lead, weak qualification, poor follow-up, or unclear pricing.

This metric is especially important for operators relying on brokers, paid search, marketplaces, or corporate leads. A lead sitting untouched for two days is often gone. An automated response can help, but the real work is routing ownership and follow-up.

AI lead tools such as Koho.ai may support prioritization once the CRM data is clean.

Complaints are operational data. Categorize them by billing, access, Wi-Fi, cleanliness, noise, booking, temperature, and staff response. A single complaint may be anecdotal. A weekly pattern is a management signal.

Support volume often predicts churn before cancellation forms do. If members complain about access three weeks in a row, the issue is no longer isolated. If billing questions spike after invoices go out, the invoice language or plan rules need work.

Measure response time and resolution time. Members forgive problems faster when the team responds clearly.

Check contracts expiring in 30, 60, and 90 days every week. This is the forward-looking revenue number many teams miss. Renewal conversations should not start when the contract is already ending.

Segment by account size, plan type, owner, and risk. A ten-person private office expiring in 60 days deserves a different process than a solo flex plan. Add notes from usage, complaints, payment history, and community engagement.

Weekly expirations turn retention from reactive email into account management.

Start with the platform you already use. Nexudus, OfficeRnD, and Archie can provide much of the raw material when configured well. Add Linxiv or another analytics layer when you need cross-tool views.

Keep the dashboard tight: seven metrics, owner, trend, action. Do not wait for a data team. A weekly export and a maintained spreadsheet can work while the stack matures.

For budget context, pair the dashboard with the technology costs breakdown. Spend decisions are better when the operating numbers are visible.