Job it-device-and-asset-register-reconciled-across-three-lists · revised 12 October 2026
One device register matching your device list and finance list, with owners checked
One register of devices that matches your device-management list and your finance asset list, with every owner checked against the staff directory and unmatched items listed.
You might be seeing
- The endpoint tool and the finance list give different device counts
- Nobody knows who holds some laptops
No passwords, keys, card details or admin invites needed to start.
What usually happened
Devices are bought, enrolled and handed out in different places that never meet. Each list is partly right, so a device can be paid for and not managed, or managed and not owned by anyone.
Who it’s for: IT lead preparing for Cyber Essentials, an insurer questionnaire or an ISO review whose device lists disagree.
Usually starts when: An auditor or insurer asked for a list of company devices and your device-management list and finance list give different counts.
The result: You receive one register of devices where every row appears in both your device-management list and your finance asset list, or is flagged as seen in one only. Each owner is checked against your staff directory. The operating system support status comes from the vendor's published dates, with the source named.
Check whether this job fits
Answer these without sending files, logins or personal data. Nothing is submitted unless you choose to contact us.
What you get
- The device register
- The mismatch list
- The owner column
- The support-status sources
Included
- Up to 300 devices across two device lists (your device-management tool and your finance assets), with owners checked against the staff directory
- A register keyed on serial number or asset tag
- A mismatch list of rows seen in one device list only, with the reason
- An owner per device and an operating system support column with its source and date checked
- A 20-row spot check, rows chosen by your admin after hand-over
Not included
- Discovering devices on your network
- Installing or changing endpoint software
- Reading device contents
- Buying or retiring equipment
- Personal phones
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Every register row appears in both device lists or is flagged as seen in one only, every owner is on the staff directory or flagged, and the counts per source reconcile to matched plus unmatched rows.
Evidence: The reconciliation table by source.
Your admin picks 20 rows after hand-over and checks them by console or in person; every device and owner is correct, and two different devices merged under one key fails the whole test.
Evidence: Your marked sample.
Every operating system support date names its vendor page and the date we checked it.
Evidence: The support column with its sources.
Sign-off. Your admin checks the sample and signs off in writing. The register is a list at one date, not a continuous record. Payment follows sign-off.
If it fails. If a test is not met, you do not pay for this fixed scope. We hand over what we found and agree whether to stop or re-quote; no surprise work.
When it fits, and when we stop
It fits when
- You can export the two device lists and the staff directory as tables
- Rows carry a serial number, asset tag or other stable key
- Device names that reveal people are replaced by asset tags before sending
We stop and tell you if
- You have no endpoint tool and no list at all, which is a discovery project, not a reconciliation
- No row has a key that appears in more than one list
- You want us to enrol or wipe devices
What could go wrong
This job reads files you send and writes a report. It changes nothing in your systems, so there is nothing to revert. Our copies of your files are deleted when the job ends.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| Two different devices are merged because a key is reused. | Matches need the same key, and clashes are listed for your admin rather than merged. |
| Device names reveal who uses them. | Asset tags replace names before files are sent, and owners are given as names only in the final register. |
| A support end date is wrong or out of date. | Each date names its vendor page and the day it was checked. |
A separate automated reviewer checks every output against the agreed test before hand-over. No person on our side reviews unless your agreement names one. Your named IT admin approves what is used.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the key columns, the owner rule and the three exports
- Normalise serial numbers and tags so the same device matches across lists
- Match each device across sources and mark rows seen in only one
- Fill the owner and the operating system support status with its source
- Separate automated review of matches and of every unmatched row
- Hand over the register and mismatch list; delete our copies
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept, and an enquiry creates no charge or booking. Work starts only after agreed inputs, secure access and any needed permissions are in place.
Need to keep it working?
Discuss a quarterly repeat of the register.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing managed lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Your endpoint tool may already export a full device list. Start there and add the finance list by hand if you only have a few dozen devices.
Questions
Do you find devices on my network?
No. We reconcile the lists you export. Finding unknown devices is a separate project.
Do you need access to my endpoint tool?
No. You run an export and send the file.
Is it kept up to date?
No. It is a list at one date. A quarterly repeat can be agreed.
Send an enquiry
Send us
- Your device-management list and finance asset list, and roughly how many devices each holds
- What identifies a device in each source
- Why you need the register
Later, once you agree
- The two device exports with the key columns, run by you
- The staff directory as name, work email and manager only, used to check owners
- A named admin for the 20-row check
- The agreement that names the model provider, its country and how long it keeps data, settled before any real personal data is shared
You keep every device and every tool. We work from exports and change nothing. Device names that contain a person's name are replaced by asset tags before the files are sent.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “it-device-and-asset-register-reconciled-across-three-lists” as the subject.