Skip to main content

Creating a Client Report

Standard Operating Procedure (SOP) for creating a new client report in EnviroAutomate, including selecting the report type, associating a project and site, linking fieldwork tasks, and assigning a report writer and reviewers.

T
Written by Trin Murphy

Objective

Create a new client report by selecting the report type, linking it to a project and site, associating fieldwork tasks, and assigning team members for writing and review.

Prerequisites

  • A Project and Site must already exist in the system

Key Steps

1. Navigate to the Create Page

  • In the left sidebar, click Client Reports

  • Click the Create Client Report button at the top of the list page

2. Enter General Information

  • Name (required) - Enter a descriptive name for the report

  • Document Code (required) - Leave blank to auto-generate a code when a project and site are selected, or enter a custom code manually

  • Report Type (required) - Select the type of report from the dropdown. The available report types depend on your organisation's configuration

  • Description / Notes (optional) - Enter any additional context or instructions for the report

3. Set Associations

  • Project (required) - Select the project this report belongs to. Changing the project will reset the site and fieldwork task selections

  • Site (required) - Select the site for this report. The site dropdown is populated based on the selected project. When a site is selected, the document code will auto-generate if left blank

  • Fieldwork Tasks (optional) - Select one or more fieldwork tasks to associate with this report. The available tasks are filtered by the selected project, site, and report type. A message below the field indicates how many fieldwork tasks are required for the selected report type, or states that no specific fieldwork task requirements apply

4. Check the Sibling Tasks Notice (if shown)

When you pick a single fieldwork task that has sibling tasks (for example Soil Classification tasks that should be combined into one report), an info alert appears below the field. It lists the Primary tasks (locked, supplies primary fields) and each sibling task with a ticked checkbox. Untick any sibling you want to exclude from the report. If no notice appears, the selected task has no siblings.

5. Assign the Team

  • Report Writer (optional) - Select the user responsible for writing the report. A report writer must be assigned before documents can be generated.

  • Report Reviewers (optional, multi-select) - Select one or more users to review the report. At least one reviewer must be assigned before documents can be generated.

  • Report Approver (optional) - Select the user who will sign off the report. Optional for most report types but required by some (for example PSI uses the Report Approver as the "Approved by" signatory on the Document Control page).

6. Set the Timeline

  • Start Date (optional) - Set when work on the report begins.

  • Due Date (optional) - Set the target completion date.

  • Historical Data Reporting Cutoff Date (optional) - Set the cutoff date for historical data included in this report. Use this when the report should only consider events on or before a specific date.

7. Save the Report

  • Click Save to create the client report

  • Click Close to return to the list without saving

After saving, you will be taken to the edit page where additional tabs are available depending on the report type (Report Settings, Additional Data, Draft Documents, and Review and Approve).

Cautionary Notes

  • The Report Type cannot be changed after the report is created. Ensure you select the correct type before saving.

  • A Report Writer and at least one Report Reviewer must be assigned before you can generate report documents on the Draft Documents tab.

  • A Report Approver is optional in general but is required by some report types (notably PSI). If a PSI report has no approver assigned at generation time, the "Approved by" section of the Document Control page will be left blank with a warning in the processing messages.

  • Fieldwork tasks are filtered by report type. If you change the report type, previously selected fieldwork tasks may be cleared.

  • The document code auto-generates only when the field is empty. If you have already entered a custom code, selecting a new site will not overwrite it.

Tips for Efficiency

  • Assign the report writer, at least one reviewer, and the approver at creation time so the report is ready for document generation immediately.

  • If you are unsure which fieldwork tasks to link, you can add or change them later on the General tab of the edit page.

  • Use the Description / Notes field to record any special instructions or scope clarifications that the report writer should be aware of.

  • Set the Historical Data Reporting Cutoff Date if the project explicitly excludes any data after a known date (for example a sale-of-site cutoff).

Did this answer your question?