Skip to main content
GullyHR

HR technology and automation · Apartment owners' associations

Attendance, Shift and Leave Software for Apartment owners' associations

Attendance, shift and leave software is the GullyHR module that captures daily attendance, holds shift patterns and rosters, routes leave requests to the reporting manager for approval, provides a defined route for regularising a missed or wrong punch, maintains a holiday calendar that can differ by location, and reports attendance and leave for management and for payroll inputs.

A shift supervisor checking an attendance tablet with an HR administrator near a workplace entrance.

The operating context

Test the roster, leave and attendance rules together

A resident welfare association runs a township or apartment complex through guards, housekeepers, gardeners and technicians. Residents give instructions all day, the committee changes every year and nobody owns the people side.

Security guards and gate staffSecurity supervisorsHousekeeping staffGardenersLift, pump and plant operatorsElectricians and plumbers
A residential property supervisor briefing security, housekeeping and maintenance staff.

The decision to work through

Configure approved shifts, calendars, leave rules and attendance correction permissions for the relevant employee groups. Workforce to consider: Security guards and gate staff, Security supervisors, Housekeeping staff.

Records and configuration to test

Roster configuration, leave balances and attendance test cases. A workforce issue to consider: Leave, advances and warnings are noted by hand, and a new committee cannot find what was promised to whom.

An exception to test

Test an overnight shift, shift swap and late correction against approved policy before accepting the configuration.

Which parts of your business should the scope cover?

The right workforce and approval structure depends on the operations you run. Confirm which of these apply, and whether they share one HR process.

  • Large gated apartment communities with a clubhouse
  • Mid-sized complexes of fifty to two hundred flats
  • Small stand-alone apartment buildings
  • Complexes still waiting for builder handover
  • Older complexes with ageing lifts and pumps
  • Villa and apartment mixed communities

When to consider this service

  • Attendance is a register at the gate that one person fills in and nobody checks.
  • A leave request came by phone on a Saturday, and the manager who agreed to it has no memory of doing so.
  • Two people on the same shift were paid differently because the roster only ever existed in a supervisor's head.
  • The device missed a punch, there is no agreed way to correct it, and so somebody edits the sheet instead.

Businesses this service is designed for

  • Businesses tracking attendance on paper registers or in spreadsheets kept by individual supervisors.
  • Multi-shift or multi-site operations where the same attendance and leave rules have quietly diverged at each location.
  • Companies where payroll is late most months because attendance and leave records are still being chased.
  • Businesses that installed a biometric device but have nothing connecting it to leave, exceptions and payroll.

What the system needs to support

GullyHR configures how attendance is captured, how shifts and rosters are assigned, and how leave and regularisation requests travel: leave types and entitlements, accrual rules, shift patterns, the correction route for a wrong entry, the holiday calendar, and the approval level behind each. You supply the current leave policy, shift patterns, holiday list and attendance method, and you make the decisions that belong to management, such as how much leave of each type an employee gets and who may approve an exception to it. This runs as configuration, a test against a sample cycle and role-based training inside a GullyHR software engagement, and we design around a biometric device you already own where it genuinely supports the process.

Attendance is recorded against the shift the person was actually on.

A daily attendance record for each employee, held against their configured shift, which every other module that needs it, payroll inputs above all, reads from rather than keeping its own copy.

An existing biometric device is assessed before anything is promised about it.

Where a punch or biometric device is already installed, we look at what it can actually export and bring that data in where it is genuinely possible. Where it is not, we say so and describe the manual alternative.

The roster leaves the supervisor's head and becomes visible.

Shift patterns configured to how the business really operates, with rosters assigned to individuals or teams and readable by the managers and employees they affect, so nobody works a shift they did not know about.

A leave request reaches the manager who is meant to decide it.

Employees apply against configured leave types and see their own balance, and the request routes along the reporting line held in the system instead of depending on who they happened to speak to.

Every approval and rejection leaves a record with a date on it.

Leave and regularisation decisions are recorded against the employee and the approver, so a disagreement months later is settled by looking rather than by remembering.

A missed punch has a correction route instead of a quiet edit.

The employee or the manager raises a regularisation for a missed or wrong entry, an approver accepts or rejects it, and only then does the attendance record and the payroll input change.

Holidays can differ by location without anyone tracking it by hand.

A configured holiday calendar that can vary by site, which matters as soon as you operate in more than one state and the lists stop matching.

Attendance and leave close before payroll inputs open.

Exception, absenteeism and balance reports built from the same records used for approval, with an agreed cut-off, so the payroll cycle starts from data that is already settled.

Configure, validate and prepare users

Map the approved process to fields, user roles, permissions and workflow rules. Inspect the source data and identify migration, integration and reporting requirements before configuration.

  1. 01

    Policy and practice mapping

    We go through your leave policy, entitlements, accrual practice, shift patterns, holiday list and current attendance method, noting where written policy and actual practice differ.

  2. 02

    Entitlement configuration

    Leave types, entitlement quantities, accrual and carry-forward rules are configured to the policy your management confirms.

  3. 03

    Shift and roster setup

    Shift patterns are configured and rosters assigned to teams or individuals as they actually run, including patterns that differ by site.

  4. 04

    Attendance source setup

    Attendance capture is configured, including bringing in data from a biometric device you already operate where that has been assessed as possible.

  5. 05

    Approval route setup

    Leave and regularisation routes are configured against the reporting hierarchy, with the approval levels and exception approvers you confirm.

  6. 06

    Roles and access

    Access is defined for HR administrators, supervisors, managers and employees to submit, approve and view attendance and leave.

  7. 07

    Sample cycle test

    The configuration is run against a sample period so entitlement, accrual and cut-off behaviour are checked before real pay depends on it.

  8. 08

    Role-based training

    HR administrators are trained on administration and cut-off; managers and employees are shown the small number of actions they will actually perform.

  9. 09

    Go-live and review

    The module goes live ahead of a payroll cycle, and after that first cycle we review whether entitlements, cut-off and approval routes held up in practice.

Test migrated records, approvals, exceptions and permission boundaries with representative users. Agree acceptance, user training, support ownership and the handling of remaining issues before go-live.

Agreed configuration and handover

  • Configured leave types, entitlements and accrual rules matching your confirmed policy.
  • Configured shift patterns and roster assignment, including patterns that differ by site.
  • A configured attendance capture method, including data from an existing biometric device where that is possible.
  • A configured leave and regularisation approval workflow based on your reporting hierarchy.
  • A configured holiday calendar, with location-specific variations where you need them.
  • Attendance, exception and leave-balance reports for management and for payroll inputs.
  • Training sessions for HR administrators, managers and employees.
  • Reference documentation for running attendance, shift and leave administration month to month.

What your team provides

  • Your current leave policy, shift patterns, holiday list and the way attendance is captured today.
  • Decisions on entitlements and on who may approve an exception to a rule.
  • Details of any biometric device you own, if you want it used for attendance capture.
  • A named person to sign off the test cycle and the monthly payroll inputs.

Share personal records only after the scope, access and handling arrangements are agreed.

Responsibilities and approvals

The client owns employee records and approves policies, spending and employment decisions. GullyHR's assigned responsibilities are documented in the engagement.

Setting leave policy and entitlements

GullyHR
Sets out the configuration options and their consequences, then configures the confirmed policy.
Your team
Decides leave types, entitlement quantities, accrual and carry-forward, which are management decisions and not software settings.

Providing shift and holiday details

GullyHR
Configures shift patterns, rosters and the holiday calendar accordingly.
Your team
Supplies current shift patterns, roster practice and the applicable holiday list for each location.

Using an existing biometric device

GullyHR
Assesses the device, configures attendance capture where it can genuinely be supported, and says so where it cannot.
Your team
Provides device details and the access needed to establish what is actually possible.

Approving leave and regularisation

GullyHR
Configures the approval workflow against the reporting hierarchy.
Your team
Managers make the approval decisions in the system once it is live.

Closing the cycle for payroll

GullyHR
Configures the cut-off and the reports payroll inputs are drawn from.
Your team
Completes approvals by the agreed cut-off each cycle.

Statutory positions on leave and hours

GullyHR
Configures what you confirm and coordinates qualified professionals where a statutory question needs answering.
Your team
Takes the statutory position with its own advisers. GullyHR is not a legal practice and gives no legal opinion.

How we agree that the work is complete

Review these outputs with your process owner and agree the evidence required for sign-off.

  • Leave types, entitlements and accrual rules match your confirmed policy, checked against written examples.
  • Shift patterns and roster assignment work for each site, including patterns that differ by site.
  • A sample cycle has been run with test data, and the exception cases behaved as agreed.
  • The leave and regularisation approval route follows your reporting hierarchy and has been tested.
  • The month-end approval and export of payroll inputs has been walked through with your team.
  • HR administrators, managers and employees have been trained, and reference documentation is handed over.

Data, configuration and adoption

Attendance and leave captured here feed payroll inputs directly, so the figures a manager approved are the figures that prepare pay, without a second entry or a reconciliation between two files. Approval routing follows the reporting hierarchy held in core employee management, which is why a leave request reaches the right manager without HR forwarding it. Where a biometric or punch device is already installed, we assess what it exports and bring that data in where it is genuinely possible; where it is not, we say so and describe the manual route instead of promising a connection nobody has tested. Employees and managers use the module on whatever device they log in from, so a supervisor at a site can approve a regularisation without waiting to reach a computer. What the system will not do is decide an exception for you: an out-of-policy leave request still goes to a person, and the record simply shows who decided and when.

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Read the full attendance, shift and leave software service guide →

Agree the engagement before work starts.

Demonstration and scoping

A walkthrough of the module against your current attendance and leave practice, followed by an agreed scope for entitlements, shifts and approval routes.

Configuration and rollout

Leave, shift and attendance configuration is set up, tested against a sample cycle and rolled out ahead of a payroll month.

Ongoing support

Continued support as the policy changes, a new shift pattern appears or another location comes on.

Scope and exclusions

  • Confirm product fit, licensing and the implementation scope before committing. Custom development, third-party integrations and GullySystem services are separately agreed; they are not automatically included.
  • You want the software to calculate salaries or file returns, which GullyHR does not do.
  • You have no agreed leave policy, so the rules to configure have not yet been decided.
  • Attendance is tracked by a single manager on paper and you do not plan to change that.
  • You need a policy or legal opinion on leave entitlements rather than a configured process.
Confidentiality, specialist review and accountability

Limit access to the records needed for the agreed work. Confirm authorised users, secure sharing, retention and return or deletion arrangements before exchanging personal information.

Applicability depends on locations, workforce arrangements and the issue under review. Confirm applicable requirements with your qualified adviser before adopting policies or employment actions; this service is not a legal certification.

Employment-law opinions, statutory filings, professional or clinical standards and safety-critical technical decisions require the appropriate qualified professional; include those dependencies in the scope.

Questions before you decide

For apartment owners' associations, identify who owns these records: roster configuration, leave balances and attendance test cases. Start with an anonymised example and the decision you need to make; agree the sample and access before sharing personal data.

Discuss your HR system

Tell us the teams and locations involved, what is happening today and what you want this work to resolve.

Start with your business need

What does your HR team need to solve?

Tell us your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

Include your country code, for example +44 or +1. Indian numbers can be 10 digits.

Your details stay private. Privacy policy