Decide what counts before reading the total
To compare two days in Ora, use consistent date and sphere criteria, keeping planned time separate from recorded time. CSV lets you work with the exported data; it does not decide whether two plans belong to one day or turn a missing record into zero minutes of work.
Weekly, monthly and custom civil-date reports, sphere and category filters, and CSV export are Pro features. Production uses the saved workspace and requires authenticated access. Demo previews use local data; they do not establish what happened in your account.
Prepare a small, explicit comparison
Start with an answerable question: “How much did I plan and record for preparing the document on these two days?” Choose the civil dates and a relevant sphere, such as your work plan. If the category filter changes between queries, document it or repeat both with the same scope.
This fictional example is not a user outcome: Monday has 60 planned minutes and 70 recorded minutes; Tuesday has 60 planned minutes and no activity record. Monday shows ten recorded minutes above plan. Tuesday does not establish a zero-minute duration: that record is missing.
Preserve the absence when discussing the result. “I can only compare Monday’s recorded duration” is more useful than manufacturing an average from one observation and one missing value.
Two Tuesday spheres are not two separate days
Ora supports multiple spheres. You can keep an alternative plan for the same date and another routine without their names alone proving which plan you used. Before adding totals, review how the report identifies dates, spheres and alternatives.
In our example, “usual Tuesday” and “Tuesday with a visitor” are two proposals for one Tuesday. Do not present them as two completed working days. If one preserves a discarded plan, keep that alternative status visible when interpreting its numbers. Reports explicitly identify alternatives for a date and missing data; your commentary should preserve that distinction.
Review the CSV before turning it into a conclusion
After setting the scope, export the report and check that its dates and sphere match your question. Keep planned and recorded values separate. If you filter or sum in an external spreadsheet, document that operation beside the result.
Avoid adding focus or break journals to activity totals as extra work: they are separate records. Nor should every minute in a plan be described as completed work. Check which record a value comes from first.
You might add a reading note: “Selected dates, work sphere, document category; Monday recorded, Tuesday missing.” That note is a manual suggestion from this article, not a required field or an automation attributed to Ora.
Use the report to choose the next check
If Monday’s record includes different tasks, narrow the scope before changing your next estimate. If Tuesday has no record, decide how you want to record a future session. A report cannot reconstruct time you never saved.
Ora shows planned versus recorded time and offers reports covering up to 366 days, adjacent-period comparisons and CSV. No report guarantees productivity or attributes change to a tool through these examples. Review the current features and plan before deciding whether they suit your work.