Operational views
Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Humanitarian & nonprofit
Coordinate consented case intake, approved eligibility review, assistance decisions, partner referrals, appeals and closure evidence.
12 workspace menus · 5 role profiles · Connected records
Designed for humanitarian programme managers and authorised caseworkers

Operational workspace and record review. Select a screen to inspect it in full.


Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Coordinate consented case intake, approved eligibility review, assistance decisions, partner referrals, appeals and closure evidence. Assistance cases can involve several partners while the beneficiary's needs, consent and outstanding actions change. The system retains an accountable case record and a controlled route for eligibility exceptions or appeals, with restricted access to sensitive beneficiary information.
From intake to authorised completion, with evidence at each decision.
Receive a request and establish consented case information.
Assess needs against approved assistance criteria.
Approve support referrals and coordinate case actions.
Review delivered assistance, appeals and case closure.
Permissions are configured and tested for the agreed responsibilities.
Interface scope, data mapping and testing are agreed for each engagement.
Provide caseworkers with permitted field intake and action records. Offline and sensitive-data handling require separate validation.
Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.
Prepare draft case summaries for authorised staff using agreed privacy controls. Eligibility and assistance decisions remain human approved.
AI extensions are scoped around the required data, business outcome and review controls.
Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.
Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.
Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.
An example operating scenario
A case is assessed against approved assistance criteria. An eligibility exception is reviewed by the responsible officer, approved support is referred to a partner and delivered assistance is recorded. The workflow includes an appeal and an accountable closure decision.
Roles, approval authority, business rules, records and reporting are configured around your operating model. Scope definition connects the required business outcome to workflows, interfaces and acceptance criteria.
Operators, reviewers and authorised decision makers have defined responsibilities. Approval limits, exception handling and access permissions are agreed with your business owners and tested against the selected workflows.
Interface requirements cover your existing business systems, data ownership, mapping and authentication. Connection design and testing form part of the agreed implementation scope.
Start with a relevant business transaction, then review its approvals, an exception, role permissions and final records. Discuss the integrations, reporting and operating requirements that matter to your organisation.