---
title: 'Operate applications reliably'
url: 'https://grassroot.it/en/artikel/anwendungen-verlaesslich-betreiben'
markdown: 'https://grassroot.it/en/artikel/anwendungen-verlaesslich-betreiben.md'
lang: en
date: '2026-11-11'
description: 'An application fulfils its purpose over time when use, maintenance and recovery are organised. The approach should be manageable and actually used. Grassroot IT scales it to the…'
taxonomy:
  category:
    - Operations
  tag:
    - 'Getting started'
    - Operations
---

Operations 11.11.2026

# Operate applications reliably

An application fulfils its purpose over time when use, maintenance and recovery are organised. The approach should be manageable and actually used. Grassroot IT scales it to the applicati…

 ![Operate applications reliably — symbolic illustration](https://grassroot.it/user/pages/03.artikel/03.anwendungen-verlaesslich-betreiben/cover.png) 

An application fulfils its purpose over time when use, maintenance and recovery are organised. The approach should be manageable and actually used. Grassroot IT scales it to the application’s importance and organisational requirements.

## Name owners and deputies

For each operational application, establish who owns the business purpose and who can make changes. These may be different people. A deputy needs access to the necessary records and approved storage.

A short operating description explains when the application runs, its inputs, how correct output is recognised and whom to contact during an incident. For a report in Microsoft Excel, reconciling a total with its source may be part of that procedure.

## Introduce changes under control

Give each approved version a clear identifier and defined location. Record why a change was made, what it contains and its test results. Distinguish the operational version from development in progress.

Before adopting a change, recheck affected business results and links to files, data sources and services. In Microsoft Access, a changed query can affect several forms and reports. These dependencies determine the appropriate test scope.

## Test recovery in practice

A backup alone does not establish recoverability. The matching program version, settings and other dependencies may also be needed. A recovery attempt using suitable data checks whether these components work together.

Define tolerable downtime and loss of recent changes for the supported business process. Derive backup and restart requirements from those limits. Briefly record the trial result and resolve gaps in the actual operating arrangements.

## Reassess use regularly

Permissions, data sources and ownership change. Regular comparison identifies obsolete access, discontinued tasks and new requirements. It also shows whether the expected value is still being delivered.

On replacement, establish which data must be migrated or retained, who will supply results and which access rights will end. Operation thus concludes with a traceable decision. [What is Grassroot IT about?](https://grassroot.it/en/konzept) explains the overall context.

---

## Navigation

- Parent: [Articles](https://grassroot.it/en/artikel.md)
- Previous: [From prototype to reliable application](https://grassroot.it/en/artikel/vom-prototypen-zur-anwendung.md)
- Next: [Develop with artificial intelligence and verify the results](https://grassroot.it/en/artikel/ki-entwicklung-pruefen.md)