By Natalie Foster, field-service contract systems analyst with 9 years of experience configuring recurring service, equipment histories, and technician workflows
Last reviewed: July 21, 2026
FieldPulse is field service management software that can connect customer assets, maintenance agreements, recurring visits, invoices, and technician records. A maintenance plan should be attached to the correct customer and equipment before recurring jobs are generated; otherwise, service history and renewal reporting can become fragmented.
This independent guide is not operated by or affiliated with FieldPulse.
Start with the customer record. Skip creating another agreement until the existing customer, asset, service frequency, and prior jobs have been checked.
What is FieldPulse?
FieldPulse is a field service management platform for companies that schedule technicians, manage customers, create estimates and invoices, and track work performed away from the office. Its current product catalog includes job management, recurring jobs, customer portals, asset management, inventory, maintenance agreements, reporting, and mobile field tools.
A maintenance workflow can connect several records:
- Customer
- Service location
- Equipment asset
- Maintenance agreement
- Recurring job
- Technician visit
- Invoice or recurring billing record
- Renewal date
Those records are related, but they are not substitutes for one another.
An asset describes the equipment being serviced. An agreement describes the service commitment. A recurring job places future visits on an operating schedule. An invoice records the charge.
Mixing them together creates vague records that are difficult to audit later.
Where maintenance agreements are found
FieldPulse documents maintenance agreements inside the customer record. In the mobile app, a user can open Customers, select the relevant customer, and choose Maintenance Agreements near the top of the record. Existing agreements can be viewed or edited there, and a new one can be created through Create Maintenance Agreement.
This route matters when a technician says an agreement is missing.
The agreement may be attached to another customer profile, especially when a household or commercial company has duplicate records. It may also belong to a different service location or have been entered under a slightly different company name.
Search first.
Do not create a second agreement merely because it is absent from one mobile view. Confirm the customer, location, user permissions, and agreement status before adding anything.
FieldPulse’s current role documentation indicates that access to create or view maintenance agreements can depend on the assigned user role. A technician who cannot see the control may have a permissions issue rather than a missing contract.
Maintenance agreement or recurring job?
A maintenance agreement records the contractual service arrangement. A recurring job automatically creates repeat work on a selected schedule.
FieldPulse describes recurring jobs as jobs that are created once and then set to reoccur at a chosen interval. Its broader job-management materials mention daily, weekly, monthly, and custom recurrence options for repeat service, inspections, and maintenance work.
The distinction is practical:
| Record | Primary purpose |
|---|---|
| Maintenance agreement | Stores service terms, frequency, pricing, status, and renewal information |
| Recurring job | Generates repeat operational work on the schedule |
| Asset | Identifies the equipment being inspected or serviced |
| Invoice | Records what the customer is billed |
An agreement can exist without every future appointment already being scheduled. A recurring job can also be used for repeat work that is not governed by a formal service agreement.
Check the agreement first. Skip using a generic recurring job as a replacement when renewal dates, equipment coverage, or contract reporting are required.
How custom service frequencies work
FieldPulse supports customized monthly and yearly intervals for maintenance agreements. The company’s November 2024 release documentation describes custom frequencies for situations where a contract does not follow a simple monthly or annual pattern.
That helps with arrangements such as service every two months, every six months, or at another approved interval.
The frequency must match the signed service terms.
A company can create a technically valid schedule that is contractually wrong. For example, entering “every three months” produces four annual occurrences, while a twice-yearly agreement requires a six-month interval.
Small field. Large consequence.
Review the interval, initial service date, contract term, and billing cycle together. Do not assume the job frequency and billing frequency are identical. A customer might pay monthly for two annual service visits, or pay once for several scheduled visits.
Linking assets to maintenance agreements
FieldPulse assets can store equipment information such as manufacturer, model, installation date, warranty details, photographs, and attached files. Assets can be connected to jobs and maintenance agreements so service history follows the actual equipment rather than only the customer account.
FieldPulse’s current changelog also notes that an existing asset can be linked directly from the Asset tab of a maintenance-agreement record.
This solves a common field problem.
A commercial customer may have four rooftop units at one address. The company has one agreement, but each unit has a different model, installation date, warranty, and maintenance history. Recording every visit only against the building makes it difficult to identify which unit received service.
Attach the specific asset.
Before linking it, verify:
- Customer
- Service site
- Equipment type
- Manufacturer and model
- Serial or internal identifier, when used
- Installation date
- Warranty details
- Existing service history
Do not create a second asset because the model name was entered differently. Search the customer’s assets and attached files first.
Why service history appears incomplete
An asset history may appear incomplete when earlier jobs were attached only to the customer or service site, rather than to the equipment record.
The job exists. The asset timeline does not show it.
FieldPulse’s asset-management feature is designed to connect equipment to work orders and maintain a consistent service history. It also supports service reminders based on asset history and agreements.
Check both paths:
- Open the asset and review linked jobs.
- Open the customer’s complete job history.
- Compare dates, technicians, and work descriptions.
- Identify earlier jobs that reference the equipment only in notes.
- Follow the company’s correction process before changing historical records.
Skip deleting or recreating an old job. That can affect invoices, technician activity, and accounting history.
A better internal rule is to require the asset selection before a technician closes equipment-specific maintenance work. The exact enforcement available depends on the company’s FieldPulse configuration.
Job templates for repeat maintenance
FieldPulse job templates can prepopulate materials and other information for common work. The current template documentation describes using templates to standardize materials required for repeated job types and reduce manual entry during job creation.
A maintenance company might create separate templates for:
- Spring cooling inspection
- Fall heating inspection
- Annual backflow test
- Generator service
- Commercial refrigeration check
- Water-treatment maintenance
Templates improve consistency, but they need review.
A template created two years ago may contain outdated materials, estimated time, instructions, or pricing references. Copying it accurately reproduces the outdated information.
Check the template before generating a season’s jobs. Skip editing dozens of individual appointments when one template correction should be made at the source.
The agreement defines what the customer receives. The template defines how the team performs and documents the work. Those two records should be compared before launch.
Renewals and agreement reporting
FieldPulse promotes centralized maintenance-agreement management with service-history tracking, upcoming work, and renewal reminders.
Its reporting documentation allows maintenance-agreement reports to be built using information such as total annual fee, last job occurrence, status, customer, frequency, and billing frequency.
These fields answer different operational questions:
- Which agreements renew soon?
- Which customers have not received the expected visit?
- Which agreements are inactive?
- How much annual contract value is represented?
- Which billing frequencies are in use?
- Which customer records have no recent job occurrence?
A renewal report is only as reliable as the underlying agreement status and dates.
Do not leave an expired agreement marked active merely because the customer might renew later. That can inflate active-agreement reporting and may continue triggering operational work.
Update the status under the company’s documented process, while preserving the old agreement for history where appropriate.
Why a recurring visit did not appear
A missing future job can come from the agreement, recurrence setup, start date, end condition, or user view.
Check these points:
| Check | Possible problem |
| Agreement status | The agreement is inactive or expired |
| Recurrence interval | The frequency was entered incorrectly |
| Starting occurrence | The first date is later than expected |
| End condition | The recurrence has already ended |
| Schedule filters | The job is outside the visible range |
| Customer record | The agreement belongs to a duplicate profile |
| User access | The employee cannot view the relevant record |
Do this before manually creating the appointment.
A manually added job may solve today’s calendar gap while leaving the underlying recurrence broken. The same problem then returns at the next service interval.
FieldPulse’s recurring-job documentation says repeat jobs are generated from the recurrence established on the original record. Correcting that source is more reliable than repeatedly adding isolated jobs.
Customer Portal visibility
FieldPulse’s Customer Portal gives clients access to selected job information, schedules, updates, service requests, invoices, and communication with the service company.
Portal visibility should not be confused with the internal maintenance-agreement record.
A customer may see upcoming service work without seeing every internal contract field. The portal experience is controlled by the service business and may vary according to configuration.
Contact the contractor first when an expected maintenance visit is missing from the portal. Skip creating a new Booking Portal request until the company confirms whether an appointment already exists.
A new booking can be interpreted as a separate service request rather than an agreement visit.
Asset and agreement reports
FieldPulse supports asset reports using fields such as manufacturer, asset type, and warranty details. Maintenance-agreement reports can be grouped by customer, service frequency, or billing cycle.
Used together, those reports can identify operational gaps.
For example, a company could compare active agreements with the assets attached to them. An active equipment agreement with no linked asset should be reviewed. An asset with an expiring warranty and no recent job may deserve attention. These are operational inferences based on the available report fields, not automatic FieldPulse conclusions.
Keep the reports narrow.
A report with every available field is harder to review than one built for a specific decision. Start with agreement status, next service timing, customer, asset, and last job occurrence.
FieldPulse pricing and support
FieldPulse uses customized pricing based on the company’s configuration rather than publishing one universal rate for every account. Maintenance agreements, asset management, job management, portals, reporting, and related products appear within its current feature catalog.
A useful pricing discussion should specify:
- Number of office users
- Number of field technicians
- Maintenance-agreement volume
- Asset and equipment tracking needs
- Recurring billing requirements
- Customer Portal access
- Reporting needs
- Data migration and training scope
FieldPulse’s Customer Success Agreement describes implementation and a soft-launch period with recurring meetings to address configuration and workflow adjustments.
For product questions, the official Help Center publishes support contact routes, including email and in-product chat.
When reporting a maintenance issue, include the customer, agreement, linked asset, expected frequency, last completed job, and whether the problem occurs on web or mobile. Do not include confidential login or payment information.
Frequently asked questions
Can FieldPulse track customer equipment?
Yes. Assets can store equipment and service details.
Is a recurring job the same as a maintenance agreement?
No. A recurring job schedules repeated work, while the agreement stores the service arrangement.
Can assets be linked to maintenance agreements?
Yes. FieldPulse supports linking existing assets to an agreement.
Why is an agreement missing on mobile?
It may be attached to another customer, hidden by the user’s role, or inactive. Open the customer record and check Maintenance Agreements before creating another one.
Can FieldPulse use custom maintenance intervals?
Yes. Custom monthly and yearly agreement intervals are supported.
Why did the next maintenance job not appear?
Check the recurrence frequency, starting date, agreement status, end condition, customer record, and schedule filters. Correct the source recurrence before manually adding repeated appointments.
What can maintenance-agreement reports show?
FieldPulse documents reporting fields including annual fee, last job occurrence, agreement status, customer, frequency, and billing frequency.
Where should I start with incomplete equipment history?
Compare the asset’s linked jobs with the customer’s complete job history. Earlier work may exist without being attached to the asset.
