# Formula field calculating on date is returning wrong result **URL:** \ **Category:** Get Help\ **Created:** [February 18, 2026, 7:30pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409 "2026-02-18T19:30:51Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![christamae](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/christamae/32/13729_2.png) [@christamae](https://community.fibery.io/u/christamae)\ **Post date:** [February 18, 2026, 7:30pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/1 "2026-02-18T19:30:51Z")
I built my Sprint space using Fibery’s template. The “Status” field is a formula field that looks at the dates: ```auto If( Dates.End(false) < Today(), "Past", If( Dates.Start() <= Today() and Dates.End(false) >= Today(), "Current", "Future" ) ) ``` An example: 1. **Sprint End** date is 2/17/2026 2. **Today** is 2/18/2026 3. Sprint Status still shows _ **Current** _ ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b21298ff792e443b9896943606a77581be1595b8.png) So, whenever my Sprint End date is Yesterday, my sprint is still showing as “Current” – which is leading to 2 active sprints at the same time & making it confusing for my team looking at “Current Sprint Board”. If I change the End Date to 2 days ago (2/16/2026), then the status updates to “Past” Is this an issue with the formula? Something to do with UTC conversion? Something else entirely? Help appreciated! ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [February 18, 2026, 10:08pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/2 "2026-02-18T22:08:26Z")
> [@christamae](#): > > Something to do with UTC conversion? Exactly! Dates are stored UTC on the backend, and the Today() function runs every day at 00:00 UTC. Its quite annoying to people who are far off of UTC. It can solved using the new Periods Integration, since you can input your timezone there, and have it update every hour. Its a bit more complex to set up though with auto-linking… Maybe someone else has a simpler solution. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 18, 2026, 10:33pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/3 "2026-02-18T22:33:26Z")
I think the issue actually relates to how date ranges are stored: > **[Date Ranges in Formulas](https://the.fibery.io/@public/User_Guide/Guide/Date-Ranges-in-Formulas-42)** Timezones are not relevant if you are not using a datetime field: > **[Timezones](https://the.fibery.io/@public/User_Guide/Guide/Timezones-41)** ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 18, 2026, 10:33pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/4 "2026-02-18T22:33:57Z")
> [@RonMakesSystems](#): > > Dates are stored UTC on the backend No. Dates are stored as dates. Datetimes are stored in UTC on the backend ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [February 19, 2026, 8:15am UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/5 "2026-02-19T08:15:53Z")
Ah yeah, whoops. Don’t you think it still has to do with timezones? As in, if a user is in gmt-12, and has a formula that returns Today(), for 12 hours the date will be different to the date the user is actually in, no? Today() is based on UTC right? I think similar to this discussion: [Date out by a whole day](https://community.fibery.io/t/date-out-by-a-whole-day/8952) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 19, 2026, 9:27am UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/6 "2026-02-19T09:27:01Z")
You’re right that my answer was glossing over the fact that the value of `Today()` changes at midnight UTC, but since > [@christamae](#): > > **Today** is 2/18/2026 I assumed that this meant that the value of Today() had been confirmed as being 2/18/2026, but you’re absolutely right that @christamae may not have meant that, and may be writing the message in a timezone where `Today()` was not yet equal to today’s date(!) Thanks for clarifying that. ---
**Author:** ![christamae](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/christamae/32/13729_2.png) [@christamae](https://community.fibery.io/u/christamae)\ **Post date:** [February 19, 2026, 1:54pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/7 "2026-02-19T13:54:55Z")
Thanks, this actually helped, I think – I removed the “false” from my formula & things seem to be behaving as I expect. > This is because `.End(false)` returns the end date _as stored internally_ ( = value shown on UI + 1 ) For clarification, I work in CST time zone (UTC -06:00). I’m hoping this solution holds when we start our next sprint (next Weds) 🙏 ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 19, 2026, 1:58pm UTC](https://community.fibery.io/t/formula-field-calculating-on-date-is-returning-wrong-result/10409/8 "2026-02-19T13:58:38Z")
> [@christamae](#): > > For clarification, I work in CST time zone (UTC -06:00). I’m hoping this solution holds when we start our next sprint (next Weds) In that case, there is a possibility that the result will not be what you expect during the time period between 6pm and midnight every day (your time) during which Fibery thinks that tomorrow has already arrived.