Execute SQL Task - Can it be set up so that it doesn't

I have an Execute SQL task inside a container that does a merge statement type piece of work.

I have further Execute SQL tasks based on a success constraint of the Merge SQL task.  My concern is that I think that if the merge task takes say a minute, the other tasks will start kicking off, trying to use the data that isn't quite there yet!

Can I get around this?  Is there a way to simply hold the downstream jobs from executing until I know the SQL Task is completed?  Output parameters maybe?

Thanks!