# Pre-qualify a number entry **URL:** \ **Category:** Ask for Help\ **Created:** [August 15, 2024, 3:50pm UTC](https://community.glideapps.com/t/pre-qualify-a-number-entry/75665 "2024-08-15T15:50:28Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [August 15, 2024, 4:38pm UTC](https://community.glideapps.com/t/pre-qualify-a-number-entry/75665/4 "2024-08-15T16:38:53Z")
Okay, if we disregard the potential for race conditions resulting in multiple users claiming the same slot, then the way I would approach it is with a Custom Form. Capture the slot number in a User Specific column, and use that to build a relation to the table where all the taken slots are stored. If the relation is not empty, then the slot is already taken. For a more robust option that eliminates the possibility of race conditions, you might want to use something like Upstash or Make to manage the allocation of slots. Have a read of the below, and the reply from David: > [@new Updates to the Glide + Make integration](https://community.glideapps.com/t/updates-to-the-glide-make-integration/67979/15): > > Okay, from what I am understanding, you are saying that if two users are trying to increment the column value for product A in its total inventory column and user 1 is incrementing it by 100 and user 2 is incrementing it by 200, then glide would queue these up, even if they requests were made at the same nanosecond, and in that queue, the last request would be processed and the requests before that would not be processed. I have spent quite a few hours trying to figure out if glide can sequenti… --- _[View the full topic](https://community.glideapps.com/t/pre-qualify-a-number-entry/75665)._