Track airdrop deadlines from Telegram
Track airdrop deadlines by giving each item one source link, one explicit time zone, one last-checked time, and one status. Keep messages without an owner-confirmed date in an undated queue instead of assigning them a deadline.
Start with one time zone
Choose a display time zone before adding deadlines. Preserve the source time and zone beside the converted value so another reviewer can reproduce it. If a message says only today or tomorrow, record the message timestamp and leave the final deadline unresolved until an owner-controlled source gives a full date and time.
Do not sort an undated item into the next twenty-four hours just because the copy sounds urgent. Put it in a separate undated queue. This prevents an old forward or a different regional clock from creating a false deadline and crowding out better-supported work.
Use one row per action window
A tracker row should contain project, action, start, end, time zone, eligibility note, source link, last checked, and status. Split separate phases into separate rows. Registration, testnet activity, claim, and withdrawal may have different dates and conditions even when a Telegram message presents them as one campaign.
Keep reward language out of the deadline field. The tracker answers when a documented action window opens or closes. It does not predict eligibility, allocation, profit, or token value. When those claims matter, link them to a separate verification note and keep the deadline row factual.
Record changes instead of overwriting them
When an official source changes a date, keep the previous value and add the new one with its observation time. Mark the old row superseded. This gives the reviewer a short history and explains why an earlier reminder changed. Quietly replacing the date removes evidence that may matter later.
Community corrections can trigger a recheck, but they should not change the canonical deadline alone. Find the matching project source and compare the update. If the owner has not confirmed the change, keep the current row and add an unresolved discrepancy rather than selecting the most repeated message.
Review the tracker in a fixed daily pass
Run a bounded review at the same time each day. Check items due soon, then unresolved conflicts, then new messages. Record the review time even when nothing changes. A stable cadence makes missed evidence visible and avoids scanning the full Telegram history every time a new message arrives.
Close completed, expired, or disproved rows with a source-backed verdict. Carry unresolved rows forward with one next check. Never turn no new evidence into completed, and never turn an absent deadline into no deadline. The tracker should preserve what is known and make the next review small.