Door Access Credential Setup in Houston, TX 77027

Why your staff are carrying two badges

In a leased building there are normally two independent access systems in play, and they do not talk to each other unless somebody deliberately makes them.

That last row is the whole problem. When someone leaves, deactivating them in your system is instant and satisfying, and completely fails to stop them badging into the garage at midnight on the landlord’s system. Offboarding here is always two actions.

Two systems in one building can share a number space

The classic 26-bit Wiegand card format carries an 8-bit facility code and a 16-bit card number. That is 255 possible facility codes and a card range that plenty of orders start at 1.

Now imagine two suites in the same 77027 building, both running their own system, both ordering the cheapest 26-bit cards with a common facility code and a low starting number. It is entirely possible for a neighbouring tenant’s card to satisfy your reader, because from your controller’s point of view it is the same number.

The ways out are straightforward if they are chosen at the start: get a facility code that is yours and record it, order cards in a documented range rather than accepting defaults, or move to a higher-bit format or an encrypted smart-card credential where the number space is not casually shared. What does not work is assuming the integrator handled it.

Bit format: why a brand-new card beeps and stays red

This is the most common brand-new-card complaint we are called for, and it is almost never a faulty card.

A controller is configured to interpret a specific bit length. Present a 35-bit card to a panel expecting 26 bits and the read is either rejected outright or parsed into a number that belongs to nobody. The event log is the giveaway: an invalid or unknown format entry, or an access-denied against a card number that looks nothing like what is printed on the card.

Diagnosing it takes minutes. We read a sample card at the reader with the panel reporting raw data, confirm the actual bit length and facility code, and compare that to what the system was told to expect. Then either the panel learns the correct format or the card order was wrong – and it is much better to find that on the first card than on the four hundredth.

Same-day onboarding, same-hour offboarding

A credential program lives or dies on whether it is wired into how the business actually hires and separates people.

Onboarding is easy: an access level per role, so a new hire is assigned a template rather than someone guessing which doors a new paraplanner needs. Exits need a written checklist, because they happen on bad days and in a hurry.

• Deactivate the cardholder in your suite system – deactivate, not delete, so the person’s event history stays readable.
• Flag the credential lost or stolen if it was not returned, so a later attempt raises a specific event rather than a generic denial.
• Send the removal request to property management the same day for the base-building badge and any garage credential.
• Revoke mobile credentials, which are separate objects from a plastic card and survive collecting the card.
• Note the return, or non-return, in the record. That note is what a future audit reads.

Badges that expire without anyone remembering

Cleaning crews, IT contractors, a build-out team, a seasonal temp, a vendor who needs the file room for two days of records work. Every one of them is a credential that will still be live in two years unless it was built to expire.

We set temporary credentials up on their own number block, on an access level restricted to the doors the work touches, with an activation and deactivation date entered at issue. The block matters: it lets an administrator void every outstanding contractor credential in one action after a project, and it makes the log readable at a glance.

For after-hours cleaning we normally build a separate level with its own schedule rather than lending someone a staff badge, which is what tends to happen otherwise and destroys the meaning of the log.

After-hours entry, elevators and the alarm nobody thought about

Three things behave differently outside business hours in a leased building.

Elevator floor control usually belongs to the landlord, so after-hours access to your floor may require a base-building credential even though your own suite door would have opened. Suite doors that are unlocked during business hours should be on a schedule that relocks on time and, ideally, unlocks only after the first valid read of the morning rather than blindly at nine.

And if the suite has an intrusion alarm, a badge entry at three in the morning without a disarm is a false alarm, a call to a key holder and sometimes a fee. That interaction has to be designed on purpose – either separate credentials and disarm codes with staff trained on the order of operations, or a deliberate integration where a valid entry by an authorised person disarms the partition.

Printing photo badges without destroying the card

Client-facing suites often want a photo badge, and there are two practical traps.

The first is the slot punch. A contactless card has an antenna running around the inside edge of the card body; punching a hole through it kills the card silently, and it will be blamed on the reader. Punch only at the position the card manufacturer specifies, or avoid the problem entirely with adhesive or clip holders designed for the card.

The second is workflow. A badge printer means somebody in the office owns card design, a consumables supply and the reprint request when a card is bent in a wallet. That is a real internal job, and it should be assigned to a person before the printer is bought rather than after.

The access review nobody runs until they need it

Every system we hand over can produce a report of which people hold which access levels, and which levels open which doors. Almost nobody runs it, and it takes about twenty minutes a quarter.

What that review looks for: records that no longer match the current staff roster, contractor credentials past their project, access levels that have quietly accumulated doors, shared or generic records, and administrator accounts belonging to people who changed jobs. In a professional practice this is also the document that answers an insurer or a compliance auditor without a scramble.

We set the report up during handover and show two people how to run it, so it is not something that depends on calling us.

How an EVOTECH suite rollout runs in 77027

• Meet property management first, and establish in writing what the base-building system covers and how tenant requests are submitted.
• Survey the suite: entry door type (aluminium storefront behaves differently from a hollow-metal door), IT closet, records room and any cash handling area.
• Confirm or establish your facility code and card number range, and document both for the business rather than for the installer.
• Build access levels by role, not by person, and map them against the current org chart.
• Enrol staff, verify one card per level at a real door, and issue temporary credentials on a separate block.
• Write the two-system offboarding checklist and hand it to whoever owns HR.
• Train two administrators, set up the quarterly report, and leave documentation with the tenant.
• Schedule any work needing the freight elevator or loading dock through building management, including after-hours windows.

What we get called back for around Post Oak

A short list, in rough order of frequency: a new card order in the wrong bit format; an employee removed from the suite system but never from the landlord’s; a shared administrator login that means nobody can say who changed a schedule; a temporary badge issued with no end date during a build-out; an aluminium storefront door whose closer was never adjusted, so it does not latch and the strike gets blamed; and a suite that auto-unlocks on a timer on a public holiday because the calendar was never populated.

All six are configuration and process, not hardware. All six are cheaper to prevent at setup than to chase later.

What drives the scope of a suite-level rollout

• Number of controlled openings inside the suite and whether cable already exists above the ceiling.
• Door type and hardware – storefront doors, existing closers and latching condition often need attention first.
• Credential technology and whether you are migrating an existing cardholder database.
• Head count at first issue, and whether photo badging with a printer is part of it.
• Coordination with property management, including after-hours or dock-scheduled work.
• Any intrusion alarm integration, which is design work before it is installation work.
• Administrator training and the number of people who need it.

EVOTECH IT LLC is a licensed and insured low-voltage contractor with 20+ years of commercial work, rated 5.0 stars, serving Houston, Katy, Sugar Land, Richmond, Fulshear and Cypress. On-site estimates are free and quotes are itemised.

Related services

Frequently asked questions