I have an app that involves large amounts of data that for the most part live-updates. That is, the users of the app can assume the data is fresh and up-to-the-moment.
We are about to release a new feature of the app called a report, which aggregates some of the app's data and displays it as pretty charts, graphs, insights, etc.
The data for this report WILL NOT be live-updating, so at the point that a user generates the report, we have added a notice about when the data was last aggregated:
Users can view the report in a browser, or they can choose to download the report as a PDF to share internally with the rest of their organization. For that reason, there is another date that displays on each page of the generated report which indicates when the report was actually created – i.e. the moment is was downloaded to PDF.
During QA, it has become apparent that users understand neither the data-aggregation date nor the date showing when the report was created.
My questions are these:
- How can I better explain in the notice what the data aggregation date indicates?
- Should the date inside the report mirror the data aggregation date or should it indicate when the report was created/downloaded?
- Are there better overall approaches I could take to conveying this info to users?