Show Notes
Why day-one failures are usually predictable
This episode of Built, Wired & Secured focuses on a simple but costly reality: most move-in and closeout failures are not caused by exotic technical issues. They usually come from small operational gaps that should have been caught before handover. The episode opens with a vivid scenario many operators will recognize immediately. A receptionist badge does not work, the backup link for the phone system never fails over, calls do not ring, people cannot get in, and a routine handover meeting turns into a firefight.
That framing sets the tone for the conversation. The point is not to debate advanced configurations or legal obligations. The point is to reduce preventable disruption with a short, repeatable smoke test sprint that can be run in roughly 30 to 60 minutes during closeout or just before a tenant move-in.
Michael Harrington joins the conversation with an operational lens shaped by property and portfolio management. His guiding question is straightforward: what breaks if this goes down? That question drives the ten rapid acceptance checks covered in the episode.
The first group of smoke tests: power, credentials, alerts, and time
The first set of checks centers on foundational systems that quietly determine whether a space is truly ready for occupancy.
Power failover smoke test: Teams should remove mains power to a targeted system or flip the breaker according to the documented procedure, then verify that the backup source supports the critical load. A pass means the right systems stay on and the correct labeled circuits remain powered. A fail means unexpected equipment drops offline or the wrong circuits stay alive. The recommended evidence is light but useful: a photo or short video of the breaker position and a timestamped status screen or closeout note.
Credential enroll and revoke test: One new sample badge or temporary account should be enrolled, tested against the expected doors or systems, then revoked to confirm access is properly removed. The key risk here is asymmetry. A badge may enroll successfully while revoke behavior fails, or access may apply to the wrong doors. The evidence should include a screenshot or log extract showing both enroll and revoke events, plus a note about the doors tested.
Monitoring alert sanity: The team should trigger a known low-risk alert and verify that the alert reaches the correct channels, whether that is email, SMS, ticketing, or a webhook. The issue is not whether monitoring exists on paper. It is whether the right people are actually notified. A pass means the alert appears where expected and reaches the right on-call contact. A fail means the alert either never fires or goes to the wrong distribution list.
Time alignment spot check: Access control, monitoring, and a core switch should all be compared to a known accurate time source. A few seconds of difference may be acceptable, but minute-level drift undermines event correlation. The evidence can be as simple as screenshots of system time or NTP status pages.
The second group: metering, temporary services, spares, and documentation reality checks
The next set of smoke tests addresses the kind of operational mismatches that create billing issues, service interruptions, or slow incident response later.
Metering sanity: A quick check confirms that meters feeding tenant or critical-area circuits display readings that make sense during a light load. Zero readings or obviously wild values should raise immediate concern. This is less about precision engineering and more about confirming that the baseline is believable before handover.
Temporary services demobilization: Teams should walk the perimeter of the tenant space and service entrance to identify temporary power or communications feeds, confirm they are scheduled for removal, and safely demobilize one harmless temporary feed to prove the permanent feed is actually carrying the load. This is one of the episode's most practical checks because temporary infrastructure often lingers longer than expected.
Spare retrieval: The test here is straightforward. Confirm that physical spares are stored where operations and maintenance documentation says they are, and verify that the spare label matches the equipment ID on the diagram. It sounds mundane, but the real question is whether a replacement can be retrieved within the expected SLA when something fails.
Closet label-to-diagram spot check: Rather than assuming the drawing matches reality, the team should pick one network or mechanical closet, verify the label on the door against the diagram, and spot-check the three highest-impact items inside, including the main breaker, core switch, and communications backhaul. If labels do not match, troubleshooting gets slower at exactly the wrong moment.
The final group: fallback communications and tenant issue intake
The final checks deal with business continuity and tenant experience.
Fallback communications bootstrap: The team should verify that a backup communications path actually works end to end. That may be a cellular hotspot, a secondary PSTN number, or a pre-approved messaging channel. Someone should place a call or send a message and confirm receipt by the duty contact. A fallback path is only useful if people know how to use it when the primary path fails.
Tenant signal intake trial: A tenant representative should submit a simple issue through the standard intake channel such as a help desk portal or dedicated email address. The team then confirms that the issue lands in the correct workflow, receives an acknowledgement, and is assigned to an owner. This is a direct test of whether tenants can actually be heard when something goes wrong.
How to run the sprint without making it heavy
One of the best parts of the episode is its insistence on speed and simplicity. Alex and Michael are not recommending a giant closeout binder or a burdensome commissioning exercise. They suggest batching by location and owner. One person can run power and metering checks in a zone. Another can handle credentials and tenant intake. A third can walk closets and confirm spares. The ownership matrix itself can stay simple: test, owner, backup owner, and evidence field.
The proposed operating model is equally practical: schedule a single coordinated 30-minute window right before move-in or just before the closeout meeting. With three people and ten checks, the sprint can be completed within an hour. If anything fails, log it, triage it, and require a retest before tenant access is granted.
Examples that show why this matters
The episode closes with three useful examples. In one case, a credential enroll and revoke check exposed a scheduled sync job that had never been enabled, preventing revocations from reaching the door controller. The fix was small, but the impact on move-in readiness was large. In another, a metering sanity check caught a mislabeled meter during handover, preventing incorrect billing. A third example involved a temporary power feed that was still carrying a server rack when the general contractor prepared to remove it. The demobilization smoke test prevented a service outage.
The rule of thumb is clear: checks that take minutes now can save hours of disruption and avoid reputational damage later.
Three immediate actions for listeners
Run a 30-minute sprint using the ten smoke tests before your next move-in, cutover, or closeout.
Record at least two evidence artifacts for each pass or fail so future teams are not relying on memory.
Add one explicit owner for operations and maintenance in the closeout packet so accountability is clear after handover.
The closing advice is simple and memorable: keep it short, keep it repeatable, and assign one clear contact to every check. As the episode puts it, things may seem fine until they fail, so verify before you hand them over. Listeners are also directed to the Built, Wired & Secured resource hub to download the printable runbook and ownership matrix tied to this episode.
Smoke tests are not glamorous, but they prevent expensive first impressions
Move-in day and project closeout are supposed to feel like milestones. Instead, they often become stress tests. A tenant arrives and a badge does not work. The phones do not fail over when they should. A backup path exists in theory but not in practice. Someone starts calling trades, facilities, IT, and vendors at the same time while the tenant waits for answers.
That is the problem tackled in this episode of Built, Wired & Secured: how to stop day-one failures with ten rapid acceptance smoke tests that can be completed in a focused 30 to 60 minute sprint.
The conversation stays intentionally practical. It is not about deep vendor configurations. It is not about legal interpretation. It is about catching the small operational gaps that create outsized disruption during handover. As Michael Harrington explains, the useful question is simple: what breaks if this goes down? That mindset turns technical closeout into operational readiness.
Why the small failures are the dangerous ones
One of the most valuable points in the episode is that the failures that hurt tenant confidence are usually not exotic. They are stale credentials, broken alert routing, mislabeled circuits, temporary feeds left in place, or documentation that does not match what is installed. These are not always expensive fixes, but they are expensive moments. They waste time, create confusion, and damage trust right when a building team or technology partner should be demonstrating control.
For owners, operators, and service partners, this is where disciplined acceptance checks matter. A short, structured sprint before move-in is a low-cost way to reduce immediate operational risk.
The first four checks verify foundational readiness
The first group of smoke tests focuses on the basic systems that underpin continuity.
1. Power failover smoke test. Remove mains power to the targeted system or flip the breaker according to the documented procedure and verify that generator transfer or UPS power sustains the critical loads. This check is fast, but the business outcome is significant. If failover does not perform as expected, the first real outage becomes the test environment.
2. Credential enroll and revoke. Enroll a sample badge or temporary account, confirm it grants access where expected, then revoke it and verify access is removed. This test protects both operations and security. A badge system that can grant access but not reliably remove it is not ready, no matter what the dashboard says.
3. Monitoring alert sanity. Trigger a known low-risk alert and confirm it reaches the right channel and the right person. Monitoring is only valuable if notifications get to the team that must act. An alert routed to the wrong list or a stale on-call contact creates a false sense of protection.
4. Time alignment spot check. Compare timestamps across access control, monitoring, and a core switch against a known accurate source. When clocks drift by minutes instead of seconds, investigations slow down, evidence loses value, and cross-system troubleshooting becomes guesswork.
None of these tests require a large report. The episode recommends minimal evidence: a photo, screenshot, timestamp, log excerpt, or short note in the closeout log. That matters because lightweight evidence makes the sprint sustainable.
The middle checks confirm the environment is actually what the drawings and assumptions say it is
The second group of tests is where operational reality often diverges from paperwork.
5. Metering sanity. Confirm that the meters feeding tenant or critical-area circuits show believable readings under light load. If a partially active space shows zero or an implausible number, that is a handover problem waiting to become a billing or troubleshooting problem later.
6. Temporary services demobilization. Walk the perimeter of the tenant space and service entrance, identify temporary power or communications feeds, confirm removal plans, and safely demobilize one harmless temporary feed to prove permanent services are truly carrying the load. This is one of the clearest examples of acceptance discipline protecting operations. A temporary service that quietly became production can turn a routine removal into an outage.
7. Spare retrieval. Confirm that physical spares exist where operations and maintenance documentation says they do, and verify that the label on the spare matches the equipment ID on the diagram. This is not just an inventory exercise. It is a recovery-time question. If a component fails, can the team retrieve the right replacement within the expected service window?
8. Closet label-to-diagram spot check. Choose one network or mechanical closet, confirm the door label matches the diagram, and verify the three highest-impact items against the drawing. This protects troubleshooting speed. In a real incident, teams need labels and diagrams they can trust immediately.
These checks reinforce a broader point that matters for commercial real estate and operational environments alike: readiness is not defined by whether a project is substantially complete. It is defined by whether the environment can be supported, recovered, and understood under pressure.
The last two tests focus on communication and tenant experience
The final pair of checks is especially important because they tie technical readiness to actual service delivery.
9. Fallback communications bootstrap. Verify that a backup communications path works end to end. That could be a cellular hotspot, a secondary PSTN number, or a pre-approved messaging channel. A backup method is not real until someone sends a message or makes a call and confirms that the duty contact receives it.
10. Tenant signal intake trial. Ask a tenant representative to submit a simple issue through the standard intake path, such as a help desk portal or dedicated email, and confirm that it creates a ticket, sends an acknowledgement, and lands with an assigned owner. This is one of the best service-quality checks in the episode because it verifies that tenants can report problems through the process they will actually use.
From a business perspective, these tests matter because the first few incidents after occupancy shape the tenant's perception of the entire support model. A building or technology environment can be technically sophisticated and still feel unreliable if communication breaks down at the first moment of need.
How to run the sprint in the real world
The episode does a good job of keeping the process practical. The recommendation is to batch by owner and location. One person handles power and metering. Another handles credentials and tenant intake. A third walks closets and checks spares. The ownership matrix only needs a few fields: the test, primary owner, backup owner, and evidence captured.
The timing is also realistic. Rather than trying to stretch checks over several days, schedule a single coordinated window right before move-in or just before the closeout meeting. Ten checks. Three people. One hour. If a test fails, log it, assign priority, fix it, and require a retest before handover.
That structure is useful because it turns acceptance from an abstract milestone into a repeatable operating habit. It also makes accountability visible. Everyone knows which checks they own and what proof is expected.
What the examples reveal
The anonymized examples at the end of the episode are especially strong because they prove the point without exaggeration. In one case, a credential test showed that revocations were not propagating to the door controller because a scheduled sync job had never been enabled. In another, a metering sanity check caught a mislabeled meter before incorrect billing could become a tenant issue. In a third, a temporary power feed was still carrying a server rack when the general contractor prepared to remove it. The demobilization check prevented a real outage.
These are not edge cases. They are precisely the kind of operational misses that show up in busy handovers and fragmented responsibility models. The fix is not more theory. The fix is a simple verification sprint with clear ownership.
Three actions to take now
If you manage tenant environments, close out technology projects, or support building operations, this episode suggests three immediate next steps. First, run the ten smoke tests before your next move-in or cutover. Second, capture at least two evidence artifacts for every pass or fail so there is a usable record. Third, assign one explicit operations and maintenance owner in the closeout packet so there is no ambiguity after handover.
That advice reflects the larger GDS Technology view of operational readiness: technology should not just be installed. It should be verifiable, supportable, and aligned to real-world business continuity. When teams treat closeout as the start of long-term ownership rather than the end of a project, move-ins get smoother, incident response gets faster, and tenant confidence rises.
If you want the printable checklist and ownership matrix referenced in the episode, listen to the full conversation and visit the Built, Wired & Secured show hub for the downloadable resource.