Skip to main content
GullySystem

Coworking Operations: Bookings, Billing, Entry and Costs

The operations side holds bookings, invoices, entry, assets, documents and building costs together. The desk plan and the ledger then draw on the same records.

Systems that run separately

A desk plan on a slide, bookings in a shared calendar, invoices in a guarded Excel file, entry cards with a vendor, and pantry orders by voice note. Each is accurate on its own. Together they give different answers about the same day. Operators who run several centres do it through a patchwork that grew with each new building. Moving to one set of records is less about new features than about agreeing, once, what a seat, a booking and a month’s cost mean in every centre.

What the operations side carries

Rooms and desks

Live availability, booking rules per plan and a diary the front desk can rely on.

Money out as well as in

Rent, power, housekeeping and internet recorded per centre, beside what the centre collected.

Entry and visitors

Who may come in, at what hours, and the pass issued to a guest at half past nine.

Things you own

Chairs, monitors, the printer and the coffee machine, with the cabin each one sits in.

Signed papers

Agreements, identity documents, and what changed in each since signing.

Internal jobs

The fit-out upstairs, the generator service and extinguishers due for refilling.

Why one system instead of five

Invoice matches the floor

Seats billed come from seats allocated. A tenant who expanded into a second cabin is billed for two.

Entry follows membership

Doors open on the strength of a live plan, so a card cannot outlive the agreement behind it.

One figure per centre

Collected, spent, occupied, for one building or for every building.

What sits outside it

The module does not run air conditioning or lifts, and it is not an accounting package. Tally stays your book of record.

Which part to switch on first

Operators who try everything at once stall. A sequence that works for most centres follows the order in which pain is felt.

First, bookings and plans

Double-booked rooms and wrong seat counts are what members notice.

Second, billing

Once seats and hours are right, the monthly run builds itself from them.

Third, access and documents

These depend on clean member records.

Last, costs and assets

Useful once a few months of collections sit beside them. By then the team trusts the records, and nobody argues over which sheet is right.

Questions to settle at scoping

  • How many centres, floors and rooms must be mapped
  • Which door system each building uses
  • Whether Tally is linked or fed by an export
  • Who inside your team owns each screen after go-live

The operations screens

Bookings

Rooms, desks and the rules behind them.

Billing

Monthly GST invoices and what follows them.

Access

Entry levels, visitor passes and exit day.

Costs by centre

Rent, power and vendor bills against collections.

Assets and stock

Furniture, equipment and the pantry cupboard.

Documents

Templates, signatures and version history.

Make an informed decision

Questions to settle before rollout.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

Coworking Operations: Bookings, Billing, Entry and Costs

Can you explain the balance from its original documents?

Select a partly settled example in “Coworking Operations: Bookings, Billing, Entry and Costs”. Ask for the invoice, allocated receipts and remaining balance to be shown together before agreeing the opening figures.

Background reading: ERPNext: outstanding invoices

Assets and stock

What happens to movements entered while a count is being checked?

For “Assets and stock”, choose a count date and trace the movements around it. Agree who investigates a difference before an adjustment changes the available balance.

Background reading: ERPNext: stock reconciliation

FAQ

Frequently asked questions

Is this an ERP in the full sense?

It is the operations half of one, shaped for workspace. Purchase orders, stores and manufacturing are not part of it, because a centre does not need them.

Can we switch parts of it off?

Yes. Operators begin with bookings, billing and the member app, then add assets and costs once those are running.

Does our accountant have to change anything?

No. Invoices and receipts can go across to Tally, either as an export or a link set up at the start. The accountant works from figures that were not retyped.

How does it handle two buildings?

Each centre keeps its own floors, rooms, staff and members. The owner reads them together, and a member who moves between them keeps one history.

How long does it take to bring a centre across?

It depends on how clean your sheets are. Mapping plans, floors and rooms comes first, then members and unpaid invoices, and a short check with your manager before go-live.

Do we need new hardware?

Not for bookings, billing or documents. Door access is the exception, since it depends on whether your controllers can be driven by another system.

What does the front desk use day to day?

The booking diary, visitor passes and the ticket queue, from a browser. Training is short because the screens mirror tasks they already do.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements