Skip to content

For municipalities

Modern market stall allocation for municipalities: structured, transparent, legally sound

Weekly markets, Christmas markets, town festivals: market stall allocation is everyday municipal business. And yet in many administrations it still runs on email, spreadsheets and phone calls.

What's missing is a platform that unites application, review, stall management and AI support in a single process. That's exactly what Jira Service Management is. No third-party apps, C5-compliant.

The challenge

What changes when stall allocation goes digital

Without Jira Service Management

Applications by email, post or in person – all in different forms
Missing documents are requested manually
Multiple systems: email, spreadsheets, PDF, phone
Double bookings are hard to prevent
Decisions aren't fully documented

With Jira Service Management

One self-service portal for all applicants

Rovo AI detects gaps and follows up automatically

One platform, everything visible centrally

The system checks stall availability automatically; double bookings are ruled out

Every decision is documented and traceable
Relationship graph of stalls in Jira Service Management Assets

The solution

With Jira Service Management you build a digital stall allocation system

Applicants submit their request through a self-service portal, upload supporting documents directly, and receive automatic status updates. Case workers review and approve requests centrally in structured queues. Stalls and events are managed via Jira Service Management Assets, with real-time availability and a complete occupancy record.

The result: a modern citizen service that supports OZG requirements and saves your team hours every day.

Core features

What the implementation looks like

Self-service portal

Applicants submit requests online, including document upload.

Form: applying for a stall in the self-service portal

Structured approval workflow

From submission through review and follow-up questions to approval or rejection.

Workflow diagram of the approval process

Central processing in queues

All requests in one place, sorted by priority and status.

Stall management with JSM Assets

Events and stalls with availability status.

Overview of all stalls as assets

Automated notifications

Status updates and confirmations by email and visible in the customer portal, with no manual follow-up.

Automatic confirmation email and request history in the customer portal

Management dashboards

Real-time overview of every application's status.

Dashboard of open and closed requests over time

AI support

AI-supported application processing: Rovo as digital first reviewer

The Rovo AI agent handles the first review step automatically – before a case worker even opens the request:

  • It checks submitted documents for completeness.
  • It categorises the application by event type and stall.
  • It requests missing documents directly from the applicant.

The result: fewer follow-up questions, cleaner queues, faster decisions.

Your benefit

What digital stall allocation gives your administration

Ready for the first step? Book a no-obligation first conversation.

Less administrative effort

Your team works with clear processes; no more endless rounds of coordination. The system checks stall availability automatically; double bookings are ruled out.

More transparency & traceability

All applications and decisions are visible centrally. Every decision is documented and traceable.

Better citizen service

Clear status updates without phone follow-ups.

Fast implementation

Prototype in approx. 15–18 person-days, no additional license costs.

Detail view of a stall asset in Jira Service Management

Technology

Technical framework

  • Built entirely on Jira Service Management, JSM Assets and native automations
  • No third-party apps required
  • Deployable on your existing Atlassian Cloud infrastructure
  • BSI C5 compliant; suitable for the public sector
  • Extensible with AI-supported features (e.g. Rovo AI agent for automatic pre-review)

FAQ

Frequently asked questions

Do we need new software or infrastructure for a digital stall allocation system?

No. If your administration already uses Atlassian Cloud, the solution runs directly on your existing infrastructure – no new system, no complex rollout.

How can market stall allocation be handled digitally and OZG-compliant?

With Jira Service Management, municipalities digitise the entire market stall allocation: from application through review to approval. The system is OZG-compliant and can be implemented without additional apps.

Is Jira Service Management also suitable for digitising weekly markets?

Yes. The solution is designed for recurring municipal event formats (weekly markets, fairs, town festivals). Stalls, application cycles and approval workflows can be configured individually per event type.

Can Jira Service Management handle stall allocation without additional apps?

Yes. The system is built entirely on Jira Service Management, JSM Assets and native automations – no third-party apps, no additional plugins, no new software licence.

How long does it take to introduce a digital stall allocation system in a municipality?

A working prototype can be built in about 15–18 person-days. The exact scope depends on the number of event types, approval stages and desired integrations.

Is Jira Service Management BSI C5 compliant and approved for German public authorities?

Yes. Atlassian Cloud holds the BSI C5:2020 Type 2 attestation for Jira, JSM and Confluence Cloud – the official security evidence for use in German public authorities and institutions. AKDB has been running the platform in production since 2023.

Next step

Ready for the next step?

We'll show you what a digital stall allocation system could look like for your organisation – in a personal demo or a no-obligation first conversation.