My interest here is mostly historical - I came from an organization that had a heavy investment in applications (engineering-related) that used license daemon style licenses. But even there, we did not perform much ‘active management’.
At my current organization, we have a small number of applications that use floating licenses and are served by a license daemon. Most of our licensing has migrated away from pooled/floating and instead are directly assigned to a device or user. Few mission-critical applications are pooled/floating so we do not invest time & effort in monitoring those.
At my current and previous org, our team was responsive only in situations where an internal customer expressed a conflict, such as “I can’t get a floating license when I need it” or “my department doesn’t have enough”. Since we do not centrally fund those applications our response in the latter is “let’s help you buy enough so that you always have enough in the pool” or “let’s find another solution such as a dedicated license for your machine”. So, we are involved in problem resolution only. Frankly, because of the complexities of cost-sharing these applications in our distributed environment, it is difficult enough to get the constituent departments to agree to cost share it at all, and they are not interested in our SAM team attempting to right-size the pooled licenses (the risk to them of not having a license when they need it is greater than the cost savings opportunity). So, we have not invested effort into active management.