Documented cap figures in lottery draw records represent the configured upper limit applied to a specific pool, prize tier, or participation variable within a draw format. These figures are written into the draw record during cycle configuration and remain as fixed reference values throughout the operational life of that cycle.
When the active pool or participation metric approaches the configured cap, ซื้อหวยลาว draw system references the documented figure to determine whether a threshold action is required. The participants encountered formats where cap figures were exposed without seeing the documented values themselves. As cap documentation is an administrative record rather than a participant-facing element. A cap figure does not direct the draw toward a specific outcome. It defines the boundary within which the draw operates and triggers a defined system response when that boundary is reached.
How to draw records store cap data
Cap figures are stored within the draw record as fixed fields written at the point of cycle configuration, each containing a defined set of data that governs how the cap is applied across the active cycle. The cap value field records the exact upper limit configured for the relevant draw variable. An applicable variable reference identifies whether the cap applies to pool accumulation, participation volume, or a prize tier allocation. A threshold action entry documents the system response configured to execute at the point the cap value is reached.
Beyond these core fields, a configuration timestamp records when the cap figure was written into the draw record during cycle setup, and a revision history field captures any formal updates made before the cycle opened for ticket acceptance. All fields are locked at the point of cycle open, preventing cap figure alteration after ticket issuance begins. This lock ensures that all participants within a cycle are subject to identical documented limits throughout the entire sales window without exception.
What happens when caps are reached
When a draw variable reaches its documented cap figure, the system executes the configured threshold action and writes a cap event entry into the draw record. This entry documents three things precisely: the point at which the cap was reached, the value recorded at that moment, and the action taken in response.
The cap event entry is appended to the draw record as a post-configuration entry, distinct from the original cap figure fields written during setup. Cycles where the cap was not reached carry no cap event entry, making the absence of this entry itself an informative data point during post-draw record review. Auditors can therefore determine cap status for any cycle by checking for the presence or absence of a cap event entry rather than comparing raw participation figures against the documented limit manually.
Cap figures in post-draw audit review
Post-draw audits reference documented cap figures to confirm that the draw operated within its configured boundaries across the full sales window. Auditors compare cap figure fields against the cycle’s pool and participation records to verify that no variable exceeded its documented limit without a corresponding cap event entry.
Any discrepancy between the documented cap and the cycle’s operational data constitutes an auditable event requiring formal administrative review before the cycle record is closed. The documented cap figure serves as the benchmark for this comparison, and its presence as a locked configuration field within the draw record ensures that the benchmark itself cannot be altered retrospectively to resolve the discrepancy.
