Operational views
Review work, evidence, exceptions and authorised decisions within a defined operating scope.
Education & research
Connect applications, qualification evidence, authorised selection, offer conditions, acceptance and enrolment readiness.
14 workspace menus · 5 role profiles · Connected records
Designed for institutional admissions directors

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.
Connect applications, qualification evidence, authorised selection, offer conditions, acceptance and enrolment readiness. An admissions team needs to see which application is waiting for evidence, selection or fulfilment of an offer condition. The system links those stages and preserves the accountable decision, giving staff a common view of progress from application to confirmed enrolment readiness.
From intake to authorised completion, with evidence at each decision.
Collect application and qualification evidence.
Route authorised eligibility and selection review.
Issue approved offer and conditions.
Verify acceptance and enrolment readiness.
Permissions are configured and tested for the agreed responsibilities.
Interface scope, data mapping and testing are agreed for each engagement.
Allow applicants to view conditions and submit permitted evidence, with responsive staff review screens.
Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.
Organise submitted evidence and draft administrative responses for staff review. Selection decisions remain authorised human actions.
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
An applicant supplies an incomplete qualification record. Admissions requests the missing evidence, an authorised selection reviewer approves the decision and a conditional offer is issued. The applicant satisfies the condition before the enrolment handover is completed.
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.