# CHT Targets Feature: Display data in Nepali Calendar (Bikram Sambat)

**URL:** <https://forum.communityhealthtoolkit.org/t/cht-targets-feature-display-data-in-nepali-calendar-bikram-sambat/5515>\
**Category:** Technical Support\
**Created:** [February 19, 2026, 6:04am UTC](https://forum.communityhealthtoolkit.org/t/cht-targets-feature-display-data-in-nepali-calendar-bikram-sambat/5515 "2026-02-19T06:04:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bhishan\_KC](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/bhishan_kc/32/1839_2.png) [@Bhishan\_KC](https://forum.communityhealthtoolkit.org/u/Bhishan_KC)\
**Post date:** [February 19, 2026, 6:04am UTC](https://forum.communityhealthtoolkit.org/t/cht-targets-feature-display-data-in-nepali-calendar-bikram-sambat/5515/1 "2026-02-19T06:04:35Z")

</div>

Recently, we deployed the **Targets** feature in the CHT app. However, the data is currently displayed in the **Gregorian calendar instead of Nepali calendar (Bikram Sambat).** Since the **Nepali calendar (Bikram Sambat)** is officially used in Nepal, our users have requested that data in the **Targets feature** be displayed in the Nepali calendar.

I would like to request the forum leads for the necessary support.

Thank you!

cc @nitin @jkuester

---

<div class="post-metadata">

**Author:** ![jkuester](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/jkuester/32/806_2.png) [@jkuester](https://forum.communityhealthtoolkit.org/u/jkuester)\
**Post date:** [February 19, 2026, 6:14pm UTC](https://forum.communityhealthtoolkit.org/t/cht-targets-feature-display-data-in-nepali-calendar-bikram-sambat/5515/2 "2026-02-19T18:14:51Z")

</div>

@Bhishan_KC thanks for raising this! Please have a read through this issue I logged:

> <https://github.com/medic/cht-core/issues/10652>
>
> \*\*Is your feature request related to a problem? Please describe.\*\*
> Requested \[on… the forum\](https://forum.communityhealthtoolkit.org/t/cht-targets-feature-display-data-in-nepali-calendar-bikram-sambat/5515).  
> 
> Currently \[CHT Targets\](https://docs.communityhealthtoolkit.org/building/targets/) and UHC counts are collected and stored per user \_per Gregorian calendar month\_. It is possible to customize the \_day of the month\_ that target collection begins/ends by setting the \[\`uhc.visit\_count.month\_start\_date\` value\](https://docs.communityhealthtoolkit.org/building/forms/configuring/uhc-mode/#settings) in the settings. This allows for adjusting target collection to be based on the \`nth\` day of the month instead of the \`1st\`, but this value is bound to the day of the Gregorian calendar month.  
> 
> In regions that use the Bikram Sambat calendar, reporting cycles may be tied to BS months and not Gregorian months. In this case we would want the Target/UHC counts to reset at the beginning of the BS month (or in a fixed interval of days from the beginning of the BS month). 
> 
> \*\*Describe the solution you'd like\*\*
> 
> We should add configuration that would allow aligning the Target/UHC counts to reset at the beginning of the BS month instead of the Gregorian calendar month.  
> 
> @bhishankc a key question here that maybe you can help with is: \`Is it possible for a BS month to ever start and end within the same Gregorian calendar month?\`
> 
> If the answer is "no" (it is not possible), then I think the code changes necessary to support this feature should be localized to just the date logic we use for calculating when the intervals should start/stop. The updates may not be "simple", but they will be limited in scope.  
> 
> If the answer is "yes", then things get more spicy. Currently target documents are stored for each user with an identifier that includes the \`YYYY-MM\` value for the Gregorian month. If two BS months can \_start\_ in the same Gregorian month, then we may have a collision for our target identifiers. Any resolution here would seem to involve challenges with compatibility when enabling/disabling this configuration. (Maybe that is fine 🤷).

Let me know if I missed something or misrepresented anything. 👍
