Scheduled client reports
Open a client case, choose Reports, then New schedule. Schedules are weekly or monthly, with an explicit timezone and local hour. Monthly schedules use days 1–28. They start paused, with Review before publishing selected.
Set the title, summary, scope, and recommendations. You may copy a report's saved layout and branding; later edits to that source report do not change the schedule. Enable the schedule when ready. The first approval window starts at activation.
Sources and delivery
A scheduled report includes evidence whose current client-visible revision was approved during the period. Optionally include newly shared notes. It never reruns a search or consumes search credits. Evidence collected earlier but approved during this period remains identified in the signed snapshot and rendered document.
Review mode prepares a private version to review and publish manually. Automatic publication requires explicit named client recipients. Access and evidence visibility are checked again before publication. Empty periods generate no report or email. Email notification also depends on the configured delivery system and recipient preferences.
There are up to 100 evidence records and 100 notes per run. Exceeding a limit pauses the schedule with a diagnostic; reports are not silently truncated. Trial, Teams, and Business support 1, 5, and 20 active schedules respectively, with up to 100 unarchived definitions per organization.
History and recovery
Run history distinguishes queued, ready for review, published, empty, and failed periods. Each run uses a fixed UTC cutoff. If several deadlines were missed, only the latest useful period is produced, marked as a catch-up; earlier missed periods are shown as outside coverage.
Pausing, editing, or archiving a schedule invalidates its pending publication authority. Revoking the scheduling member or recipient also prevents publication. Client and case archival pause schedules. A failed schedule requires explicit review and reactivation; reactivation starts a new window and does not silently publish an old backlog.
Schedules are configured by authorized internal members in the interface. They remain organization/client scoped; a personal subscription does not pay for them. Background execution uses the persisted schedule authority, not an expired browser login. Interactive changes still require the organization's SSO policy.
Private storage and interrupted renders
Reports and exports share the organization's private storage allowance: trial 100 MiB, Teams 1 GiB, Business 5 GiB. Each report format remains limited to 20 MiB. All four report files reserve space together, before any upload. Concurrent renders cannot reserve the same remaining capacity. This storage protection does not change search-credit charges.
Interrupted renders and expired worker attempts remain tracked and counted until their objects have actually been removed. Cleanup inspects up to 25 report files per pass, preserves active execution leases and files referenced by ready or published versions, and retries individual storage failures with backoff. It does not delete a completed report merely because its worker lease has ended. Exports likewise retain their referenced file for the advertised seven days unless the user deletes it sooner.
Storage and pending cleanup are visible in the workspace. Deleting stored files and deleting the whole organization are separate actions; see Reports and Data retention.