Paxton maintenance: authorised support for Net2 and Paxton10

SEG Ltd provides authorised Paxton maintenance contracts for both Net2 and Paxton10 installations across England. Paxton hardware is famously durable — we routinely see Net2 controllers operating reliably ten and twelve years after install — but the software, the door hardware, and the user database all benefit from regular structured attention. Our maintenance programme keeps your Paxton system in a known-good state, prevents avoidable user-management drift, and catches PaxLock battery issues before they leave someone at a locked door.

A typical Paxton maintenance visit covers every controller (Net2 Plus, Net2 Nano, Paxton10), every reader and credential format, every door's hardware (closer, strike, mag lock, push-to-exit, REX, break-glass), and the Net2 or Paxton10 software itself. We apply firmware updates where Paxton has released them, audit the active user list, run a database backup, verify the fire-alarm interface still releases doors per BS 7273-4, and provide a written visit report with photos.

Contracts run annually with quarterly, bi-annual, or annual visit cadences. In-contract sites get priority reactive response with a published SLA and reduced labour rates. For multi-site Paxton10 deployments we provide consolidated reporting across the whole estate — useful for facilities managers running 10+ sites under a single Paxton10 cloud tenant.

What a Paxton maintenance visit covers

Controller health

Net2 / Paxton10 controllers verified for comms, voltage, battery backup state, and event log integrity. Firmware updates applied where Paxton has released a new version worth applying.

Reader operation

Every reader tested with valid and invalid credentials. LED, beeper, and feedback paths verified. PaxLock smart handles checked for battery state and signal strength back to the controller.

Door hardware

Closer adjustment, strike/mag lock holding force, push-to-exit operation, REX sensor, contact alignment, break-glass override release. Door-by-door checklist signed off.

Net2 / Paxton10 software

Software version verified, hotfixes applied, database backed up to a secure offsite location. Scheduled tasks (e.g. nightly DB backups, user expiry sweeps) verified as running.

User & credential audit

Active user list reviewed against the latest leaver report; expired or duplicate credentials removed; PIN codes refreshed where appropriate. Mobile credential validity confirmed.

Fire-alarm interface

Fire-alarm interface activated, all exit-route doors confirmed to release per BS 7273-4 NCP. This single check is the most important compliance test we perform.

How our Paxton contracts work

1. Baseline

For systems we didn't install we start with a baseline visit — document every controller, reader, door, and any pre-existing defects. Quote any remedial work so the contract starts from a known-good state.

2. Scheduled visits

Quarterly is standard for most commercial Paxton sites; high-traffic or compliance-critical sites benefit from monthly. Visits scheduled into our calendar a year ahead and confirmed in advance.

3. Reactive cover

In-contract sites get prioritised reactive response — usually 1-2 working days for non-urgent, same-day for system-down or doors held open. Reduced labour rate and parts at trade pricing.

Paxton maintenance FAQs

Yes — most of our maintenance work is on Paxton systems originally installed by someone else. For Net2 we just need admin access to your Net2 server; for Paxton10 we either need to be invited as engineers to your cloud tenant or take over the tenant entirely. Both are routine transitions.

Generally yes — typically 2-4 years depending on traffic and temperature. Higher-traffic doors burn through batteries faster. The Net2 / Paxton10 software flags low-battery in advance, but only if someone is actually checking. Our maintenance visits verify PaxLock battery levels and we replace pre-emptively where needed.

Apply major Net2 releases once they've been out a few months and any post-launch hotfixes are also released. We don't apply day-one releases on production systems. Hotfixes (security and stability) we apply at the next maintenance visit. Paxton10 is cloud-managed and updates automatically — we verify it actually happened.

Yes. Multi-site Paxton10 (single cloud tenant, multiple buildings) is straightforward — we maintain the whole tenant under one contract. Multi-site Net2 (separate databases per site) we coordinate visits across the estate. Single PO, consolidated reporting, volume pricing.