# Earlier deadlines unfriendly to QS info (i.e. data is incorrect)

**URL:** <https://forum.beeminder.com/t/earlier-deadlines-unfriendly-to-qs-info-i-e-data-is-incorrect/1277>\
**Category:** Bugabee\
**Created:** [October 21, 2015, 12:25pm UTC](https://forum.beeminder.com/t/earlier-deadlines-unfriendly-to-qs-info-i-e-data-is-incorrect/1277 "2015-10-21T12:25:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [October 22, 2015, 8:18am UTC](https://forum.beeminder.com/t/earlier-deadlines-unfriendly-to-qs-info-i-e-data-is-incorrect/1277/6 "2015-10-22T08:18:31Z")

</div>

This is convincing me that, at the very least, @philip is right that the CSV export should include the calendar dates. That might be a nice simple #UVI in fact. (No separate export though, just throw in an additional column.)

@chipmanaged, you are amazing. Thank you so much for the incredibly thoughtful feedback.

Until we get to this, I think the workaround, as you suggested, is to stay hyperaware of the deadline as end-of-day and remember to enter data after it as “yesterday”. Also I just remembered that @philip and I argued about this way back when in the context of the confusion of graphs being red despite not being due till tomorrow. I’ve gotten pretty used to it – red just means \<24h – but it’s maybe not ideal.

PS: I’m laughing at the irony of “worse-is-better is better in theory”. I mean, in _theory_ worse is, presumably, worse, but in practice it’s better. Something like that. That was probably your point.

---

_[View the full topic](https://forum.beeminder.com/t/earlier-deadlines-unfriendly-to-qs-info-i-e-data-is-incorrect/1277)._