Distribution and redistribution methods and systems. A data-base stores rights allocation information, e.g., purchase or allocation records for tickets to an event. A
system receives a request that may be satisfied, or partially satisfied, by reallocating rights from a first party to a second party in the
database. A probability that the request will be satisfied is calculated and the party making the request receives an indication of the calculated probability. For example, some implementations include adding, responsive to receiving the request, an identifier for the second party to a
queue and calculating the probability that the request will be satisfied based at least on a position of the identifier in the
queue. In some implementations, a
server receives a request from the second party to acquire tickets to an event, where the requested tickets must satisfy one or more conditions, e.g., location, number of seats, etc., and the
server determines that the request cannot be satisfied. The
server sends the requestor an invitation to join a wait-
list queue and provides an indication of how likely the request is to be satisfied at a later time. In some implementations, the request is satisfied after the event begins, e.g., using tickets reclaimed from parties that do not use them. In some implementations, a rights holder determines to redistribute rights to a set of other people and invites the other people to join a queue to collect the redistributed rights. In some implementations, the
system works directly with a
database used for controlling admission to an event. Integration with event
access control allows for real-
time control and redistribution, as well as assurances of authenticity.