[Tom Bunch]

Hammock tasks ends are entirely extrinsic to the hammock task itself. The hammock task starts at the beginning or end of a task and ends at the beginning or end of a (potentially different) task. It's meant to represent on going effort during a certain phase of your project.

Waiting for feedback before you can move on to the next phase of your project sounds more like an external milestone. You can't really assign more of your own resources to waiting to wait faster, or control when you're actually going to receive the feedback. Depending on what your resources are doing while you're waiting for feedback I think I'd set it up like the attached image. This approach is "you have one day while you're waiting for feedback. Try to make yourself useful". I've used that to illustrate a hammock task. If the feedback comes in late, you can add a start constraint to the "receive feedback" milestone and the hammock task will lengthen. The minimum of 1 day is accomplished by a dependency with a lead time.

-Tom