An overnight security assignment can appear on two calendar dates, cross an invoice period and include a relief officer. Those boundaries create review questions even when the underlying service is straightforward. The safest administrative approach is to preserve the complete timeline first and apply the agreed billing rules second.
This guide helps NYC property and hotel managers organize evidence for the security-service invoice review process. It is not a wage calculation, a payroll instruction or a rule about which customer charges are permitted.
Write complete intervals instead of date labels
Record both start and end timestamps with their dates and time zone. A row that says “Friday night, 11–7” forces the next reviewer to infer the end date. A report that groups all entries under the start date may be perfectly usable, but the invoice reviewer must understand that convention.
For each interval capture:
- Property and specific post.
- Start date, local time and time zone.
- End date, local time and time zone.
- Source of the recorded times and any correction reference.
- Assigned service category and approved scope reference.
- The vendor's rule for allocating that interval to invoice periods.
Do not assume that a shift spanning two months must be split into two billed lines, or that it must belong entirely to the start month. Confirm how the agreement and accounting process handle that boundary.
Treat relief as a sequence of assignments
Identify when one person's recorded assignment ended and the next person's began. Then distinguish the physical presence of two people from the service the customer authorized. A brief handoff, a planned two-person post and a late relief extension are different situations.
A useful review sequence is:
- Identify the approved number of concurrent posts and their purpose.
- Arrange the available assignment records in time order.
- Mark gaps or overlaps as questions requiring explanation.
- Check the contract and relevant approval before assigning billing treatment.
- Record the vendor's explanation and the authorized reviewer's decision.
Do not automatically delete an overlap as a duplicate. Equally, do not accept every overlapping interval as an additional billable post. The distinction depends on the authorized scope and supporting evidence, not only on the timestamps.
A hypothetical relief example
Suppose one officer's record ends after the relief officer's recorded arrival. The overlap may represent an authorized handoff, delayed departure, a record-entry error or another situation. The review packet should ask which explanation applies and what supports it. It should not identify an employee as responsible for an overcharge merely because two rows overlap.
Handle ambiguous or missing times openly
A handwritten correction, an incomplete end time or a system timestamp in a different zone should remain visible. Record the question and the source of the clarification. Never replace the original with a cleaner-looking estimate and then present the estimate as contemporaneous evidence.
Clock-change weekends require particular care because local clock labels alone may be ambiguous. Ask the system or record owner how the interval was stored and how the agreed customer billing calculation treats it. Do not apply a universal adjustment to every overnight assignment or use this review to change employee pay.
The coverage-evidence worksheet helps distinguish a scheduled interval from recorded attendance. The discrepancy-request packet helps preserve the conflicting values without asserting an unsupported conclusion.
Keep extra coverage approvals next to the timeline
A property may request an additional post or an extension during an event, project or unusual operating period. Keep that request separate from the record of what occurred. Both matter, but they establish different things.
The extra-coverage approval guide sets out the useful fields: scope, start and end conditions, decision owner and the commercial reference. Where approval or interpretation remains unresolved, send that question to the responsible contract owner. Avoid inventing a default minimum shift, premium or rounding rule.
Supporting records should be organized so another reviewer can follow the service interval and resulting transaction. The IRS recordkeeping overview provides broader context on keeping invoices and related evidence; it does not establish a customer billing rule for relief assignments.
Close the review without losing the explanation
The final packet should show the original interval, the issue identified, the clarification and the accepted billing document. If a correction produces a credit or replacement invoice, follow the credit closeout process so that both versions do not remain payable.
Before approval, check that both calendar dates are explicit, overlapping assignments are explained, unresolved items have owners and accounting can trace the accepted line back to its evidence. Keep a concise lesson for the next period, such as a clearer post name or timestamp format, instead of repeatedly rediscovering the same ambiguity.
For property-specific security coverage and reporting expectations, see Guardian Consulting's services.