Check what enters the report before interpreting its total
If you selected one sphere and the work category, the report represents that scope within the date range. Do not present it as everything you did that week. Check the chosen dates, sphere and category before comparing numbers.
Reports are an Ora Pro feature. The public presentation describes reports by week, month or range, period comparisons, filters and CSV export. This guide’s invented example is solved from its own data, not from a real account.
Two spheres, two numbers answering different questions
Imagine a fictional Monday–Sunday range. In a sphere dated Monday, you recorded 30 minutes for one work activity and 20 for another. In a sphere dated Tuesday, you recorded another 40 work minutes. There are no other records in this example.
All spheres in the range with the work category total 90 recorded minutes: 30 + 20 + 40. Selecting only Monday’s sphere gives 50 work minutes within the same range: 30 + 20. Tuesday’s 40 minutes are excluded by that filter.
The missing 40 minutes are not a subtraction error. The selected set changed. Nor do the 90 minutes establish the total time spent in your weekly life: we are only adding the work records included in this example.
Check three choices without editing your records
First identify the question you want your report to answer. Then check its scope before drawing a conclusion.
- Range: check the start and end dates; a week’s name does not replace them.
- Sphere: check whether all or one is selected. Widening the dates does not remove a selected-sphere filter.
- Category: choose all categories or a particular one such as work. Do not label a subset as the overall total.
The CSV preserves different row types
Report exports include filter scope and both summary and detail rows. Do not add a summary to the activities it already summarizes. In the current CSV, record_type distinguishes row types; filter_plan_id and filter_category preserve filters, while from and to identify the range. These are file column names, not values you must type into interface controls.
Choose one data layer for your own calculation. For example, sum actual_seconds from the period’s activity rows without also adding summary, day or category rows. The file may also contain a previous-period comparison: identify row types before mixing values.
Planned and actual time are not interchangeable either. Without an actual-time record, this guide cannot infer how long you worked. Identify the missing data instead of replacing it with the plan.
Include scope in the sentence you share
A precise conclusion for our example is “50 recorded work minutes in Monday’s sphere within the Monday–Sunday range.” It is not “I worked 50 minutes this week.” Write that sentence first, then check each part against the filters.
The demo lets you explore Ora without registration; changes stay in that tab. Reading this guide verifies no account data and guarantees no productivity outcome. Check the available scope before choosing your next step.