Hi @anon54308088 , I’ll second @Stephen_Li and offer my best guess of a workaround.
I would consider creating one recurring task to “update client status.” This control task could have no due date, or a recurring one if you want updates at least monthly, say. Then, I’d set a rule that adds a comment to the task, reminding the user to update the other statuses in the project (triggered by field change).
If a user then updated the status on the control task at any time, they’d immediately be prompted to select all the other tasks and update them too.
All of this said, I think a cleaner solution could be to have a control task that team members reference to understand client status rather than relying on every task to provide this information. Often our most complex technical quandaries come down to training 
Lastly, just to save you from barking up the wrong tree as I did…it doesn’t seem like ther’s anything natively or via Flowsana that allows for changing statuses on subtasks based on parent task behavior. Flowsana Rule that Performs an Action on Subtasks Based on Parent Task Update