Municipality A
Develop once. Reuse for good.
We are building an open folder for digital specialist procedures.
Small solutions for concrete tasks – made to be reused, adapted, and developed further together.
Not every problem needs a major project. Standardordner 2030 starts where a concrete solution is missing right now: a single task, a specialist procedure, or a process. What is developed for one organisation can then be available to others.
- +Empty slot
- +Empty slot
Procedures
Requests
What’s missing
There really should be a solution for this.
Anyone working in administration or organisation knows that sentence. A task costs time every day: lists in spreadsheets, information between systems, software meant for something else.
The problem is often not that no software exists at all. The problem is that a concrete task immediately becomes a complete project. On paper it is too small for a major project – and too specific for the next all-in-one suite.
Standardordner 2030 starts one size smaller: at the concrete task.
And once that solution works, the next municipality does not have to start from zero.
Too big for the job
Many procurements deliver features for everything and nothing. Only a fraction is needed – yet you still pay for and operate the whole suite. A clearly bounded task does not need a major project.
Systems don’t talk to each other
Specialist procedures and existing systems sit next to spreadsheets and email. Data is transferred by hand even when the process is clear. Digitisation stays fragmented because the pieces do not work together.
Small change, big effort
As soon as a process changes, the matching adjustment is often missing. Instead of a new project from scratch, an existing procedure can be adapted – and the extension stays in the folder for others.
Not every specialist procedure has to be invented again.
A municipality needs a digital solution for a concrete process. Another municipality may soon face exactly the same task.
Standardordner 2030 therefore thinks not only from one organisation to the next, but from the first solution to the next reuse.
A specialist procedure can start small, be reused, adapted, and developed further together.
Procedure X
Standardordner 2030
Reuse
State
“We need that too.” A state reuses the municipal procedure.
Adaptation
Municipality C
“Our process works a little differently.” Procedure X is adapted.
Further development
X and the extension
The extension stays in the folder and is available to others again.
Reuse, adapt, or develop together.
Reuse
Something already exists. Another organisation takes the procedure instead of commissioning it again.
Adapt
Something almost exists. The process is similar, but not the same – the procedure is adapted to local workflows.
Develop together
Something is missing. One organisation starts the development, or several carry it together. Afterwards the procedure sits in the folder.
A municipality has an idea.
A municipal museum wants to digitise a particular process. For instance, recording loans, tracking objects for an exhibition, or booking guided tours. Commissioning a complete piece of software for that alone can be out of proportion.
Ten, fifty, or a hundred other museums may face a similar task. A municipality does not have to wait until someone else develops exactly this procedure. It can start small at one museum and be filed as its own folder. When several institutions share that need, the one folder becomes more than a single commission.
More budget. More perspectives. More shared vision.
Once that folder is filed, others can reuse it or adapt it to their workflow. Not every procedure will be used by hundreds – the logic stays the same.
Open source keeps the folder open.
Reuse works better when the software stays open. Open source is not the product. It keeps the folder open for reuse, adaptation, and further development.
- No artificial lock-in to one vendor
- Self-hostable
- Software you can follow
- Adaptable and extensible
- Other organisations can contribute
- Further development can happen together
The folder is not full yet.
And that is intentional. We do not know today which specialist procedures will be needed most urgently tomorrow.
That is why we are not building a huge suite and claiming that solves everything. We fill the folder where concrete needs appear.
A solution can begin for a single organisation, be developed together, and then be reused by many.
A specialist procedure does not have to do everything.
A specialist procedure does not have to be complete on day one. Incoming mail, request, appointment, file: each piece can be its own folder, filed when the task arrives.
What belongs together should know about each other. In the folder, information flows instead of being entered again.
What already works does not have to go.
Standardordner 2030 does not replace existing systems by default. Many organisations have software that does its job – and still have gaps.
Instead of procuring everything new, we ask: what is missing? What can be connected? Often it is not the whole system that is missing, but one piece a specialist procedure can add.
Your admin system
e.g. requests
Extended – not replaced
What are you missing?
You do not have to wait until someone else develops exactly your specialist procedure. Describe the task.
That can become a development – on its own or together – and then an entry in the folder that others can reuse.