HRA — HR & Attendance Module

Structure, hierarchy and step-by-step workflow — Company → HO → Project → Site → Role

BasisSheet + Final Spec, verified
ModelHO controlled · Site operated
ScopeMulti-project, multi-site
RevB — reconciled

What HRA does

HRA is the HR & Attendance module of the Construction ERP. It covers employee and worker records, attendance/muster, leave, working hours, overtime, payroll, employee self-service (ESS), documents, welfare and HR reporting — operating inside the same Company → Project → Site hierarchy as the rest of the system.

Primary ownerHead Office — Manager, HR & Admin
Operational modelHO controlled, Project coordinated, Site operated
Employee ruleOne permanent Home / HR Site
Shared accessOnly via explicit site-level grant
PayrollCentral HO run, using site-approved attendance
ConcurrencyAll projects & sites active at once — no single "current" context

Five ground rules

  • Head Office owns HR policy, employee master governance, payroll and company-wide HR control.
  • Project management coordinates manpower and HR operations across its sites, through the Project Manager.
  • Each Site operates its own HR Portal for day-to-day attendance, muster, leave and workforce activity.
  • All HR records are scoped — a Site user cannot access another site's people or transactions.
  • Every employee has one permanent Home/HR Site; shared functional access is handled separately and never changes it.

Company → HO → Project → Site

Click any row to expand it. Every project and every site shown here can be active at the same time — there is no single current project or site.

Head office Project Site HR feature
  • Company / Head office
    • HO HR & Adminowns policy, payroll, compliance
      • Employee master
      • HR policy
      • Leave & holiday policy
      • Payroll
      • Statutory settings
      • HR compliance
      • Company-wide HR MIS
    • Project Acoordinated by its Project Manager(s)
      • Site A1
        • Site A2
          • Site A3
          • Project Bruns concurrently with Project A
            • Site B1
              • Site B2

            Note on "Project": a Project does not have its own HR staff — HR at that layer is the Project Manager coordinating across their assigned site(s). It is a coordination lens, not a separate HR role. See Rules & Open Items for why this is flagged for client confirmation.

            Who owns what — HO / Project / Site

            AreaHO / CompanyProjectSite
            Employee masterOwn / create / approveRaise manpower request; verifyProvide onboarding inputs
            HR policyOwn / configureFollowFollow
            Salary / gradeOwn / configureRecommend / inputNo policy change
            AttendanceMonitor / auditFinal operational approvalRecord / verify
            LeavePolicy / roll-upApprove site employee leaveOperational support
            Working hoursPolicyConfigure within policy / approve exceptionsOperate
            PayrollRun / finalizeVerify site inputsProvide approved attendance
            Labour registrationGovernance / auditMonitorRegister / maintain
            Employee documentsMaster controlVerifyMaintain site records
            PerformanceHR governanceConduct / recommendProvide inputs
            Welfare / grievancePolicy / escalationMonitorFirst-level handling
            HR reportsAll projects / sitesProject scopeOwn site

            Role tiers

            TierDefinitionExamples
            HOCompany-wide, fixed, centrally governedManaging Director, Manager–HR & Admin, Head–Accounts & Finance, Head–Purchase, Manager–HSE, Manager–QA/QC, ERP Administrator
            SiteDynamic — created and scaled per site by the Project ManagerPM/Site In-charge, Senior Site Engineer, Site Engineer, Billing/QS Engineer, Surveyor, QA/QC Engineer, Safety Officer, Store Keeper, Site Accountant, Plant & Machinery In-charge, Junior Engineer/Supervisor, Time Keeper, Site Admin, Purchase Site (new — scope pending)
            ExternalLimited access, outside the company payrollSubcontractor Supervisor / Mukadam

            Worker categories (A / B / C)

            CodeCategoryEmployer / rollsPaid byAttendance owner
            ACompany staff — PM, engineers, supervisors, QS, store, accounts, HSE, adminCompanyCompany payroll, monthlySelf check-in → PM approval
            BDirect site labour — daily/weekly wage, engaged directlyCompanyCompany, fortnightlyTime Keeper → Site Engineer countersign → PM final
            CSubcontractor labour — item-rate / piece-rate scopeSubcontractorSubcontractor, against certified workSubcontractor Supervisor → Time Keeper verify → PM final

            Category C is still the company's compliance responsibility as Principal Employer — registered, ID-carded and tracked with the same rigour as A and B, even though the company never pays them directly.

            HRA role-based access matrix

            RoleEmployee masterAttendanceLeavePayrollESS
            EmployeeView ownView ownApply / view ownFull own-data access
            Time Keeper / Muster ClerkView own siteRecord own site
            Site EngineerView own siteCountersign own site
            PM / Site In-chargeView own siteApprove own siteApprove own site
            Manager — HR & Admin (HO)Create / edit — all sitesView — all sitesView — all sitesRun — all sites
            ERP AdministratorConfigurationConfigurationConfigurationConfiguration

            Step-by-step workflows

            Click a workflow to expand every step, in order, with who performs it.

            HO HR Site / PM Employee External System

            Feature set, by area

            Employee self-service (ESS)

            • Profile view / update (sensitive changes need HO approval)
            • Attendance history & daily status
            • Leave apply, status & balance
            • Holiday calendar
            • Payslip download after payroll finalisation
            • Attendance regularisation request

            Attendance & muster

            • Site-scoped, per worker category capture method
            • Geo-fencing at the site boundary
            • Regularisation workflow for disputes
            • Locked after payroll processing; reopen is audited

            Leave management

            • Policy owned by HO, approval executed at site
            • Category-specific entitlement rules
            • Auto balance update on approval
            • HO consolidated leave / compliance view

            Payroll

            • Central HO run using site-approved attendance
            • Consolidates every active project & site in one cycle
            • Payslip generation, visible via ESS only
            • Statutory filing (PF/ESI/TDS) gated as a separate scope flag

            Documents, welfare & grievance

            • Identity & statutory documents, PPE/ID card records
            • Bank / payment documents
            • Appointment, joining & relieving documents
            • Site accommodation & welfare records
            • First-level site grievance, escalates to Project/HO

            Performance evaluation

            • PM conducts periodic / quarterly site staff evaluation
            • Submitted to HO HR, who hold the official record
            • Covers performance, attendance, discipline, technical ability, safety, quality, productivity

            Notifications

            • Leave submitted / approved / rejected → employee & approver
            • Attendance regularisation → site approver
            • Payslip generated → employee
            • Missing muster → Time Keeper / PM
            • Compliance exception → Project & HO HR
            • In-app is baseline; email/SMS/WhatsApp only if in approved scope

            Reports & MIS

            • HO dashboards: all active projects & sites, no closing required
            • Project dashboards: authorized sites only
            • Site dashboards: own workforce & transactions only
            • Employee: own payslip / attendance / documents only

            Multi-site isolation & security rules

            • All site-level APIs enforce server-side Company → Project → Site authorization — front-end hiding is never the security boundary.
            • A user cannot reach another site by editing an ID in the URL, query or request payload.
            • Every role assignment and site-access grant is auditable.
            • Sensitive employee changes require approval; attendance, payroll and leave changes preserve audit history.
            • Shared site access is explicitly granted and independently revocable — it never merges site HR records or funds.
            • HO users see data per their permission scope; not every HO login gets unrestricted HR detail.
            • ESS is strictly self-service — an employee never sees another employee's personal data.
            • An employee cannot have two simultaneous Home/HR sites.

            Working hours, leave & payroll baseline (verified against the source sheet)

            RuleBaseline
            Standard site day9 hours on site incl. 1 hour rest — 8 working hours. Default 08:00–17:00.
            Site adjustmentPM may configure within HO policy; exceptions require an HO-level approval role name unconfirmed
            Weekly offSunday half day; PM approval required
            Ordinary working weekCapped at 48 hours
            OvertimeTime beyond 48 hours, compensated as paid leave, with PM approval
            Night shiftWritten PM approval + HSE clearance + certified lighting
            Minimum ageNo person under 18 on site, any category, no exceptions
            Geo-fencingApplied at site level
            CategoryCycleCut-offPay byMode
            A — StaffMonthlyLast day of month7th of following monthBank transfer only
            B — Direct labourFortnightlyLast day of monthWithin 10 days of cut-offBank transfer; cash by written exception only
            C — SubcontractorAgainst certified RA billPer work orderPer work order termsBank transfer to subcontractor

            Open items — confirm before this is treated as final

            • HO approver for working-hour exceptions — the HR notes name an approver title that does not appear anywhere in the current HO role list. Confirm the exact title (or that it is the Managing Director) before build.
            • "Purchase Site" role — a new site-level role appears in the latest sheet with no accountability description yet. Not an HRA function, but it should be defined before the role/permission matrix is finalised.
            • Project-level HR authority — the Final Development Specification introduces Project as a distinct HR approval tier. The role sheet itself only defines HO and Site tiers (the Project Manager is a Site-type role). Confirm with the client whether "Project" is meant as a real separate authority, or simply the PM's oversight across their site(s) — this page treats it as the latter, flagged here for visibility.
            • ESS access for Category B & C — full self-service, or a simplified payslip/attendance view? Still open per the approval checklist.
            • Statutory payroll filing & biometric integration — both explicitly gated as separate scope flags, pending client confirmation.