Upload Filled Schedule

Distribute the template to your FSE team (email or SharePoint), then upload the completed CSV here. Rows are validated and any soft warnings can be fixed on the review screen before approval.

How it Works

1. Download the template, share with your team via email or SharePoint.
2. The team fills in the rows for their sites and uploads back to you.
3. You upload the completed file here. The system validates each row.
4. Review the batch on the next screen: fix any soft warnings, then approve per FSE.
5. Approved entries become preventive tickets visible in the FSE mobile app, and the FSE gets a digest email.

CSV Columns

The first six columns are required (first row is the header); job_type and priority are optional:

• site_code - must match an existing site code
• asset_label - general for whole-site PPM, or a device name / serial number
• fse_email - the assigned FSE's email; must be an active FSE/FSR/FST user
• scheduled_date - YYYY-MM-DD or DD/MM/YYYY (day first), with a four-digit year
• sla_hours - integer 1-720 (hours from scheduled_date until SLA breach)
• task_description - short description of the work
• job_type - optional: must match one of the job types listed below, exactly. Left blank or unrecognised, the row imports with a default and a warning you can correct on the review screen.
• priority - optional: low / medium / high / critical (defaults to medium)

Rows with soft warnings (unknown site, missing FSE, unrecognised job type) are still imported as pending entries; you can fix them on the review screen before approving. A row whose scheduled_date cannot be read is the exception: it is rejected outright, because the date cannot be stored to be corrected later.