You’re renting equipment you already own
The equipment list says you own it. The new job rented one anyway. Before blaming the decision, check whether anyone could establish that the owned item was available.
KLYX builds equipment and tool tracking workflows for commercial subcontractors. Track what you own, where it sits, who signed for it, when it is due back, and when service is due. Connect utilization to reviewed job costs and estimating history. Start with an Operations Review of your existing records and handoffs.
Book an Operations ReviewEquipment earns its place on the next job when your team can find it, confirm its condition, and make a reliable assignment. If location and availability live in one person’s memory, every new request becomes a search. If use never reaches job cost, your estimate loses that history too.
Integration access and capabilities are confirmed during discovery.
Drafts and recommendations are reviewed by your team before a pricing decision, technical response, submission, or purchasing commitment.
Bring a representative example, the tools involved, and the person who owns the workflow.
Agree on permissions, source records, approval boundaries, and exception handling.
Test on a limited scope, compare against your baseline, and train the team before expanding.
A lift moves from a framing job to a punch list. Stilts ride in a truck. A laser is borrowed for a layout and never gets a return entry. None of those movements is unusual. The problem is that the office cannot distinguish available, assigned, in transit, awaiting service, and missing information.
Start with those operating states. Your crew needs a practical way to report movement; your office needs a record it can trust. The equipment list should explain where to look and who can confirm availability. It should not pretend that an old assignment is a live location.
Before approving another rental, compare the request with owned equipment that can actually do the work. The lift across town may be on a job that finished in April. Or it may still be needed for return work. A status check needs an owner and a date, not an assumption based on the original job schedule.
A useful register makes both possibilities visible. Track the current assignment, expected return, condition, and any committed next use. Then the person making the rental decision can evaluate a transfer, service requirement, or continued rental with the relevant facts. A list of serial numbers alone cannot answer that question.
No theft needs to happen for a tool to disappear from the office’s view. Someone moves it to another truck, lends it to another crew, or leaves it in a locked room during turnover. With no movement record, everyone has a different last-known location.
Record the handoff to a person and a job. When it transfers, update both. When it comes back, record condition and readiness. An unresolved item should have someone responsible for checking it, without treating every missing record as a personal failure. Your people need a system that makes the normal movement easy to record.
Service due is a planning input, not a decoration on the equipment list. A workflow can surface upcoming service using the interval your team approves and the usage information you can reliably capture. It can also distinguish an item awaiting inspection or repair from one available for assignment.
Your qualified people remain responsible for inspections, service decisions, and safe use. The system organizes records and reminders. It does not certify equipment condition or replace the manufacturer’s requirements. A completed service record should state what was done and who confirmed the item can return to the available pool.
If every equipment dollar lands in overhead, a lift-heavy job can look better than it did in practice. A job that used little equipment carries the same broad burden while the estimator loses a useful signal. Start by connecting assignment and utilization records to the job, then agree with accounting on a defensible allocation method.
Assignment days are not automatically productive operating hours. Keep those measures separate. Rental invoices, owned-equipment rates, transport, and service treatment need reviewed rules. The goal is a traceable job-cost record your team can reconcile, then use as estimating history. It is not an automatic declaration of a job’s true profit.
Take twelve months of rental invoices and compare them with your owned-equipment list. For each overlapping item, check dates, location, capacity, condition, and existing commitments. Count a rental as potentially avoidable only after that review. The arithmetic starts with your invoices, not an invented industry average.
Next, total annual tool replacement spend from your own records. Separate wear, planned replacement, damage, and unknown disposition where you can. Then compare idle assignment periods with rental periods. Hours recorded as idle are worth investigating; they do not prove the item was available or suitable for another job.
Use those questions to choose the first equipment category to track. A focused register that people maintain is more useful than an enormous list that goes stale. Establish the baseline and the owner of each record before deciding how broadly to roll out the workflow.
Check out to a person. Assign to a job. Record the expected return and any relevant condition note. When a crew transfers the item, update the assignment. When it checks back in, confirm where it is and whether it is ready for use. Missing or conflicting updates go to a named reviewer.
Bring service due into the same operating view so a planned assignment does not hide a known service requirement. Review utilization by job, then pass approved information into job-cost reporting and estimating history where your accounting access permits. The audit defines the records and review steps before selecting any capture method.
We do not assume a particular tag, device, app, or partner product. We first inspect your current register, tools, permissions, and field routines. The approved scope names the method only after it is confirmed. Capability is the starting point; the implementation choice follows the review.
The warehouse manager knows which equipment is reliable, what a crew will actually need, and which return date deserves a second look. Put routine assignments and movements into a shared record so the office can answer straightforward questions without interrupting that judgment all day.
Build the workflow with that person. Let them define the exceptions, inspect the first records, and explain where the list disagrees with reality. Their experience helps the system reflect the work. The objective is to make their knowledge usable across the operation and keep them involved in the decisions that need it.
Equipment and tool tracking can be a standalone engagement or part of a broader operations implementation. The starting scope might be a specific equipment category, warehouse-to-job movement, or the job-cost handoff. The Operations Review identifies the first useful boundary and what needs to be investigated.
Standalone equipment tracking is scoped in the Operations Review. No fleet-size price or hardware package is assumed. When it is part of broader operations work, implementation scope, integrations, revisions, support, and third-party fees are agreed in writing. Bring the equipment list you have today, even if it is a spreadsheet.
No universal tagging requirement is assumed. Start with the equipment categories where a reliable record will help your operation. The review determines what identity and movement information is needed and how your team can maintain it. Hardware and capture methods are scoped after that assessment, not promised before it.
We first look at the tools and routines they already use. A checkout needs an identifiable item, responsible person, job, and return expectation. The agreed method must capture those facts reliably. We do not promise an app-free implementation before reviewing your access and field requirements.
Yes, that is a capability we can scope using reliable assignment and utilization records. Accounting must approve allocation rules and reconcile the result. Assigned days, operating hours, rental charges, and owned-equipment rates are different inputs. The system should make those assumptions visible rather than hide them in a total.
The audit checks your accounting product, permissions, cost codes, available interfaces, and review requirements. QuickBooks and Foundation are among the environments we assess. A reviewed export or handoff may be appropriate where a direct connection is unavailable. We confirm the proposed path before promising an integration.
Bring it. A spreadsheet can be a useful register when identity, ownership, and updates are consistent. We examine whether the problem is the file, the handoff, or the lack of a responsible updater. The scope can improve the process around an existing record instead of assuming a replacement.
There is no published fleet-size cutoff. The useful question is whether repeated movement, unclear availability, service coordination, or missing job-cost records justify a scoped build. We assess the operating problem and the effort to maintain accurate information before recommending a standalone engagement or a broader implementation.
It can organize service dates, approved intervals, available usage records, and reminders for a responsible reviewer. Qualified personnel still decide inspection, repair, and readiness for use. The workflow supports maintenance coordination; it does not certify safe condition or replace manufacturer instructions.
Yes. Equipment tracking can be standalone or bundled with other operations workflows. Standalone pricing is scoped in the Operations Review after we understand your equipment, records, team, and required handoffs. No hardware, app, partner product, or ongoing software fee is assumed before the written scope is agreed.
The equipment list says you own it. The new job rented one anyway. Before blaming the decision, check whether anyone could establish that the owned item was available.
Safety programs fail on paperwork more often than on intent. How automation keeps toolbox talks, inspections, and incident records complete without adding field burden.
Tools disappear, rentals stay out past their need date, and nobody is sure what is on which job. A tracking approach that field crews will actually use.
Daily reports are the contractor's contemporaneous record and the most commonly skipped paperwork on a job. How to make them complete without adding an hour to the day.
Warranty calls arrive months after the job is closed, to a team that has moved on. How to handle them without losing the relationship or absorbing costs you do not owe.
We’ll discuss how work moves through your company, identify where to investigate first, and determine the scope of an operations audit.
Walk away with a map of how work moves through your office and a ranked list of what to investigate and fix first.
A real conversation. With the person who builds it.