It is the Monday after the time change and your first employee is standing outside the back door at 6:45 in the morning with a coffee in one hand and a badge in the other, and the door will not unlock. The schedule in the access control panel still thinks it is an hour earlier, so as far as that little box is concerned the building does not open yet. She calls you. You are not awake. Somebody eventually props the door with a rock, which is now your security posture for the day.
That is the mild version. The expensive version is the one where a customer disputes a transaction eleven weeks later, you pull the camera footage to settle it, and the timestamp on the video is off by an hour from the timestamp on the receipt. Now you have two records that disagree, and the one thing you needed them to do was agree. None of this is exotic. It happens twice a year, quietly, to businesses that have no idea it happened until they need something.
Why a One Hour Shift Breaks Real Equipment
In the United States, daylight saving time starts at 2 a.m. on the second Sunday in March and ends at 2 a.m. on the first Sunday in November, according to the National Institute of Standards and Technology, which distributes official time for the country. Your phone and your laptop handle that automatically because they check in with a time server and they carry an up to date list of the world’s time zone rules. That list is a real thing, maintained publicly as the IANA Time Zone Database, and it gets updated whenever a government somewhere changes its rules.
The problem is that half the equipment in a small business does not check in with anything. A door controller in a closet, a camera recorder in the back room, an alarm panel, a time clock, an older phone system. Many of these were installed once, set by hand, and never updated. Some carry a time zone list that is a decade stale. Some run on an internal battery clock that drifts a few seconds a week and nobody notices until the drift adds up. And some are sitting on a network segment that cannot reach the internet at all, which is often a deliberate security decision, so they never get corrected.
The Systems That Actually Get Bitten
- Door and gate controllers. Unlock schedules, lockdown schedules, and holiday overrides all live in a panel that may or may not know the date changed. This one is the most likely to interrupt business on the first morning.
- Cameras and the recorder they feed. The camera and the recorder can disagree with each other, and either can disagree with your point of sale system. A video timestamp that does not line up with a transaction record is worth a lot less when you actually need it.
- Phone systems and auto attendants. Your business hours greeting, your after hours routing, and your voicemail all key off the phone system’s clock. Customers calling at 8:05 and getting the closed message is a slow leak you may never hear about.
- Backups and scheduled jobs. A backup set to run at 11 p.m. and a report set to generate at 11:30 p.m. can swap order or collide when one of them shifts and the other does not. The backup does not fail loudly. It just runs against a database mid update.
- Time clocks and payroll exports. An hour of drift on a punch clock is an hour of payroll error multiplied by every employee, and it is the kind of error people notice on payday.
- Thermostats, lighting, irrigation, and signage. Not urgent, but a lobby that heats up an hour late in November is a comfort complaint and a utility bill you did not plan on.
The Twice a Year Walk Around
Put a recurring reminder on your calendar for the Monday after each change, and do a physical lap. It takes about thirty minutes once you have done it a couple of times, and it is the cheapest insurance in the building.
- Look at the clock on every screen you pass. The recorder, the alarm keypad, the time clock, the register, the label printer. Compare each against your phone. Write down anything that is off, even by a few minutes.
- Badge in at the earliest scheduled unlock. Or have your opener text you when the door works. Do not assume the schedule survived.
- Call your own main line before and after opening time. Confirm you get the open greeting when you are open and the closed greeting when you are not. Two calls, one minute.
- Check that last night’s backup finished and finished when you expected. Not just the green checkmark. The timestamp.
- Pull one camera clip and compare it to a receipt from the same moment. If they match, you know your evidence chain is intact. If they do not, you just found the problem on a calm Monday instead of during a dispute.
The Real Fix Is One Source of Time
Walking around twice a year catches problems. Pointing everything at the same clock prevents them. The mechanism is Network Time Protocol, or NTP, which is simply the standard way a device asks a trusted server what time it is and corrects itself. Most business equipment supports it and most business equipment is not configured to use it, because the installer typed the time in by hand on the day it went in and moved on.
- Configure NTP on every device that supports it. Same server, same time zone setting, across cameras, recorders, door panels, phone systems, servers, and network gear. Consistency matters more than which server you pick.
- Give isolated equipment a local time source. If a device is deliberately kept off the internet, point it at an internal server or a network appliance that does have accurate time. Isolation should not mean abandonment.
- Update firmware on the old stuff. Firmware is the software burned into a device. Old firmware is the usual reason a recorder still believes daylight saving time ends in October. This is also how the security holes in those devices get closed.
- Write down what you found. A one page list of every device, where its clock comes from, and who to call for it. Next time this takes ten minutes instead of thirty.
One more note. Congress periodically debates doing away with the switch entirely and staying on one time year round. If that ever happens, the twice a year clock change goes away, but this audit does not. A rule change means every device in your building needs to learn the new rule, and the ones that do not check in with anything will be exactly as wrong as they are today.
The Bottom Line
Time is infrastructure. When your systems disagree about what time it is, your logs stop being evidence, your schedules stop being reliable, and your automations start fighting each other in ways that are genuinely hard to diagnose later. Two calendar reminders a year and one lap around the building fixes almost all of it. Point everything at the same clock and even the lap gets easy.
If you would rather somebody else keep track of which box in which closet has the wrong time, that is a large part of what we do for businesses in Lewisville, Flower Mound, Highland Village, and across Denton County. Reach out at harrisonward.com/contact.
Comments are closed