Inspection Tracker Skill

Permit Object

{
  "id": "PERMIT-001",
  "type": "Building Permit",
  "number": "BP-2025-4521",
  "date_applied": "2025-02-01",
  "date_issued": "2025-02-20",
  "expiration": "2026-02-20",
  "jurisdiction": "City Building Department",
  "status": "active",
  "conditions": ["Final inspection before occupancy", "Weekly inspection during excavation"],
  "inspections_required": ["INSP-001", "INSP-003"],
  "notes": ""
}

Fields:

• id: Unique identifier (PERMIT-001, PERMIT-002, etc.)
• type: Permit classification
• number: Official permit number
• date_applied: Application submission date
• date_issued: Date permit was issued; null if pending
• expiration: Expiration date for renewal tracking
• jurisdiction: Issuing authority
• status: applied, issued, active, expired, renewed
• conditions: Array of permit conditions or special requirements
• inspections_required: Array of inspection IDs required per permit
• notes: Additional remarks or tracking notes

Standard Inspection Types

Healthcare-Specific Inspections

PEMB-Specific Special Inspections

Pre-Engineered Metal Building (PEMB) requires specialized inspections per AWS D1.1 and manufacturer specs:

Special Inspection IDs: INSP-PEMB-001, INSP-PEMB-002, etc.

Auto-Linking Intelligence

The inspection-tracker skill automatically links inspections to project intelligence:

Schedule Activity Linking

Query project intelligence for schedule activities matching inspection date and type:

• "Concrete Pour Day" → auto-link to concrete pre-placement inspection
• "Steel Erection Week 3" → auto-link to structural steel inspection
• "Electrical Rough-In Phase" → auto-link to electrical inspection

Hold Point Linking

Cross-reference spec hold points from project spec database:

• Inspection type matched to standard hold point (HP-02, HP-05, etc.)
• Override if project-specific hold point defined
• Display linked hold point ID to superintendent

Specification Section Linking

Auto-populate CSI specification section reference:

• Foundation → 03 11 00
• Concrete → 03 30 00
• Structural Steel → 05 12 00
• Electrical → 26 00 00

Hold Point Auto-Population

Read specs-quality.json → hold_points[] → match inspection type to hold point by work_type:

• Pull the hold point's inspection_name, trigger condition, inspector, and spec_reference
• Auto-populate the inspection's linked_hold_point and linked_spec_section fields
• Example: Scheduling "Concrete Pre-placement" → match hold_points where work_type contains "Concrete" → auto-link HP-02 with trigger "Before concrete placement" and spec reference

Weather Threshold Check

Before scheduling outdoor inspections:

• Read specs-quality.json → weather_thresholds[] → match by the inspection's work type
• Cross-check forecasted weather against min_temp, max_temp, max_wind, and moisture_ok
• Flag if weather conditions may prevent the inspection or the underlying work (e.g., concrete pour inspection + temp < 40°F cold weather threshold)
• Include mitigation measures from the spec when flagging

Spec Section Deep-Link

When an inspection type is identified:

• Read specs-quality.json → spec_sections[] → find the matching CSI section
• Pull specific testing requirements (frequency, type, agency), acceptance criteria from key_req, and required documentation
• Auto-populate inspection notes with testing protocol and acceptance criteria
• Example: Compaction inspection → pull "95% modified Proctor, testing every 500 CY" from spec section

Schedule Activity Linking (Enhanced)

• Read schedule.json → critical_path[] and milestones[] → match inspection date/type to schedule activities
• Auto-link inspection to schedule activity and flag if the activity is on the critical path
• If critical path: add note "Critical path activity — inspection delay will impact project completion"

Drawing Reference

When inspection location is identified:

• Read plans-spatial.json → sheet_cross_references.drawing_index[] → find relevant structural/MEP drawings for the inspection location and discipline
• Include referenced sheet numbers in inspection record for field use
• Example: Foundation inspection at Grid C-3 → reference sheets S2.1, S5.1

Re-Inspection Workflow

When inspection result = fail:

1. Create Re-Inspection Entry:

   • Auto-generate new INSP ID (sequential)
   • Set type as "{Original Type} (Re-inspection)"
   • Set related_to field to original inspection ID
   • Suggest date 48 hours after deficiency notification

2. Track Deficiencies:

   • Collect detailed deficiency descriptions
   • Log which contractor responsible for correction
   • Reference section of spec violated
   • Attach photos of deficiency

3. Notification:

   • Alert responsible trade contractor
   • Flag in morning brief
   • Include in daily report until re-inspection passed

4. Closure:

   • Log re-inspection result
   • Document corrective action taken
   • Release hold if pass
   • Create additional re-inspection if still fail

Permit Tracking & Expiration Alerts

Auto-Alert Thresholds:

• 30 days to expiration: Yellow flag in status report; suggest renewal inquiry
• 7 days to expiration: Red flag; escalate to project manager
• Expired: Red flag; mark status as expired; notify responsible party

Renewal Workflow:

• Track date application submitted for renewal
• Update status to renewed upon reissuance
• Maintain continuous permit coverage throughout project

Integration Points

Morning Brief (/morning-brief)

Display under "Inspections & Permits" section:

• Upcoming inspections (next 24 hours) — show type, time, location, inspector
• Overdue inspections (no result logged) — Red flag with days overdue
• Permits expiring within 30 days — Yellow alert with days remaining

Look-Ahead Schedule (/look-ahead)

Include scheduled inspections in weekly look-ahead:

• Inspections integrated by date into weekly view
• Show impact on critical path if hold point inspection
• Cross-reference with material delivery/contractor schedule
• Highlight PEMB special inspections with bold/asterisk

Daily Report (/daily-report)

Section: "Inspections Today"

• Scheduled inspections for the day (time, type, location, inspector)
• Completed inspections from previous day (result, notes summary)
• Pending re-inspections affecting schedule
• Permit status reminder (expiring within 14 days)

Error Handling & Validation

• Duplicate Re-inspection: Warn if re-inspection already exists for same deficiency
• Invalid Inspector: Log "External Inspector" if not in approved list; alert PM
• Missing Linked Activity: Alert if schedule activity cannot be found; allow manual entry
• Permit Conflict: Warn if inspection scheduled outside permit scope
• Date Validation: Reject inspection scheduled before permit issued
• Status Consistency: Prevent result logging if status ≠ scheduled

Triggers & Voice Commands

• "Schedule an inspection"
• "Log inspection INSP-042"
• "Show inspection status"
• "What inspections are overdue?"
• "Upcoming inspections?"
• "Schedule a rebar inspection for Monday"
• "Inspection failed — need re-inspection"
• "Track permits"
• "When does the building permit expire?"
• "Special inspection — anchor bolts"
• "Healthcare inspection — state health dept"

Safety Incident Cross-Reference

For safety incidents discovered during inspections, route to the safety-management skill for incident documentation, root cause analysis (5-Why, Fishbone), OSHA recordkeeping (300/300A/301), and corrective action tracking. Write incident data to safety-log.json, not inspection-log.json.

When an inspection failure reveals a safety concern:

1. Log the inspection result normally in inspection-log.json (result: "fail", deficiencies noted)
2. Create a separate safety incident via the safety-management skill → writes to safety-log.json
3. Cross-reference the inspection ID in the safety incident record
4. The safety-management skill handles TRIR calculation, OSHA compliance, and corrective action lifecycle

Extended reference: Detailed examples, templates, scoring rubrics, and best practices are in references/skill-detail.md.