“Dell PowerEdge R740” identifies a server family; it does not identify a server a buyer can accurately price. CPU count, DIMMs, drives, controllers, networking, accelerators, licences, rails, condition and location can turn two examples of the same chassis into completely different commercial propositions.
The useful question is not “What percentage of its original price is it worth?” It is “Can a buyer identify, test, move and resell this exact configuration with confidence?” This worksheet helps you assemble that evidence without pretending there is one fixed server price.
1. Quote-readiness scorecard
Score one point for each completed evidence group below. Five points does not guarantee a higher offer; it means a buyer can assess the estate with fewer assumptions. Missing information tends to widen risk and reduce confidence, especially across a large batch.
| Point | Evidence group | Minimum useful detail |
|---|---|---|
| 1 | Identity | Manufacturer, exact model/generation, service tag or machine type |
| 2 | Configuration | CPU, memory, storage, controllers, networking, accelerators and PSUs |
| 3 | Condition | Power-on/POST result, management warnings, faults, damage and missing parts |
| 4 | Supportability | Firmware/access state, licences or support that can legitimately transfer, and reset status |
| 5 | Logistics | Quantity, site, rack/loose state, packaging, rails, access and collection constraints |
2. Establish the exact identity
Start with the physical asset label and management controller, not an old purchase-order description. Record the full model, form factor, generation, service tag, serial number, machine type and any chassis or backplane variant. Keep serial-controlled data in the private asset register; a quotation sheet can use an internal asset ID where sharing the serial is unnecessary.
Where available, export the current hardware inventory. Dell documents that iDRAC can display installed processors, DIMMs, drives, controllers, NICs, GPUs and power supplies in its system inventory. Other manufacturers provide their own service-tag or management tools. Reconcile the export to a physical sample because components can be removed and inventory can be stale.
3. Complete the configuration worksheet
“Dual Xeon, lots of RAM” is not enough. Record the exact CPU model and quantity; total memory plus DIMM size, type and speed; every drive’s model, capacity and interface; RAID controller or HBA; networking and Fibre Channel cards; GPUs or other accelerators; PSU quantity and rating; and proprietary items such as risers, caddies, bezels and rails.
| Area | Record | Evidence |
|---|---|---|
| Compute | CPU model/count; accelerator model/count | Inventory export plus photographs where accessible |
| Memory | Total, DIMM count, size, type and speed | Slot inventory and warning state |
| Storage | Drive model/count/capacity/interface; backplane; controller | Inventory, bay photographs and health/fault state |
| Connectivity | NIC, HBA and other card model/port count | Slot inventory and rear photographs |
| Completeness | PSUs, caddies, blanks, risers, bezel and rails | One labelled set of photographs |
If several systems are truly identical, state the sampling method and note exceptions separately. Do not copy one known configuration across an entire rack merely because the front badges match.
4. Describe condition in testable terms
Separate cosmetic condition from functional evidence. Record whether the server powers on, completes POST, reaches its management interface, reports hardware warnings and sees the listed components. Photograph obvious chassis damage, bent rack hardware, missing blanks, broken latches and liquid or corrosion signs.
Avoid broad claims such as “fully tested” unless you can explain what was done. “Powered on, completed POST, iDRAC inventory exported, two fan warnings shown” is far more useful. Also state whether passwords and configuration have been reset and whether any transferable support or licence claim has been verified with the provider.
5. Use completed-market evidence properly
Active listings show what sellers ask, not what buyers pay. Refurbished-retailer prices can include VAT, testing, configuration work, returns exposure and warranty. A trade quotation reflects handling, testing, stockholding, resale risk and margin. Treat each as a different layer of evidence.
Build a small comparison set from recent completed sales with the same generation, chassis/backplane, CPU family, memory level, storage inclusion, controller, condition and geography. Note material differences rather than forcing an average. Refresh the evidence at least quarterly because enterprise-component demand and logistics can move faster than the chassis badge changes.
Do not add the retail value of every installed component and call the sum a server value. Some parts increase the system’s usefulness; others sell better separately; some licence or support rights do not transfer at all. The sale route determines which costs and risks sit with the seller.
6. Worked example: show uncertainty, not a fake number
Suppose the first record says only “R740, dual CPU, 256GB”. That establishes a family and a few broad facts, but it leaves CPU models, DIMM layout, backplane, controllers, drives, NICs, PSUs, rails, condition and location unknown. A buyer must price defensively or ask a long list of questions.
After inventory, the record contains two exact CPUs, sixteen matching DIMMs, an eight-bay SFF backplane, controller model, four drive caddies with no drives, two 10GbE ports, redundant PSUs, rails, clean POST and one non-critical management warning. The added evidence improves confidence, not an invented price. Current comparable sales and the intended sale route must still determine the commercial figure.
7. Include logistics and estate-level differences
Quantity can create efficiency, but a large mixed estate is not simply one unit price multiplied by a count. Record which systems are racked, loose or palletised; site access and loading restrictions; collection postcode; lift and parking information; packaging; deadline; and whether rails, drives or loose cards are separate.
For repeated configurations, provide counts per configuration rather than one total. Put damaged, incomplete or data-held items into exception groups. This lets a buyer discuss a coherent scope without silently assuming every asset has the best specification in the batch.
8. Keep data clearance separate from valuation
Do not expose customer data, credentials, hostnames or network diagrams in a sales pack. Your organisation remains responsible for authorising and evidencing the data treatment applied before hardware leaves its control. The NCSC’s secure sanitisation guidance explains why ordinary deletion is not a universal answer.
This page does not provide a wiping procedure or decommission project plan. Use an approved organisational process for media, licences, legal holds and ownership. Valuing the chassis and clearing its data are connected project dependencies, but they are not the same service or approval.
9. Prepare a concise enquiry for GPUsed
For an individual or mixed enterprise estate, start at GPUsed’s enterprise server-hardware page. For compute cards, use the data-centre GPU route; for larger mixed lots, use bulk computer-component enquiries.
Send the configuration groups, quantities, condition, location, time frame and clear photographs. Explain what is excluded as well as included. GPUsed can then assess the hardware presented; the final quote still depends on accurate details, inspection and the agreed commercial scope.
Sources, review cycle and limits
Technical and process guidance checked on 12 September 2026. Market evidence is deliberately not hard-coded into this permanent guide and must be refreshed when the hardware is valued. No page can guarantee a price without the actual configuration, condition and sale scope.