Skip to content
Noma Serve

Platform

Case managementOne clear case journeyServices & referralsFrom need to delivered supportEvents & outreachProgrammes beyond the case fileReportingEvidence without unnecessary exposureAccess by roleNeed-to-know by designSecuritySensitive data deserves deliberate controls

Experience

Mobile & tabletDesigned for the device at handBrowser-basedNo desktop install to maintain

Solutions

Child protectionChild protection information managementGBV responseGBV information managementConfigurationStrong standards, local fitImplementationA practical path to adoption
PricingAbout Noma
Sign inRegister
Home
Strong standards, local fit

Configure the programme deeply without rebuilding the product.

Create forms, sections, fields, reusable lists, languages, conditional logic and workflows around your programme. Noma keeps configuration governed and understandable for smaller organisations.

Request a walkthrough Open Noma

Flexible enough for your SOP. Stable enough for shared practice.

secure.noma.app
Search
ENAM

CONFIGURATION

Programme map

Draft v3
Case record6 sections · 34 fields
AssessmentConditional questions
Access rules5 roles configured
Indicators12 aggregate measures
One governed configuration, connected end to end

What this changes

Strong structure, without the heavy interface.

Each capability is designed to make daily work more understandable while preserving the controls and evidence behind it.

01

Visual form builder

Organise forms and sections without hard-coding every programme change.

02

Workflow stages

Define the lifecycle, approvals and process tasks that guide each record.

03

Permissions in context

Set read and write access at section and field level as forms are configured.

04

Multilingual content

Manage labels, guidance and option lists for the languages teams use.

05

Conditional logic

Show relevant questions and reduce noise based on previous answers.

06

Governed changes

Keep sensitive configuration changes behind administrative controls and an accountable process.

How it works

Configuration as a managed programme asset

Move changes through a clear path so the live system remains coherent.

  1. 01

    Map

    Translate SOPs, forms, indicators and access rules into a system model.

  2. 02

    Build

    Configure modules, fields, lists, roles and workflows.

  3. 03

    Test

    Run realistic scenarios with users and information-management staff.

  4. 04

    Publish

    Release an agreed configuration with training and change notes.

  5. 05

    Govern

    Review requests, impacts and versions before future changes.

Operational outcomes

What teams should feel in practice.

  • Faster programme adaptation
  • Less custom-code dependency
  • More consistent forms and definitions
  • Safer change management

Important assurance

Flexible does not mean ungoverned

Administrative controls, testing and documented ownership help prevent a configurable system from becoming an inconsistent one.

Continue exploring

Connected capabilities

Implementation & support

A right-sized rollout with clear ownership from day one.

Explore

Access by role

Access follows responsibility, not convenience.

Explore

Reporting & insights

Useful evidence, with privacy kept in the frame.

Explore

See how this fits your programme.

Walk through your case journey, access model and reporting needs with us.

Request a walkthrough