Door Schedule & Access Profile Setup in Richmond, TX 77407

Programming a building that nobody works in yet

A new building’s busiest access period happens before the tenant ever shows up. Punch-list trades, flooring crews, the fire alarm technician, the cleaner doing the final wipe-down and the furniture installers all want in, often at odd hours, and usually before there is anyone on site to let them.

The temptation is to leave the front door on a wide-open window until move-in. That habit is how buildings in this corner of Fort Bend County end up with construction-era credentials still live two years later. What we set instead:

• A construction profile with a hard end date. Every badge issued during the build carries an expiry that falls on the substantial-completion date. If the job slips, someone extends it deliberately rather than by inertia.
• A separate schedule name that looks temporary. Call it TEMP-Construction-Ends-MMDD. When it appears in a list a year later, its own name tells you it should be gone.
• No permanent administrator account for a contractor. Trades get credentials. They do not get the ability to write schedules.
• A dated cutover. On handover day the construction profile is deleted, not disabled, and the occupancy schedules take over the same afternoon.

A vehicle gate is not a door, and scheduling it like one causes tailgating

Large parts of 77407 sit outside any city limit, in unincorporated Fort Bend County, so the entrance to a neighbourhood or a flex park is the association’s or the management company’s problem rather than a municipality’s. Gates therefore show up in almost every schedule conversation we have here — and they behave differently from doors in three ways.

Hold-open erases your record. A door on an unlock window at least keeps its camera and its held-open timer. A gate on a hold-open window logs nothing at all: every vehicle that rolls through during the morning school run or the afternoon delivery block is anonymous. If your reason for having a gate is knowing who came in, a wide hold-open window cancels the reason.

There are two clocks, not one. Gate operators carry their own internal timers — auto-close delay, timer-to-close, sometimes a built-in time clock for hold-open — and the access panel has its own schedule. When those two disagree, nobody can explain the behaviour by looking at one device. We decide which one owns the schedule, then neutralise the other so there is a single source of truth.

Safety hardware is not part of the schedule. Reversing devices, photo eyes, edge sensors and the free-exit loop stay live at every hour. A schedule may decide when a gate opens for a visitor; it never decides whether the gate is safe to close on a vehicle or a child.

Six a.m. crews, split shifts, and badges that expire without anyone remembering

The flex and light-industrial suites along the Westpark and Grand Parkway corridor rarely run one set of hours. A typical tenant here has a warehouse side starting before dawn, an office side starting two hours later, and a rotating cast of freight drivers, techs and temporary labour.

That maps cleanly onto profiles if you stop thinking in terms of doors:

The expiry column is the one that saves you. Set an activation and a deactivation date on every credential that belongs to somebody outside your payroll, at the moment you issue it. A badge that stops working on its own is worth more than a policy that depends on a manager remembering to revoke it during a busy week.

The first week of occupancy rewrites whatever you planned

Planned hours and actual hours are never the same. The useful move after a few days of real operation is to stop guessing and read the event log, which is already telling you the truth.

Three numbers are worth pulling:

1. Earliest genuine badge per door, per weekday. If people are consistently arriving twenty minutes before the window opens, they are standing outside in the heat, and someone will eventually prop the door to fix it themselves.
2. Last exit. If the after-hours group is being used nightly by the same two people, they should have a longer window rather than a rule everyone quietly works around.
3. Denied events clustered at one time. A pile of denials at the same minute is almost never a broken badge. It is a boundary in the wrong place, or the midnight-crossing mistake on a night crew’s schedule.

We build in a review at the end of the first fortnight for exactly this reason. Schedules that survive are the ones adjusted once against reality, not the ones drawn on a whiteboard before anybody moved in.

Freight does not take the same holidays your office does

The first long weekend after occupancy is the real test, and in a mixed warehouse-and-office tenant it exposes an assumption people rarely notice they made: that the whole building closes on the same days.

It usually does not. The office observes the holiday; the dock still receives on the day either side, and someone has to be able to get in. Handle it by giving door groups their own holiday behaviour rather than applying one calendar to the whole site — the front entry drops to no-unlock and credential-only, while the dock keeps its receiving window live for a named group.

The gate deserves its own decision on those days too. A hold-open window that makes sense on a Tuesday morning makes no sense on a holiday Friday when the only vehicles arriving are ones nobody is expecting. Holidays are the right time for a gate to be at its strictest, not its most relaxed.

What you can change from your own portal, and what you should not

Plenty of this is genuinely self-service, and we would rather tell you so than sell you a visit. Move a window, add a person to an existing group, issue a badge from a template you already have — that is your job and it takes minutes.

Bring in a licensed low-voltage contractor when:

• A gate operator is involved. Interfacing a schedule to an operator touches the vend and hold-open inputs, and mistakes there create a gate that closes when it should not.
• You are commissioning from scratch and there is no known-good configuration to fall back on.
• The system spans buildings — an amenity centre, an entrance and a maintenance yard on one platform, each with different hours and different people.
• Electrified hardware, magnetic locks or fire-alarm release are in the path. Those are life-safety items signed off by the local building and fire officials, and they are not a place to experiment.
• You want named administrator roles so a site manager can issue badges without being able to rewrite a door’s hours — and a change log that shows who altered what.

What EVOTECH does on a 77407 commissioning visit, step by step

1. Inventory first. Every reader, gate operator, callbox, lock type, contact and exit device recorded with its location, because a schedule is only as good as the hardware it drives.
2. Confirm the time source. Panel time zone, network time, and the operator’s own clock checked and aligned before a single schedule is written.
3. Draft the groups on paper with whoever runs the site, in plain language, before anything is typed.
4. Build schedules, then profiles, then assign. In that order — schedules that nothing references yet are harmless; profiles built on half-finished schedules are not.
5. Drive and walk the test. A test credential at each opening on both sides of every boundary time, and an actual vehicle through the gate to confirm the free-exit loop, the reversing devices and the close timing.
6. Prove the failure modes. What the site does on a power loss and a network loss, and that egress is unaffected either way.
7. Set expiries and hand over. Construction credentials removed, administrator roles created in real names, a printed profile sheet left with the manager, and a short training session with the person who will run it day to day.

What changes the number on a Richmond 77407 estimate

We give an itemized quote after we have seen the site, never a figure over the phone, because the same door count can be an afternoon or a week depending on what is already in place.

• How many openings and gates, and whether they share a single controller or several that do not talk to each other.
• Whether the developer’s or builder’s vendor left a working configuration and credentials, or whether ownership of the platform has to be established first.
• Gate interface work, which is more involved than a door: operator inputs, loops and safety devices all get verified as part of the test.
• How many distinct groups you need and how many people are being enrolled at once.
• Whether badges are being issued and printed, and whether temporary credentials need managing on an ongoing basis.
• Integrations to intercoms, callboxes, cameras or an intrusion panel, each of which adds its own testing.
• Whether the work can happen during the day or has to fit around a dock schedule or a community’s traffic.

The on-site estimate costs nothing, and the quote separates programming from hardware so you can see exactly what you are buying.

Related services

Frequently asked questions