Online applications are more than digital forms: they only become truly useful in day-to-day work when they are backed by well-thought-out workflows, clear responsibilities and the right portal. Companies and public-sector clients can bring together applications, approvals, queries and status updates in a web portal, making processes easier to structure. This article is aimed at decision-makers, specialist departments and project owners, and focuses on practical planning questions rather than technical how-to guidance. It gives you a structured overview – from goals and processes through data and interfaces to quality assurance, operations and further development. If you would like to explore the topic in more depth, the article on digitising processes in a structured way is also helpful.
What online applications should achieve
The starting point is not choosing a form, but defining the purpose of the portal: which online applications should be submitted, reviewed, supplemented, approved or completed digitally? Only once this framework is clear can you make a sensible decision about which functions a solution in web development actually needs.
It is just as important to look at the groups involved. Depending on the process, these may include:
- Applicants
- Case handlers
- Specialist departments
- Reviewers
- Approvers
- External partners
The focus should not be on the visible form, but on the entire process from submission through to the decision or completion. Typical goals include fewer media discontinuities, a better overview of processing status, clear responsibilities and a consistent data basis.
It is also worth distinguishing between simple and complex procedures. A short standard application usually needs different functions from a process involving supporting evidence, follow-up questions and several decision stages. That is why it makes sense to define the intended outcome early on, for example in terms of processing quality, transparency in the process and reduced manual transfer effort.
Many of these principles apply not only to online applications, but to digital workflows in general. If you would like to place the topic in a broader context, the article on a structured approach to process digitisation offers a useful deeper dive.
Capture processes, roles and decisions properly
Before a portal for online applications is designed, the existing process should be made visible. This includes not only submission and review, but also queries, approvals, notifications, documentation and archiving. Only when the current process has been described clearly and comprehensibly can you assess what can be simplified, automated or structured more clearly.
The business decisions within the process are just as important. Typical points include:
- Which documents are mandatory?
- Which deadlines apply?
- Who is responsible?
- What exceptions are there?
- When is escalation required?
In planning, a clear distinction should be made between business logic and individual cases. In other words: what applies as a general rule, and which special rules apply only in certain situations? This distinction helps prevent processes from being modelled in an unnecessarily complex way.
A separate planning section should cover roles and permissions. You need to clarify who is allowed to create, view, edit, approve or reject applications. Status values should also be defined clearly, so that applicants and internal teams understand the processing status in the same way.
In many procedures, queries are a normal part of the workflow and should therefore be included in the concept. The same applies to templates and text modules where recurring messages or notifications are created.
A specification sheet or a structured description is helpful here, as it turns specialist requirements into a sound project plan. The article on the functional specification as a basis shows how this becomes a workable plan.
Build forms, data and interfaces sensibly
An online application consists of more than the visible input screen. The data model behind it and the processing that happens after submission are just as important. The form is therefore only one part of the system. If you would like to explore the structure of an application in this context in more detail, the article on planning a web app provides a useful overview.
When structuring forms, it is best to take the applicant's perspective rather than mirroring the internal organisational structure. Steps should be based on situations and tasks, not on the responsibilities of individual departments. This makes the process easier for users to understand and follow.
Plausibility checks are also helpful. They can validate entries early and clearly, for example when mandatory fields are missing or information does not match up. Uploaded documents, supporting evidence and attachments should also be planned from the outset, including their clear allocation to the relevant application.
The basis for this is a clean data model. It defines which information is needed in the long term, can be found again, evaluated or passed on to other systems. This becomes particularly important when data needs to flow into CRM, specialist systems, databases, Microsoft 365 or other existing solutions.
An interface is a defined connection through which systems exchange information automatically.
This is exactly why data synchronisation and responsibilities between systems should be clarified at an early stage, to avoid duplicate maintenance. The article on planning data synchronisation between systems offers more detailed guidance.
Consider the portal, user access and operations from the start
A portal for online applications should do more than provide forms. It can also bring together personal overviews, status displays, documents and communication steps in one place. This gives applicants a clear view of their own case, while internal teams benefit from a more structured way of working.
User access is just as important. Internal staff, external applicants and partners often need different views and permissions. That is why it should be defined early on who sees which information, which actions are possible and how access is managed.
Entra ID is a Microsoft service for sign-in and identity management that can be used to manage user access centrally.
Notifications can support the workflow, for example in the event of queries, status changes or missing documents. However, they should be used selectively so that important information is not lost in too many messages. The article on using notifications effectively explores this in more depth.
Operations are also part of the portal. Availability, updates, logging, the protection of sensitive access and traceable changes are not secondary issues, but part of the overall planning.
Microsoft Azure is a cloud platform on which applications, databases and related services can be run.
Data protection, retention and other legal requirements should also be taken into account from the outset and reviewed with data protection officers or legal specialists. If you would like to understand the structure of an application more broadly, the article on planning a web app properly is helpful.
Organise implementation, quality assurance and ongoing development
For implementing online applications, it is advisable to work in manageable steps. This allows specialist departments to provide regular feedback, refine priorities and identify misunderstandings early, before they run through the whole project. The article on a structured approach to software projects also provides practical guidance on the process.
A typical project can be structured as follows:
- Initial discussion covering requirements, expectations and a rough estimate of effort
- Concept and design with cost estimate
- Development with regular coordination
- Quality assurance and go-live
- Support and further development
If you would first like to assess your project, the cost calculator, a project profile based on your description or a no-obligation initial consultation can help.
Quality assurance involves more than simply testing whether functions work. What matters is traceable testing, clear sign-off and a carefully prepared transition into live operation.
Automated tests check recurring functions by machine, so that changes do not unintentionally disrupt existing workflows.
CI/CD refers to a structured process through which changes are built, tested and deployed in a controlled way.
After launch, a portal for online applications is rarely finished. New procedures, roles, forms or interfaces are often added. That is why further development should be managed through planned releases and clearly defined priorities. The article on structured planning for further development is suitable if you would like to explore this in more detail.
Frequently asked questions about online applications
What makes a good online application apart from the form?
A good online application above all includes a clear workflow, understandable status messages, defined responsibilities and clean downstream processing of the data. It also includes uploads for supporting evidence, queries during the ongoing case, notifications at the right points and an overview in which applicants can track the status of their application. It is just as important that internal teams can review, supplement and decide on applications in a structured way. If you would like to assess which components typically work together for this, the services around portals and applications provide a useful overview.
When is a dedicated web portal for online applications worthwhile instead of a standalone solution?
A dedicated web portal is usually worthwhile when more than a single form is to be digitised. This is the case, for example, when several procedures are brought together, different roles work together, documents are exchanged or applicants are expected to work repeatedly with the same login. A standalone solution is also often not enough where status displays, personal overviews or connections to existing systems are important. In such cases, a portal provides a shared framework for recurring workflows.
How many processes should we include in an application portal at the start?
For the launch, a limited scope is usually sensible. A proven approach is to start with one easy-to-understand procedure or with a small number of similar processes. This allows form logic, roles, approvals and communication to be tested in day-to-day use without overloading the project from the outset. Further procedures can then be added in an orderly way. What matters is less the quantity than a sensible scope for the start.
Which existing systems should be considered early on for online applications?
At an early stage, you should primarily look at systems in which master data, cases, documents or responsibilities already exist. Depending on the organisation, these may include CRM, specialist systems, databases, Microsoft 365 or identity services for sign-in. Knowledge sources can also become relevant if support through search, assistants or document extraction is planned later on. The article on planning an AI assistant sensibly is also relevant here.
How do we get from an initial idea to a robust project description?
The most practical route is to compile a structured overview of the goals, user groups, processes, decisions, data and desired integrations. Examples of forms, notifications, emails or existing work steps are also helpful. From this, a robust description gradually emerges that makes concept work, implementation and scope definition easier. To get a feel for what such projects look like in practice, the examples from completed projects can also be useful.
How to turn your plans into a workable project
Good online applications do not happen by accident. They become sustainable when goals are clearly defined, workflows are described, data structures are designed appropriately, access is regulated sensibly, and implementation and operations are planned properly from the outset.
ballmüller solutions develops web platforms and bespoke business applications, for example a platform on which municipalities can manage their sewer network, its condition and planned measures in one place. Concept work and development are carried out by the company’s own developers and designers in Germany; operation in the Microsoft Cloud is also possible.
Depending on how far your project has progressed, there are three possible next steps:
- assess a rough cost range
- have a project profile created from a description or specification sheet
- request a no-obligation initial consultation via Microsoft Teams