--- title: "CSV Schedule Upload" slug: "csv-schedule-upload" updated: 2026-03-24T20:15:17Z published: 2026-03-24T20:15:17Z canonical: "docs.verdi.ag/csv-schedule-upload" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.verdi.ag/llms.txt > Use this file to discover all available pages before exploring further. # CSV Schedule Upload This document explains the format required for CSV files when importing irrigation schedules into the Verdi Dashboard. ![](https://cdn.document360.io/21bcacda-1800-45ee-8df3-7d1d6186e001/Images/Documentation/image(252).png?sv=2026-02-06&spr=https&st=2026-11-19T04%3A38%3A15Z&se=2026-11-19T05%3A38%3A15Z&sr=b&sp=r&sig=%2BS7jcll4Dw7wZfjoiX8Im2Od1Uq1vqyZbGkt%2BbzUe8w%3D) Upload CSV file at [https://app.verdi.ag/settings](https://app.verdi.ag/settings) ## Required Columns Your CSV file must include the following columns | Column | Description | Example | | --- | --- | --- | | Zone | The name or ID of the zone to irrigate | "Block A" or "zone-123" | | Start | The start date and time of the irrigation | "2023-06-01 08:00" | | Duration | The duration of irrigation in minutes | "60" | ## Optional Columns The following columns are optional but provide additional control | Column | Description | Example | | --- | --- | --- | | End | End date for repeating events | "2023-12-31" | | RepeatEvery | Number of days between repeats | "3" | | RepeatOnDaysOfWeek | Days to repeat (su,mo,tu,we,th,fr,sa) | "mo,we,fr" | | Hours | Hours component of duration (alternative to Duration) | "1" | | Minutes | Minutes component of duration (alternative to Duration) | "30" | ## Column Name Flexibility All column names are case-insensitive. The system recognizes various alternative column names: - **Zone**: "Zone", "BlockName", "Block" - **Start**: "Start", "StartDate", "Date" - **End**: "End", "EndOn", "EndDate", "LastEvent" - **RepeatEvery**: "RepeatEvery", "RepeatEveryNDays", "RepeatEveryN" - **RepeatOnDaysOfWeek**: "RepeatOnDaysOfWeek", "RepeatOnDayOfWeek" ## Zone Identification You can identify zones using either: - The zone's name (e.g., "Block A", "North Field") - The zone's ID (e.g., "zone-123", "64f5a2b7e12c456789abcdef") ## Duration Formats Duration can be specified in several formats: - As minutes: "60" (60 minutes) - As hours and minutes: "1:30" (1 hour and 30 minutes) - As separate hours and minutes columns: Hours="1", Minutes="30" ## Date and Time Formats All times are interpreted in the local time zone of the user's computer, unless a specific timezone is included. The following formats are accepted: - ISO 8601 format: "2023-06-01T08:00:00" - ISO 8601 with timezone: "2023-06-01T08:00:00Z" (UTC) - ISO 8601 with timezone offset: "2023-06-01T08:00:00-07:00" (PDT) - Date with time: "2023-06-01 08:00" - Natural language: "June 1, 2023 8:00" We recommend using ISO 8601 with timezone information as it is the most unambiguous: - "2023-06-01T08:00:00Z" (UTC/GMT) - "2023-06-01T08:00:00+00:00" (UTC/GMT) - "2023-06-01T01:00:00-07:00" (Pacific Daylight Time) - "2023-06-01T03:00:00-05:00" (Eastern Daylight Time) - "2023-06-01T09:00:00+01:00" (British Summer Time) ## Example CSV Files Basic Single Irrigation ```plaintext Zone,Start,Duration "Block A","2023-06-01 08:00",60 "Block B","2023-06-01 09:00",45 ``` Repeating Irrigation (by interval) ```plaintext Zone,Start,Duration,RepeatEvery,End "Block A","2023-06-01T08:00:00",60,3,"2023-08-31" "Block B","06/01/2023 8:00 AM",90,7,"08/31/2023" ``` Repeating Irrigation (by weekday) ```plaintext Zone,Start,Duration,RepeatOnDaysOfWeek,End "Block A","2023-06-01 08:00",60,"mo,we,fr","2023-08-31" "Block B","June 1, 2023 8:00","1:30","su,sa","August 31, 2023" ``` Using Hours and Minutes Instead of Duration ```plaintext Zone,Start,Hours,Minutes,End "Block A","2023-06-01 08:00",1,30,"2023-08-31" "zone-123","01/06/2023 08:00",2,15,"31/08/2023" ``` ## Notes and Limitations - Duration must be at least 10 minutes (600,000 milliseconds) - If no end date is specified for repeating events, the system defaults to 1 year from the start date - The system will attempt to match zone names even if they're not exact matches - Times should be in 24-hour format or include AM/PM designation - All times are interpreted in the local time zone of the user's computer, unless a timezone is explicitly specified in the time string - For timezone-specific scheduling, use ISO 8601 format with timezone information (e.g., "2023-06-01T08:00:00-07:00") - See [https://en.wikipedia.org/wiki/ISO_8601](https://en.wikipedia.org/wiki/ISO_8601) for more details on ISO 8601 format - You can give this documentation page to an LLM like ChatGPT and ask it to create an irrigation management plan (in the Verdi accepted CSV format) for you based on additional context you provide.