Skip to content

Resource · evaluation

Test software with a real working question.

Use the scorecard to compare the same job, a change, a blocked step and an export. Record what was shown and what still needs proof.

Spectra guide · Source review: 3 November 2026

Use the working documents

Start blank, or inspect the clearly labelled fictional example.

Download editable CSVOpen printable A4 sheetOpen fictional completed exampleDownload fictional example CSV

At a glance

A fair evaluation records what was demonstrated, what needs configuration or a third party, what is planned and what was not shown. Test the operational hand-off you need to improve—not a polished feature tour.

01 / Define

Turn current friction into a test.

Describe the failure you want to reduce: missing survey evidence, proof confusion, workshop reconstruction, installation exceptions or unclear actuals. Name the role and success condition.

02 / Test

Include a change, a block and an export.

Ask the supplier to run your scenario, change an approved detail, block a delivery condition, show who can release it and export the resulting record. Record the observed result and dependency.

Score only what you saw. If a step was described as planned, configured by a partner, or unavailable in the session, write that status. Do not convert a roadmap answer into a pass, and do not treat Spectra's public sample as evidence that another product, or Spectra itself, is live.

03 / Decide

Keep data and commercial questions explicit.

Verify current terms, total cost, implementation effort, migration responsibility, permissions, security, retention, export, deletion and support directly with each supplier.

Bring the job. Explore the next step.

Discuss your workflow