What is the Operational Notes section for?

The Operational Notes section allows you to capture job-specific observations, instructions, or supporting information that's not caotured in the standard sections of a job. This video explains how it fits into your workflow.

The Operational Notes section in Dronedesk provides a flexible space to capture additional job-specific information.

A common use case might be for agricultural spraying, where you need to record details like spray rate, spread, or other relevant data that wouldn’t normally be included in a standard drone job. This allows you to retain non-standard information as part of the same job in the system.

To create a custom layout for Operational Notes, start with a blank page. For example, if you already have a form or table set up elsewhere, you can copy it using Ctrl+C and paste it into Dronedesk using Ctrl+V.

When you paste the table into Dronedesk, you’ll likely notice that the formatting is not preserved. This is expected, and you may need to manually clean up the formatting. The good news is that this is a one-time setup—once you've created and saved the format, you won’t need to repeat the process.

To style the table:

  • Right-click and open Table Properties to add borders and set a border colour

  • Use Cell Properties to apply background colours, such as light grey, to make labels stand out

  • Resize and adjust layout as needed

You can also insert placeholders into the table for dynamic job data. For example:

  • In the Location cell, insert the Location Reference placeholder

  • For the Pilot, insert the Pilot Name

  • For the Date, use the Job Start Date

  • Leave fields like Spray Rate, Spread, and Additional Notes for the pilot to complete after the job

Once the layout is complete, click Save.

Assuming the Operational Notes section is enabled in your Job Sections settings, the updated content will now appear automatically in all new jobs.

Keep in mind that this change will only apply to jobs created after the update. Existing jobs are not affected, because each job gets its own individual copy of the Operational Notes section at the time it is created.

Did this answer your question?
😞
😐
😁