How to Plan IT Equipment Disposal Across Multiple Sites: A Collection and Reconciliation Checklist

Retiring equipment from several offices, campuses or branches involves more than booking a vehicle. Local teams may use different asset lists, collection dates may depend on replacement equipment arriving, and the final paperwork needs to account for equipment from every location.

This guide explains how to organise the disposal stage of a programme across multiple UK sites: prepare a collection schedule, agree responsibilities, control handovers and reconcile the equipment received with its recorded outcomes.

For delivery support, explore Astralis’s IT asset disposal services. This checklist focuses on the planning work your organisation and its appointed provider should agree before collections begin.

At a glance: what should a multi-site disposal plan include?

A practical plan needs one programme owner, a named contact at each location, a consistent equipment list, agreed collection and security requirements, and a process for resolving differences between expected and received assets. Close each collection against its own records, then consolidate the results across the programme.

• Confirm which assets are authorised for retirement.
• Agree the scope and access arrangements for each site.
• Schedule collections around operational dependencies.
• Record what is handed over and what is received.
• Resolve discrepancies and track processing outcomes.
• Reconcile the final records before closing the programme.

1. Give the programme one owner and each site a clear role

Appoint a central owner who can approve the scope, coordinate dates and resolve issues with the provider. Each location also needs a contact who understands the equipment being released and the collection arrangements.

Agree who is responsible for:

• Authorising equipment retirement and confirming ownership.
• Identifying equipment that must remain in use or be returned to a lessor.
• Preparing equipment and providing access to the collection team.
• Signing the handover record.
• Checking receipt reports and investigating differences.
• Accepting the final documentation and closing outstanding actions.

A local contact should know when to pause a collection and seek approval. For example, an unexpected server or a leased device should not be added simply because it is beside the equipment awaiting removal.

2. Build a collection schedule around each location

Use a shared schedule with a consistent site code for every location. Record estimated quantities early, then confirm them before the collection date. Distinguish a provisional booking from a confirmed collection so that local teams do not prepare equipment against an unagreed date.

The example below is illustrative. It shows the structure of a planning schedule rather than an Astralis project or a promised service timetable.

Include the full address, named contact, contact details and dates in your controlled working version. Share it only with the people who need it. Where replacement deployments determine when old equipment can be released, connect this schedule to the wider technology refresh programme.

Before confirming each visit, check stairs, lifts, loading restrictions, parking, building permissions, equipment packaging and any requirement for onsite activity. Agree arrangements with the provider rather than assuming every location can follow the same collection plan.

3. Use one equipment-list format across all sites

Different spreadsheets and naming conventions make reconciliation harder. Give local teams a common format and explain which fields must be completed before collection and which will be confirmed during processing.

• Source: site code and department or cost centre where relevant.
• Identity: asset tag and serial number where available, equipment type, make and model.
• Ownership: owned, leased or another status requiring confirmation.
• Authorisation: approval reference and any excluded equipment.
• Requirements: agreed data treatment, reuse restrictions or other handling instructions.
• Tracking: collection reference, receipt status, recorded outcome and exceptions.

If a complete serial-number list is unavailable, agree how quantities and identities will be recorded and reconciled. A quantity-only handover and an item-level receipt report provide different levels of detail; both parties should understand that distinction before equipment leaves the site.

Keep passwords, recovery keys and unnecessary personal information out of the asset list. Agree a separate controlled process for any access or device-management actions needed before treatment or resale.

4. Agree the treatment and reporting requirements before handover

Mixed collections can contain devices intended for reuse, media requiring destruction, leased assets and equipment with no data storage. Make the instructions clear enough that local teams and the provider can distinguish these groups.

Record how failed erasure, unidentified equipment or an asset outside the agreed scope will be handled. Identify who can approve an alternative route and which items must be held while a decision is made.

Agree the reporting milestones for each collection or processing batch. In a phased programme, waiting until the final site has been collected before checking earlier batches can leave discrepancies unresolved for weeks.

Ask which records apply to each equipment type. Data erasure or destruction certificates relate to the data-bearing assets treated; monitors and other non-data-bearing equipment need the appropriate asset or disposal records.

5. Control the handover at each site

Before the collection team arrives, the local contact should confirm the authorised equipment is ready and separated from devices that must remain. Check the collection team against the arrangements agreed with the provider.

At handover, record the collection reference, source site, date, authorised representatives and the equipment or quantities transferred, at the level of detail agreed. Record any substitutions, additions or shortages rather than relying on a later email to explain them.

Retain the handover record centrally and give the local contact a clear route for reporting a concern. The record should explain what changed hands; it should not imply that processing or data sanitisation has already been completed.

6. Reconcile expected assets, receipt and final outcomes

Reconciliation connects three stages: what your organisation expected to release, what the provider received, and what happened to the equipment during processing. Differences require investigation; a missing match should not automatically be treated as proof of a lost asset or a completed disposal.

Maintain an exception log with a reference, issue, responsible person, next action and resolution date. Link every exception to the relevant site and collection. This makes a discrepancy manageable without losing it inside a larger programme total.

For background on the processing stage, see what happens after IT asset collection.

7. Close each collection, then close the programme

A collection is not administratively complete simply because the equipment has left the building. Check that receipt has been reconciled, the agreed treatment and disposition records are available, and any commercial adjustments or resale returns have been accounted for.

• Every site and collection reference appears in the programme record.
• Expected and received equipment has been reconciled, with differences explained.
• Data-bearing assets have the applicable treatment records and certificates.
• Other equipment has the appropriate asset or disposal records.
• Resale statements and agreed charges can be matched to the relevant assets or batches.
• Environmental reporting, where included, has a clear scope and identifies estimates appropriately.
• Outstanding exceptions have been resolved or formally assigned for follow-up.

Update your internal asset register using the agreed evidence and approval process. Retain the final pack in line with your organisation’s record-retention requirements.

Common mistakes in disposal programmes across multiple sites

• Mixing provisional and confirmed lists: local teams release equipment before retirement approval is complete.
• Using inconsistent site references: reports cannot be matched back to the originating location.
• Assuming the same access arrangements everywhere: a collection is delayed because parking, lifts or building permissions were not checked.
• Closing assets too early: the internal register records disposal before receipt and outcomes have been reconciled.
• Reviewing only the final total: matching programme quantities can hide differences between sites or individual assets.

How Astralis supports a phased IT retirement programme

Astralis helps UK organisations coordinate secure collections, asset registration, data erasure or physical destruction, and appropriate reuse, resale or recycling. We use our own vehicles and personnel for all collections, with the scope, security requirements and reporting arrangements agreed before work begins.

Our standard reporting milestones are a collection report provided on site, a booking-in report within two working days of receipt at our facility, and full audit trail documentation within 30 working days of receipt. For phased programmes, we agree how collection references, reporting batches and any project-specific requirements will be managed.

Planning equipment retirement across several locations? Explore our ITAD services for UK organisations and discuss your sites, equipment and timescales with our team.

Frequently asked questions

Do all sites need to be collected on the same day?

No. Collections can be phased around equipment availability, deployment dates and access arrangements, subject to an agreed schedule. Each visit should have its own reference and records so that it can be reconciled separately.

What if a site does not have a complete asset list?

Agree how equipment will be counted, identified and recorded before the collection. Make clear what the handover record will contain and how the provider’s receipt report will be checked against it. Record any limits to the available starting information.

How should discrepancies between sites be managed?

Log each difference against the relevant site and collection reference, assign an owner and investigate it using the handover and receipt records. Do not offset an unexplained shortage at one location against an unexplained addition at another.

Should there be one consolidated report or separate site reports?

A programme may need both. Site or collection records support reconciliation, while a consolidated view helps the central owner track completion. Agree the reporting structure, identifiers and access requirements before collections start.