Request access

Project intake

Intake in Duxer Cloud is project-led. You don't pile assets into a flat list and reconcile them later — you create a project (one collection, one client, one date), and assets attach to it.

This page covers the practical mechanics. For the why, see For Operators.

Why project-led

The bottom of every ITAD workflow is a single fact: a load of stuff came from a client. Everything else — assets, documents, ESG impact, revenue — attaches to that load. Modelling the project as the unit (rather than the asset) means:

  • Waste Transfer Notes generate from data you already entered.
  • DEFRA submissions stay grouped correctly.
  • Client-facing reports cover the project, not "all assets ever".
  • Audit is per-collection, not per-asset detective work.

Creating a project

Projects → New project. Required fields:

| Field | Used for | | -------------- | --------------------------------------------- | | Project name | Display + report titles | | Client name | Links to a client record (or creates one) | | Start date | Project timeline |

Highly recommended:

  • Collection address & postcode — needed for WTN and DEFRA submissions.
  • Contact person on site — appears on chain-of-custody documents.
  • ATF details — the Authorised Treatment Facility's name, address, postcode, and waste permit number. Pre-fill these on your tenant default and they auto-populate every new project.

Adding assets

Three ways:

  1. Manual — Assets → New. Best for low-volume collections.
  2. CSV import — Assets → Import. We supply a template; map columns once and the import remembers the mapping for that client.
  3. Mobile scan-in — scan barcodes / serial numbers using the iOS app. Each scan attaches to the currently-open project.

Whichever route you take, every asset gets:

  • A device type (Laptop / Desktop / Server / Monitor / Phone / Other).
  • A status (new by default).
  • A unique tag — printable as a QR sticker for bench tracking.

The status pipeline

Assets progress through a fixed set of statuses. The platform refuses illegal transitions and stamps every change with the operator and timestamp.

new → collected → inspected → tested → wiped → ready → listed → sold
                                                    ↓
                                              in_repair / in_storage / retired / disposed

Status drives downstream behaviour:

  • wiped / ready / listed / sold automatically flips data_wiped to true.
  • sold automatically sets disposition type to remarketed.
  • retired / disposed require a disposition type — recycled or scrapped.

You override any of these manually if your workflow needs it; the auto-behaviour exists so the common case takes zero clicks.

Documents

Once your project has a collection address, ATF details, and at least one asset, you can generate:

  • Waste Transfer Note — non-hazardous waste collection.
  • Hazardous Consignment Note — when the project includes WEEE Annex IIIb hazardous codes.

Both PDF documents carry your branding, your reference number (auto-generated in DX-{YYYY}-{YYYYMMDD}-{NNNN} format), and a draft → signed → emailed status workflow.

DEFRA Digital Waste Tracking

Once you've signed off a transfer document, you can submit the Receipt of Waste record direct to DEFRA's Digital Waste Tracking service from the project page. Each submission is logged on the project with the DEFRA reference returned.

DEFRA integration requires the standard waste-carrier credentials — set these up in Settings → Integrations.

What to read next