Report Scheduling Best Practices

Some best practices to consider when scheduling reports are as follows:

Avoid excessive reports and potential performance issues by planning for the report contents before submitting it to run. Choose the report design and filters appropriate to the required output.
For reports that run regularly, particularly large reports, where feasible, schedule them to run outside of the usual business hours.
When setting the schedule time, avoid regular maintenance times, when the server may be being taken down.
For reports that focus on data at a point in time, take into account that users who enter the data may have their working day in a different time zone.
Ensure other recipients of the report have permission to access the report and the data therein. Recipients will only be able to view the report output if they are a user of the system with access to the Report module.

Note that other than any EAC Area restrictions, it is possible for a report to contain data that a recipient would not usually have access to when accessing Supplier Evaluation. For further details on the reporting permissions rules, see Appendix: Permissions.
Select the report output formats (typically Excel or PDF) that are appropriate to the report type and the recipients. Avoid choosing more formats than are necessary.
After submitting a report to run, avoid repeatedly resubmitting it while waiting for it to complete. Use the schedule monitoring facility (see Monitoring Scheduled Reports).
Where it is not necessary to retain previous versions of the report, use the option to overwrite existing report outputs rather than creating a new output each time the report is run.
Delete report outputs that are no longer required, rather than relying on the automated purging.
If historic copies of the report are required to be retained, save the report output to a local or network location rather than storing them within the system.