A cleaning employer may have a worker assigned to several buildings, a dispatch change midweek, and a sick-leave request routed through a supervisor who also handles payroll. If those records live in unrelated notebooks and spreadsheets, it can be difficult to answer simple questions: how much leave accrued, what was used, and whether the worker's medical details were shared too widely. A reliable process separates the leave balance from the reason for a worker's absence.
New York's paid sick leave law covers private-sector workers across industries, including part-time and seasonal employees. Employers should build records around the state requirements and their own written policy, not infer a worker's balance from attendance or pay stubs alone. This guide summarizes key record practices for janitorial operations; it is not individualized legal or tax advice.
Confirm coverage and identify the governing policy
The New York State Department of Labor's paid-sick-leave guidance says private-sector employees are covered regardless of industry, occupation, part-time status, or overtime-exempt status. A cleaning business should therefore avoid assuming that part-time, temporary, or relief staff fall outside the law simply because they do not work a standard five-day schedule. Questions about a worker's actual employment status should be analyzed separately from leave administration.
The statute, New York Labor Law § 196-b, provides the framework for sick and safe leave. Employers should maintain a current written leave policy explaining how employees request and use leave, what increments apply, and any other limitations permitted by law. NYSDOL's guidance describes written notice or posting of relevant restrictions before leave is earned; a company should confirm policy language and notice practices with counsel when local or collective-bargaining rules also apply.
New York's guidance sets annual leave amounts by employer size and, for the smallest employers, net income: employers with 100 or more employees provide up to 56 hours of paid leave; those with 5 to 99 provide up to 40 paid hours; and employers with 0 to 4 provide up to 40 hours, paid or unpaid depending on net income. Because the size and income thresholds determine the minimum benefit, document how the employer counted and which policy year it uses.
Track accrual and use separately from shift attendance
NYSDOL describes accrual at no less than one hour for every thirty hours worked, beginning September 30, 2020, and says employers may alternatively front-load the required amount under the law. A running balance should therefore distinguish hours earned, leave taken, adjustments, and any annual use limitation. Do not combine sick time with vacation or unpaid absence codes if doing so obscures the statutory balance.
Cleaning operations have practical edge cases. A worker may clock into a building for a partial shift, change sites, attend required orientation, or be called off before the scheduled assignment. Payroll and HR should establish how compensable work time and leave entries flow into the ledger, and should not assume that a scheduled hour was worked when attendance shows otherwise. Corrections should explain the source and reviewer.
Consider an employer with 68 employees that uses accrual rather than front-loading. A worker records 27 hours of work during a period; at the statutory accrual rate, that period would add 0.9 hour of leave before any lawful rounding or plan-specific treatment. The arithmetic is illustrative, not a substitute for verifying the employer's size tier, policy year, work-hour records, and applicable rule. StockPoint's time and payroll connection can help keep the punch record and payroll inputs aligned, but HR owns the leave calculation.
Keep the six-year record complete and retrievable
NYSDOL's paid-sick-leave guidance and employer information state that employers must retain payroll records for six years, including the amount of sick leave accrued and used by each employee on a weekly basis. It also explains that an employee may request a summary of accrued and used leave and the employer must provide it within three business days. A system should make those records retrievable by employee and week rather than rely on an annual total alone.
The employer's record should show the week, hours worked, accrual, hours used, balance, relevant adjustment, and the source of any manual entry. Preserve the original entry and record the reason, date, and approver for a correction. An employee who disputes the total should be able to see a clear reconciliation from the opening balance through the current period.
Store leave data with payroll and attendance records, but control permissions separately. A supervisor scheduling coverage may need to know that the employee is unavailable and the expected duration; that supervisor ordinarily does not need a diagnosis or family member's medical information. A leave administrator can keep supporting material in a restricted file and share only the status needed to coordinate work.
Protect confidentiality without losing an audit trail
The system should use the least sensitive absence code that still supports payroll, staffing, and required recordkeeping. A code such as paid sick leave, safe leave, or another policy category may be sufficient for routine scheduling. Avoid asking a worker to enter a diagnosis into a group chat or client-facing portal. If documentation is requested under an applicable policy, HR should review whether it is permitted and store it outside the general timekeeping record.
Use role-based access and a defined retention schedule for any sensitive material. The audit trail should show that a leave balance changed and who authorized the change without exposing the reason to every manager who can view attendance. If the employee asks for a leave summary, provide the requested payroll record through a controlled channel and log the date it was supplied.
StockPoint's bilingual workforce surfaces can help a Spanish-speaking or English-speaking employee submit an absence request and read a pay-period record in a familiar language. A bilingual interface does not eliminate the need for a consistent privacy policy: translate the request path, explain who sees it, and keep client portal access limited to service information. For related payroll-statement controls, see New York §195.3 pay-stub requirements.
Design a reporting and approval path that works on a night shift
Cleaning work often happens outside the office's normal hours, so the leave process should not depend on a worker locating one HR specialist at 9 a.m. Give employees a defined channel for submitting a request, identify a backup contact, and explain how an urgent absence is reported before a shift. The policy should distinguish requesting leave from obtaining immediate schedule coverage.
Supervisors should acknowledge the request, route it to the designated reviewer, and avoid making informal promises about balances or eligibility. HR or payroll should reconcile the leave ledger with time records, apply the written policy consistently, and communicate the decision to the worker. If a request is disputed, preserve the original message, the response, and a neutral summary of the review.
Do not put medical detail into a cleaning assignment or a facility manager's proof-of-work view. A site contact may need to know which route needs coverage; that operational update can be separated from the employee's leave record. StockPoint's audit-logged operations records can document who changed a schedule or attendance entry, while sensitive leave content should remain in the employer's restricted HR process.
Reconcile leave with payroll and client billing
Sick leave affects staffing, wage records, and sometimes the hours included in a customer invoice, but those are separate accounting questions. A client contract may price a fixed service regardless of which employee covered the work. A cost-plus contract may use hours actually worked, not the employee's separate leave balance, unless the agreement says otherwise. Avoid billing a customer for leave hours as if they were cleaning time.
When a worker uses paid leave during a scheduled assignment, keep the leave entry distinct from the replacement worker's punches. This helps the employer pay the absent worker under the leave policy while recording actual site service by the person who completed it. If one shift spans multiple buildings, maintain the right work allocation without exposing the employee's reason for absence to the customer.
Cost-plus billing should use the same punches used to pay the worker, so a paid-leave transaction should not be mistaken for a building visit. A manager should review whether an invoice rule uses worked labor, scheduled coverage, or a fixed price and make the decision visible. Per-worker payroll locking helps prevent a duplicate payroll run, not a mistaken client charge.
Audit exceptions and corrections before they become disputes
Each payroll close should include a check for leave requests without a disposition, balances below zero, duplicated use entries, and corrections made after approval. A flag should route a case to a person rather than automatically deny leave or create a discipline note. Compare the worker's request, schedule, punch events, pay record, and prior balance, then preserve the review outcome.
For example, if a worker reports using four hours of leave but a manager entered eight, retain the original eight-hour transaction, add a dated correction to four, and record who approved it and why. The corrected balance should flow into the next payroll and the employee's available summary. Never rewrite a prior period without enough context to reconstruct the original calculation.
Review recurring discrepancies by site, supervisor, and system source. If a mobile form truncates a partial-shift request, fix the workflow rather than making a series of undocumented manual edits. StockPoint's audit log can support a traceable correction path across time and payroll records, but the employer still must verify leave eligibility, balance, pay treatment, and notice obligations.
Train managers and preserve a fair employee experience
Managers should know how to receive a request, preserve confidentiality, route it, and arrange coverage without asking intrusive questions. They should not promise that a leave request will be rejected because the worker is assigned to a difficult building or has used leave earlier in the year. HR should provide a neutral escalation channel when an employee believes the ledger or response is wrong.
Training should reflect the actual policy and languages used by the workforce. Explain the difference between an absence report, a leave request, a time punch, and a payroll correction. A bilingual message that tells a worker where to report a missed punch or request leave can reduce confusion, but the employer should maintain the same approval standard in both languages.
An annual review can compare the written policy with payroll configuration, employee notices, and weekly records. Ask a reviewer who did not enter the transactions to sample balances across different buildings and shifts. StockPoint provides a bilingual operations environment for attendance, payroll inputs, and audit history; to set up documented field-service operations and give workers a clearer route to their records, visit getstockpoint.com and sign up for StockPoint.