Jobs

Jobs is for service businesses: an electrician, an HVAC company, a plumber, anyone who sends somebody to a site to do a piece of work. A job is that visit. It lives under Oppdrag in the sidebar.

A job is not a project and not an activity, and the difference is the clock. A project runs for weeks and you have a handful of them. A visit runs two hours and you might have thirty in a day. An activity records contact with somebody, a call or a meeting; a job records work done at a place, by a crew, using materials, that somebody pays for.

So a job carries things nothing else in DealJourney carries: a site address that is usually not the customer's billing address, a start and end time rather than just a date, several people rather than one owner, and a list of priced lines that changes while the work is happening.

Where jobs come from. Most often from a deal. You can mark one of your own pipeline stages as the stage that creates a job, and then moving a deal into it makes the visit and copies the quote onto it. But nothing requires you to use deals: a job can be created straight from the Jobs page, from a customer, or under a project when one installation needs several visits.

The bit that matters for money. Winning a deal used to mean the invoice was known. For service work it is not: you quote a price, then find rot behind the panel, or a part that has to be replaced, or a job that took two hours less than expected. So when a job carries the billing for a deal, the deal itself does not invoice. The job does, from the lines the technician actually delivered.

Quoted lines arrive on the job ready to be ticked off. The person doing the work marks each one delivered, changes a quantity, or marks it not delivered, and adds anything that came up on site. Only the delivered lines are billed. That is the whole design: the quote is a starting point, not a promise about what the invoice says.

Statuses are yours. Draft, Scheduled, En route, On site, Work done, Awaiting approval, Approved, Invoiced and Cancelled are what you start with, and you can rename them, delete the ones you do not use, or add your own. Nothing in the module is hardwired to a name. Instead each status carries what it means: whether the job is booked, whether the crew is on site, whether it needs a manager to approve it, and whether entering it bills the work. That is how the same module works for a window cleaner and for an electrical contractor with a parts-on-order step.

Every change is recorded. Each move from one status to the next is written down with who did it and when, alongside the edits to the job itself. That trail is not paperwork for its own sake: it is what answers "when did we actually arrive", "who signed this off" and "what did we agree to do" months later, when the customer remembers it differently.

Jobs is off unless we turn it on for you. It is not part of any plan. Ask us and we enable it for your company.

Jobs is in alpha. It is genuinely usable and the record of a visit is safe, but parts are unfinished and the shape can still change between releases. The technician's phone view in particular is not built yet, so today a job is planned and completed from a computer. Talk to us before you put a whole field crew on it.