Configure the organization
Set up employer rules and the workflows that applied to its workforce.
Historical result · rapid compliance delivery
A vaccine-and-test management system delivered in under a month.
During the COVID-19 pandemic, a pending federal vaccination mandate changed employer requirements quickly. The original SafePass case reports that a small team designed, built, tested, and deployed the expanded compliance system in less than a month.
Business consequence
A policy shift created a new operating system problem almost overnight.
SafePass began as a mobile application for storing encrypted vaccination documentation. When a federal mandate for companies with more than 100 employees was pending, employers faced a wider operating burden: vaccination status, weekly testing, exemption requests, test proctoring, documentation, and changing rules.
The mandate was later blocked by the Supreme Court. This case records the delivery response during that historical period; it does not claim that SafePass is currently available or that it provided medical efficacy.
Reported delivery result
Designed, built, tested, and deployed in less than a month.
Under one monthwas the timeline reported by the original case.
Connected workflowslinked employer setup, employee records, and proctored testing.
Historical pivotresponded to requirements that changed before the mandate took effect.
This is a historical, self-reported Intelligence Factory case. Exact dates, elapsed days, customer identities, deployment scale, and compliance certifications are not published here.
Operating explanation
Coordinate employer rules, employee evidence, and supervised tests.
The reported system included a corporate portal for onboarding organizations and configuring compliance rules, plus an employee portal for vaccination-card uploads, testing status, and history.
Test workflows included live video, waiting rooms, identity validation, and medical-document handling. The operating model also accounted for exemption approvals, location-specific rules, and audit records for tests, results, and logins.
Collect employee evidence
Record vaccination documentation, testing status, exemptions, and history.
Supervise tests
Coordinate waiting rooms, live video, identity checks, results, and supporting documentation.
Adapt the rules
Update location and testing logic as the historical requirements changed.
Technical reason to believe
Model the rules so a small team can change the system coherently.
The original case describes a model-driven delivery pipeline built around Buffaly and an ontology engine. High-level specifications drove generation of stored procedures, type-safe repositories, business logic, data-access layers, and interface scaffolds.
Application code used stored procedures as its database boundary. That provided a consistent interface between data and application layers and supported audit-oriented change records as rules evolved.
When testing or workflow rules changed, the case reports that the team updated the ontology and regenerated affected procedures, APIs, and logic trees. This is evidence about the historical delivery method—not a claim of current SafePass availability, certified compliance, or medical effectiveness.
Case authorMatt Furnari, CTO, Intelligence Factory
Talk to Us
What operating change do you need to respond to faster?
Start with the rule change, the workflows it affects, and the evidence the organization must retain.
Talk to Us