A support message that arrives more than any other in analytics products: the number I looked at this morning is different now, and nothing happened in between. Nine times out of ten the cause is not a bug in the counting. It is the range.
If a dashboard opens on a rolling window, the last twenty four hours, then every refresh moves both ends of the window. A quiet hour drops off the back and a busy one joins the front, and the figure the operator screenshotted at nine has genuinely stopped being true by eleven. Nobody is wrong and everybody is annoyed.
The rule
Every range picker in Scalegram opens on Today, and Today means the calendar day of the person reading the screen, from their local midnight to now. Not the last twenty four hours. Not the server's day. This is one of the few conventions applied identically across every SINGUARD product, and it exists because we broke it once and spent a fortnight explaining numbers to people who were right to complain.
The effect is boring in the good way. The number stops moving for reasons the operator cannot see. Yesterday, once yesterday is over, is a fixed quantity forever. Two colleagues comparing screens are comparing the same thing as long as they are in the same city, and when they are not, each one sees their own day, which is the version they can act on.
Why the server's clock is the wrong clock
A server sits wherever it was convenient to put it. Ours are not chosen for the convenience of anybody's reporting day. If the panel counted a day from the server's midnight, an operator in Dubai would see their morning attributed to what they think of as yesterday, and an operator in Bucharest would see a different distortion in the other direction. Neither would be told about it.
Timestamps are stored in a single reference and converted for display, which is the ordinary way to do this. What is less ordinary is being disciplined about the boundary as well as the label. It is easy to convert the time shown on a chart point and still cut the range on the server's midnight, and the result is a chart whose labels are local and whose edges are not. That mismatch is invisible until somebody adds up the daily bars and gets a different total from the monthly figure.
One exception is worth stating plainly. Events that arrive from an outside system carry that system's own timestamp, and a payment confirmed at 23:58 in one timezone can legitimately belong to a different calendar day for the person reading it. The panel shows what it received and when, and does not quietly re-date anything.
Today is also the right default, not just the correct one
Correctness aside, Today answers the question people actually open the panel with. An operator checking a Telegram business is asking whether anything is happening right now: did the campaign launched this morning bring anyone in, did the flow that was edited at lunchtime break anything, is the bot answering. A seven day default buries today's signal inside six days of history and makes a fresh problem invisible for most of a week.
The longer ranges are one tap away and they are the right tool for a different question. Direction over a month is a line chart question, and it is worth reading with the rule from the dashboard walkthrough in mind: look at the slope, not at yesterday's height.
What this interacts with elsewhere in the product
The same clock discipline shows up in places that are not charts. Follow-up timing is written against the person receiving the message, so a nudge does not arrive at three in the morning in a market you never think about, which is covered in the follow-up rules. Quiet hours are read in the contact's local time rather than the operator's. Conversion events keep the timestamp they were confirmed at, so the number a pixel receives and the number the panel shows describe the same moment.
Ranked comparisons inherit the boundary too. A top ten list for Today is only meaningful if Today has one definition, otherwise the ranking silently includes a slice of last night for some readers and not others. How those lists are drawn is in reading the rank bars.
The failure mode we were avoiding
Here is the version of this bug that costs real money rather than just goodwill. An operator compares two campaigns on a dashboard with a rolling window. One campaign has been running for three days, the other for six hours. The rolling window flatters the newer one because its whole life sits inside the window while the older one is being judged on a partial slice. The operator moves budget to the wrong campaign and only finds out a week later.
Fixed calendar boundaries do not make that comparison good, since comparing campaigns of different ages is a flawed idea in the first place. They do make it possible to notice that is what you are doing.
What we ask of an operator in return
One thing: set the timezone on your account to where you actually work, and tell a new team member to do the same on their first day. Everything above is derived from that setting, and a colleague who left it on the default will keep seeing days that start at an hour that means nothing to them. On a team with per area permissions, it is worth adding to the same onboarding checklist as access, described in team permissions.
None of this is clever. It is the sort of decision that only gets noticed when it is wrong, which is a fair description of most of the work that makes a panel trustworthy.
"If a number changes when nothing happened, the operator stops believing every other number on the page. Fixed days are the cheapest trust you can buy in a dashboard."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Every range picker opens on Today, meaning the reader's own calendar day from their local midnight, never a rolling 24 hour window.
- Cutting on the server's clock produces charts whose labels are local and whose boundaries are not, which is invisible until daily and monthly totals disagree.
- Today is the default because it answers the question operators actually open the panel with: is anything happening right now.
- Set each user's timezone on their first day, since ranges, quiet hours and follow-up timing are all derived from it.
Frequently Asked Questions
Can I change the default range to something else?
Longer ranges are one tap away and the picker remembers what you are looking at while you work. Today is where every screen opens, because a fresh problem is invisible when it is buried inside a week of history.
Whose midnight is used when my team is spread across countries?
Each person's own. The range is derived from the timezone set on the account viewing the panel, so two colleagues in different countries each see their own day rather than a shared compromise.
What happens to an event that arrives near midnight?
It keeps the timestamp it was confirmed at, converted for display. Nothing is re-dated to make a day look tidier, so a payment confirmed just before midnight in one timezone can belong to a different calendar day for a reader elsewhere.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.