Skip to main content

Built for the Americas.

Colombia · Government

A digital process infrastructure supporting millions of government interactions.

A long-term digital-government evolution: from document management to the orchestration of institutional processes at municipal scale.

Operating model

DEPARTMENTSCITIZENSDOCUMENTSSYSTEMSDATAPROCESSORCHESTR.PQRSHEALTHCONTRACTSRECORDS

Client

Municipio de Envigado

Colombia

  • Process Engineering
  • BPMS
  • Document Management
  • Integrations
10.5M+
registered records / radicados
6M+
task instances
3,200
users
1,758
active users

The operational challenge

What was actually happening in the operation.

  • 01

    Municipal operation depends on many departments, each with its own processes, documents, records and systems.

  • 02

    Citizen requests, healthcare processes, contractual management and document management have to remain traceable across departments over years, not months.

  • 03

    Scale is not the exception in this environment; it is the normal operating condition.

Before

How the process operated before AF.

  1. 01

    Department-level processes

  2. 02

    Documents as the record

  3. 03

    Separate systems

  4. 04

    Manual coordination

What AF changed

Not a technology list — a change in how the work runs.

AF's relationship with the municipality goes back approximately to 2012, beginning with document management and evolving into the orchestration of multiple institutional processes. The BPMS environment is known internally by the municipality as Débora.

  • People

    • Thousands of municipal users work inside defined processes rather than parallel manual routines.
  • Process

    • Institutional workflows are modelled, deployed and versioned instead of being described in documents only.
  • Documents

    • Records and radicados are registered and traceable through the process that produced them.
  • Systems

    • Integrations connect municipal systems without replacing them.
  • Citizen requests / PQRS
  • Healthcare processes
  • Contractual management
  • Document management
  • Other institutional workflows
  • Integrations across municipal systems

Operating model

How the solution works end to end.

  1. 01

    Departments

  2. 02

    Citizens

  3. 03

    Process orchestration

  4. 04

    Documents & records

  5. 05

    Municipal systems

Schematic

DEPARTMENTSCITIZENSDOCUMENTSSYSTEMSDATAPROCESSORCHESTR.PQRSHEALTHCONTRACTSRECORDS

Measurable impact

Verified figures only.

10.5M+
registered records / radicados
6M+
task instances
3,200
users
1,758
active users
261
processes deployed
108
processes executed in the previous reported year

Figures reflect the operational scale of the municipal process environment. They are not annual volumes, and they do not represent improvements generated exclusively by AF.

This is not the story of a single implementation. It is the story of a municipal operation that has been progressively organised around digital processes, starting with document management and growing into the orchestration of institutional workflows across departments.

What makes it institutional is continuity: people, documents, data, systems and processes stay connected as administrations, priorities and volumes change. The scale visible today is the accumulated result of that continuity, not of one project.

What this demonstrates

Capabilities another operation can apply.

Each organisation's context is different, so this describes demonstrated capability — not a result another company will reproduce identically.

  • High-volume workflow orchestration across many organisational units
  • Legacy-system interaction without replacing the core systems
  • Traceability across people, data and documents over years of operation
  • Long-term institutional continuity of a digital operating model

More evidence

Other success stories.

Talk to AF

What part of your operation should work better?

Tell us where the work slows down and an AF specialist will review it with you.

Already an AF client?

Support requests are handled through the Client Portal — not this form.

Open Client Portal