OUR APPROACH

How we evaluate.

Useful software guidance should make its evidence and limits clear.

Our planned testing approach

When comparing tools, we plan to use the same agency scenario and tasks for each product. The evidence record should include the date, plan used, whether access was purchased or provided, source material, steps completed, errors and limits. Demonstration data will be identified.

Articles will distinguish hands-on testing from vendor documentation. A product will only be described as tested when the scenario and evidence have been recorded. Prices and features can change, so each verified price needs a source and date.

What we do not assume

One tool will not fit every agency. Team size, client requirements, access controls, integrations and total cost can all change the choice.

This approach is planned; it does not imply that product tests have already been completed.