CASE COMPLETION • EVIDENCE & ARCHIVE

A clear closure boundary after sponsorship transfer.

Verify how cases transition from payment confirmation, through external legal processes, to final ID Card upload audit checks and read-only archival.

Closure Sandbox

Archival & Closure console

Simulate uploading the Omani national ID Card, auditing verification requirements, and committing the case record to read-only archives.

Operations Closure Lab

Case CS-2048: Archival Workspace

Archive Ready
Legal Sponsorship Boundary:

The visa and sponsorship transfer processes occur entirely outside the platform's boundaries (offline / government portals). The platform does not submit visa requests. It remains in an **"Awaiting ID Card"** queue until the final Omani ID Card is uploaded as evidence of transfer completion.

Closure status pipelineActive Stage: pending
Paid
ID Uploaded
Case Closed & Archived
Stage 1: Evidence Capture
Upload Resulting Omani ID Card

Upload the newly issued Omani ID Card to close out case **CS-2048**. (Actor: **agency**)

Stage 2 — Verification & Archive
Awaiting evidence document upload to activate audit controls...
Out-of-Scope Post-Transfer:

Following case closure, the platform enforces strict boundaries. No ongoing helper salary payouts, worker timesheets, attendance tracking, visa renewal alerts, or legal dispute resolution portals are supported.

Operations Boundaries

Defining the Legal Sponsorship Transfer Boundary

All visa application filings, Omani labor contract executions, residency clearances, and sponsorship approvals happen entirely outside of Digital Elliptical's scope. The system does not integrate with municipal visa API systems. It strictly operates as a booking directory and case mediator, waiting for proof of completion.

Transfer TaskSystem Role / Scope
Visa Application:Strictly Excluded
Contract Sign:Strictly Excluded
Transfer ID Upload:Required Proof of Close
Evidence Collection

Two Allowed Upload Actors: Agency or Admin Console

Following sponsorship transfer, the final ID Card scan must be submitted. The platform restricts upload access to ensure documentation is logged correctly:

Roster Creator

Agency User Upload

Agencies upload scans inside their workspace. Triggers admin verification alerts.

Operator Role

Admin Console Upload

Operators upload documents directly if received offline or via municipal registries.

Restricted

Omitted Customer Upload

To preserve helper privacy, customers cannot upload ID documents directly to case directories.

Archive Metadata FieldsCompliance
Document ID: Masked ID (ending ••73)
Verified profiles: Profile HS-1042
Responsible Admin: Operator OP-04
Admin Verification

Operator Audit Verification & Case Archiving

Admin operators verify that the ID Card upload is legible, matches the selected profile code, and represents a successful transfer. Once validated, the operator clicks **"Approve ID & Close Case"**. The registry sets the helper status to Closed, archives the case details as read-only, and locks out any edits to ensure audit consistency.

Post-Transfer Accountability & Scope Warnings

Archived files are kept for regulatory audit trails. Following closure, the platform enforces strict boundaries: it does not manage monthly helper salaries, visa renewals, worker leaves, or labor disputes. All employment actions belong offline under customer and agency responsibilities.

Have a complex workflow that needs a custom platform?

We can map your operations, design the software architecture, and build the dashboards, apps, and automation layers needed to run it.