Skip to main content

The Scheduled Send

The Daily Report goes out through a Scheduler event, configured under Project Settings ▸ Scheduler. It appears on the Scheduler calendar alongside the project's other rules.

The Scheduler calendar, with the Daily Report event repeating alongside the other rules

Nothing is pre-provisioned — a new project starts with an empty Scheduler, so until someone creates a Daily Report event, no report is ever compiled or sent.

The SHOW chips above the calendar filter it by rule type, each with its own count. A Daily Report event shows on every date it fires, prefixed DR and stamped with its send time.

Configuring the event​

The Edit Scheduled Event panel for a Daily Report event

SettingNotes
Rule typePicked at the top of the panel — Daily Report, Submittal Overdue, Issue Overdue, Issue COB Digest, RFI Overdue, or Change Order Overdue
Event nameFree text; this is the label the calendar shows
RepeatsDaily or Weekly. Weekly requires at least one weekday chip; the picker locks the last remaining day so it cannot be unchecked
TimeThe send time — also shown as the deadline on the edit screen's warning banner
Time zoneOne of nine: Ho Chi Minh, Singapore, Bangkok, Tokyo, Seoul, Dubai, Sydney, London, UTC. A Next send line under the field previews the next firing in that zone
ToChip-style picker; at least one To recipient is required to save
CCChip-style picker; the same address cannot appear on both To and CC
Start dateWhen the event begins
End dateOptional
Active toggleTurns the event on or off
NotesFree text

Recipient suggestions come from the project's member directory. A valid email address that is not a project member is accepted as an external recipient.

There is no Monthly option

Daily and Weekly only. A daily report covers one day of site work, so firing it 30 days apart would skip 29 days of site record rather than summarize them. Other rule types, such as Submittal Overdue, do offer Monthly.

If you switch an event's rule type, a Weekly pattern you already selected is preserved as long as the new rule type also offers Weekly. It falls back to Daily only when the new type cannot show the recurrence that was selected.

What happens when the event fires​

For the whole project, in order:

  1. AECIS gathers every stakeholder's current report data — Report tab fields, attachments, photos grouped by zone in their saved order.
  2. It compiles one PDF per stakeholder, substituting the No Daily Report or No Photo fallback pages where they apply.
  3. It compiles one merged PDF covering every stakeholder — the ALL file.
  4. Every file is saved to the Reports archive under the archive naming convention.
  5. One notification email goes out for the project — not one per stakeholder.

The notification email​

One email per project per run.

Subject — the project abbreviation, DAILY REPORT, and the date:

[SAL][DAILY REPORT] 03-August-2026

Body, in order:

  1. Header logo.
  2. A greeting naming the report date and project.
  3. One line per stakeholder — a download link to their compiled report if they filed one, or a "no daily report" note if they did not.
  4. An automatic-notification disclaimer.
  5. A regards line from the sending system.
  6. A confidentiality notice.
  7. A "Powered by AECIS" line.
  8. A support contact line.

There are no file attachments — every stakeholder line is a download link, matching the archive's link-based access.