01 · PortalEvery submission is structured from the start.
The portal is the interface for people outside your organization: applicants, requesters, partners and beneficiaries. It does not merely collect a file; it builds a case with stages, required fields, expected documents, save-and-resume, and passwordless or SSO authentication.
What it changes- An incomplete case cannot be submitted
- Requesters can see their case status without calling
- Reference data pre-fills information that already exists
Example ruleIF a required document is missing THEN submission is blocked and the expected-document list is shown
Your rules determine the route—not an agent’s memory.
The workflow defines stages, sequential or parallel approvals, escalations and delegations. Every transition has a condition. When a rule changes, active cases follow it from their current state.
What it changes- Exceptions automatically reach the right level
- Absence does not block a workflow because delegation is built in
- A case’s route remains explainable after the fact
Example ruleIF amount > threshold THEN Management approval is required before decision
Work stays visible, not merely stored.
Teams work in list and Kanban views by status, with search, filters, pinning and comments. A status change can require a written reason. Changes made by the requester appear immediately for the processing team.
What it changes- Teams can see where a case is blocked without sending an email
- Every decision records its author and reason
- Exports reflect the real status, not a re-entry
Example ruleIF status changes THEN reason, author and timestamp are recorded
Scores are calculated. Differences become visible.
Weighted multi-criteria grids support several evaluators and levels. Scores are consolidated automatically and evaluator gaps are detected against your thresholds. Reports are pre-filled from the results.
What it changes- No consolidation spreadsheet to maintain
- A disagreement triggers a rule, not a meeting
- The final report can be defended line by line
Example ruleIF evaluator difference > threshold THEN a third evaluation is requested
Every outcome becomes a verifiable document.
Attestations, certificates, contracts and reports are generated from validated data, with an identifier, QR code and public verification page. Every reissue is logged with its reason.
What it changes- A third party can verify authenticity without calling you
- The document remains attached to the case history
- Templates can evolve without changing past cases
Example ruleIF status = Decided THEN certificate generation is allowed, otherwise denied
What is recorded stays recorded.
Every action, change and approval is stored with its author and timestamp in an immutable audit trail. Roles define who can view, edit, approve or administer. Partner entities manage their own access without central administration.
What it changes- Audits are prepared by reading, not reconstructing
- An entity sees only its own cases
- Your data remains yours: exports, API and hosting choice
Example ruleIF role = Regional entity THEN visibility is limited to that region’s cases
