How to read several fantasy welcome offers on the same sheet, before you sign up

Three figures — qualifying deposit, rollover multiplier, smallest eligible entry fee — are enough to convert a single offer into a single rupee number, and the desk has a slower read on that conversion that sits a page or two back. Comparison is a different problem. A reader who has opened the APK and is staring at two, three or four welcome offers on different apps is not trying to convert one offer; the reader is trying to keep several offers in mind at the same time without losing the differences between them. The reading desk's habit, after several months of post-install reading, is that three figures are not enough rows for that task. Three figures collapse an offer into a cost; five rows keep an offer readable enough to compare.

The five rows are eligibility, trial-credit shape, venue or series-specific terms, expiry, and cancellation. Eligibility is the platform's filter — who the offer is for and who it is not. Trial-credit shape is the form of the credit — a deposit match, a free entry, a venue credit, or a tiered combination. Venue terms are the small list of conditions the offer inherits from the venue or the series running at the moment the offer was opened. Expiry is the date and the path by which the credit has to be redeemed. Cancellation is the rule for what happens to an unused credit when the reader decides not to use it.

None of the five rows alone is the answer. The rows together are the answer. A reader who has the five rows for two offers has the comparison; a reader who has the five rows for three offers has the choice. What follows is the desk's working method for filling those rows. The method assumes nothing about the platform, the season or the headline figure; hypothetical numbers are used throughout to keep the read focused on the rows rather than on any live offer.

Row one is eligibility. Eligibility is the smallest set of conditions the platform applies before the offer is opened: state of residence, age verification status, payment method, account age, and whether the reader has previously held an account on the platform under a different email. The conditions are usually listed on the offer screen, but the list is often the smallest possible list that the platform's compliance team will sign off on, and a reader who skims the offer screen will sometimes read only the first condition and miss the others.

The desk's habit, when filling row one, is to write the conditions down as a short bullet list in the order they appear on the offer screen, then to add a fourth column for "verified by" — the place inside the app where the platform will check the condition when the qualifying deposit moves. State of residence is verified by the KYC flow; age is verified by the PAN or Aadhaar step; payment method is verified by the deposit rail; account age is verified by the platform's own records. A reader who has the verification column filled in for each condition has a way to spot a condition the platform will reject at deposit time, and a rejected deposit is the most expensive mistake a post-install reader can make.

To keep the read concrete, the desk uses a running example of two hypothetical offers. Offer A on platform one is open to residents of all states except a handful named on the platform's restricted-states list; the offer requires the KYC flow to be complete before the qualifying deposit, and the deposit must be made through UPI or netbanking, not wallet balance. Offer B on platform two is open to residents of the same set of states but adds a check that the reader has not previously held an account under any other email on the same device. The two eligibility lists are similar at first reading; the device-fingerprint check on offer B is the difference, and the difference is the kind of detail that turns a "this offer looks fine" read into a rejected-deposit read at the moment the offer is accepted.

Row two is trial-credit shape. Trial-credit shape is the form the credit takes once it has been opened: a deposit match (a percentage of the qualifying deposit credited to the wallet), a free entry (one or more settled entries into a stated contest list, paid by the platform rather than the wallet), or a venue credit (a small rupee credit usable only against a stated venue or series). The three shapes are different products, and they have different rollover rules, different eligible-market lists, and different cancellation behaviour. Treating them as the same offer is the most common mistake a reader makes when two welcome offers are on the same screen.

A deposit match is the most familiar shape. The platform credits the wallet with a stated percentage of the qualifying deposit, up to a stated cap. The credit is fungible with the wallet balance, and the rollover rules apply to the credit and sometimes to the credit plus winnings. A free entry is a less familiar shape. The platform books one or more settled entries into a stated contest list on the reader's behalf, using the credit rather than the wallet. The credit does not enter the wallet; it enters the contest. The rollover rules apply to the entries, not to a wallet balance. A venue credit is the smallest shape. The platform credits a small rupee amount that can be used only against entries into a stated venue's contests, often a particular ground or a particular series, and the credit expires at the end of the stated series regardless of whether it has been used.

For the running example, the desk compares the two hypothetical offers on the basis of trial-credit shape. Offer A is a 100% deposit match up to a hypothetical cap of ₹1,000 on a qualifying deposit of ₹500; the credit is fungible with the wallet and is subject to the platform's standard rollover. Offer B is a free entry — a single settled entry into a stated contest list, paid by the platform, with no rupee credit entering the wallet. The two offers have different headline figures (₹1,000 against the cap on offer A; the entry fee of the listed contest on offer B), but the more important difference is that offer A is fungible with the wallet and offer B is not. A reader who treats offer B as if it were a wallet credit will end the offer window with no wallet credit at all and one settled entry they did not pay for, and that mismatch is the shape difference doing its work.

Row three is venue or series-specific terms. A welcome offer is built on top of a contest list, and the contest list is built on top of a season schedule. The schedule has its own conditions: a venue's eligibility list (which states the venue recognises for ID), a broadcaster's content window (which fixtures the broadcaster will carry live), and a tournament's rescheduling policy (what happens to a settled entry if the match is abandoned, washed out, or moved to a different venue). The welcome offer inherits all three sets of conditions whether or not the offer screen mentions them, and the offer screen often does not mention them.

The desk's habit, when filling row three, is to write three short sub-rows. The first sub-row is the contest list: the named contests whose settled entries count toward the rollover, including any minimum entry fee. The second sub-row is the venue eligibility list: the states or the IDs the venue will accept for entry, including any states the venue does not recognise. The third sub-row is the rescheduling policy: the rule that applies if a match in the offer window is abandoned, washed out, or moved. A reader who has all three sub-rows filled in for an offer has a way to read the offer against the real calendar rather than against the offer screen.

For the running example, the two hypothetical offers diverge on row three in a way the headlines do not show. Offer A's contest list includes the full season schedule but excludes matches moved to venues outside the platform's recognised list; the offer also credits only settled entries against contests whose first ball was bowled within the offer window. Offer B's contest list is narrower — it covers a single stated venue for the first two weeks of the season and adds a second venue from week three — and the offer's rescheduling policy voids the credit if the match is moved to a third, unlisted venue. The two offers' headline figures are similar; their venue conditions are not. A reader who lives near the first listed venue of offer B but who plans to read matches across both venues is reading a different offer from a reader who only plans to read matches at the first venue, and the row-three sub-rows are the place where that difference is captured.

Row four is expiry and the redemption path. The expiry is the date after which the credit is no longer usable, and the redemption path is the route the platform requires the reader to take to convert the credit into either a settled entry or a withdrawable balance. A reader who has only the expiry date has half the row, and the half is the part most often missed by readers who assume the credit can sit in the wallet until they have time to use it. Most credits cannot. Most credits expire on a stated date regardless of whether they have been used, and the date is often earlier than the season's end.

The redemption path is the more useful half of row four. The path usually includes a stated minimum number of settled entries, a stated contest list, a stated entry fee band, and a stated window within which the entries must be settled. The path is the platform's way of saying the credit is not a wallet gift; the credit is a coupon for a stated kind of play, and the coupon is void if the play does not happen within the path. The desk's habit, when filling row four, is to write the expiry as a single date and the redemption path as four short sub-rows: minimum settled entries, contest list, entry fee band, and the redemption window. A reader who has all four sub-rows filled in for an offer has a way to check whether the offer still fits the week's reading schedule before the qualifying deposit moves.

To finish the running example, the two hypothetical offers diverge on row four as well. Offer A's expiry is the end of the second week of the season; the redemption path requires three settled entries into contests in the first week and the second week, with an entry fee band of a hypothetical ₹30 to ₹100, and the entries must be settled within the two-week window. Offer B's expiry is the end of the first week; the redemption path is a single settled entry into the stated venue's contest list, with no entry fee band stated because the credit is a free entry, and the entry must be settled within the first week. A reader who plans to read matches across two weeks cannot use offer B; a reader who plans to read only the first week's matches cannot use offer A efficiently because the offer's three-entry requirement exceeds the reader's planned entries. The mismatch is row four doing its work, and the row is where the offer stops fitting the reader's actual week.

Row five is cancellation and what happens to an unused credit. Cancellation is the rule that applies when the reader decides — at any point in the offer window — that the offer is not for them. The rule covers three questions: can the credit be cancelled, can the qualifying deposit be withdrawn, and what happens to any unused portion of the credit at the end of the expiry window. The offer screen often treats cancellation as a footnote, and the footnote is where the most expensive post-install surprises tend to appear.

The desk's habit, when filling row five, is to write three sub-rows in the same short format. The first sub-row is the cancellation right: whether the platform allows the credit to be cancelled at all, and the time window inside which the cancellation has to be requested. The second sub-row is the deposit behaviour: whether the qualifying deposit remains withdrawable after the credit is opened, or whether the platform treats the deposit as the entry fee for the credit and locks the deposit for the duration of the offer window. The third sub-row is the unused-credit behaviour: whether the unused portion of the credit is forfeit at expiry or whether the platform returns the unused portion to the wallet on a stated schedule. A reader who has all three sub-rows filled in for an offer has a way to walk away from the offer before the qualifying deposit is locked, and the walk-away is the row's purpose.

To close the running example, the two hypothetical offers diverge on row five in a way that is invisible on the offer screen. Offer A's cancellation right is unconditional within the first 24 hours; the qualifying deposit is fully withdrawable inside that window, and the unused portion of the credit is forfeit at expiry. Offer B's cancellation right is conditional — the reader can cancel only if no settled entry has been paid from the credit; the qualifying deposit is treated as the entry fee for the credit and is locked for the first week; the unused portion of the credit is returned to the wallet on a stated schedule at the end of the offer window. The two offers' headlines look similar; their cancellation rules do not. A reader who walks away from offer B after the first settled entry has been paid cannot recover the deposit during the first week, and that difference is row five doing its work.

The desk's comparison method, once the five rows are filled in for each offer, is to put the offers on the same printed sheet with the rows as the columns. Row one (eligibility) becomes the first column. Row two (trial-credit shape) becomes the second column. Row three (venue terms) becomes the third column. Row four (expiry and the redemption path) becomes the fourth column. Row five (cancellation) becomes the fifth column. The offers are the rows of the sheet, one row each, with the offer name at the left and the five-row read across the columns. The headline figure, if the reader still wants it, sits above the sheet as a reminder of what the offer screen showed.

The single most useful column, in the desk's experience, is the second column — trial-credit shape. Two offers with similar eligibility, similar venue terms and similar expiry windows often differ materially on whether the credit is a wallet balance, a free entry or a venue credit, and that difference decides whether the offer behaves like a bonus the reader can ignore or a coupon the reader has to use. An offer whose credit is a wallet balance can sit unused for a few days; an offer whose credit is a free entry into a stated contest has to be used on a stated date. The shape decides the urgency, and the urgency decides whether the offer fits the reader's actual week.

The second most useful column is the fourth column — expiry and the redemption path. Two offers with similar eligibility and similar credit shape often differ on the redemption path, and the path decides whether the credit is usable inside the reader's real week. An offer whose path requires three settled entries across two weeks is a different offer from an offer whose path requires one settled entry inside a single week, and the difference is in the column the offer screen rarely shows in full. The single sheet, with five columns and three or four rows, is how the desk keeps those differences visible without re-reading the offer screen.

The week-fit check is what the sheet is built for. Once the five rows are filled in for two or three offers, the desk asks a single question for each offer: does the offer fit the reader's actual week? The actual week is the week the reader has, with its stated reading schedule, its stated entry budget, and its stated willingness to be in the app on the dates the offer requires. The week is not the week the offer screen assumes, which is the week of a reader who has unlimited time and no other plans.

The desk's habit, when an offer does not fit the week, is to skip it without reading the rest of the offer's terms. The terms matter, but the fit matters more, and the fit has already been decided by the five rows. A reader who skips an offer can return to it later, after the week has changed or after a smaller qualifying deposit is feasible. The skip is a pause, not a refusal. The pause lets the reader pick a different offer or a different week without the offer clock running.

For the running example, a reader whose actual week is one evening of reading on the day of the offer's free entry will pick offer B and skip offer A, because offer A's three-entry requirement across two weeks exceeds the reader's planned entries. A reader whose actual week is three evenings across two weeks will pick offer A and skip offer B, because offer B's one-week window does not cover the second week of the reader's reading schedule. A reader whose actual week does not include any of the venues offer B lists will skip both offers. The week-fit check is the answer; the five-row sheet is the question; the offer screens are not the answer.

The five-row comparison sheet assumes the APK has been verified. A reader who has not yet verified the SHA-256 hash, the package name, the certificate and the file size of the APK is reading welcome offers on a file that may not be the platform the offer screen claims, and the comparison sheet on a non-official APK is a comparison sheet on an offer that may not exist. The file-verification checklist that sits a few pages back on the APK download reading desk is the slower read that the desk returns to before any welcome offer is opened. The combination — file verification first, comparison sheet second — is the desk's working order for the post-install session.

The same order rule applies to the offer window. A reader who has already deposited the qualifying amount and has already opened the credit is past the point where the comparison sheet does its best work. The sheet's purpose is to decide which offer to open; the sheet is less useful once one of the offers has already been opened, because the cancellation row of the open offer is the only row that still applies, and the other four rows have already been decided by the deposit that has already moved. The desk's habit is to fill the five-row sheet before any qualifying deposit moves and to keep the sheet on the desk for the duration of the offer window, so the week-fit check can be run against the sheet rather than against the offer screen.

The order rule is the only editorial point in this read that is not a row in the comparison sheet. The order is the desk's working habit, and the habit is worth a paragraph because it is the part of the read the offer screen does not advertise. The offer screen is built to convert the headline into a deposit; the comparison sheet is built to convert several offers into a single decision, and the single decision is best made before any of the deposits has moved.

For now, the next read is the three-figure cost-of-claim test that sits a page or two back on this desk, and the slower read on the welcome bonus headline that lives on the bonus-code page of this desk. Both fit inside the post-install window, and both leave the offer screens to the reader — as they should be. The desk is also drafting a shorter companion note on the venue eligibility lists most often changed between series, for readers who would like to know which of the five rows tends to be stable across a season and which tends to move without notice.

The five-row comparison sheet is the desk's working method for comparing welcome offers. It is not a complete framework for offer reading — it is a starter framework, and it is the framework the editorial team has found useful enough to publish. Readers who have a method of their own are welcome to keep it; the desk's only stake is that the five rows be written down before any qualifying deposit moves. The cost of accepting the wrong offer is a known number before it is a real number, and the comparison sheet is how the desk turns an unknown offer into a known one.