Skip to main content

Generating reports and evidence packs

Written by Sven Poppelmann

Generating reports and evidence packs

Reports assemble supported agreement, land and evidence records into a shareable document. The sections included depend on the report type; not every report embeds every file or audit event.

Where to start

Use the agreement's Reports tab or Generate Report menu action where offered. The farm's Reports page is the central report library; older My Reports links may redirect there.

  1. Choose a supported report type and the relevant agreement or year.

  2. Review the available options and generate.

  3. Wait for processing to finish and inspect the result.

Report status and sharing

In-progress reports show their processing state. Failed reports show the reason and retry controls. The Successful and Failed tab bar appears when failures exist.

Click a successful row to open its report. Use its download control for the PDF, or the available add-to-documents and sharing actions to publish it into the farm's document workflow. Opening a row is not the same as downloading it.

Organisation format

Authorised users can manage report branding and format under Manage organisation > Branding.

Before sharing

Check action codes, selected year, land assignments, evidence dates and approval status. Keep the source agreement and official submissions. A generated pack is only as accurate as the records included; it does not certify compliance.

Design this report

New reports open a preview while they generate. For a supported report, choose Design to change that report's margins and available sections. Non-ROC reports can choose an available brand; supported evidence packs can edit evidence descriptions. ROC offers its own photo and wording controls. Choose Apply and regenerate, wait for generation and inspect the finished output. These edits change this report, not your source evidence or organisation defaults. Controls differ by report type and permissions.

RPA submission packs with rotational actions include the claim year's recorded field placements where available, falling back to agreement history. Check those fields, areas and the source period; a generated pack does not submit the declaration.

Did this answer your question?