← Back to ProjectsFeatured Case Study // Recorded Outcomes
Automation

D.C. Work Order Automation Platform

Engineered the Python platform that runs work orders for 900+ D.C. public facilities, with approval and backup on every change.

18 / day

Status changes vs target 12

Average per active day, with a team-high of 22, on a 1,400+ work order portfolio.

~870

Duplicate records found

Found by auditing Salesforce data with Python, the REST API and CLI, closing a major reporting gap.

0

Writes without approval

Every change runs a dry run, waits for approval, takes a backup, writes, then reads the record back.

Operating Context

Project Brief

A manual, high-volume government operation became an engineered system: a 5,300-line Python platform that moves 1,000 to 3,000 work orders a month from intake to an audit-ready close, with a person approving every change to live records.

Role
Program Analyst (IT contractor) and platform engineer
Scope
Work order intake, triage, vendor and cost handling, change control, verification and reporting on the Salesforce REST API
Timeframe
Jan 2025 to present, in daily production
D.C. Work Order Automation Platform
01 // SITUATION & CHALLENGE

The Operational Bottleneck

D.C.'s Department of General Services runs repair work orders for 900+ public facilities (schools, parks, fire, police) through Salesforce. A 3-person team handled 1,000 to 3,000 work orders a month by hand: intake, assignment, vendor emails, costs, field verification and reporting.

02 // ACTION & ARCHITECTURE

Engineering Strategy & Solution

Engineered a 5,300-line Python platform (58 tools, 8 modules) on the Salesforce REST API that runs the work order from intake to an audit-ready close. Every write to live records goes through a dry run, approval, backup and read-back, and AI-drafted vendor and stakeholder messages wait for human approval before anything goes out.

03 // VERIFIED RESULT

Delivered Operational Impact

Work order handling went from hours to minutes. 18 status changes per active day against a target of 12 (team-high 22), about 870 duplicate records found and cleaned, and 0 writes to live government records without approval.

Architecture

System Flow

  1. 01

    Intake & triage

    Requests become tracked tickets, emergencies first: schools, parks, fire and police.

  2. 02

    Change control

    Dry run, approval, backup, write and read-back on every update to a live record.

  3. 03

    Vendors & data quality

    Vendor emails, estimates and purchase-order reconciliation, plus duplicate and missing-cost detection.

  4. 04

    Verify & report

    170+ field inspector site checks, 50+ reporting workbooks and a daily team briefing.

Delivery Conditions

Constraints

  • Live government records feed funding and compliance decisions, so a wrong write is not an option.
  • A 3-person team covers 900+ facilities, so the system had to remove work, not add another dashboard.
  • Every tool had to match how the team already works and be documented before it shipped.

Judgment

Engineering Decisions

01

Put a human on every write

Automation drafts and prepares; a person approves. The team gets speed without risking the integrity of government records.

02

Build small tools, not one big app

58 focused tools across 8 modules, each shipped after a requirements review with the team lead and a built-in self-test.

03

Use AI only where a person reviews it

AI drafts vendor, building manager and stakeholder messages; nothing goes out until someone approves it.

Supporting System Visuals

More on IG →
D.C. Work Order Automation Platform proof asset 1
D.C. Work Order Automation Platform proof asset 2
D.C. Work Order Automation Platform proof asset 3

Technologies & Protocols Used

PythonSalesforce REST APICLIExcel ReportingAI with Human ApprovalData Quality

Similar Operational Problem?

Turn the bottleneck into a working system.

Discuss the System