--- title: Work notes in state flows description: Work notes are used to communicate information about state transitions. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/field-service-management/work-order-management/work-notes-in-states.html release: australia product: Work Order Management classification: work-order-management topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Customize state flows, Work orders, Set up work orders and tasks, Configure, Field Service Management] --- # Work notes in state flows Work notes are used to communicate information about state transitions. The state flow adds work notes into the **Work notes** field of any task making this transition. For example, you might include the note, "Task rejected by agent" in the **Reject** state flow, which occurs when the task moves from **Assigned** to **Pending Dispatch**. If an agent rejects the task and fails to enter a work note, this note tells the dispatcher why the task reappeared in the dispatch queue. Work notes added by an agent rejecting the task are appended to the work notes that are inherited from the state flow. These rules apply to state flow work notes: - For a state flow with no **Starting state**, the work note is added every time the task transitions to the **Ending state**. - For a state flow with a **Starting state** and an **Ending state**, the work note is added only when the task transitions from that starting state to that ending state. - If two state flows with work notes have the same **Ending state**, but only one has a **Starting state**, the system adds the work notes from the state flow with the starting state. This better matches the state flow work note to the more important transition between specific starting and ending states. In the example here, the work note information is more pertinent to a task moving from **Assigned** to **Pending Dispatch** than to a task that reaches the Pending Dispatch state from an undetermined beginning state.