CORE / Explore

See how programme
operations connect.

CORE is designed around programme delivery. Its data model connects the people and entities programmes work with to the activities, locations, teams and implementation records that describe what actually happens.

01 / The operational model

See how programme operations connect.

CORE brings participant records, activities, locations and teams into one centralised system. Authorised colleagues share information, see who is responsible and coordinate support across programmes.

Participant overview illustration. — **Participants.** Register individuals, households, collectives and facilities in a connected way.

CONTRACTUAL FRAMEWORKProject

Donor, contract, sectors, budget, codes and period.

→

OPERATIONAL CONFIGURATIONActivity

Outputs, targets, geography, team and target population.

→

ACTUAL DELIVERYActivity Implementation

The operational centre of CORE.

Activity Implementation is where the model comes together.

WHO — Individual, Household, Collective or Facility · WHAT — Activity · WHERE — Location · BY WHOM — Team · plus implementation-specific information.

02 / Configure once

Implement many times.

An Activity is configured once and then instantiated repeatedly as programme delivery takes place. Relevant metadata is inherited; teams add only what is specific to each implementation.

Activity implementation illustration. — **Implementations.** CORE documents actual delivery rather than only the intended plan.

Identify

Find an existing participant or register once. Unique IDs, standard fields, entry controls and duplicate detection improve data quality from the start.

Configure

Set up the Project and Activity, including outputs, target population, geography and team.

Implement

Create Activity Implementations, assign or reassign work between team members and managers, and track actual delivery.

Enrich

Connect forms, assessments, distributed items, referrals and supporting documents to the relevant operational record.

Reuse

Share authorised records across teams and sectors. Keep history and references available through handovers instead of re-entering information.

Analyse

Reuse consistent records and counting rules for cross-programme analysis and automated reporting, with less manual reconciliation and fewer errors.

Keep a trace of the work.

Actions are logged with timestamps, while participants, Activity Implementations and distributed items remain referenced. Programme, Finance and Supply colleagues can follow the evidence for later audits, subject to access and retention rules.

03 / Explore the building blocks

One connected operational model.

These modules share records and references. The same structure can support collaboration with local NGOs as part of localisation, with agreed responsibilities and access rights for each partner.

Connected operational records form a shared model.

A structured operational data backbone.

Structure once. Share and reuse throughout delivery. Fewer manual steps and less rework mean better data, time saved and more efficient use of programme resources.

Discover the CORE approach

Who uses CORE in practice?

Explore field situations, the colleagues involved and the practical benefits.

Explore real-world uses →

See how programme
operations connect.