Scheduling of review and update task

Yasser -

I think it's important to have deliverable review expectations clearly laid out so you don't go through a never-ending set of review cycles - for example, a maximum of three review cycles per deliverable. That will make it a bit easier to predictably schedule your activities.

If the reviews are done by stakeholders whose effort you wish to track and you wish to show progress against the review activity, then you could set them up as individual activities or tasks. On the other hand, if the reviews are done outside of your team and you only wish to keep an eye on the duration, you could use a lag between the development/submission activity and formal approval milestone.

Kiron

I would set a timeline with tasks such as
task feeding into DD
DD execution - 3d
DD review/update period - 4d
DD approval - 1d
....

I would only want to capture the actual task, understanding there will be iterations.