Additional Security Coverage Approval Record

An additional officer for a tenant reception and an extension of the regular lobby post are different purchases, even if both appear as “extra coverage” on an invoice. Property teams need enough detail to connect the request, the approval, the service delivered and the eventual charge without reconstructing the arrangement from scattered messages.

This guide covers the property-side approval record for an additional assignment. Use it with the security-service invoice review guide. It does not determine payroll obligations, interpret a contract or authorize a reduction in required coverage.

Separate the request from the approval

Start a record when someone asks for a change. An employee's request is useful evidence of what was wanted; it is not automatically evidence that the person could approve the purchase. Similarly, a vendor's acknowledgement that it received a message does not establish acceptance of every proposed term.

Record these stages separately:

Requested: someone described an operational need.
Reviewed: the property and vendor clarified the assignment.
Authorized: the designated decision-maker approved the documented scope.
Confirmed: the vendor confirmed the assignment it would provide.
Performed: the delivery record shows what occurred.

Keep the original messages linked to the record. If a telephone discussion changes the arrangement, record who participated and ask for written confirmation through the property's established process.

Illustrative property manager and security supervisor comparing paper service records at an office desk. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

Write a scope that can be matched to a bill

Use one reference for the additional assignment and carry it into the schedule, service record and invoice review. A building address alone may be insufficient when several tenants or departments request coverage at the same property.

The operational approval card should include:

Property, requesting department and assignment reference.
Purpose and exact post or area covered.
Service category and the duties requested.
Start and end dates, times and time zone.
Whether this adds a post or extends an existing one.
The agreed pricing reference and any unresolved charge questions.
Property and vendor contacts for changes.
The person authorized to approve an extension or cancellation.

Keep technical or qualification requirements with the responsible operational reviewer. An invoice clerk should not have to decide whether one type of security or fire-life-safety assignment can substitute for another.

Illustrative security officer recording an arrival at a reception desk, one source of context rather than proof of a complete assignment. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

Make the end point explicit

Temporary coverage should have a defined end point or a documented review time. Avoid “until further notice” unless the authorized parties have actually agreed how that instruction will be managed.

Illustrative blank sequence cards beside a clock and ruler representing a chronological review of service intervals. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

A hypothetical approval record

A hotel requests an additional lobby officer for a private reception from 17:00 to 22:00 on a specified date. The record says that the assignment supplements, rather than replaces, the ordinary lobby post. It identifies the manager who may approve an extension and the written agreement used to price it.

If the reception ends at 23:00, do not silently edit the original 22:00 end time. Add an extension entry showing when it was requested, who approved it, what the vendor confirmed and what the service record supports. The overnight and relief-hours review helps when a change crosses a date boundary.

Give urgent changes their own review path

Sometimes the operational need is immediate and the commercial paperwork is incomplete. Follow the property's approved safety and escalation arrangements first. The record should state which facts were known, which terms were unresolved and who was contacted, rather than inventing a retrospective approval.

After the immediate situation, assign a named reviewer to resolve the commercial record. An internal note explaining why a request was urgent does not itself show that both parties accepted a particular charge.

Illustrative staff member writing a dated operational note at a desk for another reviewer. — AI-generated editorial illustration. People, location and documents are illustrative, not an actual client or billing record.

Reconcile the approved and performed versions

Before approving the invoice line, compare the original request, authorized changes and actual delivery evidence. Use the coverage evidence worksheet to separate scheduled hours from the records supporting service.

Check whether the charge belongs to the correct property and period, whether an extension was recorded twice, and whether an added post has been confused with ordinary coverage. Send unresolved differences through a focused discrepancy request, not an informal alteration to the vendor's invoice.

The FTC's business-invoice guidance emphasizes clear approval procedures and checking invoices. This assignment card is a practical implementation idea, not an FTC-prescribed form or a guarantee against errors.

For help discussing property staffing scope and operational responsibilities, explore Guardian Consulting's security services.