Why Untracked Devices Are Your MSP's Silent Margin Killer

Every unmanaged device sitting outside a contract is a tiny, invisible invoice you'll never send. Multiply that by a few hundred endpoints across your client base, and you're not running an MSP. You're running a very expensive charity.

The frustrating part is that most of these billing gaps aren't caused by negligence. They're the natural byproduct of growth: a technician swaps out a failed workstation, a client adds a server during a busy quarter, or a new device gets synced in from Datto RMM without anyone stopping to ask, "Is this thing under contract?" Six months later, you're absorbing the cost of managing it anyway, just not billing for it.

This post walks through how to surface those gaps using Autotask's contract review tooling, and how to build a process that catches them before they compound into a real margin problem.

The Revenue Leak Nobody Puts on a Slide

Devices fall outside billing coverage in three predictable ways:

• Hardware replacements: A technician replaces a laptop, creates a new device record, and the new record never gets mapped to the client's existing contract. The old device had coverage; the new one silently doesn't.
• Onboarding oversights: During a client onboarding sprint, devices get created in Autotask faster than contracts get finalized. The devices go active; the contract association never catches up.
• Scope creep without billing adjustment: A client adds a NAS, a managed switch, or a new workstation. Your team handles it because that's what you do. The device record exists. The additional billing doesn't.

Most MSPs only discover the full extent of this damage during a quarterly business review or when a new operations manager decides to audit the asset list. By that point, you've been absorbing that cost for months.

The uncomfortable math: if you're managing 500 devices at $40/device/month and 10% of them are unbilled, that's $2,000 per month in services you're providing for free. Not because you made a business decision to, but because nobody noticed.

How Autotask's "Reviewed for Contract" System Works

Autotask has a built-in mechanism specifically designed for this problem. It's called the Reviewed for Contract status, and it works on a simple logic:

• Devices associated with an active contract automatically have the Reviewed for Contract checkbox set to checked. Autotask assumes if it has a contract, someone's already looked at it.
• New devices, and devices created by Datto BCDR, Datto Network Manager, or Datto RMM integrations, come in with that checkbox cleared by default.

That cleared checkbox is your signal. It means the device exists in your system, but nobody has confirmed it's generating revenue.

You can surface all unchecked devices using the filter built into the Datto RMM Devices dashboard tab. This gives you a live list of every device that hasn't been reviewed for contract coverage. From there, you have two paths:

• Assign the contract: On the device's edit page, populate the Contract and Service or Bundle fields. When you do, Autotask automatically marks the device as reviewed and disables the checkbox (because it's handled).
• Deliberately mark it as no contract needed: If a device genuinely doesn't warrant a billable contract, right-click the device and select Set as Reviewed - No Contract. The checkbox checks itself, and the device disappears from your unbilled queue. This matters because it separates "we decided not to bill for this" from "we haven't looked at this yet."

That distinction is worth keeping clean. One is a business decision; the other is a gap.

Copying Devices and the Silent Reset

One thing that catches MSPs off guard: when you copy a device in Autotask, the Reviewed for Contract status resets to unchecked on the new record, even if the original was fully contracted. This is intentional behavior, documented in the Copying a device documentation, because a copied device is a distinct record that needs its own contract review.

This matters operationally. If your team uses the copy function during hardware refreshes (which is common), every copied device enters your system in an unreviewed state. Unless someone has a habit of checking, those devices accumulate quietly.

The fix is straightforward once you know about it: add "review copied devices for contract assignment" to your hardware replacement checklist. It takes two minutes and closes a gap that would otherwise cost you monthly.

Building a Repeatable Audit Process with Contract Widgets

Catching unbilled devices reactively is better than not catching them at all, but building it into a recurring workflow is better still.

Autotask's contract widgets give you a dashboard-level view of your contract health. Two widgets are worth running together:

• Contracts Expiring (Next 60 Days): Shows the count of contracts by type that expire in the next 60 days.
• Expiring Contracts by Contract Type: Breaks down expirations by month, including contracts that expired in the last 30 days.

Here's how to pair these with device review in a practical workflow:

• Weekly: Filter the Datto RMM Devices dashboard for devices with Reviewed for Contract cleared. Any device on that list older than 7 days needs immediate assignment or a deliberate "no contract" decision.
• Monthly: Pull the Expiring Contracts widget. For every contract expiring in the next 60 days, review the associated device list before renewal conversations with the client. Devices not under that contract (or any contract) become line items in the renewal discussion.
• Quarterly: Full device audit against active contracts. Cross-reference total device count per client against billable units on their contract. Any discrepancy gets investigated.

The weekly check takes 15 minutes. The monthly review takes an hour. The quarterly audit takes a half day. Set against the revenue you recover, this is not a difficult ROI to justify.

What This Looks Like at Scale

An MSP managing 500 devices across 40 clients is a reasonable mid-market scenario. Based on what I've seen in the field, an 8-12% unbilled rate is realistic if no formal contract review process exists. That's 40-60 devices generating zero revenue despite consuming support time, tooling costs, and technician hours.

Run the numbers at $35/device/month (conservative):

• 40 unbilled devices: $1,400/month, $16,800/year
• 60 unbilled devices: $2,100/month, $25,200/year

That's not a rounding error. That's a technician salary.

The path to closing that gap doesn't require a platform overhaul or a new headcount. It requires:

• Turning on the Reviewed for Contract filter and making it part of a weekly dashboard check
• Training your team that copied and newly synced devices need contract review before the week closes
• Using the expiring contract widgets to proactively align devices to renewals rather than discovering gaps after a contract lapses

None of this is complex. The tooling is already in Autotask. The gap is usually process, not platform.

Closing the Loop

The devices billing problem is boring, unglamorous, and 100% fixable. Here's what to do with this information:

• This week: Filter your Datto RMM Devices dashboard for unchecked "Reviewed for Contract" records. See what's sitting there unresolved.
• This month: Add the Contracts Expiring (Next 60 Days) widget to your operations dashboard and build a monthly review into your billing cycle.
• Ongoing: Update your hardware replacement and device onboarding checklists to include contract assignment as a required step before the ticket closes.

The goal isn't perfection on day one. It's building a system where unbilled devices have a lifespan measured in days, not quarters. Autotask gives you the tools to do exactly that. Whether you use them is a process decision, not a technology one.