Joblogic Blog

Most guides to LOLER get one thing backwards: which records need keeping for two years and which need keeping for the life of the equipment. This piece covers what equipment LOLER actually applies to, when inspections are due, what a thorough examination involves, and the record-keeping rules as they actually stand.

The term "operating system" gets used loosely in software marketing. In this essay, Joblogic CPO Subhayu Ghosh defines exactly what it means architecturally for service contractors. Most FSM platforms are digital and automated, but still built around the job. An operating system is different. The contract and compliance are first-class inputs the system acts on in real time. Humans stay in command of judgement. The systematic work runs underneath.

Most businesses assume there's a threshold, a certain number of staff, before a fire risk assessment has to be written down. That threshold was removed years ago, and every responsible person now has to record it regardless of size. This piece covers what the assessment needs to include, who's actually on the hook if it's wrong, and the five-step process for getting it right.

Knowing an asset's location isn't the same as knowing its condition, cost, or compliance status, and most businesses only find out the difference during an audit or a client review. This piece breaks down the four stages of asset lifecycle management, where information gaps quietly cost the most, and what a connected asset register actually needs to hold.

Two systems, two versions of the truth, one argument in every review meeting about whose number is right, while the actual decision, hiring, pricing, which contract to renew, waits on a figure nobody's sure they can trust. Here's what's actually causing the gap, and the six things worth checking before you trust another platform's numbers.

Three months after a good demo, engineers quietly go back to paper and phone calls, and nobody notices until invoicing falls behind. This guide covers what separates an app engineers actually use from one that gathers dust: offline capability, form customisation, GPS tracking, adoption ease, back-office sync, and security, plus a scorecard to test any vendor against.

Some contractors lose contracts on price. Most lose them on a certificate nobody could find in 48 hours, an expired accreditation, or a service history nobody could reconstruct in time. Here's what buyers are actually scoring in every tender and renewal, and how to stop losing work you were fully qualified to keep.

Your customers shouldn't have to ring you to find out where their engineer is. Here's what actually separates software that keeps clients confident from software that just adds another login nobody uses.

If your FSM platform and accounting software don't talk to each other, someone's re-entering the same data twice. Here's what to look for in an integration, and how Xero, Sage, and QuickBooks each connect to field service software.

You've got enough engineers. The problem is scheduling by gut feel, no visibility into skills and certifications, and a field-to-office handoff that costs hours every week. Here's what actually closes the gap.

A busy diary and healthy invoicing don't guarantee the work underneath is actually profitable, they just confirm it's happening. This piece covers what a proper profitability report should capture, the most common ways margin disappears unnoticed, and how to compare actual costs against quote to protect the number that actually matters.

Five people at the same company will usually describe the job-to-invoice process five different ways, each filling in the gaps with their own workaround. This piece breaks down the five stages every FSM workflow should follow, where they typically break down, and how automation keeps them consistent as the business grows.