FieldCamp
Job Management

Custom Job Log Templates | FieldCamp

Create custom job log templates in FieldCamp to track miles, expenses, labor hours, and any other field service costs. Reuse templates across jobs and teams.

Job logs track the financial side of every visit -- miles driven, materials used, labor hours, and expenses. FieldCamp gives you default fields for the most common metrics, but your business may need to track things differently. Custom log templates let you define exactly what gets recorded.

The Fastest Way: Ask the Command Centre

Open the Command Centre to pull up cost data without digging through tabs:

  • "Show me the costs for the Johnson job"
  • "What are the total expenses on job 1036?"
  • "How much labor was logged for the City Hospital HVAC project?"
  • "What's the profit on last week's completed jobs?"

The Command Centre returns financial summaries from job logs instantly.


What Job Logs Track

Every job and visit in FieldCamp can log the following by default:

Default FieldWhat It Captures
MilesDistance traveled to and from the job site
Miles CostMileage expense calculated at your configured rate
ExpensesMaterials, supplies, equipment rental, and other costs
Labor CostTechnician pay based on hours worked and hourly rate
Personal HoursTime each technician spent on the visit
Job IncomeTotal billable amount for the job

These fields cover most field service scenarios. For the full breakdown of how logs work, see Tracking Job Logs.

Default fields are always available on every job. Custom fields from templates are added on top of the defaults.


Why Use Custom Templates

Standard fields work for general tracking, but your business might need more detail:

  • A plumbing company wants to log water shut-off time and permit numbers
  • An HVAC service tracks refrigerant type and pounds used per visit
  • A landscaping company records equipment hours for mowers and blowers separately
  • An electrical contractor logs wire footage and breaker panel details

Custom templates let you capture this data consistently across every job of that type.


Creating a Custom Log Template

Step 1: Open Settings

Navigate to Settings from the main menu, then select Job Cost Tracking.

Step 2: Create a New Template

Click Create Template and give it a descriptive name, like "HVAC Service Log" or "Plumbing Visit Tracker."

Step 3: Add Custom Fields

Add fields that match what your technicians need to record. For each field, choose:

  • Field name -- What the technician sees (e.g., "Refrigerant Used (lbs)")
  • Field type -- Number, text, dropdown, currency, or checkbox
  • Required or optional -- Whether the technician must fill it in before completing the visit

Step 4: Save and Assign

Save the template. It becomes available when creating or editing jobs. Assign it to specific job types so the right template appears automatically.


Per-Visit vs. Per-Job Logging

FieldCamp tracks logs at two levels:

Per-visit logging records data for each individual service appointment. This is where technicians enter their hours, miles, and expenses after each trip to the site.

Per-job logging aggregates all visit-level data into a job-wide summary. Managers see totals for the entire job across all visits.

Custom fields work at both levels. A custom field for "equipment hours" appears on each visit log, and FieldCamp totals the values on the job-level summary automatically.

For recurring jobs with many visits, per-visit logging is especially valuable. You can compare costs across visits to spot trends -- for example, noticing that the Smith Residence pool cleaning consistently takes longer in summer months.


Using Templates on Jobs

Once a template is created:

  1. Open the job detail page or create a new job
  2. In the Logs tab, the assigned template's custom fields appear alongside the defaults
  3. Technicians fill in the fields from the mobile app or desktop
  4. Data flows into the job's financial summary and analytics

Changing a template after jobs have been logged does not alter existing data. New fields appear on future logs only.


On this page