for processing (delivery with processing rights. The first one who opens the process reserves it for himself, with all the others the ToDo disappears, it is done by him for all the others ... "no duplication." That would not work with an internal e-mail.
You can delay the delivery by submitting an appropriate delivery date before the due date. The time required controls the utilization but also the distance between due and the delivery date. To the right of the entry for the time requirement are the available working hours. If the value turns red, it does not match until due. Then the recipient would not have enough time for it.
for info (bookmarks are distributed directly ... "avoids the e-mail and copies")
ToDo (in the picture "Develop key figures")
In the ToDo you deposit what to do. (You separate several entries with semicolon.) In addition you give in the ToDo what still needs to be done. As soon as the process is presented again in the ToDo, everyone sees quickly what to do.
Submitted events appear in the ToDo overview of the recipients. There the work packages deposited by you are shown in green with a checkbox. The priority "A" is shown as a red runner.
Processes that are loaded for a later date, see the recipient already in the forecast under "To Do, Resubmission".
You can see further processes as sender in the ToDo \ delegated overview arranged according to their due date including their recipients. So you have the overview and you have a task backlog that you can discuss with the team.