5 gates · Public CSV · No signup

An installed agent is not an accepted endpoint.

Use these five evidence gates before expanding an RMM pilot. Each gate defines a success criterion, the proof to retain, and a stop condition that blocks a wider rollout.

Download the CSV Add the result to client onboarding Troubleshoot a missing check-in Resolve installation before acceptance Map the test to core RMM functions Ask vendors to prove the pilot path Run the 25-test pilot plan Test remote-access authorization Plan the implementation rollout Track migration waves Define support response clocks Use the new-MSP RMM guide Use the full evaluation checklist Use the Data Package

1. Identity and placement

Prove one current, stable endpoint record under the intended tenant, customer, and site. Stop for duplicates, stale check-ins, or ambiguous identity.

2. Controlled detection

Create a harmless known condition and retain the alert, timestamps, device context, severity, and owned route. Stop if it is missing, late, or misrouted.

3. Authorized action

Run one low-risk approved action and retain who targeted what, when it ran, its output, and its final state. Stop on the wrong target, privilege, or unknown result.

4. Patch reconciliation

Reconcile the baseline scan, attempted change, reboot state, post-action scan, and any exception. A dispatched job alone is not completion evidence.

5. Removal and handoff

Prove that access, tokens, and the agent can be removed while required evidence survives. Stop if the endpoint still checks in or residual access remains.