Skip to content
English
  • There are no suggestions because the search field is empty.

Jobs

 What is a Job?

A Job in EZ Ops is a project-level record used to plan, document, and cost a defined body of field work — a turnaround, a workover, a construction project, or any multi-day operational effort. A Job holds the location, the dates, the budget, the planned crew size, and the customer being billed, and it is the record that Field Tickets, Job Forms, assets, and tasks all attach to.

Jobs are created and managed online. The work recorded against a Job — Field Tickets and Job Forms — is filled in by field staff and rolls up to the Job automatically.

Jobs are available when your organization has the Job/Project Forms setting enabled, and budget fields appear only when Job/Project Budgets is also enabled.

Job Details

Each Job record contains:

  • Name — a descriptive name for the Job, such as "Well 12 Workover - Spring 2026"
  • Location — the plant or field location where the work is taking place
  • Start date / End date — the planned dates for the Job. These set the Job's duration but do not stop anything from being recorded outside them
  • Company — the customer being billed. Optional, but an invoice cannot be raised for a Job with no Company
  • Total budget — a single overall budget figure for the Job
  • Daily budget — an expected per-day cost for the Job
  • Number of Assigned Users — a planned crew size. This is a number you type in for planning purposes, not a list of people
  • Budget categories — named cost categories, each with its own daily budget
  • Assigned users — the actual named people working the Job, managed separately from the crew-size number

How the budget fields relate to each other

They do not. This trips people up, so it is worth stating plainly:

  • Total budget and Daily budget are two independent numbers you type on the Job. Nothing calculates one from the other.
  • Each budget category carries its own daily budget — a per-day figure, not a share of the Job total.
  • Nothing in EZ Ops validates category budgets against the Job's total budget. You can set a $10,000 total budget on a Job whose categories add up to far more, and the app will save it without complaint.

To compare a category budget against the Job total, multiply the category's daily budget by the Job's duration in days. Budget-vs-actual reporting does this for you; the Job screen does not.

Assigned users vs. actual crew

Number of Assigned Users is a planning figure — how many people you expect to need. Assigning real, named people to the Job is a separate action on the Job record.

Named assignments have no start or end date. A person is either linked to the Job (or to a specific Field Ticket) or not. There is no record of which days each person was on the Job.

Job Assets

Assets are the equipment, tools, and materials tracked against a Job. Each asset record holds:

  • Item — the Misc Item / Inventory record being assigned
  • Type — the item's category, from your Misc Types catalog
  • Vendor — supplier or service provider
  • Description — what the asset is, or what it is being used for
  • Daily cost — a planning reference for the item's cost per day. Recorded only; it is not charged to the Job
  • Consumable — whether the item is used up during the Job
  • Rental — whether the item is rented rather than owned
  • Quantity used / units — how much of the item is being used
  • Assigned date — when the asset was brought onto the Job
  • Released date — when the asset left the Job. Blank while it is still on the Job

Assets come from Misc Items / Inventory only. The Equipment module is a separate system. Cataloguing something as Equipment does not make it assignable to a Job, and assigning an item to a Job does not create any equipment utilisation or maintenance history.

When a non-consumable item is assigned to a Job, its status changes to Assigned and it cannot be picked for another Job. Releasing it returns it to Available. Consumable items behave differently — their stock quantity is deducted on assignment instead.

Why the released date matters

Leaving Released date blank keeps the item marked Assigned, so it stays unavailable to every other Job — indefinitely, including long after this Job's end date has passed. An item left unreleased on a Job that finished months ago is still blocking anyone who needs it.

The dates do not price anything. A job asset carries no cost; equipment cost reaches a Job only through a Field Ticket line. What the dates drive is availability, and they are the record anyone planning a future Job relies on.

Entering the released date frees the item. Marking the Job Complete also releases its non-consumable assets automatically, backdating the release to the Job's end date.

Job Status

Jobs have two states:

  • Active — the Job is open and ongoing
  • Completed — the work is done and the Job is closed

Jobs can also be deleted, which is a soft delete with the option to restore.

How to Create a Job
  1. Navigate to Jobs — go to Reports → Operations → Job Dashboard
  2. Click Create Job — open the Job creation form
  3. Fill in the Job details — name, location, start and end dates, and the number of assigned users
  4. Attach a Company — pick the customer being billed. Do this now if there is any chance the Job will be invoiced
  5. Set the budgets (optional) — enter the total and daily budget for the Job
  6. Add budget categories (optional) — pick a category and give it a daily budget. Add one row per category
  7. Save — the Job is now active and visible to your team
How to Add Assets to a Job
  1. Open the Job — expand the Job on the Job Dashboard
  2. Add an asset — open the asset assignment form
  3. Select the type, then the item — items come from your Misc Items / Inventory catalog
  4. Fill in the asset details — vendor, description, daily cost, consumable and rental flags, quantity, and the assigned date
  5. Save — the asset is linked to the Job, and a non-consumable item's status changes to Assigned

To release an asset when its work is done, edit the asset record and enter a Released date.

How to Complete a Job
  1. Open the Job — find it on the Job Dashboard
  2. Mark as Complete — select the Complete action
  3. Confirm — the Job moves to Completed and out of the active list

Completing a Job also releases every non-consumable asset still open on it, setting each released date to the Job's end date. Completed Jobs stay visible in history, and Un-complete reopens one if more work is needed.


What Gets Recorded Against a Job

Four separate things attach to a Job. Only two of them carry cost:

What What it captures How it carries cost
Field Tickets A discrete visit, day, or event of billable work Priced line items — Misc Items used plus Other Expenses rows
Job Forms Daily activity, crew, equipment, and category spend Answers on questions configured as budget-category questions
Job assets Equipment and materials reserved for the Job No cost. A reservation only — it marks the item busy
Job tasks Tasks linked to the Job No cost roll-up. Cost and man hours are recorded per task but never totalled

Field Tickets and Job Forms both record something that happened on a date, and both produce real cost. Job assets and job tasks do not. An asset's daily cost and a task's cost are captured and displayed on their own records, but nothing sums them into any Job total — they are planning and documentation figures.

They rarely overlap. Most Jobs use one or two of the four, so the right choice depends on how your organization works: Field Tickets suit service companies billing a client, and Job Forms suit operators tracking spend against internal budget categories. Neither replaces the other.

Field Tickets on a Job

A Field Ticket is a form filled out against a Job that captures priced, billable work — labour, equipment, chemicals, and inventory used, each as a line with a quantity and a rate. Field Tickets are the source data for invoices.

Field Tickets have two states: a draft saved with Save Progress, and a completed ticket saved with Save and Submit. There is no submitted-for-approval or approved state, and no reviewer is recorded. If your process needs tickets checked before they are billed, that has to be a team convention.

A Field Ticket can be attached to an invoice whether it is complete or still a draft.

Job Forms — Capturing Event Details

A Job Form is a form configured with the Job type and linked to a specific Job. Each submission is a discrete event or activity during the Job's life.

What you can record with Job Forms:

  • Daily activity summaries or shift reports
  • Spend against a budget category
  • Hours worked on the Job
  • Crew, vendor, or subcontractor activity
  • Equipment changes, incidents, or any other event that needs a traceable record against the Job
  • Images and attachments

How to Submit a Job Form

From the field (offline)

  1. Navigate to the location (plant or well site) in the EZ Ops field app
  2. Find the Job Forms section on the location page
  3. Tap New Job Form — the form associates with the active Job at that location
  4. Fill in the event details and submit
  5. The submission syncs to the server when connectivity is restored

Online (from the reports page)

  1. Navigate to Reports → Forms
  2. Set the form type filter to Job
  3. Optionally filter by the specific Job you want to add the event to
  4. Click New Job Form to open the form submission linked to that Job
  5. Fill in the event details and save

Charging a Budget Category from a Job Form

A Job Form question charges a budget category when your administrator has flagged it as a Category budget question in Form Config and linked it to one of your organization's Job Categories.

Two things follow from how this is built:

  • The answer type decides the unit. A question with a money answer type records dollars against the category. A question with a number answer type records hours. The same category can receive both, from two different questions.
  • It only produces cost on a Job form attached to a Job. The setting can be switched on for other form types, including Field Tickets, but the answer is simply saved and contributes nothing to Job cost. Field Ticket costs have to be captured through the ticket's own line items instead.

Because budget-vs-actual reporting matches a question to a category by name, the question wording and the Job Category name need to stay identical. Renaming either one breaks the link silently — the spend is still recorded, but it stops lining up against its budget.

How Job Cost Adds Up

The Total Cost ($) column on the Job Dashboard counts Field Ticket totals only. The column's own tooltip says so. Job asset daily cost, Job Form category spend, and task cost are all excluded from it.

A Job's true total cost is therefore normally higher than the number on the Jobs page — often substantially, and on Jobs that use Job Forms rather than Field Tickets the Jobs page can read $0 against real spend. The full picture, with all four sources broken out side by side, comes from job cost reporting rather than from the Job Dashboard column.

Nothing in the app compares actual cost against the Job's budget or against its category budgets. Budget-vs-actual is a reporting exercise.

Viewing Jobs
  • Active and completed Jobs are listed separately, so you can see what is open at a glance
  • Assigned to Me filters the list to Jobs where you are assigned to the Job itself or to any Field Ticket under it
  • Each Job expands to show its assets, budget categories, Field Tickets, Job Forms, and tasks
  • Jobs are tied to a location, so all Jobs for a plant or field location can be found in one place
Reporting on Jobs

Reports → Forms — filter by form type Job or Field Ticket. The report includes the Job name alongside every submission, so you can pull all events recorded against a Job in one list. Results export to Excel.

Reports → Operations → Job Dashboard — the Job list with its Field-Ticket-only Total Cost column.

Reports → Operations → Invoices — invoices raised from Field Tickets on a Job.

Embedded reports — if your organization has EZ Insights or the Report Dashboard enabled, interactive reports built in Power BI or Sigma can be embedded directly in EZ Ops. This is where full job costing lives: all cost sources on one Job, budget versus actual by category, equipment still held past its Job's end date, and cost per job-day against comparable Jobs. Contact your administrator to find out what is available for your organization.

What Jobs Do Not Do
  • No cost roll-up on the Job screen. The Jobs page Total Cost column is Field Tickets only.
  • No budget validation. Category budgets are not checked against the Job's total budget, and nothing warns you when actual cost passes either.
  • No equipment integration. Job assets come from Misc Items / Inventory. Equipment records cannot be assigned to a Job.
  • No dated crew assignments. Named assignments record who, not when.
  • No approval step on Field Tickets. Draft and complete are the only states.
  • No accounting-system export. Invoicing produces a PDF.
Tips & Recommendations
  • Attach the Company when you create the Job. A Job with cost and no customer cannot be invoiced, and it is a common reason a finished Job sits unbilled.
  • Release assets the day they leave site. An unreleased asset stays marked Assigned forever and cannot be picked for another Job. This is the single largest source of equipment that looks unavailable when it is not.
  • Set the assigned date to the day the asset actually arrived. These dates are what availability reporting reads, and an assigned date after the Job's end date is accepted without warning.
  • Keep the budget question wording identical to the Job Category name. Renaming one side breaks budget-vs-actual reporting silently.
  • Complete Jobs promptly. Completing is what releases the remaining assets and frees them for other work.
Common Issues

"The Total Cost on the Jobs page is far lower than what we have spent." That column sums Field Ticket totals only, so Job Form category spend is the usual missing piece — on a Job that uses Job Forms it can read $0 against real spend. Use job cost reporting for the full figure. Job asset daily cost and task cost are not in that column either, and are not counted as cost anywhere.

"We entered daily costs on our job assets but they never show up in any total." That is expected. Daily cost on a job asset is recorded for planning reference and is not charged to the Job. Equipment cost reaches a Job only when the item is added as a line on a Field Ticket, priced by rate × quantity.

"A Misc Item won't appear in the picker for a new Job." It is still assigned to another Job. Release it there first. Deleting a Job does not release its assets — they stay marked Assigned, so restore the Job, release the assets, then delete it again.

"Our category budgets add up to nothing like the Job's total budget." They are unrelated figures, and category budgets are daily. Multiply each category's daily budget by the Job's duration before comparing it to the Job total.

"We ticked Category budget question on a Field Ticket form and no cost appeared." The setting only produces cost on a Job form attached to a Job. On a Field Ticket, put the cost in the ticket's line items or Other Expenses instead.

"Budget-vs-actual shows spend against a category we don't have a budget for." The question wording and the Job Category name no longer match — usually because one of them was renamed. Set them back to the same text.


Remember: A job asset reserves equipment; it does not cost the Job anything. Releasing assets as they leave site, and completing Jobs when the work is done, is what keeps equipment availability true — and Field Tickets are what make Job cost true.