Submitting & Approving

The daily log review workflow — submitting, the approval queue, returning with a note, and who is allowed to do each.

Quick Summary
  1. Open a draft and press Submit — at least one substantive section must be filled in
  2. The log locks. It can no longer be edited or deleted
  3. Approvers see it on the Daily Reports tab, badged Pending
  4. Open it from that tab to get the Approve and Return buttons
  5. Return needs a note; the log goes back to draft with a Returned for edits banner
  6. Approve is final — approved logs are permanent and cannot be reopened

Submitting

Submit appears on the bottom bar of a draft log's detail page, next to Save Draft.

Before the log will go, at least one of these must be filled in:

  • Manpower — a row with both a company and a headcount above zero
  • Work Performed — a row with both an area and a description
  • Delays — a row with both a description and a duration above zero
  • Notes — any text

If none of them is, a message asks you to fill in at least one before submitting. Weather, equipment, visitors, safety and photos on their own are not enough — the log has to say something about the work.

Confirm in the Submit Daily Log dialog. Once submitted, the log is read-only: "This log is pending review and cannot be edited."

The Approval Queue

Submitted logs land on the Daily Reports tab of the register, which carries a badge with the count waiting. Cards there are badged Pending.

The approval queue — every submitted log, with a count on the tab

Open the log from the queue

Approve and Return only appear when you open a log from the Daily Reports tab. Reaching the same log from the My Logs list opens it in plain read-only view, without the reviewer's controls.

Approving

Approve on the bottom bar signs the log off. The banner changes to "This log has been approved and is read-only." Approval is the end of the line — there is no un-approve and no route back to draft.

Approved logs are also the only ones that feed a client report. A log left in draft or sitting in the queue contributes nothing to a compiled report.

Returning for Changes

Return sends the log back to its author as a draft.

1

Press Return

The Return Daily Log dialog opens with one field, Note for the author.

2

Explain what needs correcting

The note is required — Return Log stays disabled until you have written something. Be specific: the author sees exactly this text.

3

The author picks it up

The log reappears as a draft carrying a Returned for edits banner with your note and the date it was returned. They correct it and submit again, which clears the note.

Who Can Do What

Daily logs use their own permission set, so this does not follow whatever a role can do elsewhere.

RoleCreateReadEditDeleteApprove
OwnerYesYesYesYesYes
Project managerYesYesYesYesYes
SuperintendentYesYesYesYes
ForemanYesYesYes
Everyone elseYes

Two rules sit on top of that table:

  • You cannot approve a log you submitted yourself. This is enforced on the server, not just hidden in the interface — approval always needs a second person.
  • Only drafts can be edited or deleted. Once a log is submitted, both are closed off, whatever your role.

The Approval Setting

Whether review is required at all is a project setting: Daily Log Approval Required, under the project's settings, on by default. The Daily Reports queue and the Approve and Return buttons only appear while it is on.

Notifications

Each transition raises an in-app notification: Daily Log Submitted, Daily Log Returned and Daily Log Approved.