Guard scheduling: software vs spreadsheets

Take one changed shift through your billing records before choosing between scheduling software and a spreadsheet. Can a colleague explain the extra hour on the invoice from the records you kept, without calling the dispatcher who handled it?

Use the same case in each actual setup. You are testing the evidence trail, not comparing feature lists. This exercise concerns client billing records, not employee wage calculations or legal advice.

Set up one hypothetical shift

The following shift and billing terms are fictional assumptions for this exercise, not a customer example or a recommended contract rule.

A post is scheduled from Monday 18:00 to Tuesday 02:00 in the site's time zone. The guard's worked-time record shows Monday 18:00 to Tuesday 03:00. Assume no break adjustment or clock change. At Tuesday 01:30, the client contact requests an extension to 03:00 and the authorized contact confirms it in writing.

For this example only, assume the signed billing terms support charging for the reconciled worked time, including an extension confirmed through that approval process. There is no minimum charge or premium in the example. The recorded interval is nine hours, one more than the original eight-hour schedule. That arithmetic does not establish a billing entitlement in any real contract. If your actual terms do not resolve a quantity or category, leave it unresolved.

Create a sample shift reference, SHIFT-EXAMPLE-01, and use it throughout the exercise. Keep any demonstration records fictional or properly redacted. The record locations below are examples to look for, not capabilities verified in any product.

1. Find the original and corrected time

Ask the reviewer to find the original 02:00 scheduled end, the 03:00 worked end and the explanation for the difference. Can they distinguish the schedule from the worked-time record?

In a spreadsheet process, the evidence might be in a retained schedule file, a worked-time row and a linked correction note. In a software setup, ask where those same records are retained and how to retrieve them. Verify the actual version, settings and working practice rather than assuming either approach preserves history.

Write the location beside SHIFT-EXAMPLE-01. If the original value has been overwritten and cannot be found, record that gap instead of reconstructing an apparently original record.

2. Find the billing term

Next, locate the signed term or approved change that supports the proposed quantity and category. For the fictional case, the reviewer should be able to explain why nine worked hours appear on the sample billing line under the stated assumptions.

Record the document reference beside the shift. If your real terms instead involve a minimum charge, a premium or another adjustment, keep that basis separate from worked time and resolve it with the responsible commercial contact.

Our Billable vs Payable Hours guide connects a worked-time baseline to the post and contract term. Use that distinction when reviewing the sample; a column name is not the supporting agreement.

3. Find the request and approval

Find the Tuesday 01:30 request, the written confirmation and the requested 03:00 end. Check that the approval reference identifies the authorized contact under the example's assumed process.

The request might live in a retained message with its reference recorded beside the shift. That is a sample location, not proof that a particular tool captures or authorizes it. A dispatcher's summary and a client's confirmation should remain distinguishable.

Our Holiday and Callout Shifts guide recommends preserving the original request and approved extension. Apply that check here even though this example has no holiday or callout premium.

4. Follow the invoice reference

Give the fictional invoice line a reference that points to SHIFT-EXAMPLE-01. Ask the reviewer to follow that reference to the nine-hour worked interval, the assumed billing basis and the extension approval.

Record where each item was found. If your workflow uses separate files or a separate approval log, include those dependencies. If a vendor says an export supplies the needed reference, ask to see the relevant behavior in the version and configuration you would use. Leave untested behavior unresolved.

5. Hand the packet to another person

Let a colleague trace the line without your narration. Ask them to identify the original eight-hour schedule, the nine-hour worked record, the reason for the extra hour, the applicable billing term and the approval.

Use three outcomes for each check: found, unresolved, or not applicable with a reason. Keep a named internal owner and next action beside every unresolved item. Avoid an overall score that hides a missing approval or an unexplained correction.

The result is a concrete list of records your current process can produce and gaps to resolve. It is not evidence that one tool category is more accurate. A purchase comparison still needs the actual product behavior, configuration and full workflow costs. Start with the trace you observed, then verify the specific change you expect a different setup to make.