Skip to main content
GullySystem

Employee Database for Coworking Centres

The module keeps one record per staff member, covering role, posting, pay structure, documents and dates. A question about who worked at the centre in a past year is answered by a search.

Where staff paperwork sits

A joining letter may be in a folder behind reception, an identity copy in a chat thread, and a salary revision in a conversation nobody wrote down. Building passes for everyone on site then depend on one supervisor’s memory. A single record replaces these scattered copies.

What the record carries

Person and posting

Name, role, reporting manager and the centre they work at, with a photograph.

Dates that matter

Joined, confirmed, changed role, resigned and the last working day, each with its date.

Pay structure

What was agreed and what it was revised to, with the date of each revision.

Documents

Identity proof, the signed appointment letter, bank details for salary and an emergency contact.

Agency and contract staff

Held the same way and marked against the agency that sends them, so the building pass list can include them.

What you can answer from it

Who was on the desk in March

Past employees keep their file after the exit date, since that is when a question about them arrives.

Whose papers are missing

A short list of people with no identity proof on file, or no signed letter.

It stores and does not verify

An uploaded document has not been checked by anyone. Background checks, police verification and agency vetting stay with you.

Moving a staff list in without a mess

Most centres start from a sheet. A clean import saves months of correcting later.

Fix names first

One person, one spelling. Duplicate rows become two employees and two payslips.

Choose a starting set of columns

Name, role, centre, joining date and salary are enough for day one.

Attach papers in rounds

Collect letters and identity copies centre by centre and tick them off against the missing list.

Confirm with each person

A short message asking staff to check their own details finds typos early.

Treating staff data with care

Staff files hold identity numbers and bank details. Limit who can open them, and ask your advisor how India’s data protection rules apply to employee records. The module restricts access by role as you set it.

  • Pay and documents: owner and HR only.
  • Roles and contact numbers: centre managers.
  • Exit files: kept, but read-only.

Small errors that cause big confusion

A staff file looks simple until the same mistakes repeat. Watch for these.

Two spellings, two people

Check names against identity proof when creating the record.

Wrong centre posting

A transfer without an update puts the person on the wrong roster.

Old bank details

A closed account delays salary. Ask staff to confirm details before each year starts.

Fields to agree before loading anyone

Decide the shape of the record once. Changing it after fifty files are loaded is tedious.

  • Employee code format and who issues it.
  • Designations that match your appointment letters.
  • Whether agency staff carry the agency name in a separate field.
  • Which documents are compulsory and which are optional.
  • How long closed files stay on screen before archiving.

Screens next to this one

  • Joining and leaving: the checklist that fills this file in.
  • Attendance and salary: what the pay structure feeds every month.
  • Statutory paperwork: registers and renewal dates built on these files.
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.

Where staff paperwork sits

Which observation would change the proposed scope?

For “Where staff paperwork sits”, observe someone completing the task with a representative example. Record where they stop, ask another person or re-enter information, then choose the smallest change whose result the team can verify.

Background reading: GOV.UK: researching user needs

FAQ

Frequently asked questions

Who can open an employee file?

Only the people you allow. Pay and documents are restricted to the owner and whoever runs HR, while a centre manager sees roles, postings and contact numbers.

Can we move our existing staff list in?

A spreadsheet of names, roles, joining dates and salaries imports, and documents are attached afterwards as you collect them.

What happens to the file when somebody resigns?

It closes with a last working day and stays readable. The login stops working the same day.

Do we have to fill in everything on day one?

No. Start with names, roles, joining dates and salaries. Documents are attached as people bring them, and a list shows what is still missing.

Can one person work at two centres?

Yes. The file shows a main posting and can note a second centre, with hours counted in one place.

Can we keep a photo of each employee?

If you choose to, yes. The photo also prints on the building pass.

Can the file hold a salary revision history?

Yes. Each revision keeps its date, so an old payslip can be explained by the structure in force that month.

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