Built around your agency

A shared mission.
Meaningful differences.

Agencies protect children and support families within distinct policies, responsibilities and communities. Those differences should shape the software from the beginning.

Beyond screen configuration

The difference can be in the decision.

Changing a field label is one kind of adaptation. Changing who may approve an action, which policy applies or how an exception is reviewed reaches further into the way a case is worked.

Chiron’s approach brings a common product foundation together with explicit agency adaptation. We start by understanding which practices the agency wants to standardize and which differences its responsibilities require.

What meaningful adaptation involves

Follow each difference through the work.

These illustrative questions show how agency differences can shape connected casework.

Agency variation and its design implications
Where agencies can differWhat the design must consider
Decision authorityWho can propose, review and approve an action? How do delegated authority and organizational boundaries affect the next step?
Policy and effective datesWhich rule applies to the action at hand? What happens to work already in progress when a new policy takes effect?
Exceptions and reviewWhat makes an exception valid, who considers it and how is the reason preserved for later review?
Local responsibilitiesHow does work pass between state, regional, county or partner teams? Which responsibilities remain with the originating team?
Connected systemsWhere does information originate, who maintains it and how are conflicting or delayed updates reconciled?

An illustrative policy change

What changes for the case already open?

Imagine an agency changes the approval required for a particular action. A form update alone does not settle what happens to an item awaiting review, a decision already recorded or a related task assigned to another team.

Discovery needs to establish the intended treatment of each situation. Design and verification then follow those answers through the workflow, with historical decisions and their context preserved appropriately.

This is why we treat policy adaptation as a connected design question. The agency’s authoritative interpretation and intended practice guide the implementation.

Fit with discipline

Consistency where it helps.
Variation where it matters.

Make intended differences explicit

Distinguish required variation from a workaround the agency wants to retire. Record the reason for the difference and the work it affects.

Keep the wider journey in view

Check the effects on access, review, reporting and connected services. An adaptation should be evaluated in the context of the child and family’s continuing casework.

Continue the conversation

Start with the work.
Keep the mission in view.

Talk with us Explore modernization with continuity