Skip to main content

Preview and Submit

Preview is a full-screen surface showing the real compiled report — the same PDF the scheduled send would produce for the project's currently configured send time, built from the report's data as of the moment you open it.

It is not a mock-up or an approximation: what you see is what would go out.

The Preview surface, with Download PDF and Submit report

Opening Preview​

Preview is blocked until validation passes. If a numeric field holds text, AECIS returns you to the Report tab so you can fix it first.

Three actions that are easy to confuse​

ActionWhat it doesWhat it does not do
SubmitWrites the moment you press the button — date and time — into the roster's Submission column, and shows a confirmation dialogDoes not produce a PDF file, does not archive anything, does not send an email
Download PDFDownloads the rendered PDF you are looking at, on demandDoes not stamp completion, does not create an archive record
Scheduled sendCompiles every stakeholder's report, files the PDFs in the archive, and emails the projectRuns on its own schedule — it is not triggered by Submit

Submit is the only place a report's completion is recorded. There is no separate status field and no approval workflow — one stamp, and it is done.

Submission Date is the click, not the day

The Submission Date is the timestamp of the button press itself. It is not the date the work happened, not a date you can pick, and not the time the scheduled send runs.

Press Submit at 22:40 and the roster carries 22:40. Leave the same report untouched and press Submit the next morning instead, and it carries the next morning — the report's contents make no difference to the stamp.

Because the module has no status field, this timestamp is the project's only record of when a stakeholder declared their report done. It is an audit trail: submit when the report is actually finished, not in advance and not long after.

What the compiled report contains​

Every page shares a header (report title, project name, date, reporter name, project logo) and a footer (license logo, page number, partner logo).

#PageContents
1Main data pageReporter name and submission date; a General Summary laid out as three columns — Planned progress %, Actual progress %, and Working hour period — each with its remark on the row directly beneath it; Health and Safety (incident count, incident-impact hours, remark); Equipment Summary (total quantity + remark); Man Power Summary (total quantity + remark)
2PDF attachmentsThe stakeholder's uploaded PDFs, inserted as-is right after the main data page
3Per-zone photo pageOne section per zone, headed by the zone name, photos in a grid sized to the count
—No Daily Report pageUsed instead of pages 1–3 when the stakeholder filed nothing

The two fallback pages​

Both use the same design — a centred stakeholder name plus a short message — and differ only in wording and where they are inserted:

ConditionResult
The stakeholder filed no report at allA single "No Daily Report" page replaces their entire report
The stakeholder did report but uploaded zero photosA "No Photo" page is inserted at the photo section's position only; the rest of the report renders normally