Smart terrace permit (Slimme terrasvergunning)
Install the Slimme terrasvergunning extension and walk a terrace permit on the public domain from request to on-site inspection — automatic checks with sources, all advice in parallel, an AI decision proposal, and the authorised official deciding.
A local government grants a business owner permission to put a terrace on the pavement. The work behind it crosses services: someone checks the company, the terrace rules and the planned roadworks, mobility, local economy and police give advice, and an authorised official decides. The Slimme terrasvergunning extension models that flow in Flemish, with an AI that prepares every step and a person who confirms or decides at every gate.
What it models
| Stage | Who acts | What happens |
|---|---|---|
| Aanvraag | Case manager | Takes over the request from the municipality's e-loket. The AI reads it, lists what is missing and proposes a layout. |
| Controles | AI, then case manager | The AI checks the request against the terrace rules and source data (company register, planned works, pavement width), each check with its source. In a separate step, Scrydon drafts an e-mail to the business owner from the checks and the case manager edits and sends it. The completeness review comes next, and rejecting it sends the case back to Aanvraag. |
| Advies | Mobility, local economy, police | All three advise at the same time, each with an AI summary that puts the deviations first. The case manager can add the fire brigade when a case needs it. |
| Voorstel | AI, then case manager | The AI proposes a decision with conditions and sources; it also appears as an advisory banner on the official's decision. The AI then turns the proposal into a draft decision, which the case manager checks and edits directly. A third step sends the checked draft to the authorised official by e-mail; sending it confirms the check. |
| Beslissing | Authorised official | Approves, or sends one point back. Only the proposal and the draft re-open; the advice stays done. |
| Communicatie | Case manager | Calculates the retribution, then sends the decision with the price in one e-mail that Scrydon drafts and confirms the permit and status were updated in the municipality's own systems. A workflow then creates the payment invitation in the municipality's financial system; its financial-system block ships switched off, so it completes without calling anything and the flow never waits on it. The case manager records the payment, and the inspection waits for it. |
| Handhaving | Inspector | Checks on site that the terrace matches the permit. |
Every AI step is optional, so the flow also completes without a language model.
The extension has no connectors to the Flemish building blocks (MAGDA, GIPOD, the Basiskaart). The case manager pastes their data into the Bronnengegevens step. In a demo that is sample data; in a pilot, it is the output of those connectors.
Set it up
Install and turn it on
In Settings → Platform → Extensions, upload the file you downloaded and click Install. Then open Extensions and click Turn on for your workspace.
Create a case
Go to Process Flows and create a flow from Slimme terrasvergunning. Assign the personas to users. Use a different user for the authorised official than for the case manager.
Test scenario
The extension ships with a full test scenario in Dutch, with sample data for every
step and the expected outcome of every AI step:
packages/sdk-authoring/src/process-flows/examples/slimme-terrasvergunning/README.md.
It runs one fictional case through both loops:
- The request arrives with a terrace that is too deep and no facade width. The checks find a free passage of 1.20 m instead of 1.50 m and roadworks in June. The case manager rejects, and the case returns to Aanvraag.
- After the correction, the three advisers advise in parallel and the AI proposes approval with three conditions.
- The official sends one condition back. Only Voorstel re-opens; the advice stays done. The second decision approves.