Skip to content
OGETAR Branch Intelligence
Help Sign in

Branch intelligence · Kenya

See every branch. Act with evidence.

One controlled view of branch performance, operational exceptions, owners, evidence and approvals, without replacing the bank’s systems of record.

Sign in to OGETAR See how it works
Bank to branch scope hierarchy A four level tree from the bank, to two regions, to four clusters, to eight branches, with one authorised path highlighted. BANK REGION CLUSTER BRANCH
Scope resolves from the bank down to a single branch. A user sees only the nodes their role and assignment authorise.
Branch scoped accessBank, region, cluster and branch assignment
Maker and checker approvalIndependent review before material closure
Complete audit historyAttributable changes, decisions and exports

01 / Operating model

From signal to verified closure.

Every item follows the same path. Nothing closes because a dashboard says so. It closes because a named person produced evidence and an independent reviewer accepted it.

  1. 01

    Signal

    An exception, finding or measure arrives from an approved bank source of record.

  2. 02

    Context

    It lands inside branch, cluster and region scope, carrying its definition and data freshness.

  3. 03

    Ownership

    A named accountable owner and a due date are attached before work begins.

  4. 04

    Evidence

    Supporting files are stored privately, integrity checked and attributed to the uploader.

  5. 05

    Closure

    A second reviewer approves. The system enforces it, convention does not.

02 / Pillars

Five disciplines,
one control spine.

Two bank officers reviewing a branch report together in a banking hall.
G 01 / Governance

Decisions with a clear authority trail

Apply role, branch scope and independent approval at the point where operational decisions are actually made.

  • Scoped access
  • Maker and checker
  • Attributable decisions
Operating principle Accountable by default

03 / Workspaces

The work your teams
already own, connected.

Each register shares the same branch context, accountable actions, evidence controls and decision history.

Operational workspaces available in OGETAR
# Workspace What it holds Primary owner
01 Branch 360 Source backed branch health and prioritised intervention Branch and regional management
02 Controls and RCSA Control definitions, effectiveness assessments and challenge Risk and control
03 Audit findings Root cause, remediation actions and validated closure Internal audit
04 CDD and KYC Exception queues, outreach, ageing and remediation Compliance
05 Revenue assurance Leakage identification, recovery validation and impact Finance
06 Process and customer operations REA initiatives, service requests, training and campaigns Operations

04 / Governance

Control is part of the workflow, not a footer note.

Access and accountability are evaluated when people view, change, approve, export or close operational information.

Privacy and deployment notice

01

Scoped access

Bank, region, cluster and branch assignment is applied on every read and every write.

02

Maker and checker

Material closure requires a reviewer who is not the person requesting it.

03

Private evidence

Files sit outside the public root with SHA-256 integrity checks and controlled downloads.

04

Append only history

Business records are corrected, never destroyed. Every decision keeps its author and time.

05 / Access

Authorised bank identity only.

Sign in to open the workspace available to your role and branch scope.

Sign in to OGETAR Contact the service desk
01
Sign in with the bank identity that has already been approved for you.
02
Your role and branch assignment are resolved at sign in and applied to every view.
03
Access problems go to the bank service desk, never to a shared password.