ProductPricingDemoContactBlogLoginTry Now It's Free
HomeBlogMember Feedback for Co-Working

Member Feedback for Co-Working Spaces

Average member tenure in co-working is 22 months and retention decides profitability. A member feedback system captures the facility friction that ends memberships.

A member feedback system for co-working spaces lets members report facility and amenity problems — a meeting room double-booked, patchy wifi in one corner, a printer out of toner, noise in a quiet zone — by scanning a QR code where the problem is. Each report is assigned to the community or facilities owner and closed with a reply the member can see. It replaces the Slack channel where issues scroll away unread.

Retention Is the Whole Business Model

1

Average member tenure is 22 months and healthy retention benchmarks sit between 65% and 85% (Allwork.space, Coworking Statistics and Key Trends 2026, retrieved September 8, 2026).

2

The average space runs at 68% occupancy and only 54% of spaces globally make a profit.

3

Acquisition costs a tour, a trial day and a discount; retention costs a working printer.

4

Community and hospitality quality separate high-retention spaces from churning ones.

Co-working economics are unforgiving in a specific way: the margin lives in the last few percentage points of occupancy. The average space runs at 68% occupancy and only 54% of spaces worldwide make a profit, with average member tenure at 22 months and healthy annual retention benchmarked between 65% and 85% (Allwork.space, Coworking Statistics and Key Trends 2026, retrieved September 8, 2026). A handful of departures a month is the difference between the two halves of that profitability split.

Members almost never leave over price. They leave because the space stopped working for them — the meeting rooms are always booked, the wifi drops in the corner they like, the phone booths are occupied by people holding meetings, the kitchen is a mess by two in the afternoon. Each of these is small. Together they mean the member starts working from home two days a week, then three, and then does not renew.

This is also why community and hospitality quality, rather than desk price or square footage, is what distinguishes spaces with strong retention. Those are operational qualities made of hundreds of small resolutions, and a space can only deliver them if it knows what is going wrong.

The Slack Channel Is Not a Reporting System

1

Issues posted in a general channel scroll away within an hour and have no owner.

2

Members can see that nobody replied, which teaches them not to post next time.

3

Nothing is categorised, so recurring problems look like unrelated one-offs.

4

Community managers absorb everything verbally and hold the backlog in their head.

Almost every co-working space runs a member Slack or WhatsApp community, and almost every one uses it as the de facto issue channel. It fails at that job in a visible way. A member posts that the printer is out of toner at 10:15; by 11:00 the message is buried under lunch recommendations and a job posting. Nobody owns it, nothing records it, and if it is fixed the member never learns that their message caused it.

The visibility of the failure is what makes it corrosive. Unlike a lost email, an unanswered Slack message sits there permanently for the whole community to see. Members read the absence of a reply as the space's attitude to problems, and they stop posting. Reported volume falls, the community manager concludes things have improved, and the underlying friction continues unrecorded.

The community manager ends up as the system. They know the meeting room booking system is being gamed, that the second-floor wifi is weak, and that one member plays music without headphones, because they hold all of it in memory. That works until they take a week off, or leave, at which point the space's entire operational knowledge walks out with them.

Report It Where the Problem Is

1

A QR code in each meeting room captures booking conflicts, AV faults and cleanliness.

2

Codes in phone booths and quiet zones catch etiquette and noise issues members will not raise directly.

3

Kitchen and washroom codes catch the recurring facility complaints.

4

Codes at desks in the open plan catch wifi, temperature and power problems by location.

Location is the information. A member who reports 'the wifi is bad' has given the operator nothing actionable; a member who scans the code on desk bank C has reported that the wifi is bad at desk bank C, which is a survey point. Across a month, location-tagged reports draw an accurate map of the space's weak spots without anyone commissioning a site survey.

Meeting rooms deserve their own codes because they generate a distinctive complaint mix: double bookings, someone overrunning, a screen that will not connect, a room left unusable by the previous group. These are the complaints most likely to cost a membership, because they occur when the member has a client in front of them and the space has made them look unprofessional.

Phone booths and quiet zones need codes for the same reason class feedback needs anonymity in a gym. Nobody wants to confront the person taking a loud call in a silent area, and community managers cannot police what they did not witness. An anonymous report — booth 2, ongoing noise from the adjacent open desk — lets the manager address it as a general reminder rather than a confrontation.

How to Set Up Member Feedback in a Co-Working Space

1

Step 1 — Choose five categories: facilities and maintenance, meeting rooms, connectivity, cleanliness, community and etiquette.

2

Step 2 — Generate location-specific QR codes for meeting rooms, booths, kitchen, washrooms and each desk bank.

3

Step 3 — Assign owners: facilities lead for maintenance, community manager for etiquette, IT contact for connectivity.

4

Step 4 — Set a same-day acknowledgement standard and publish it beside the codes.

5

Step 5 — Allow anonymous submission on the community and etiquette category specifically.

6

Step 6 — Post a fortnightly 'fixed this week' summary in the member channel.

Separate connectivity from facilities. In most spaces the wifi is managed by an external IT provider or a landlord, on a different response timescale from a broken chair. Merging them into one category means every connectivity report goes to a facilities lead who has to forward it, adding a day to something members are least patient about.

Publish the acknowledgement standard next to the code, not in the member handbook. Members submit when they expect a response and stop when they do not, and the sign is what sets the expectation. It also creates the internal pressure that makes the standard real, which is the actual reason to write it down.

The fortnightly summary is the piece that rebuilds the reporting habit the Slack channel destroyed. Members who see 'reported and fixed: meeting room 3 HDMI cable, kitchen tap, desk bank C access point replaced' understand that reports produce outcomes. It is also, incidentally, the best possible marketing to the members deciding whether to renew.

Set up your first co-working feedback board in under 2 minutes. Free plan available, no credit card required.

Reading the Data Before Renewal Season

1

Reports per member, watched by company account rather than only by individual.

2

Meeting room complaint volume against booking utilisation — the classic capacity signal.

3

Time from report to fix by category, published to members.

4

Silence from a previously active account is a churn signal, not a good sign.

Track reports at company-account level, not just per person. In a space where teams take multi-desk memberships, one team's accumulating frustration is the renewal that matters, and it is invisible when reports are counted individually across a hundred members. Three reports from three people at the same company in a month is a retention conversation waiting to happen.

Meeting room complaints read against booking utilisation give the clearest capacity signal a space has. Rising complaints with rising utilisation means you need more rooms or a booking limit. Rising complaints with flat utilisation means the booking rules are being gamed — held bookings, no-shows, overruns — which is a policy fix rather than a construction project.

Treat sudden silence from a previously active member as a warning rather than a resolution. Members who have stopped reporting have usually not stopped experiencing problems; they have stopped believing it is worth mentioning, which is the last stage before they leave. A community manager who notices this and asks directly can often recover the relationship while there is still something to recover.

FAQs

Why not just use our member Slack channel?

Slack has no owner, no status and no memory. A report scrolls away within the hour, nobody is accountable for it, and members can see that it went unanswered — which teaches them to stop reporting. Keep Slack for community and route issues to a board where each has a name and an age against it.

Do members need an account to report a problem?

No. They scan the code at the meeting room, booth or desk bank and submit in seconds. This matters for day-pass users and visitors, who have no member account but experience the same facility problems and often notice things regular members have stopped seeing.

How do we handle complaints about other members?

Allow anonymous submission on the community and etiquette category. The community manager then addresses it as a general standard rather than a confrontation between two members, which is the only approach that works in a space people choose to spend their days in.

What does a co-working feedback system cost?

The Free plan is $0 with QR codes, anonymous submissions and tracking codes, enough for a single site. Starter is $19 per month, Growth is $49 per month and adds the location-based QR codes most spaces want for room-level and desk-level tagging, and Business is $79 per month.

Ready to fix your feedback loop?

Set up your first complaint board in under 2 minutes. No credit card required.

Try FeedSolve Free
M
Maduranga, founder of FeedSolve
Founder, FeedSolve
Maduranga builds FeedSolve and writes about SMB feedback and complaint resolution.