It's to easily (programmatically) highlight and surface "pertinent" (to resolution) actions, as opposed to "informational" worknotes.
In "regular" incident management, it's "not hard" to sort out when a worknote speaks to an action taken, to resolve or in an attempt to resolve.
...for "major" incidents, that's a bit more tricky & also a bit more important...so this supports that concept.
"Tricky" because there are more "cooks in the kitchen" (usually more people working on a major incident, thus more worknotes) and "important" because the "order of operations" in terms of actions taken, to resolve a major incident is important to root cause analysis and full end-to-end resolution.
Whereas "regular" incident management's goal is to simply restore client service as quickly as possible, less emphasis is put on analyzing why something happened and preventing it from happening again, "major" incident management has a primary goal of restoring service and preventing a future major incident (bypassing the usual need for recurring major incidents by Problem Management processes - "When you're this big, they call you mister" so to speak)
