---
title: Create To-Do Lists
slug: help/en-us/pulse/create-to-do-lists
docTags: 
createdAt: 2026-02-09T13:08:55.444Z
---

Before you can process your to-do lists in PULSE or the mobile app, you must first generate them in PULSE, or set them up in DairyComp with the \K switch and then send them to PULSE. PULSE then sends them out to the mobile app in its next care package update.

Expand the sections below to learn more:

:::ExpandableHeading{isOpen="true"}
## Create To-Do Lists in PULSE

You can generate worklists in PULSE from multiple locations: 

- [Dairy Reports/Worklists](docId\:unglSr18amY6xYaMsFdnh): Use this tab to generate reports or worklists saved from the Gallery.
- [Template Gallery](docId:2pH37I7mwSj79BZCM4WCA): Use the Gallery to check out available report and worklist options.
- [Report/Worklist Builder](docId\:I7vcqxLA9mWQWNm-o_eXz): This tool allows you to build custom reports and worklists using an easy drag & drop interface.

See [Build a To-Do List](docId\:B4Qr-zkZa_aFjVqGk2-Kj) for step-by-step instructions for building a to-do list.
:::

::::::ExpandableHeading{isOpen="true" customAnchorSlug="CreateTodosDC306"}
## Create To-Do Lists in DairyComp

:::::ExpandableHeading{isOpen="true"}
### Step 1: Create PULSE To-Do Tasks in DairyComp

For customers who are familiar with the VAS PCC product, you may already know how to create and send a list to PCC handhelds. The command is similar when creating a to-do list to send to PULSE.

Set up the command as shown in the example below:

::::WorkflowBlock
:::WorkflowBlockItem
Start with the **SERVER** command to define what you want the worklist to do.
:::

:::WorkflowBlockItem
Use the **\K** switch to tell DairyComp to send this list to PULSE.
:::

:::WorkflowBlockItem
If you want to define a PostProcess or OnDone command, enter **\~** for PostProcess or **^** for OnDone, followed by the command that should be run:

- PostProces&#x73;**&#x20;Example:&#x20;**&#x53;ERVER ID VETC FOR VC>2 LHDAT\<TODAY \K \\\~SETVET
- OnDon&#x65;**&#x20;Example:&#x20;**&#x53;ERVER ID VETC FOR VC>2 LHDAT\<TODAY \K \\^SETVET
:::
::::

::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/ckwNbq5Owo0QpOUTh_O18_worklist-command-example.png" size="37" isUploading="false" initialPath="../../../../Resources/Images/Platform/dairycomp/worklists/worklist-command-example.png" githubPath="Content/Resources/Images/Platform/dairycomp/worklists/worklist-command-example.png" position="flex-start" width="819" height="393" darkWidth="819" darkHeight="393" showCaption="false"}

::::ExpandableHeading{isOpen="true"}
### Cautions when planning follow‑up routines

Use caution when scheduling follow‑up routines for DairyComp to run after a list is processed (i.e., PostProcess lists), especially if **all** animals on the list must be processed **before** kicking off the next routine. **DairyComp does not wait for the entire list to be&#x20;**&#x44;ON&#x45;**.** It will kick off the follow‑up routines for each animal **as** it receives notification from the mobile app that the animal is DONE.

:::hint{type="warning"}
**IMPORTANT:&#x20;**&#x55;se caution when scheduling follow‑up routines for DairyComp to run after a list is processed (i.e., PostProcess lists), especially if **all** animals on the list must be processed **before** kicking off the next routine. **DairyComp does not wait for the entire list to be&#x20;**&#x44;ON&#x45;**.** It will kick off the follow‑up routines for each animal **as** it receives notification from the mobile app that the animal is DONE.\:::ExpandableHeading\{customAnchorSlug="video"}

### Click here for video tutorials on this feature!

For more information on how to use OnDone and PostProcess routines in DairyComp, check out the following videos on the VAS website:

::embed[]{url="https://player.vimeo.com/video/274759138"}

::embed[]{url="https://player.vimeo.com/video/305782522"}

\:::
:::
::::
:::::

::::ExpandableHeading{isOpen="true"}
### Step 2: Send your To-Do Tasks to PULSE

:::hint{type="warning"}
**IMPORTANT:&#x20;**&#x42;e aware that if DairyComp sends multiple versions of the same list to PULSE in one day, the most recent list overwrites the earlier ones but does NOT affect any progress or changes made against the list.
:::

Unlike the PCC product, which requests each worklist during a refresh, PULSE does **not** request worklists from on‑premise DairyComp. Instead, DairyComp must manually send worklists to PULSE. This ensures that on‑premise users control the lists that are sent out to PULSE mobile app.

You can send Platform Worklists from DairyComp manually or schedule DairyComp to send them automatically. Follow the instructions below to proceed.

:::ExpandableHeading
### Send Lists Manually

Follow these steps to send worklists from DairyComp to PULSE manually:

1. Go to the DairyComp command line.
2. Type PLATFORM\K and press enter.

This command instructs DairyComp to find all Platform-enabled (\K) SERVER commands and generate the corresponding worklist files. The worklist files are then sent to PULSE the next time it synchronizes data from DairyComp.
:::

:::ExpandableHeading
### Schedule DairyComp to Send Lists

If you prefer not to do a manual send each time you want to update your PULSE lists, you can set up a DairyComp Scheduled Task that automatically executes the PLATFORM\K command at a convenient daily or weekly interval. Please contact [VAS Support](http://platform-docs.vas.com/default.htm#cshid=1004) if you need help scheduling this type of task in DairyComp.
:::
::::
::::::