FForklift
Explore verified sandbox

For agency, district, and municipal operations leaders

Map where requests disappear before changing the case system.

A read-only assessment uses process interviews and aggregate volume data to document intake, routing, deadlines, and status. It does not access student, applicant, or case records.

Evidence before claims

What this page is—and is not—promising

Assessment goal: identify a bounded way to give requests an owner and visible status without making consequential decisions.

Resolver status

unsupported

No matching entry exists in the governed resolver catalog.

Data boundary

Regulated or consequential records; map read-only boundaries before building.

Economic buyer

Department COO, CIO, service director, or administrator

Why now

The conditions that make the workflow worth examining

These are discovery signals, not proof that Forklift has delivered the outcome for a customer.

Common triggers

  • Requests are spread across email and forms
  • Status inquiries consume service capacity
  • Published service deadlines are missed
  • Backlog age cannot be reconciled

Observable symptoms

  • Staff check several systems to answer a status question
  • Incomplete submissions are discovered late
  • Requests are duplicated across departments
  • Transfers become invisible

First artifact

Intake and Routing Operating Map

Target assessment timeline: three weeks, subject to scope

  • Every intake channel and its current destination
  • Completeness checks and avoidable restarts
  • Formal and informal routing paths
  • Deadline ownership and escalation gaps
  • Accessibility, records, and consequential-decision boundaries

Governed progression

Prove the control loop before increasing authority

Every engagement progresses through explicit gates. Natural language expresses intent; it never grants production authority.

1. Diagnose

Confirm the repeated problem, owner, systems, data, decision rights, baseline, and economics.

2. Observe

Use interviews, fixtures, or controlled exports before requesting a read-only connector.

3. Control exceptions

Give bounded exceptions owners, deadlines, approvals, and reconciliation evidence.

4. Prove

Measure the agreed result against the approved baseline and preserve provenance.

5. Automate selectively

Permit only cataloged, tested, reversible actions under the exact approved plan.

6. Operate or stop

Monitor cost, health, incidents, recovery, upgrades, and exit—or record why the hypothesis failed.

Proof metrics

Agree on the baseline before claiming improvement

A metric becomes evidence only when its definition, source, window, owner, and comparison baseline are approved.

Time to first action
Backlog age
Incomplete submissions
Transfers between teams
Missed service deadlines
Status inquiries per case

Hard boundary

What remains outside this engagement

These exclusions are commitments. Changing one requires a new classification, plan, review, and approval—not an expanded prompt.

  • Eligibility, benefits, admissions, discipline, or enforcement decisions
  • Replacing the authoritative case system
  • Reading student, applicant, or case records during assessment
  • Reducing accessibility of any public intake channel

Commercial entry

Assessment first

The assessment scope, deliverables, fee, and credit toward any later build are agreed in writing before work starts.

No unmeasured agent price is published.

The first written proposal identifies the work, evidence, operating obligation, and commercial terms before authorization.

Request an assessment

Questions

What buyers usually need clarified first

Will AI make eligibility decisions?

No. Consequential determinations remain with authorized officials under published policy.

Why does this start with an assessment?

Regulated records, accessibility, and public-records duties must be mapped before proposing a workflow.

What does the assessment cost?

The scope, fee, and any credit toward a later build are agreed in writing before assessment begins.

Adjacent outcomes

Scope the next problem without inventing a page

Unpublished outcomes route to Open Flow. They do not produce a broken page or an implied implementation claim.