Access Schedule Configuration in Houston, TX 77057

In a Post Oak tower your schedule is the second schedule, not the first

The 77057 footprint runs from Post Oak Boulevard and the Galleria out through San Felipe, Chimney Rock, Fountain View and the Tanglewood and Briargrove blocks. Very little of the access work here is a standalone building. It is a leased suite on the ninth floor, a dental office in a low-rise off Chimney Rock, a showroom in a Westheimer strip, or a unit in a residential tower.

So two systems decide whether a person gets through a door, and only one is yours. Schedule your suite entry to open an hour before the elevator will carry anyone to your floor and the programming is flawless while the result is useless.

We ask for the building’s standard hours in writing first, because one tower’s “normal business hours” is 7:00 to 6:00 with Saturday half-days and the tower across the street is 8:00 to 6:00 with no weekend coverage at all.

What actually gets programmed when we say ‘schedule’

Whatever brand is on the reader, commercial platforms store three separate objects, and confusing them is where self-programmed systems go wrong.

• The time schedule — a named set of intervals with start times, end times and days of the week. It has no idea what a door is.
• The holiday calendar — dates that override normal day-of-week behaviour.
• The access level — a door or group of doors paired with a time schedule. Credentials receive access levels, never schedules directly.

That indirection keeps a system maintainable: take the suite next door, add two openings to one access level, and every badge inherits it. Where hours were entered badge by badge, one change becomes an afternoon of typing and a guaranteed inconsistency.

Why a suite door should not unlock just because it is 8:00 a.m.

A plain scheduled unlock is blind. At 8:00 the panel releases the strike and the suite entry stands open to the elevator lobby until relock fires, whether or not one employee made it in. On the morning after an ice event on the Loop, or the Friday after Thanksgiving when the office quietly took the day, that is an unattended open door on a floor with public elevator access.

Most mid-range platforms and up have the fix — first-person-in, supervised unlock or office mode, depending on the vendor. The door does not latch when the window starts; it waits, and the first valid credential presented inside the window arms the unlock. Nobody arrives, nothing opens.

Three settings people forget alongside it

• The relock. Days-of-week flags set on the wrong object leave a leaf latched from Friday evening to Monday morning.
• The door-held-open timer. While a leaf is intentionally latched, the propped-door alarm annunciates all day unless the schedule suppresses it. Staff learn to ignore the sounder, and it is then useless at 9 p.m.
• Lockdown priority. A lockdown command must outrank an active unlock schedule, or the building cannot be secured during the window it most needs to be.

None of this touches egress. The lever or push bar inside releases mechanically with no power and no software involved — a hardware property we verify on the walk, not something we program.

Floor access, turnstiles, and the elevator side of the problem

In a Post Oak or Sage Road high-rise the elevator is an access control device. During published hours the cab usually accepts any floor button. Outside them, a cab reader or a destination-dispatch kiosk authorizes the floor and the controller energizes a floor relay for a few seconds before the button will take.

This produces the most confusing symptom we get called about in 77057. The badge works, the suite door opens at 6:30 a.m., and the tenant is certain the system is broken — because the employee could never reach the floor. The suite window started at 6:30 and the building’s floor authorization for that badge started at 7:00. Nothing was faulty; two schedules simply did not overlap.

The request to the property team therefore has to be specific, and we help write it: extend floor authorization for this list of badge numbers, to these hours, on these days. Expect a form, a lead time, and in most towers a certificate of insurance on file.

Night cleaning, day porters, and the vendors with their own windows

A typical Galleria-area suite has more non-employees carrying access than employees: janitorial in the evening, a day porter at midday, an IT vendor, shredding, plant service, and whoever the landlord sends for filters and lamps. The lazy build puts them all on the staff level, or a 24/7 level, and then nobody can answer the one question that matters after an incident — who could have been in the file room at 7:40 on a Tuesday. Separation is what makes an audit log worth keeping.

• One access level per vendor, not per person, covering only the doors they need on the nights they come.
• Activation and deactivation dates on the credential. A badge issued for a six-week project stops working in week seven with nobody remembering anything.
• Doors excluded on purpose. Cleaning rarely needs the server closet or records room — a two-minute decision at build time, an impossible conversation later.

Whose clock the audit log is actually using

Events are timestamped by whichever device made the decision — usually the field panel, not the management server and not your workstation. A panel keeps time on a battery-backed real time clock, and if it was never pointed at a network time source it drifts quietly, a few seconds a week, for years.

Two things then break. Schedules start and end at the wrong wall-clock minute, which shows up as a door unlocking early or a badge failing right at the boundary. More expensively, the access log stops agreeing with the camera recorder, and a four-minute offset between the two is the difference between evidence and an argument. So we point the panel at a time source it can actually reach from its VLAN, set the zone to US Central with daylight saving handled at the panel rather than faked by shifting hours twice a year, and marry the recorder to the same source.

One warning about the March change: local time jumps from 2:00 a.m. to 3:00 a.m., so that hour does not exist and any boundary inside it never fires that day. If you run an overnight security presence, move those boundaries to 1:00 or 4:00 and the problem is gone permanently.

When a property manager can do this alone and when they cannot

We will tell you when you do not need us. One or two openings on a modern cloud platform, fifteen people, no holiday complexity and no alarm integration — the web interface is genuinely good enough and an office manager can run it. Bring in a technician when any of these is true:

• More than one controller, or a controller nobody can physically locate.
• A door that changes state on its own, or anything on a maglock.
• An alarm partition that arms or disarms on schedule, where an error becomes a false dispatch.
• Elevator floors, turnstiles or a garage gate that must line up with your hours.
• A lease clause, insurer or client contract requiring access reports.
• A system you inherited with the suite, with no administrator password and no documentation.

That last one is the most common call we take in 77057, and it is usually a half day rather than the disaster tenants expect.

What an EVOTECH technician does on a 77057 schedule call, in order

1. Export before we edit, so there is always a known state to return to.
2. Walk every opening. Leaf type, fail-safe or fail-secure lock, whether a request-to-exit and door position switch are present and working, and which openings sit on the egress path.
3. Get the real week — not the posted hours. Who opens, who closes, which nights cleaning comes, what December looks like.
4. Draft on paper. Schedules, holiday calendar and access levels agreed before a field is typed.
5. Build and download to every panel, then confirm each panel actually took it. A panel that missed a download is the invisible failure here.
6. Test on the boundaries. Live badge reads at the opening minute and the closing minute, one credential per level, event log open.
7. Document and hand over a one-page map of levels, schedules, holidays and administrators.

Coordinating after-hours testing, the certificate of insurance and freight access with building management is part of the job.

The five programming errors that send us back to Uptown

• An unlock with no verified relock — found on a Monday, after a weekend of the suite standing open.
• No holiday calendar at all, so doors run ordinary weekday behaviour on Thanksgiving and through the week between the holidays.
• A second door added to a level without checking its hardware. The first is a fail-secure strike, the new one a maglock, and “unlock” means something different on each.
• Everyone left on a 24/7 level, almost always residue from a move-in where broad access got granted and never narrowed.
• Propped-door alarms never adjusted for the latched window, so the sounder runs all day and gets taped over.

What changes the number on an Uptown schedule job

We quote after we look, and the quote is itemized. What actually moves it:

• How many openings and controllers, and whether all of them reach one workstation or need a laptop at each panel.
• Whether usable documentation of the current configuration exists, or we are reverse-engineering it from the hardware.
• How many genuinely distinct populations you have — three is quick, eleven is a design exercise.
• Whether elevators, turnstiles or a garage gate need coordinating with property management.
• Whether boundary testing must happen outside business hours, which in most towers also means a freight reservation.
• Whether anything physical is missing: a door position switch never installed, a dead power supply, a drop to a controller.

We do not quote this work over the phone, because the panel almost never contains what the last person said it contains. The on-site estimate is free.

Related services

Frequently asked questions