Skip to main content
GullySystem

HRMS for Coworking Centre Staff

The module covers rosters, attendance, leave and salaries for front desk, housekeeping and community staff. It sits inside the system that runs the floor they work on.

Two groups in the building

Members have an app, a plan and an invoice. Staff keep a printed roster and a group chat, so overtime, leave and salary corrections end up in different places. Staff records sit beside the member system here.

What the staff side holds

A file per employee

Role, posting, joining date, pay structure and papers are held in one record for each person on your payroll, from the joining letter to the exit date.

The weekly roster

Desk, pantry and maintenance duties are placed across seven days and published where staff can read them.

Hours and overtime

Marked daily, including the evenings when staff stay back for a members’ event.

Leave with a balance

Leave is requested, approved or refused, and counted against each employee’s balance. Year-end balances are totalled from the logged requests themselves.

The salary run

The run reads the month’s attendance and leave, then issues payslips that staff open themselves. Corrections are made in the record.

Why it sits beside the member system

One login for the manager

The person handling a renewal on Monday can approve leave on Tuesday from the same login. When these live in two systems, one of them stops being updated.

Cover follows the floor

Room bookings on a Saturday show where reception needs cover, so the roster is built against what the building is doing that week.

Staff entry

Employees get their own entry level alongside members, where your access hardware allows it.

Where it stops

This is a staff module for a centre. It is not a full HR suite for a large company, and recruitment sits outside it.

What Indian HR buyer guides ask, and where this module fits

Buyer guides for Indian HR software list a familiar set of checks: several shift patterns, biometric import, state holiday calendars, self-service for staff, and statutory payroll. A coworking team is small, so weigh each against what your centre needs.

Shift patterns and holidays

Reception, housekeeping and maintenance run different hours. Ask to see your own patterns on the roster during the demo.

Biometric import

Depends on the device. It is confirmed with your hardware before anyone promises it.

Statutory payroll

Provident fund and tax filings stay with your accountant. The module supplies the attendance and salary figures.

Self-service

Staff open their roster, leave and payslips themselves, which cuts the small questions that reach the manager.

Starting the staff side in three steps

Do not switch on everything at once. A staged start gives the team time to settle.

Step one: records and roster

Load every employee and publish next week’s roster. This alone replaces the printout and the group chat.

Step two: attendance and leave

Begin marking the day and taking leave requests on screen for one full month.

Step three: the salary run

Run payroll in parallel with your old method once, compare, then switch.

Scoping questions for the staff module

Staff modules go smoothly when decisions come early. Take these to the first workshop.

  • How many staff, across how many buildings?
  • Which parts do you want first: roster, leave, payslips?
  • Who runs payroll today, and who will tomorrow?
  • Is any staff on contract through an agency?
  • Is a biometric machine already in use?

The staff screens

  • Attendance and payroll: hours in, salaries out, from one record.
  • Shift scheduling: next week’s roster and its gaps.
  • Employee records: joining letter to exit date.
  • Staff portal: what an employee can look up alone.
  • Leave, training, compliance and onboarding: the pages that follow.
Make an informed decision

Agree the evidence before signing off this part.

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

One login for the manager

Can an ordinary account reach a record outside its allowed scope?

For “One login for the manager”, agree two accounts with different permissions and test direct requests. Record the expected refusal and include exported or downloaded data in the assessment.

Background reading: OWASP: authorisation checks

Shift patterns and holidays

Which calendar and policy apply to the dates being counted?

Use an example in “Shift patterns and holidays” that crosses a holiday or shift boundary. Have the responsible manager confirm the expected count before accepting the calculated result.

Background reading: Frappe HR: leave applications

FAQ

Frequently asked questions

Is this for our staff or our members?

Your staff. Members have their own app for bookings and invoices. This side is for the reception, housekeeping, maintenance and community staff you pay every month.

Can agency housekeeping be included?

Yes, as staff records with their own roster. The agency’s monthly bill is a purchase and belongs with accounts.

Do we need the HR part at all?

The answer turns on size. A small team in one building may manage on a paper roster. It matters more when shifts cross two buildings or overtime is disputed.

Does payroll reach Tally?

Yes. Salary entries export for Tally along with the rest of your accounting. Statutory filing is not done from here. Your accountant carries on.

Can we switch on only part of the HR module?

Yes. Centres begin with rosters and attendance, and add leave, payslips and compliance records later.

Is there a limit on staff numbers?

Its design suits centre teams, from a handful to a few dozen people per building. Larger HR needs belong in a dedicated HR suite.

Who can see salaries?

Only the people you nominate, normally the owner and whoever runs HR. Centre managers see rosters and attendance for their own team.

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