It never ceases to amaze me how many ways an eQMS can subdivide a task. CAPA actions, change actions, meeting actions, supplier actions, etc, etc, etc. It is dizzying.
Tasks are all the same. They comprise of an objective, which is they why. A task (the who, when, what) and a deliverable (proof it is done)
I can count some off the shelf eQMS platforms that have 6+ workflows for this. Absolutely no need. It just makes the end user confused.
Just a little rant brought to by my favorite activity, implementing and improving eQMS functionality.
Investigations of a Dog 