Teams cannot require completion of a record's to-dos before users move it to the next status.
Required fields by status help teams capture information, but they do not enforce completion of the activities documented in to-dos. These activities do not always require a workflow approval or a workflow approval may be too-heavy.
Product managers can submit records for review before completing the supporting work, such as documenting impacts on other teams or systems.
Teams rely on a required fields to confirm that they completed the to-dos, but they can update this without completing the to-dos. This adds manual work without verifying that the to-dos are complete.
Add a workflow setting, similar to required fields by status, that requires all to-dos attached to a record to be complete before it moves to a specified status.
When a user attempts the transition with incomplete to-dos, keep the record in its current status and explain why the transition is blocked.
Show the outstanding to-dos so users can identify and complete the remaining work, then retry the status change.
Keep this setting independent of workflow approvals so teams can enforce completion of activities that do not require formal sign-off.