Institutional Systems/Migration & Citizenship
A case is the record it leaves behind.
Migration and citizenship casework is statutory, document-heavy and slow to resolve. A single case can outlast the officials who touch it — so the system’s real job is not to move an application along a queue, but to hold one accountable record whole, from intake to a status the applicant and the state will depend on for years.
Why it demands control
Not a form. A case that has to answer for itself.
A migration or citizenship decision can be revisited, appealed or relied upon long after it is taken. When it is, the question is never only “what was decided” — it is who decided, on what evidence, under whose authority, and whether the record still proves it.
That is why these environments cannot be a queue of forms over a database. They have to keep identity, documents, requests, decisions and status connected as one history that stays accountable across years, staff and changes of law.
The case record
A case does not move forward. It accumulates.
Each stage adds an attributed entry to a single record and takes nothing away. Follow one case down the thread: every step leaves what it produced behind it, under the authority that carried it, so the whole history stays readable from the outcome all the way back to intake.
Intake & registration
An application becomes a case. The identity it rests on and the documents it depends on are captured and attached from the first moment.
Left on the recordCase openedIdentity evidenceSupporting documents
- Controlled intake turns an application into a case record that carries its own history.
- Identity evidence and supporting documents are captured with the case and never separated from it.
- Configurable categories decide, from the start, which requirements a case has to satisfy.
Case record & classification
The case is built around a verified identity and classified against the categories, statuses and requirements that govern it.
Left on the recordClassificationRequirementsStatus
- An identity-aware case record keeps every later action tied to the same person.
- Configurable categories, statuses and requirements are set to the statute, not hard-coded into the software.
- What a case still needs is known and tracked, so its exact position is readable at any moment.
Authorized review
An authorized officer examines the case against the rules. Work is allocated by role, and each step is recorded under whoever carried it.
Left on the recordReviewVerificationOfficer of record
- Role-aware allocation directs each case to the officer authorized to handle it.
- Review and verification are recorded against the person and authority that performed them.
- Nothing advances without an accountable actor behind it.
Requests & responses
Where information is missing, a request goes to the authorized party and the response returns to the case. The whole exchange stays in the history.
Left on the recordRequest issuedResponse receivedCorrespondence
- Requests for further information are issued, tracked and given a due date.
- Responses are captured back into the case, next to the request that prompted them.
- The reason for a delay or a condition stays on the record, not in someone’s inbox.
Decision & determination
A controlled decision is made and set down with the reasoning the law requires it to show. Approvals follow the institution’s own authority structure.
Left on the recordDeterminationReasoningApproval
- Decisions are made by authorized people — never by the system on its own.
- The determination is recorded together with the reasoning behind it.
- Approvals follow the authority structure the institution already works to, and the basis for the outcome stays reconstructable.
Status & documents
The outcome establishes a status, and the institutional documents that express it are generated from the record and issued.
Left on the recordStatus setDocuments issued
- The determination becomes a status the applicant and other authorities will rely on.
- The documents that express it are generated from the case, not re-keyed beside it.
- What was issued, to whom and when is itself recorded, so it is never in doubt later.
Coordination
A determination rarely stays with one office. The authorities that depend on it are kept in step — each within the boundary it is allowed.
Left on the recordAuthorities notifiedShared status
- The responsible units and authorities an outcome affects are coordinated around one status.
- Information crosses a boundary only where the law permits, and every crossing is recorded.
- Each authority works from the same controlled history, to the extent it is permitted to see it.
History & continuity
The complete, attributable history of the case remains. Years later, the outcome can be traced back through every step that produced it.
Left on the recordComplete historyTraceable outcome
- Every action, request, decision and document is held as one attributable history.
- The outcome can be traced back through the lifecycle that produced it.
- The case stays complete and accountable long after it closes — and long after responsible personnel have changed roles.
Eight stages, one continuous record — and an outcome that can always be traced back to the evidence and the authority that produced it.
What holds it together
One accountable history, not scattered fragments.
One identity, one case
Every action, document and decision hangs off the same identity-aware record, so a case is never fragments spread across separate systems.
The record is the case
The documents and the record of decision are the substance of the case. They stay with it, not in a separate store that can drift out of step.
Attributable by default
Every entry carries who did it, under what authority and when. Accountability is a property of the system, not a policy written down beside it.
Controlled access
Authorized parties see and act on the same history, each within the boundary its role allows — and every access is part of the record.
Built to last, and to connect
A system a case can grow old inside.
The same operational discipline that composes an institution’s internal systems — see Operational Infrastructure.
Under institutional control
Runs on-premises or in private infrastructure the institution controls; case data is never required to leave it.
Connected to what already runs
Integrates with the authorized systems an institution already operates, so an outcome reaches the registries and services that depend on it.
Built to be maintained
Engineered for maintainability and extensibility, so a change in statute becomes a configuration or an extension — not a rebuild.
Responsible for the long term
CREA-KO carries the analysis, development, implementation, maintenance and modernization across the years a case system actually lives.
Discuss long-running public casework.
The conversation starts from your statutory process, your volume, and the record you need to be able to stand behind years from now.