Originally Posted by
Vessbot
Say there was a flap setting or altitude change, but you had missed that fact. Then this system doesn't work, does it? Within this logic, the same failure that leads to missing the change, also leads to not doing the checklist that would catch the missed change.
If there was a need for that it would be flagged while preparing and briefing both versions at the gate, which would then trigger a discussion about mitigation and the optional departure change checklist would be the logical mitigation measure. For an unplanned departure change i do it anyway.