Organizational AI for Institutional Coordination
Turn fragmented institutional information into shared memory, coordinated action and better policy.
NCC's work is not dozens of disconnected workflows. It is one continuous operating loop: ingest evidence, update institutional memory, resolve requests through authorised collaboration, and learn from the results.
Inputs update what the institution knows. Requests use that knowledge to produce governed outcomes. Results return to strengthen memory and policy.
Concept model with a proposed phased delivery plan for NCC discussion
At a glance
What the operating model provides
One continuous loop
A shared operating loop connects the workflows, while each retains its own participants, authority, lifecycle and completion criteria.
Entity-centred memory
Information becomes a durable understanding of people, institutions, mandates, cases, decisions and outcomes—not another document repository.
Governed coordination
Human and AI participants contribute context and action according to their authority.
Ecosystem-ready
Stable semantics and provenance create a foundation for authorised coordination across institutions and countries.
The Challenge
Dozens of workflows can hide one underlying institutional function.
Reports, registers, proposals, referrals, action lists, payments, decisions and policy reviews may look like separate processes. Underneath, NCC repeatedly performs the same essential work: gather information, structure understanding, coordinate a response, distribute the outcome and record what happened.
When each workflow is automated in isolation, the institution keeps the same fragmentation in a newer form. Information remains trapped in documents and systems, coordination depends on individual memory, and outcomes cannot easily improve the next decision.
Work also enters through fragmented channels—including email, forms, files, systems and authorised online messaging such as Viber. Limited staffing and workload capacity make manual consolidation harder, while compliance with Executive Director directives is not consistently traceable from instruction to owner, deadline, evidence and closure.
The workflow inventory guides delivery priorities. Shared memory and operating capabilities connect the individual workflows.
See the Single Operating Loop →The Operating Model
One loop connects knowledge, work and outcomes.
The model separates two things that are often mixed together: Inputs and Requests. Inputs change the institution's understanding. Requests create an obligation to use that understanding.
- 01
Ingest Inputs
Reports, records, Executive Director directives, RA 11930 and Strategic Plan requirements, evidence, institutional changes, media, Viber and other authorised messages, and outcome confirmations enter through a governed ingestion layer.
- 02
Update Shared Memory
Sources become traceable Data Blocks that update the histories of relevant entities while preserving provenance, time and authority.
- 03
Receive Requests
A request for analysis, statutory or strategic compliance monitoring, Executive Director directive implementation, advice, coordination, decision, training or awareness delivery, action or resolution creates a governed Work Object.
- 04
Assemble Context and Resolve
Authorised people, institutions and agents contribute evidence, judgement and action until a final governed outcome is reached.
- 05
Re-ingest Results and Improve
Results return as new evidence, update Shared Memory and support better operating rules and policy.
Institutional Memory
Authorised sources build traceable, reusable institutional memory.
The system does not treat a new report as another file to store. It identifies the facts, events, relationships and evidence inside the source, converts them into Data Blocks, and uses them to update the institution's understanding of the relevant entities.
This creates a living, time-aware memory of institutions, mandates, authorities, cases, issues, decisions, actions and outcomes. Authorised users and agents can query the same memory without losing the lineage back to the original evidence.
This is the target information model. Delivery starts with the memory needed for the selected reporting scope. Documents, structured records, workflow histories, policy rules and relationships require different implementation and control arrangements; further types are added as their workflows become ready.
Work Objects and Context Assembly
Every participant contributes within their authority.
A Work Object carries a request from intake to final resolution. It may move across multiple stakeholder and agent nodes. Each participant contributes the context, evidence, judgement or authorised action they are responsible for.
Intermediate exchanges remain part of Context Assembly. Resolution means the governed final state: a decision, report, referral, coordination instruction, directive compliance record, RA 11930 or Strategic Plan status report, delivered training or awareness initiative, payment confirmation, action package or closure outcome.
Each workflow needs its own configured lifecycle and completion criteria. Where an outcome depends on DOJ, an LEA or another institution, that institution retains its authority; the Work Object tracks the permitted handoff and returned evidence.
Discovery and Validation
The operating model is grounded in NCC responsibilities and validated system boundaries.
Prevention, training and awareness
These are core mandate activities whose audiences, delivery, evidence and outcomes belong in Shared Memory.
Statutory and strategic compliance
Monitoring compliance with RA 11930 and with the Strategic Plan is core governance work, not generic back-office administration.
Directive traceability
Executive Director directives require governed assignment and traceability: owner, deadline, status, dependencies, compliance evidence, exception, escalation and closure.
CyberTipline integration
CyberTipline workflow improvement must integrate with the management software already being deployed and focus on a streamlined internal journey rather than duplicating the existing intake platform.
The consolidated 1 September 2026 readout incorporates Executive Director, CTIP Operations, PRPMD and Data Management validation. It also includes later administration and procurement interview evidence awaiting assigned-owner confirmation. The catalogue remains 24 identified workflows; detailed validation status is retained in the invited reference.
The reporting mandate is confirmed. A complete Monitoring and Evaluation framework remains a business dependency. Legal case management, service referral and compensation retain distinct functions and access requirements.
See How Coordination Works →Reusable Outcomes
Reports become living information products—not dead-end documents.
A report can still be read, reviewed and transmitted in a familiar format. But behind that presentation, its claims, evidence, entities and meaning remain structured and queryable.
This Rich Data Block can be reused within the next participant's authorised purpose, with links to the underlying evidence where access permits. Shared definitions and source versions support interpretation alongside other approved information.
Beyond One Organisation
When institutional memory becomes interoperable, coordination can scale.
Each organisation or country can operate its own protected memory, permissions and work. When their information products use aligned semantics, an authorised coordination layer can match related signals, identify shared risks and organise work that no single institution could see alone.
This is not unrestricted data centralisation. It is governed semantic interoperability: institutions can coordinate because information has stable meaning, clear provenance and enforceable authority.
From fragmented handling to a connected institutional operating system.
Today
- Reports, registers and inboxes hold separate versions of reality.
- Viber and other online messages may contain mandate-relevant work that is difficult to capture and trace.
- The same information is interpreted repeatedly.
- Coordination depends heavily on individual knowledge and relationships.
- Limited staffing and workload capacity amplify manual delays.
- Compliance with Executive Director directives is difficult to trace.
- RA 11930 and Strategic Plan monitoring depend on fragmented evidence.
- Reports are difficult to query or trace to case-level evidence.
- Outcomes rarely update a complete institutional memory.
- Policy review is limited by incomplete evidence about results.
With Organizational AI
- Mandate-relevant sources—including authorised Viber and online messages—enter through structured ingestion.
- Entity-centred Shared Memory preserves history and provenance.
- Requests become governed Work Objects with complete context.
- Executive Director directives have owners, deadlines, evidence and closure.
- Statutory and strategic monitoring can expand around agreed indicators and available evidence.
- People and agents coordinate according to authority.
- Outcomes remain reusable, queryable and evidence-linked.
- Results support continuous institutional and policy learning.
Proposed first delivery · Wave 1
An approved ecosystem brief — and the memory to update it.
Start with one agreed report family and a named group of reporting institutions. Receive permitted submissions, check the agreed fields, resolve missing or conflicting information, and assemble a source-linked brief for human review and approval.
Save the accepted evidence, corrections, institution records and approved output. The first delivery is complete when NCC can use the brief, trace its material claims and retrieve the saved context for the next request.
The value extends beyond preparing a document. Accepted submissions help NCC understand which institutions are participating, what they report, how evidence relates to its responsibilities, and where further clarification or coordination is needed. That picture grows as the agreed reporting cohort expands.
Recurring weekly or monthly updates can then reuse reviewed evidence. Audience-specific briefs and newsletters can make NCC's contribution more visible to leadership and partners, with editorial review and disclosure approval for each audience.
A stronger coordinating role
A shared view of contributions, evidence gaps and follow-up needs can help NCC convene better-informed discussions.
Visible institutional contribution
Reliable, approved updates can demonstrate the Secretariat's work and support leadership and partner recognition.
Evidence for later action
The same institutional context can support later programme, directive and operational workflows as their scope is configured.
Proposed Wave 1: one agreed report family and reporting cohort. Recurring publication templates, broader audiences, additional institutions and a new statistical extraction pipeline expand in Wave 2.
Explore the delivery approach →One roadmap, two tracks
Five delivery waves expand both capability and workflow coverage.
Waves describe the successive results NCC can receive. P1–P5 describe capabilities that grow across those waves. Each workflow uses the capabilities it needs, and its agreed coverage increases as more scenarios, partners and lifecycle steps are delivered.
Wave 1 · Reporting loop
Deliver an approved, source-linked brief and reusable reporting memory for the initial scope.
Wave 2 · Governance and internal execution
Extend reporting, statistical products, directive tracking and selected internal coordination or administrative subtypes.
Wave 3 · Handoffs and registries
Connect permitted operational intake, one receiving-party feedback loop and an agreed registry update/query scope.
Wave 4 · Specialist-domain expansion
Configure validated investigation, cross-border, legal, compliance and service pathways with their own authority and exceptions.
Wave 5 · Full agreed scope and improvement
Complete the remaining agreed catalogue scope and introduce approved evaluation, policy-change and institutional-improvement cycles.
Capabilities expanded across the waves
- P1 · Ecosystem memory. Evidence, entities, rules and persistent institutional context.
- P2 · Coordination and execution. Owners, configured lifecycles, reviews, handoffs and closure.
- P3 · Core business support. Domain-specific assistance and controlled operational integrations.
- P4 · Cross-agency collaboration. Participating institutions, governed exchange and feedback agreements.
- P5 · Evaluation and improvement. Quality baselines, outcome evidence and authorised change.
A complete first outcome can cover part of a workflow's broader scope. The detailed plan shows proposed cumulative acceptance-unit coverage, not achieved automation, staffing reductions or a fixed schedule.
Review the delivery approach and access the detailed plan →Value and evidence
Measure a stronger coordinating function as well as faster work.
Start by measuring whether the agreed reporting scope produces reliable, traceable and reusable information that NCC staff and leadership find useful. As later workflows expand, add the operational and mission measures appropriate to their outcomes.
Evidence quality
Reporting-cohort completeness, source traceability, corrections and the accuracy of accepted information.
Capacity and reuse
Time to prepare or update a brief, repeated data gathering, rework and reuse of previously approved evidence.
Coordination and visibility
Visibility of participating institutions and evidence gaps, use of leadership updates and the usefulness of follow-up.
Later mission outcomes
Track downstream action and outcomes with the responsible agencies; assess contribution and dependencies separately from reporting delivery.
Agree baselines and targets with NCC. The plan makes no quantified claim about increased rescues, leads, prosecutions or other downstream results.
Transition
Design the core together. Expand through complete, scoped outcomes.
Ingestion, memory, work, resolution and learning share one coherent operating model. Each delivery wave implements the parts needed for a useful outcome, then expands them across more agreed workflow scope. P1–P5 remain capability tracks that grow across the waves. Priorities, scope and acceptance are agreed with NCC.
As responsibilities change, version the affected rules, templates, data and workflow configurations. Review their impact on ongoing work, agree any migration, and show new scope against an updated coverage baseline. New memory types, integrations and subtypes remain explicit delivery work.
View the Delivery Approach and Detailed Plan →See the institution as one connected operating system.
Explore how NCC's existing workflow requirements map into Inputs, Shared Memory, Requests, Outcomes and supporting capabilities.