Release 1.6 of foreknown introduces the "Assign Project" function at orders, which allows order items to be assigned to projects for implementation.

The product release 1.5 provides some new controlling features on the task level. In the list view as well as in the detail view of a task, many KPIs are provided, such as the target and actual efforts, billable and non-billable working hours and the billing rate.

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.