Skip to main content

Overview

FieldPulse gives you three record types for managing work: Projects, Jobs, and Site Visits. Each one serves a different purpose, and understanding how they relate to each other will help you keep your work organized and your team on the same page. Here’s the short version:
  • Projects are the big picture: a folder that holds all the jobs and invoices for a large or long-running engagement.
  • Jobs are the individual units of work, whether they stand alone or live inside a Project.
  • Site Visits are extra appointments tied to a single Job, perfect for return trips, call-backs, or multi-day work that doesn’t warrant its own separate job record.

Projects

What is a Project?

Think of a Project like a folder. It organizes all the Jobs, estimates, invoices, and files related to a single large scope of work, so everything stays connected and easy to reference. Projects are ideal for long-term work: work that span weeks, months, or even years, involve multiple phases, or require multiple invoices over time.

When to use a Project

Consider creating a Project record when:
  • You’re building an entirely new facility
  • You’re doing work across multiple units (e.g., rewiring each unit in an apartment complex, where each unit can be its own Job record within the Project)
  • You’ll be invoicing your customer multiple times as phases of work are completed (e.g., plumbing new construction floor by floor)
  • You’re managing a large commercial installation that goes through multiple defined stages before final completion

Key things to know

  • Project Notes cascade to any Job record created within that Project, so your team always has the right context.
  • You can create Custom Status Workflows for Projects to track exactly where each one stands.

Example Project Status Workflows

Electrical New Construction: Accepted → Deposit Collected → Permits Approved → Materials Ordered → Rough In → Trim-Out → Final Inspection → Final Invoice → Completed Overhead Door Installation: Accepted → Deposit Collected → Site Measured/Verified → Door & Parts Ordered → Materials Received → Installation Visit #1 → 2nd Payment Received → Installation Visit #2 → Inspections → Final Invoice Sent → Completed Commercial Elevator Installation: Accepted → Deposit → Pit & Framing (Phase 1) → Rough In (Phase 2) → Selections → Final Measures → Equipment Procurement → Pre-Install Checklist → Ready for Install → Equipment Installation → Ready for Inspection → Final Invoice → Paid and Completed

Jobs

What is a Job?

A Job is the core work record in FieldPulse. Jobs can be standalone records for work that’s completed that day, or they can be part of a Project, representing individual appointments, stages, or phases within a larger scope of work.

When to use a Job

  • As a standalone record: Use for any single visit or day’s work, like a service call, installation, or repair that starts and finishes within a relatively short window.
  • Within a Project: Use Jobs to represent individual phases or appointments. Each one can be scheduled, invoiced, and tracked separately under the umbrella of the Project.

Key things to know

  • You can create Custom Status Workflows and Status Action Flows for Jobs, giving you granular control over how your team moves work through your process.

Example Job Status Workflows

Install: New → Install Scheduled → Truck Preparation → On the Road → Prep & Inspection → Install in Progress → Testing & Clean Up → Install Complete → Invoice Paid & Complete → Pending → Canceled Emergency: New → Emergency Dispatch Scheduled → En Route → On-Site → Service Complete → Invoice Paid & Complete → Paused → Canceled Service Call: New → Service Scheduled → On the Way → Service in Progress → Service Go Back → Service Complete → Invoice Paid & Complete → On Hold → Canceled

Site Visits

What is a Site Visit?

A Site Visit is a sub-record tied to a Job. It lets you schedule an additional appointment under an existing Job without creating a brand-new record. All the visits stay organized in one place, each with their own date, team assignment, notes, and status.

When to use a Site Visit

Site Visits are best for return trips: situations where your team needs to come back, but you’re not creating new work or a new invoice. Common examples include:
  • Service call-backs or “go-backs”
  • Follow-up appointments tied to the same job

Key things to know

  • You can create Custom Status Workflows for Site Visits. Since overall progress is tracked at the Job level, it’s best to keep Site Visit workflows simple.

Example Site Visit Status Workflows

Simple: New → On the Way → On Site → Completed With escalation: New → On the Way → In Progress → Management Needed → Completed

Quick Reference

ProjectJobSite Visit
Best forLong-term, multi-phase workIndividual units of workReturn visits / call-backs
Can be standaloneYesYesNo (must be tied to a Job)
Supports invoicingYes (multiple)YesNo
Custom Status WorkflowsYesYesYes
Status Action FlowsNoYesNo

Have additional questions? Contact us at support@fieldpulse.com or use the chat feature in the bottom right corner of your screen.