Scheduling a Job: Step by Step

In my experience, the scheduling workflow is where most teams either find their rhythm or start accumulating delays. What I typically recommend is taking a deliberate approach to each step rather than rushing through the creation process — the extra thirty seconds you spend upfront will save you significant dispatcher time later, especially when coordinating multiple technicians across shifting priorities.

This guide walks through the complete scheduling process from initial job request through final technician assignment. I'll also highlight a few configuration decisions you'll want to make early, as changing them later can require retraining your dispatch team.

Prerequisites

Before you begin scheduling, ensure the following elements are in place. In my experience, teams that skip this verification step often discover mid-assignment that a technician lacks the required certification or that a customer's service address hasn't been validated.

Customer record — must exist in your FieldPulse account with at least one service location
Service type — configured in your Settings > Service Types menu (this drives estimated duration and required skills)
Available technician — with appropriate skills, certification, and unblocked time in their calendar
Parts inventory — verified if the job requires specific components (see Reserving Inventory for Upcoming Jobs)

Step 1: Initiate the Job Record

There are three entry points for creating a scheduled job, and what I typically recommend depends on your team's workflow pattern:

Entry Point	Best For
New Work Order button on Dashboard	Ad-hoc requests, walk-in customers, phone calls
Customer record > Create Job	Follow-up work, recurring customers with known history
Convert Estimate from approved quote	Contracted work with predefined scope and pricing

Select your entry point, then proceed to the job creation form. The interface will vary slightly depending on your starting point, but the core fields remain consistent.

Step 2: Define Job Details

Complete the following fields with attention to downstream impacts:

Service Type — This selection triggers several automated behaviors: estimated duration populates the time block, required certifications filter the available technician list, and the default checklist template attaches to the job. In my experience, teams that customize their service type library extensively see significantly faster scheduling decisions.

Priority — Standard, High, or Emergency. Priority affects visual indicators on the Dispatch Board and can trigger notification rules. What I typically recommend is reserving Emergency priority for genuine same-day requirements that displace existing commitments, as overuse dilutes its operational meaning.

Description — Enter sufficient detail for technician preparation. This field supports rich text formatting and appears prominently on the mobile app work order view.

Requested Date/Time — Customer preference, not commitment. The actual scheduled window is determined in Step 4.

Step 3: Assess Technician Availability

Before committing to a time slot, review the Team Calendar or Dispatch Board to understand current capacity. I find the Find Available Technician tool particularly valuable here — it accepts your required date range, estimated duration, and required skills, then returns matching technicians with their nearest available windows.

Key considerations during this assessment:

Technician skill matching — indicated by badge icons on their profile cards
Geographic proximity — to preceding and following appointments, reducing transit time
Existing commitments — including non-work calendar blocks you may have configured for training or administrative time
Workload balance — across your team for the target day

What I typically recommend for growing teams is establishing a dispatcher decision framework — perhaps prioritizing skill match over geography for complex jobs, but favoring proximity for routine maintenance calls. Documenting these preferences reduces decision fatigue and improves consistency.

Step 4: Assign and Schedule

With availability confirmed, proceed to assignment. You have two primary methods:

Direct Assignment — Select a specific technician and time slot. This method offers maximum control and is appropriate when you have full visibility into technician skills and customer requirements.

Pool Assignment — Assign to a skill-based pool (e.g., "Commercial HVAC Certified") and allow the first available qualified technician to claim the job. This method requires Self-Scheduling permissions to be enabled for your technicians.

When using direct assignment, click the desired time slot on the technician's calendar lane. FieldPulse will create the appointment block and immediately update the technician's mobile application. If the selected window is within the next four hours, the system also triggers a push notification to the assigned technician's device.

Step 5: Configure Notifications and Confirm

Before finalizing, review notification settings for this specific job:

Customer confirmation — automatic email or SMS with appointment details
Technician notification — push, SMS, or email based on their preferences
Reminder scheduling — advance notices to reduce no-show rates

Notification templates are configured globally in Settings > Notifications, but can be suppressed or customized per job when circumstances warrant. In my experience, high-value commercial accounts often appreciate customized messaging that reflects your specific relationship.

Click Schedule Job to commit. The job immediately appears on the Dispatch Board and technician calendars. At this point, the status transitions to Scheduled and automated workflows may trigger based on your configuration.

Post-Scheduling Considerations

Scheduled jobs are not static records. What I typically recommend is establishing a cadence for proactive review:

Day-before verification — Confirm parts availability, technician assignment, and customer readiness
Morning-of dispatch — Final status check and route optimization if using Route Optimization
Real-time adjustments — Using Drag-and-Drop Scheduling to respond to delays or emergency insertions

For complex multi-day projects or jobs requiring sequential technician specialties, consider using Assigning Multiple Technicians to a Single Work Order or creating dependent work orders with explicit predecessor relationships.

Common Questions

Can I schedule recurring jobs?
Yes — during creation, expand the Recurrence section to define patterns. For detailed configuration, see Recurring Work Orders: Setup and Management.

What happens if a technician becomes unavailable?
The job remains scheduled but shows a conflict indicator. Dispatchers receive an alert and can reassign using the same availability assessment tools.

Can customers self-schedule through a portal?
This requires the Customer Portal module. When enabled, customers can request windows that enter your queue for approval rather than direct scheduling.

Scheduling a Job: Step by Step