Blog

Co-working: member plant and amenities fixed before the morning tour

· Facilities desk

  • co-working
  • multi-site
  • contractors
  • members
  • proof

The west wing hit 28°C before 7am. A member on an early call posted in Slack. A prospect tour was booked for 9:30. The community manager pinged city ops, forwarded the landlord after-hours number, and checked the community app for a duplicate. By the time someone found last month’s heating and cooling invoice, the tour had walked a warm floor and a washroom that still smelled of overnight cleaning product.

Co-working sells readiness. Members and prospects judge the space in the first ten minutes: temperature, doors, washrooms, meeting rooms that work. A hot floor or failed access reader is a churn event before it is a facilities ticket. Reports land in Slack, the community app and a front-desk note — and nobody owns the contractor clock.

OpsChase puts every site and floor on one queue: landlord and operator contractor books ordered separately, each job followed up until photos and sign-off, and a record city managers can trust before the next tour.

From a Slack ping to a work order

Whoever spots the defect raises it with photos and the floor named: community manager, front desk or city ops. It becomes a work order against that site and amenity — hot desk zone, meeting room, washroom, kitchenette or access point — so the job is not trapped in a channel thread.

Add an access note: lift bank, swipe zone, whether landlord base-building must escort, and when the first tour lands. The regular contractor for that site, ownership lane and trade gets the job first.

Landlord plant versus operator fit-out

A heating and cooling fault might be base building. A broken tap or failed meeting-room display might be the operator’s fit-out. At 7am that argument does not cool the room.

Keep two books, each in its own order, on the same site: landlord vendors for base-building plant, operator vendors for fit-out and amenities. Ownership sits on the work order so the member update is honest — “base building attending” or “our plumber is on the way” — without a tour-day blame loop.

Community managers raise; ops owns the clock

Community managers should not become facilities. They raise the defect with photos and the floor. Ops assigns the trade and preferred contractor. Follow-up is not another member-channel message.

Site roles say who raises, who assigns and who watches stalled clocks across the city. Contractors keep getting follow-ups whether or not the community manager is on a tour floor. City managers see open jobs before standup, not after a churn ticket lands in the membership system.

The failures that show before the first tour

  • Floor heating and cooling. A warm wing empties desks and kills tours. Route it to heating and cooling or electrical with the zone and thermostat reading on the job.
  • Access readers and entry doors. A failed controller strands people at the glass. That is doors and shutters or your locksmith, with door ID and landlord escort note attached.
  • Washrooms, taps and kitchenettes. Prospects remember broken taps and unclean amenities. Send plumbing to plumbing and amenity resets to cleaning with before photos from that floor.
  • Meeting-room displays that are plant, not IT. When power or cabling plant is the cause, keep it on the facilities queue with the room name so IT is not left holding the contractor clock.

Attend-by times that match the tour board

Every job carries an attend-by time set against the first tour, peak member arrival, a host event or a boardroom booking. Late jobs show against your response targets, so city ops sees the floor that will not be tour-ready before 9:30, not after the prospect has left.

Access and cleaning are not set-and-forget

Access contractors and cleaners often sit on a standing arrangement until a Monday door fail or a washroom that is not tour-ready. Standing arrangements still need a clock. Raise outages as work orders on the same queue, regular contractor first, proof on the job. A cleaner’s “done” without a photo from that washroom is not enough when a tour is walking the corridor.

Contractor compliance before they swipe in

Keep licence, public liability, induction and site-access details on file for each contractor so ops can check them before anyone is sent to reception. See contractor compliance for what to collect. Mark landlord-approved and operator-approved contractors so the wrong book is not sent into a base-building plant room.

Proof city managers and landlords can read

City managers, landlords and finance all ask who attended, when, and what they left behind. Set proof templates per trade — before and after photos for heating, cooling and plumbing, access test notes for doors, service reports for fire protection, and a clean amenity photo for washrooms. Proof of completion means the member update and the landlord email can cite the same record without digging through Slack.

Planned servicing between tour peaks

Filter changes, test and tag, fire equipment, emergency lighting, pest control and deep cleans need regular servicing across every site. Run planned maintenance through scheduling on the same queue as morning defects, booked for quiet windows so a planned maintenance visit does not collide with a prospect walkthrough.

What a multi-city operator sees on one queue

With every site on one queue:

  • Slack, app and front-desk reports become work orders with photos and the floor named.
  • Landlord and operator contractor books stay ordered separately per site and trade.
  • Community managers raise; ops assigns trade and regular contractor.
  • Attend-by times follow tours, member peaks and room bookings.
  • Photos, reports and certificates are attached to the work order.

OpsChase sits beside your community platform, access system and landlord portal. Those stay the record for members, credentials and building notices; OpsChase is the contractor follow-up and proof behind each plant job. If your current process is a spreadsheet and a shared inbox per city, see how that compares with spreadsheet and email follow-up.

Starting before tomorrow’s first tour

Pick the sites that sell tours this week. Import floors, landlord and operator contractor books, and the trades they cover. Set site roles for community, front desk and city ops. Set proof templates for heating and cooling, plumbing, doors and cleaning. Raise the next Slack defect into OpsChase instead of another channel ping, then add the next city.

Read the co-working industry page or book a demo with your site list and both contractor books. Check pricing when you are ready to put every floor on one flow.

Members and prospects judge the space on simple things: the floor is comfortable, the door opens and the washroom is ready. Put every defect and every service on one queue, follow up the right contractor until the proof is in, and give city managers, landlords and finance one record to point to.

Related on OpsChase

Questions

Can community managers raise jobs without becoming facilities?
Yes. They raise the defect with photos and the floor named. Ops assigns the trade and regular contractor. Follow-up stays on the queue, not in the member Slack channel.
How do we keep landlord and operator contractors separate?
Keep landlord and operator vendors as separate books, each in its own order, on the same site. Ownership sits on the work order so the member update is honest while the job still moves.
Will this work for a multi-city co-working operator?
Yes. Each site is a site. Preferred books can differ by city without a second login, and city managers see stalled clocks across the network.
Does OpsChase replace our community app or landlord portal?
No. Your community platform, access system and landlord portal stay the record. OpsChase handles contractor follow-up and proof on each maintenance job beside them.

All articles

OpsChaseOpsChase

Start with the part you need today and add the rest when you’re ready. One site or many.

Book a demo