In FSM, a rejected task produces a specific task-level outcome called WO Task rejected. This keeps the history clear for auditing and follow-up, while other items like templates, time logs, and rate fields relate to different aspects of work orders and billing.

Multiple Choice

If a task is rejected, what outcome is recorded?

In FSM, actions on a Work Order Task produce a task-level outcome that shows what happened to that specific task. When a task is rejected, the system records that exact event as WO Task rejected. This dedicated outcome distinguishes a rejection from other possibilities like a task being completed, held, or reworked, and it keeps the history clear for auditing and follow-up actions. The other items listed—Work Order Template, Time recording, and Rate Type field—are unrelated to the act of rejection: templates relate to creating work orders, time recording logs labor time, and the Rate Type field deals with billing rather than the outcome of a task.

When a field service task hits the status of rejected, the system doesn’t just shrug and move on. It records a precise outcome that signals a clear result for that individual task. In the ServiceNow FSM (Field Service Management) world, especially under Paris, this distinction matters. It isn’t just a label tossed into a log—it’s a data point that informs everything from audits to future scheduling, reporting, and how teams communicate about what happened on the ground.

Let’s unpack what this means in practice and why the “WO Task rejected” outcome matters more than it might first appear.

What does a task-level outcome actually capture?

Think of a Work Order Task as a micro-project inside a larger job. Each task has its own lifecycle: it can be scheduled, assigned, started, paused, completed, reworked, put on hold, and yes, rejected. The key idea is granularity. A single work order can contain multiple tasks, each with its own fate. The FSM engine in Paris makes this possible by tying outcomes to each task, not just to the Work Order as a whole.

When a task is rejected, the system records “WO Task rejected.” This outcome is specific to the task in question, not to the entire work order. It’s the digital equivalent of a supervisor saying, “That step didn’t meet the mark, so we’re not moving forward with it as-is.” And because it’s task-specific, you can review exactly which step failed, which technician or team was involved, and what the rejection was based on.

Why not just mark the whole Work Order as rejected?

The temptation to think of a rejection as a simple “the job is off” is natural, but it misses the nuance. A work order often includes a sequence of tasks, each with its own dependencies and requirements. Sometimes one task goes off track while others are on track. In those cases, you don’t want to discard the entire Work Order or erase the history of what went right. A task-level rejection preserves the integrity of the data. It tells you, with precision, what needs attention, what needs rework, and what should be escalated or re-assigned.

For example, imagine a field tech who finds a broken sensor during a fault diagnostic. The diagnostic task is rejected because the sensor needs replacement rather than repair, or perhaps the calibration step didn’t meet the standards. That rejection is captured as WO Task rejected. Meanwhile, other tasks in the same Work Order—like parts retrieval, documentation, or customer sign-off—might still proceed as planned or follow their own paths. The outcome at the task level becomes a map of reality on the ground.

Auditing and traceability: why the exact outcome matters

Auditing isn’t just about ticking boxes; it’s about understanding how a service operation evolves in real time and over time. When a task is rejected and logged as WO Task rejected, you’ve got a precise breadcrumb trail. If someone asks, “Why did we need to rework this task?” you can point to the rejection event and the context around it. Was there a missing part? Was the issue misdiagnosed? Was additional information required from the customer? The answers live in the task-level history, linked to the Work Order, with timestamps and user identifiers.

This kind of traceability is essential for continuous improvement. It helps managers spot recurring rejection patterns—say, recurring calibration issues or approvals that consistently slow down a job. With Paris, you’re empowered to slice data by task, by technician, by asset, or by location, giving you fresh ground for optimization without losing sight of the details.

Operational implications: what happens after a rejection

A task rejection triggers a natural set of follow-on actions that your FSM configuration should support. Depending on your business rules, those follow-ups could include:

  • Reassignment: A different technician or a more specialized resource takes over that task. The system can auto-allocate a new assignee or prompt a supervisor to re-match skills.

  • Rework or revision: The task is queued for rework, possibly with updated instructions, updated parts, or altered diagnostics. This ensures the team tackles the right problem the next time around.

  • Customer notification: It’s common to loop in the customer if a task can’t be completed as planned. The rejection record can trigger a status update, a note for the customer, or a revised appointment window.

  • Escalation: If a rejection signals a deeper issue—equipment failure, access problems, or safety concerns—an escalation workflow can kick in to bring in the right stakeholders.

  • Documentation update: The knowledge base or asset records can be updated to reflect learnings from the rejection, improving future diagnostics and maintenance planning.

All of these actions can be configured in ServiceNow to align with your operating rhythm. You get a flexible framework where what happens next is dictated by the context of the rejection, not by a one-size-fits-all rule.

A closer look at Paris: what’s new or improved around task outcomes

Paris brings a refined lens to FSM, focused on clarity and agility in field operations. When it comes to task outcomes like WO Task rejected, there’s a steady emphasis on:

  • Clear, task-level visibility: You don’t need to guess which task failed. The outcome name itself is explicit and tied to the exact task.

  • Better workflow transitions: With precise outcomes, transitions between states (like from “in progress” to “rework needed”) become more natural and traceable.

  • Enhanced reporting flexibility: Filters, groupings, and dashboards can center on task-level events, giving managers the granularity they crave.

  • Stronger integration cues: If your FSM talks to parts catalogs, HR systems, or customer communication tools, knowing the task-level status makes those integrations more reliable and meaningful.

The human side: what this means for technicians and supervisors

For technicians in the field, a rejection can feel like a snag, but the value becomes clearer once you see the bigger picture. A rejection is not a verdict on the person—it’s a signal that the task needs a different approach. The recorded outcome helps keep conversations constructive: instead of debating whether a job was done, teams can focus on what happened, what’s needed next, and how to prevent repeat issues.

For supervisors and dispatchers, task-level outcomes streamline scheduling and resource planning. If rework is trending in a certain asset category, you know where to allocate more experienced technicians or bring in specialized tools. If a particular time window consistently yields rejections due to access constraints, you can adjust scheduling practices accordingly. It’s proactive management, fuelled by precise data.

Connecting the dots with real-world scenarios

Let me paint a couple of quick, relatable scenes that illustrate the value of WO Task rejected:

  • Scene one: A field tech pulls up to a site only to discover a mismatched part. The diagnostic task is rejected because the fix requires a different component. The rework path is kicked off, a new part is ordered, and the customer’s appointment window is updated. The rejection is logged so leadership can see how often part constraints influence timelines and where to optimize stocking or supplier lead times.

  • Scene two: A tech attempts to calibrate a device, but the device fails a calibration check. The calibration task is rejected, and a rework task is created with acceptance criteria tied to a successful calibration. The team retains a clean history showing exactly what failed and what’s needed next, which helps prevent similar calibration issues in the future.

Practical tips to maximize value from task-level outcomes

  • Define clear rejection criteria: Work with field teams to document what constitutes a rejection for each task type. Clear criteria reduce ambiguity and speed up the routing of rework tasks.

  • Build actionable follow-ups: When a rejection happens, auto-create the next-step tasks (rework, escalation, or reassignment) with pre-filled context. Fewer clicks mean faster resolution.

  • Tie outcomes to asset history: Link task-level outcomes to asset records so you can see how equipment behaves over time. This supports smarter maintenance planning and better resale notes.

  • Enable targeted analytics: Create dashboards that highlight task-level outcomes by asset, crew, or region. Patterns become visible, and action becomes easier.

  • Integrate customer-facing updates: If a task is rejected, a well-timed notification to the customer can improve transparency and trust. It’s not just about the hardware—it’s about the service experience.

The thread that ties it all together

In field service, precision matters. The ability to record a task-level outcome such as WO Task rejected isn’t just a data point; it’s a lever for accuracy, accountability, and improvement. Paris reinforces this through a design that treats each task as a distinct unit with its own story, while still letting the larger Work Order form the overarching narrative.

If you’re thinking about how your teams operate on the ground, consider how a subtle shift to task-level outcomes could illuminate how work unfolds in real time. It’s not about adding complexity for its own sake; it’s about giving you a sharper lens to understand what happened, why it happened, and what should happen next. In the end, that clarity pays off—quietly, steadily, and in ways that show up in smoother operations, happier customers, and a better feel for what’s possible when the field meets smart software.