Skip to main content
GullySystem
Other industries

Attendance & Time Tracking for Facility management companies

Record working time, absence and approved attendance corrections.

Project Management

Does this function belong in your operation?

Use when staff attendance or working time affects pay, deployment or reporting.

A shift starts, ends or needs correction.

Supervisors mark housekeepers, technicians and pantry staff present at each site by role. Shortfall against contract strength appears the same day. Overtime and absent cover go to the bill.

Bring the records the workflow depends on.

  • Employee and shift list
  • Attendance sources
  • Overtime and correction rules

Outputs to check

  • Approved attendance register
  • Correction and overtime history
  • Payroll-ready period totals

Follow the attendance & time tracking workflow.

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

  1. 1. Assign the work calendar

    Set employee shifts, breaks and approved attendance rules.

  2. 2. Capture events

    Record attendance from the agreed manual or device source.

  3. 3. Review exceptions

    Resolve missing events, overnight shifts and disputed entries.

  4. 4. Approve the period

    Confirm corrections and payable overtime through the responsible supervisor.

  5. 5. Handover totals

    Send the checked attendance to payroll or reporting and retain later adjustments separately.

Who uses the module, and who approves?

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

Employee or supervisor

Records attendance and reports missing or incorrect entries with the supporting explanation.

HR administrator

Checks shift assignments, approves corrections and closes the period after unresolved entries are reviewed.

Payroll preparer

Uses the approved attendance totals and returns unexplained differences before calculating pay.

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.

Missing punch

Ask for a correction with evidence and approval rather than assuming a full working day.

Overnight shift

Apply the assigned shift boundary instead of splitting attendance at midnight without review.

Unapproved overtime

Keep recorded extra time separate from overtime approved for payment.

Can this work independently?

Attendance can use manual entries or imported device records. Employee and shift identifiers are required; payroll, leave and project time are separate processes. Device integration must define how missing, duplicated or delayed events are reconciled before a period closes.

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.
  • Project time tracking: Approved task hours and their billable classification.
  • Biometric attendance devices: Device event imports and rejected or duplicated attendance events.

Configure, test and introduce the workflow.

  • We go through the register, the sheets and the machine reports in use today. You supply samples from a recent month. You get back a written note of how attendance flows.
  • Shifts, grace periods, half day and overtime rules are listed in plain words. You confirm them. A rules sheet comes back that you can show staff. We look at the biometric model and at each place where marking happens. You say who marks where. A note returns on what connects directly and what needs a file.
  • Last month’s records are loaded into a trial screen. The admin team compares the result with the sheet they really used. Differences are discussed. Supervisors and the admin team practise marking and correcting. You choose the start date. The old register retires after a clean month close.

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.

  • Overnight shifts use the correct dates.
  • Corrections retain the approver.
  • Approved totals reconcile with the attendance period.
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 attendance & time tracking?

Use when staff attendance or working time affects pay, deployment or reporting. A shift starts, ends or needs correction.

What should we bring to the requirements discussion?

Bring anonymised examples of Employee and shift list; Attendance sources; Overtime and correction rules. 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. Record working time, absence and approved attendance corrections. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Location tracking, biometrics and payroll connections require agreed scope and appropriate permissions.

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. Overnight shifts use the correct dates. Use this check when reviewing the first working version.

Talk to us

Discuss attendance & time tracking 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