There are times when a blanket work order makes sense. A few examples would be for tracking training hours for a team of techs or for tracking time used for operations support or even tracking morning meeting time. In these cases, we are not losing historical data and in fact are tracking a meaningful metric with the blanket work order.
The best way I have seen to limit the creation of blanket work orders is to ask yourself these two questions before you create one:
- Does this need to be charged to the asset for historical cost reporting?
- Would we want to know how often this reoccurs at the asset level?