In foreknown, there are already a variety of controlling functions that enable the control and evaluation of orders, services and now also tasks. But why is the topic of "controlling" so important to us that we even break it down to individual tasks?

With the current release 1.4 we have laid the foundation for a project and task management in foreknown. But why does foreknown need this functionality? There are two main reasons, which we would like to explain in this article.

In foreknown, orders not only represent the commercial basis between contractor and client, but also serve with their key performance indicators (KPIs) to constantly monitor success during the implementation of the requirements defined in the order.

In order to monitor the success of a company or of orders, key performance indicators (KPIs) should be easily accessible on the basis of service entries created.