Evaluation scorecard
Know what to ask — and what evidence to look for.
A working scorecard for evaluating ERP for ITAD, electronics recycling, refurbishment, and resale. Set your own priorities, note the evidence you saw, and record open questions. It contains no vendor scores or pass marks.
How to use it
- Set a priority for each requirement before the first demo
- Ask to see the evidence listed — not a description of it
- Record open questions and who owns the answer
- Share the printed scorecard with each stakeholder
The scorecard
Entries stay in this browser tab until you reload. They are not saved or sent anywhere.
0 of 30 requirements reviewed · not saved or sent
Asset identity
RequirementEvidence to reviewPriorityReview stateOpen question / notes
One record per asset from first scan to final dispositionTrace a single asset end to end in the demo.
Serial, asset tag, and client reference are all searchableSearch by each identifier you use today.
History is retained after the asset is sold or recycledOpen a closed asset and review its history.
Receiving & grading
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Receipts are matched to the expected orderA receipt with a short line and an unmanifested item.
Exceptions are held for review rather than lostWho resolves exceptions, and where they are recorded.
Grading standards are configurable and consistent across benchesYour grading definitions modeled in configuration.
Chain of custody
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Each handling event is time-stamped with a userThe custody timeline for one asset.
Sanitization evidence stays with the assetWhere erasure evidence is kept, and what happens when it is missing.
Downstream disposition is recordedRecycling and downstream vendor records.
Warehouse
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Locations model your sites down to the binYour location hierarchy.
Movements are recorded against the assetMovement history for one unit.
Available, committed, and held stock are distinctAn order reserving specific serials.
Contracts & settlements
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Client contract requirements are recorded, not kept in spreadsheetsA contract with your pricing model and charges.
Valuation, grading devaluation, and charges are visible per lineA settlement explained line by line.
Settlements are reviewed before publicationThe approval step and who performs it.
Client reporting
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Clients can retrieve certificates and reports themselvesThe client portal for one job.
Access is limited to authorized client usersHow client users are added and removed.
Reports use references the client recognizesClient references on reports and certificates.
Integrations
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Each required connection has a named owner and support routeOwnership for each system you need.
Records, direction, and timing are documentedA written integration scope.
Failure and mismatch handling is definedWhat happens when a transfer fails or a record does not match.
Migration
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Open records to move are identifiedA migration scope by record type.
History treatment is agreedMigrate, archive, or read-only — decided per record.
A reconciliation plan exists before cutoverCount, value, and spot-check approach.
Security
RequirementEvidence to reviewPriorityReview stateOpen question / notes
ISO/IEC 27001 certificate and certified scope reviewedThe certificate and scope statement.
Your security questionnaire is answeredQuestionnaire responses.
Data ownership and export at end of contract confirmedContract terms and export formats.
Commercial scope
RequirementEvidence to reviewPriorityReview stateOpen question / notes
Proposal scope matches your sites, teams, and modulesThe written proposal.
Implementation responsibilities are statedWho does what, by phase.
Integration scope and ownership are clearIntegrations listed in the proposal.
Review view · 0 of 30 requirements reviewed · not saved or sent
ITAD ERP evaluation scorecard
0 of 30 requirements reviewed · not saved or sent
Prepared with the RazorERP evaluation scorecard. Entries are not saved or sent.
Asset identity
One record per asset from first scan to final disposition
Evidence: Trace a single asset end to end in the demo.
Priority
Not set
Review state
Not reviewed
Notes
—
Serial, asset tag, and client reference are all searchable
Evidence: Search by each identifier you use today.
Priority
Not set
Review state
Not reviewed
Notes
—
History is retained after the asset is sold or recycled
Evidence: Open a closed asset and review its history.
Priority
Not set
Review state
Not reviewed
Notes
—
Receiving & grading
Receipts are matched to the expected order
Evidence: A receipt with a short line and an unmanifested item.
Priority
Not set
Review state
Not reviewed
Notes
—
Exceptions are held for review rather than lost
Evidence: Who resolves exceptions, and where they are recorded.
Priority
Not set
Review state
Not reviewed
Notes
—
Grading standards are configurable and consistent across benches
Evidence: Your grading definitions modeled in configuration.
Priority
Not set
Review state
Not reviewed
Notes
—
Chain of custody
Each handling event is time-stamped with a user
Evidence: The custody timeline for one asset.
Priority
Not set
Review state
Not reviewed
Notes
—
Sanitization evidence stays with the asset
Evidence: Where erasure evidence is kept, and what happens when it is missing.
Priority
Not set
Review state
Not reviewed
Notes
—
Downstream disposition is recorded
Evidence: Recycling and downstream vendor records.
Priority
Not set
Review state
Not reviewed
Notes
—
Warehouse
Locations model your sites down to the bin
Evidence: Your location hierarchy.
Priority
Not set
Review state
Not reviewed
Notes
—
Movements are recorded against the asset
Evidence: Movement history for one unit.
Priority
Not set
Review state
Not reviewed
Notes
—
Available, committed, and held stock are distinct
Evidence: An order reserving specific serials.
Priority
Not set
Review state
Not reviewed
Notes
—
Contracts & settlements
Client contract requirements are recorded, not kept in spreadsheets
Evidence: A contract with your pricing model and charges.
Priority
Not set
Review state
Not reviewed
Notes
—
Valuation, grading devaluation, and charges are visible per line
Evidence: A settlement explained line by line.
Priority
Not set
Review state
Not reviewed
Notes
—
Settlements are reviewed before publication
Evidence: The approval step and who performs it.
Priority
Not set
Review state
Not reviewed
Notes
—
Client reporting
Clients can retrieve certificates and reports themselves
Evidence: The client portal for one job.
Priority
Not set
Review state
Not reviewed
Notes
—
Access is limited to authorized client users
Evidence: How client users are added and removed.
Priority
Not set
Review state
Not reviewed
Notes
—
Reports use references the client recognizes
Evidence: Client references on reports and certificates.
Priority
Not set
Review state
Not reviewed
Notes
—
Integrations
Each required connection has a named owner and support route
Evidence: Ownership for each system you need.
Priority
Not set
Review state
Not reviewed
Notes
—
Records, direction, and timing are documented
Evidence: A written integration scope.
Priority
Not set
Review state
Not reviewed
Notes
—
Failure and mismatch handling is defined
Evidence: What happens when a transfer fails or a record does not match.
Priority
Not set
Review state
Not reviewed
Notes
—
Migration
Open records to move are identified
Evidence: A migration scope by record type.
Priority
Not set
Review state
Not reviewed
Notes
—
History treatment is agreed
Evidence: Migrate, archive, or read-only — decided per record.
Priority
Not set
Review state
Not reviewed
Notes
—
A reconciliation plan exists before cutover
Evidence: Count, value, and spot-check approach.
Priority
Not set
Review state
Not reviewed
Notes
—
Security
ISO/IEC 27001 certificate and certified scope reviewed
Evidence: The certificate and scope statement.
Priority
Not set
Review state
Not reviewed
Notes
—
Your security questionnaire is answered
Evidence: Questionnaire responses.
Priority
Not set
Review state
Not reviewed
Notes
—
Data ownership and export at end of contract confirmed
Evidence: Contract terms and export formats.
Priority
Not set
Review state
Not reviewed
Notes
—
Commercial scope
Proposal scope matches your sites, teams, and modules
Evidence: The written proposal.
Priority
Not set
Review state
Not reviewed
Notes
—
Implementation responsibilities are stated
Evidence: Who does what, by phase.
Priority
Not set
Review state
Not reviewed
Notes
—
Integration scope and ownership are clear
Evidence: Integrations listed in the proposal.
Priority
Not set
Review state
Not reviewed
Notes
—
Bring your scorecard to a demo.
We will work through your priorities and open questions.