Lapse
NYC Open DataVarsity Plbg and Htg Inc
Duty officerVarsity Plbg and Htg IncLIVE · synced 2026-09-14 13:40 UTC

53 decisions are yours.

33 already past their date, the worst by 1,208 days late

The overnight pass did the reading. 235 items screened, 179 held without a word.

1,208 days late is the worst of them: type LBLVIO, violation V042523LBLVIO10409 at 4301 7 Avenue, Brooklyn. A response is drafted and waiting on you.

What is due, and when

3 cases of 53: carrying no class, at Brooklyn, most overdue first.show all 53

no clock on this one

no class

no date on record

271 Melrose Street, Brooklyn

violation · type C, violation V041725CSR30401MA · BIN 3071962

When is the response due for construction violation V041725CSR30401MA at 271 Melrose Street?

What DOB wrote on it

FAILURE TO MAINTAIN BUILDING EXTERIOR FACADE AND/OR APPURTANCES IN CODE COMPLIANT MANNER. AT TIME OF INSPECTION IT WAS OBSERVED AT EXPOSURE 1 AND 3 MISSING FACADE PANNELS. REMEDY: REPAIR AND/OR REPLACE

What the engine checked

  • passcategory activeDOB categorises this as 'V-DOB VIOLATION - ACTIVE'
  • passnot disposedDOB has recorded no disposition date
  • passissue date knownissued 2025-04-17
  • passoutstanding by text[claude-sonnet-4-5-20250929]No disposition comments and no disposition date. Category is V-DOB VIOLATION - ACTIVE. Nothing indicates this has been resolved. (confidence 0.95)
  • passcure path knownConstruction violation: Correct the condition and give proof of the correction to the unit that issued it, and pay any DOB civil penalty. There is no court appearance on a DOB violation, and there is no published number of days, so how fast this moves is set by the job rather than by a rule.
  • passcontractor is respondentthe city names the either on a Construction violation
now tracked to December 13, 2026

DOB publishes a cure path for this one and no deadline, so Lapse will not invent a date and this clock is yours to set. Once it is set, Lapse tracks it like any other deadline and goes quiet until it is close. Nothing is sent.

the published rule this deadline comes fromDOB record on a810-bisweb.nyc.govOpen Data 3h2n-5cm9violation:2790961:none:DECIDE:3f75160e46

no clock on this one

no class

no date on record

271 Melrose Street, Brooklyn

violation · type C, violation V102224CSR30402DO · BIN 3071962

When is the response due for construction violation V102224CSR30402DO at 271 Melrose Street?

What DOB wrote on it

FAILURE TO MAINTAIN BUILDING IN CODE COMPLIANT MANNER. AT TIME OF INSPECITON OBSERVED MISSIN GPANNEL AT EXPOSURE ONE AT PARAPET WALL CENTER OF BUILDING OBSERVED ONE COVERED BY PLYWOOD. AT EXPOSURE #3 OBSERVED MISSING PANNEL NEAR PARAPET WALL. REMEDY: REPAIR AND/OR REPLACE

What the engine checked

  • passcategory activeDOB categorises this as 'V-DOB VIOLATION - ACTIVE'
  • passnot disposedDOB has recorded no disposition date
  • passissue date knownissued 2024-10-22
  • passoutstanding by text[claude-sonnet-4-5-20250929]No disposition comments and no disposition date. Category is V-DOB VIOLATION - ACTIVE. Nothing indicates this has been resolved. (confidence 0.95)
  • passcure path knownConstruction violation: Correct the condition and give proof of the correction to the unit that issued it, and pay any DOB civil penalty. There is no court appearance on a DOB violation, and there is no published number of days, so how fast this moves is set by the job rather than by a rule.
  • passcontractor is respondentthe city names the either on a Construction violation

DOB publishes a cure path for this one and no deadline, so Lapse will not invent a date and this clock is yours to set. Once it is set, Lapse tracks it like any other deadline and goes quiet until it is close. Nothing is sent.

the published rule this deadline comes fromDOB record on a810-bisweb.nyc.govOpen Data 3h2n-5cm9violation:2783447:none:DECIDE:e29f7e8d09

no clock on this one

no class

no date on record

2052 Fulton Street, Brooklyn

violation · type C, violation V100924CFEU30501BS · BIN 3042157

When is the response due for construction violation V100924CFEU30501BS at 2052 Fulton Street?

What DOB wrote on it

FAILURE TO MAINTAIN.BLDG LEANING APPRX6" TO 8"@TOP,W/LEAN TO EXP4 THAT BEGIN ON 1ST STORY&CONTINUES TO TOP STORY.COSMETIC RPAIRS W/O PRMT OBSRVD SINCE 2023.RECEVNG WALL@EXP4(WEST) SIDE OF BLDG INTACT.1.FULLY VACATE BLDG UNTIL RPAIRS ARE CMPLTD UNDR PRMT,2.IMMED RTAIN NYSPE STRCTRL ENG TO EVAL ENT BLDG,3.FILE FOR RPAIRS

What the engine checked

  • passcategory activeDOB categorises this as 'V-DOB VIOLATION - ACTIVE'
  • passnot disposedDOB has recorded no disposition date
  • passissue date knownissued 2024-10-09
  • passoutstanding by text[claude-sonnet-4-5-20250929]No disposition comments and no disposition date. Category is V-DOB VIOLATION - ACTIVE. Nothing indicates this has been resolved. (confidence 0.95)
  • passcure path knownConstruction violation: Correct the condition and give proof of the correction to the unit that issued it, and pay any DOB civil penalty. There is no court appearance on a DOB violation, and there is no published number of days, so how fast this moves is set by the job rather than by a rule.
  • passcontractor is respondentthe city names the either on a Construction violation

DOB publishes a cure path for this one and no deadline, so Lapse will not invent a date and this clock is yours to set. Once it is set, Lapse tracks it like any other deadline and goes quiet until it is close. Nothing is sent.

the published rule this deadline comes fromDOB record on a810-bisweb.nyc.govOpen Data 3h2n-5cm9violation:2783719:none:DECIDE:3419825048

What ran while nobody was watching

all 23 passes on record
FinishedPassScreenedHeldOpenedDraftedAskedFiledVetoed
2026-09-16 11:04 UTC2 days agosingle case filing140 permits, 95 violations23517925151144
2026-09-15 11:04 UTC3 days agosingle case filing140 permits, 95 violations2351792517955
2026-09-14 14:12 UTC4 days agosingle case filing140 permits, 95 violations23517911000
2026-09-14 14:05 UTC4 days agosingle case filing140 permits, 95 violations23517911000

That pass classed 127 dated items across the whole portfolio:33 lapsed4 critical10 due80 clear

Configured cadence: EventBridge schedule lapse-daily, cron(0 11 * * ? *) UTC, reported ENABLED against function lapse-run. That is the EventBridge schedule the deploy script writes, read out of this deployment's configuration. What it has actually done is the table, not this line.

Already closed

Lapse deadline sheetDOB · NYC Open Data
Read from
lapse-cases, us-east-1
Partition
VARSITY PLBG AND HTG INC
Rows
58 cases, 23 run records
Read at
2026-09-18 12:01 UTC