# 'last-saved' ODK feature

**URL:** <https://forum.communityhealthtoolkit.org/t/last-saved-odk-feature/3113>\
**Category:** Development\
**Created:** [October 18, 2023, 4:19pm UTC](https://forum.communityhealthtoolkit.org/t/last-saved-odk-feature/3113 "2023-10-18T16:19:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aboulle](https://communityhealthtoolkit.b-cdn.net/letter_avatar_proxy/v4/letter/a/e5b9ba/32.png) [@aboulle](https://forum.communityhealthtoolkit.org/u/aboulle)\
**Post date:** [October 18, 2023, 4:19pm UTC](https://forum.communityhealthtoolkit.org/t/last-saved-odk-feature/3113/1 "2023-10-18T16:19:00Z")

</div>

Hi all  
Is the feature to persist or carry forward previously saved data available in CHT?  
I see here other ODK implementations with this.

[![](https://communityhealthtoolkit.b-cdn.net/uploads/default/original/2X/5/5a3f552c9f87eac6710c81f560cb11966df1e303.jpeg "“last-saved” in ODK, KoBoToolbox, and XLSForm") ](https://www.youtube.com/watch?v=hRz4t8Zv8Dk)

For repeat visits to households where most data remain unchanged but need to be verified, this is an essential feature. I am new to the platform so might have missed this somewhere.

Thanks  
Andrew

---

<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:** [October 19, 2023, 7:02pm UTC](https://forum.communityhealthtoolkit.org/t/last-saved-odk-feature/3113/2 "2023-10-19T19:02:13Z")

</div>

The short answer is no, unfortunately the CHT does not support this `last-saved` functionality.

That being said, the CHT data-model is somewhat different from many other ODK implementations in that it supports a hierarchical structure, allowing for _normalized_ storage of contact data. In this context, data about a household is stored on the household’s contact document and _is not repeated in the reports submitted for the household_. Avoiding _denormalization_ of the household’s data into each report can save a huge amount of storage space (as well as avoiding having to re-enter this data when filling out each form).

> For repeat visits to households where most data remain unchanged but need to be verified

The CHT does have a couple features that may be useful in this context. For starters, an `edit` [contact form](https://docs.communityhealthtoolkit.org/apps/reference/forms/contact/) is able to automatically load the existing data for the contact into the form. The user can change the necessary values and save the form leaving everything else set to the previous values. Additionally, `app` forms are able to [load read-only contact data](https://docs.communityhealthtoolkit.org/apps/guides/forms/form-inputs/#loading-additional-contact-data) into the form. This would allow the user to review the contact’s data (but they could not edit it directly in the `app` form).