Hi,
My example may not be exactly like yours, but here is how I work under the
following circumstances:
I put the logical successors for both conditions along with any other
logical links for these two conditions into the plan. Then I simply delete
the tasks that do not apply once the decision point has been reached. It is
easier for me to delete tasks than it is to add them along with the l;inks
to their logical successors. I also work with the same types of projects
over and over again. Therefore, having a standard project file for repeated
use works best for me. Your resulting project will be the pessimistic
(longest) of all the possible tasks.
This idea may not work at all for you.
I want to explain why this works for me.
1) It doesn't really impact the end date of the project.
2) I have a custom field (flag) that I call "Optional" so that I can filter
for these tasks to manage and work with them.
3) There are only a few tasks like this in the entire project.
4) I don't have to notify the assigned resource until shortly before the
task is due and long after the decision point is reached.
In Research, none of this may be appropriate - or may be difficult to create
meaningful reports.
Alternately, you may be able to create a master project that has the
subproject inserted after the decision point has been reached. (Don't count
on me for advice on Master Projects and Subprojects - just see some of my
other posts and you will understand that I'm just beginning to use them.)
Good Luck.