Forum Discussion
predecessors as starting date for big tasks that has other task below it
I'm not sure why you say, "...it's not best practice to create this kind of connection...". A good plan should be fully linked to create dynamic network logic.
Looking at your screen shot, it appears your starting point is 11/9/22 and the "start" milestone is at that date. If your intent is to start several tasks at that milestone, then you really don't need a bunch of links to do that. Simply set your Project Start Date (Project > Properties group > Project Information) at 11/9/22 and all tasks that do not have other predecessors will start on that date.
For any other task or group of tasks that are not initiated by the Project start date, those tasks should have an appropriate predecessor.
It seems a little unusual that you would have a significant number of tasks (i.e. 200) that all start some time after a previous task but I could envision a scenario that has pre-contract tasks. Something like that could be handled by setting the Project Start Date at the contract date, not the actual start date. For example, in this case there is a pre-contract effort ahead of the project start date. Multiple tasks then automatically are "kicked off" by the contract.
John