Being able to block patrons from placing holds when their account has exceeded the financial limit or expiration date is extremely important and surprising that it isn't built into the software.
Patrons that don't realize there is a problem with their account until they try to pick up their item. This can be even more frustrating with locker pickup since the library is closed and now they can't even get someone to help them. We have heard comments such as "How come I was able to place the hold, why didn't it stop me?"

If the system prevented the hold in the first place, the patron could call or come into the library to rectify the problem. This would save a tremendous amount of time for staff, delivery and also creates a more positive patron experience.

In a large system, the volume of holds that can be placed and then potentially not picked up/checked out is huge and not having an option to block holds based on card status fundamentally affects our operations. With this option, we would be able to streamline staff time and workflows substantially.

This would help us greatly, since many of the items placed on hold for our Patrons are at other libraries around the state and must be shipped to us. If the Patron does not clear the block so they can have the item, we just then ship it back without is being used at all. This costs time and money that it should not if the Patron had been prompted to clear the block before they placed the hold.

This should be a opt in or out SA setting. For our Library, we allow holds on accounts regardless of status on regular cards. We only block the checkout when the account is in question. We figure if someone wants an item bad enough to put a hold on it, they will have their account status corrected.

We wouldn't object to this being available as a configurable option - but not as the default or only option. We have no objection to customers that owe too much money placing holds and we definitely want the option for staff to place holds in Leap - despite how much money a customer might owe.

I would like to add that Leap is a staff tool and should not be included with this logic. Also, the block should be configurable by the library under SA access.

This improvement is especially relevant with off-site holds lockers. Patron places hold, staff pull items and travels to holds locker to load, patron receives notification hold is available but then unable to check out items due to blocking condition. This creates undue staff workload and patron frustration.

My staff are asking about this. We have some patrons who are blocked due to lost items placing holds and then taking them.

This should maybe be linked to this idea, too: https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46813915-block-patron-hold-requests-in-the-pac-if-they-are