Delays

A Delay is any event that pushes a lot’s schedule out — a rainout, a backordered material, a permit holdup, a buyer change order. SMART tracks delays in a small batch system so multiple lots can be moved together.

At a glance

• Delays are applied in batches (one DelayBatch row, many DelayBatchSeq rows for affected lots).
• A delay shifts an Activity (or activities) by N days; every dependent activity recomputes; Lot.SchComplete updates.
• Trades can submit delay-related requests through the Trade Portal; builders file builder delay requests in the Builder Portal (email workflow).
• Notifications fire to homeowners (HOP), trades (Trade Portal), and builders.

How a delay works

1Open a Delay Batch (DelayBatch row) with a reason and date.

2Add lots to the batch via DelayBatchSeq. Optionally an Area-wide delay via AreaDelayMessage.

3Choose which Activity(ies) shift, by how many days.

4Recalculate — every dependent activity moves forward; Lot.SchComplete updates.

5Notifications fire to home owners (via the Home Owner Portal), trades (via the Trade Portal), and builders.

Tables

DelayBatch is the header; DelayBatchSeq is the per-lot fan-out. DelayType is the reason taxonomy (Weather, Supply Chain, Permit, Buyer, Trade).

Full delay table reference

Table	Purpose
DelayBatch	Header per delay batch.
DelayBatchSeq	Sequence of lots in the batch.
DelayType	The reason taxonomy (Weather, Supply Chain, Permit, Buyer, Trade, etc.).
AreaDelayMessage	Whole‑area broadcast delays.
vwDelayBatch, vwDelayBatchSeq, vwDelayBatchDisplay	Reporting views.
vwLookupLotToDelay	Lots eligible to delay.

Portal delay workflows

Trade Portal (delay-details.aspx) — trades submit delay information from the field (see Trade Portal docs for what gets written to the database).

Builder Portal (DelayRequest.aspx) — superintendents submit a new delay request for their default project: pick lot/activity/trade/variance/delay type, then the page emails the area manager (via spGetBuilderPortalDelayRequestInfo_v2). It does not approve Trade Portal submissions or insert DelayBatch rows directly in the page code.

Formal Delay Batch creation (DelayBatch / DelayBatchSeq) still happens in SMART Production (Delay Builder) or through CSR scripts after the request is processed.

Notifications and CSR scripts

Scheduled email jobs and CSR SQL helpers used most often (hosted outside the interactive apps — schedules live on the SQL/job server).

Scheduled notifications and CSR delay scripts

• Jobs that email when a lot’s projected completion (SchComplete) changes.
• Jobs that bulk-email trades when a delay batch is applied.
• CSR helpers: DelayHelper.sql, DelayHelper-Houston.sql, DelayHelper-MoveLotsActivityBasedOnNewDates.sql, DelayMoveActivity.sql, BufferDelays.sql, Buffer Delay & Changing Critical Activity.sql.

Where in the apps

App	Where
SMART	Production → Delay Builder
Builder Portal	DelayRequest.aspx (submit builder delay request → email to area manager)
Trade Portal	delay-details.aspx
Home Owner Portal	Schedule.aspx reflects the new dates