Skip to main content
Apps/ZaakAfhandelApp
Betav0.2.7NL · EN1,874 downloads

ZaakAfhandelApp

Zaakgericht werken (VNG GEMMA/ZGW) on your Nextcloud. Case workers manage zaken from intake to formal closure, log klantcontacten, and expose a ZGW (ZRC/ZTC/DRC/BRC) REST API — no separate case system, no second login.

Zaak Afhandel App (ZAA) is an open-source case-handling app for the Nextcloud workspace. It manages Dutch zaakafhandeling end-to-end: zaaktypen, statussen, rollen, besluiten and resultaten; taken (tasks); klanten, personen and organisaties with contactmoment logging; in-case berichten with a message audit trail; opschorting and verlenging (suspend/extend) on a running case; a personal werkvoorraad dashboard; and a ZGW (ZRC/ZTC/DRC/BRC) REST API surface. Data, search, RBAC and audit are provided by OpenRegister. Released under EUPL-1.2 and maintained by Conduction since 2019. ZAA is no longer actively developed — new deployments should look at Procest or Pipelinq.
What it does

Zaakgericht werken for case-workers, on Nextcloud.

Case-workers manage zaken from intake through formal closure in the same Nextcloud where they store the documents — zaaktypen, statussen, rollen, besluiten, resultaten, tasks and klantcontact, all backed by OpenRegister.

Cases (zaken), start to close.

Zaaktypen, statussen, rollen, eigenschappen, besluiten and resultaten — the full ZGW case lifecycle, with opschorting and verlenging (suspend/extend) on a running case.

Tasks (taken).

Assign taken to medewerkers or klanten, track deadlines and status from the werkvoorraad dashboard.

Klanten, personen and organisaties.

A 360° relation view with contactmoment logging for every interaction, and berichten (in-case messages) with a message audit trail.

ZGW REST API surface.

A ZGW (ZRC/ZTC/DRC/BRC) REST API surface for zaken, taken, besluiten and documenten, so other ZGW-speaking systems can integrate.

Audit trail per case.

Every status change, every task, every case-worker action gets a tamper-evident trail via OpenRegister, ready for inspection or appeal.

Partners

Partners shipping ZaakAfhandelApp

Implementation, hosting, and integration partners that deliver ZaakAfhandelApp to their customers. Pick the partner you already work with, or one whose stack matches yours.

Three ways ZaakAfhandelApp earns its place

One case-worker queue, every step audited.

Scroll the cards. Each pins as you reach it; the next slides up to cover.

Case lifecycle

Zaken, start to close.

Zaaktypen, statussen, rollen, besluiten and resultaten model the full ZGW case lifecycle, with opschorting and verlenging to pause or extend a running zaak.

See ZaakAfhandelApp
ZGW REST API

A ZGW API other systems can call.

Zaken, taken, besluiten and documenten are exposed through a ZGW (ZRC/ZTC/DRC/BRC) REST API surface, built on OpenRegister for storage, search and RBAC.

See OpenRegister
Audit-ready

A tamper-evident trail per case.

Every status change, task and case-worker action is logged through OpenRegister's audit trail. Each zaak also carries a computed archiefactiedatum, derived from its ZGW afleidingswijze.

See OpenRegister
Widgets we ship

The case-worker's morning view.

Install ZaakAfhandelApp and these widgets show up on the dashboard: open and active cases, open tasks, and contact moments.

Open cases

A live count of open zaken, one click through to the Cases list.

open
done
open
done

Open tasks

Open taken across the queue, assigned to medewerkers or klanten.

4
this month

Contact moments

Logged contactmomenten with klanten, filterable by date range.

How ZaakAfhandelApp plugs into the workspace

Cases and documents, one Nextcloud.

ZaakAfhandelApp keeps a case's attachments in Nextcloud Files and exposes the case data as a ZGW REST API for other systems.

Each zaak, taak, besluit and document carries a Files widget on its detail page — attachments live in the same Nextcloud the case-worker already uses.

See the docs
Pairs well with

Built on OpenRegister.

ZaakAfhandelApp requires OpenRegister for storage, search, RBAC and audit. ZAA itself is no longer actively developed — for new deployments, see Procest or Pipelinq.