Skip to main content
GullySystem
Other industries

Employee Database for Facility management companies

Maintain one employee record for HR, attendance and payroll.

Human Resources

Does this function belong in your operation?

Use when several processes depend on the same staff list.

Someone joins or an employment detail changes.

Every worker has an identity record, a site posting, a role and a joining date. Transfers between sites are logged. Supervisors find a trained substitute without phoning around.

Bring the records the workflow depends on.

  • Employee identifiers
  • Reporting lines
  • Employment and payroll fields

Outputs to check

  • Approved employee master
  • Employment change history
  • Missing-information list

Follow the employee database workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Create the employee

    Assign a unique identifier and record required employment fields.

  2. 2. Verify sensitive details

    Check payment and identity information through the approved process.

  3. 3. Approve activation

    Confirm the joining status before downstream processes use the record.

  4. 4. Record changes

    Preserve effective dates for transfers, pay-related fields and employment status.

  5. 5. Reconcile downstream use

    Check that payroll, leave and attendance references identify the same person.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

HR executive

Adds joiners, records transfers and keeps the list true. It is the first screen opened each morning.

Accounts assistant

Reads bank and tax ID details for payment, and does not collect them again each tax year.

Branch manager

Sees who is on the team’s rolls, on which shift, and who reports to whom.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate employee

Resolve identity before merging records; preserve references used by other processes.

Bank-detail change

Hold the change for verification and record who approved it.

Backdated transfer

Keep the effective date and review which future and historical reports should reflect it.

Can this work independently?

The master can be maintained independently, with reviewed exports to existing tools. Attendance, payroll and leave need a shared employee identifier before they exchange data. A department change must not silently alter historical payroll or attendance.

Systems and records it connects with

  • Payroll management: Approved pay inputs, deduction calculations and payment instructions.
  • Leave and holiday management: Approved absence and branch calendar information.
  • Attendance and time tracking: Approved shift attendance, absence and correction records.
  • HR document management: Restricted employee documents and completeness status.

Configure, test and introduce the workflow.

  • You share the sheets and registers that carry staff details. You get a note on which fields will be kept and which dropped. Duplicates will appear.
  • Agree required employment fields and the authorised audience for sensitive information. Import a representative group of employees and review duplicates, missing details and effective dates before loading the remainder.
  • Payroll, leave and attendance read from the master. The HR team checks names and dates across them. The old sheets are marked as closed. The HR team is trained to add, change and close a record.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Identifiers are unique.
  • Transfers update department views.
  • Sensitive fields follow access rules.
Facility management companies

How the business operates.

Your client judges you on a clean washroom, a working lift and a quick reply to a complaint, and each of those is visible to the client every day. You judge each site on manpower cost and consumables. Both views should come from the same data.

Sites, contracts and deployment

Hold each client site with the manpower its contract promises by role and shift, so deployment can be read against that strength.

Attendance at the site

Mark attendance on the supervisor’s phone at shift start, with cover arranged when somebody does not report.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Sites and contracts. Hold each client site with its blocks, posts, service scope, rate per grade, billing cycle and the dates the agreement runs.
  • Deployment and headcount. Set the staffing requirement for each grade at a site, and compare the plan with actual postings.
  • Staff records. Keep housekeeping staff, technicians, gardeners, pantry staff and supervisors with their papers, skills, wage basis and site history.
  • Shift roster and cover. Build the monthly roster by shift and post, mark weekly offs, and send a reliever when a post falls vacant.

Operational bottlenecks to check

Every site reports differently

One supervisor sends an Excel, another photographs, and a third sends nothing until asked. Head office rebuilds the picture by hand each month. That takes days.

Short deployment is argued at month end

The client counts fewer housekeepers on the floor than the contract promised, and deducts for it. An attendance sheet cannot settle it.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Contract and site set-up

    A new client site is opened with its address, the staff types deployed, the rate per type and the services the agreement covers, from pest control to garden care.

  2. 2. Deployment and roster

    Staff are posted to the site by grade and shift. A reliever is named against each absence, so the supervisor knows who is coming before the shift starts.

  3. 3. Shift start at the site

    Attendance is marked where the staff report, with a photo or a device reading. Short posts show on the operations screen the same morning.

  4. 4. Complaints and service work

    A resident or an office admin raises a complaint. It is categorised, handed to a technician or the housekeeping team, and closed with what was done.

  5. 5. Scheduled and inspection rounds

    Planned rounds falling due are listed per site. The facility manager walks the checklist and records readings, photographs and pending points.

  6. 6. Month end

    Attendance, extra duties, consumable issue and maintenance work build the invoice for each site. The wage sheet is drawn from the same duty records.

Industry reports to connect with

  • Headcount deployed against headcount contracted, site by site
  • Attendance, absence and reliever cover by site and grade
  • Complaints logged, attended and pending, by site and type
  • Planned maintenance due, completed and overdue

Questions before implementation.

When should facility management companies consider employee database?

Use when several processes depend on the same staff list. Someone joins or an employment detail changes.

What should we bring to the requirements discussion?

Bring anonymised examples of Employee identifiers; Reporting lines; Employment and payroll fields. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Maintain one employee record for HR, attendance and payroll. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Collect only the personal information needed for your employment processes.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Identifiers are unique. Use this check when reviewing the first working version.

Talk to us

Discuss employee database for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements