Reports ​

Reports turn captured Airtable activity into a short operational briefing. Start with the useful outcome, then open the supporting activity when you need to check a conclusion.

A daily report at a glance ​

Example of a generated report from captured activity.

Use daily and weekly reports ​

  • Daily reports help you catch up on recent work. Use them to see what was completed, what changed, and what needs attention after a day of activity.
  • Weekly reports summarize the completed week. Use them to discuss delivery progress, movement in important measures, and work that still needs an owner or client response.
  • Supporting activity lets you check the source history behind a summary for that report’s period.

Each report is tied to a time window and its captured activity, so a briefing can be sparse or incomplete when the underlying history is delayed or out of scope.

Interpret results in context

Orloi works from the activity captured within your selected scope. When a result matters, check its time range and supporting activity. A connection or processing warning can make the newest period incomplete.

Tell Orloi what to emphasize ​

Report instructions are optional. Open the connected base’s AI report settings, enable the daily or weekly cadence you want, and add a short instruction about the operational question that matters to your team. Instructions change emphasis and presentation; they do not expand the selected Airtable scope or replace the captured history.

Useful positive instructions include:

  • “Highlight completed deliverables, client approvals, and work at risk of missing launch dates.”
  • “Start with progress and wins, then list items that need an owner or client response.”

You can use separate instructions for daily and weekly reports. For example, a daily instruction can emphasize approvals and launch risk, while a weekly instruction can ask for progress first and a clear follow-up list second.

Report settings show enabled daily and weekly reports and instructions that start with progress and wins before follow-up items.
Advanced report behavior

These rules explain report scheduling, stored metadata, and recovery behavior for operators and advanced readers.

Periods, timezones, and availability ​

  • Daily reports cover one completed local calendar day.
  • Weekly reports cover the completed local week and combine the saved daily-report context for that week. Weekly reports require daily reports to be enabled.
  • The report timezone is stored with each report. When report settings are updated, Orloi saves the browser’s timezone. If no valid report timezone is configured, Orloi falls back to UTC.
  • Report boundaries are local midnights, so a daylight-saving transition can make a calendar-day window shorter or longer than 24 hours. Read the displayed period and stored window rather than assuming every report represents exactly 24 hours.
  • Daily and weekly reports are configurable outputs and are disabled until you enable them in AI report settings. The automatic provider is used only when reports are enabled and the provider remains set to Auto. Disabling daily reports also disables weekly reports; disabling reports does not stop capture, remove stored activity, or prevent metrics calculated without AI from being stored.
  • A missing report can mean that its period is incomplete, the cadence was disabled, processing failed, or no terminal report was saved. Missing or failed daily windows can also make a weekly briefing incomplete; check the relevant activity and report status before treating the gap as a result.

Stored report lifecycle and inputs ​

Report work can include preparing its input, generating and formatting content, saving the result, and optionally delivering email. The stored report record retains its cadence, time window, processed-activity count, status, model and token metadata, validation links, delivery state, and an error message when generation fails.

Reports use bounded processed activity, configured metric context, saved daily-report context for a weekly report, and reference data needed to render related Airtable links and labels. A report reflects only captured and processed activity for its window. Processing lag, sparse history, insufficient comparison windows, or a scope change can make a briefing delayed, sparse, or incomplete.

When a full report is open, the workspace can download the rendered report as an HTML file. The export is a copy of the report presentation, not a replacement for the stored supporting activity.

Retry, failure, and delivery behavior ​

An unsuccessful report appears as Failed and shows its error instead of a report body. Automatic retry is handled by Orloi’s task system and depends on the underlying failure. If a report remains failed or delayed after capture and processing are healthy, use the operational task history and stored report metadata to investigate. Regeneration and email resend are administrative operations for an operator after the cause is understood.

Email delivery is optional and is stored separately from report generation. A report can be generated successfully while its email delivery fails; the stored report and captured activity remain available in the workspace while the delivery issue is addressed.

For bounded report metadata and direct database investigation, use the AI agent access and SQL and BI guides under Advanced.