If projects are already created in Octaved Flow in the offer phase, information can be stored in the wiki that is directly in the right place when it comes to the order.
The use of tasks simplifies the calculation of effort and prices. In addition, the tasks are preserved and can be processed - when the order arrives - in the same way as they were created in the offer phase.
If a project with work packages is created in the offer phase, the work packages get the status Offer.
The wiki can be used to store information that will be useful when it comes to the order. For example, files from the customer can be stored, which are then directly in the right place when the work begins.
It also maps a workflow between the project manager and team members: The project manager instructs the team members to break down the work packages into tasks and provide each task with a time estimate.
The sum of the estimated tasks is displayed in Octaved Flow and on this basis the project manager calculates the effort and price of the offer.
If the order is placed, exactly these tasks serve as a checklist for the implementation of the work package. Also, the list of tasks can be used as a copy template for other quotes and projects.
Time recording in the offer phase
Time recording for work packages with the status Offer is not possible, because without an order the legitimation is missing. As booking object a separate work package can be created in the project with the billing type Without calculation and the reason Pre-Sales. On this the time can be booked, which is spent in the context of the Pre-Sales. Thus, there are statistical evaluation options even regardless of whether an order is created from the offer or not.