Plan your seven-day free trial with 100,000 analysis rows

Understand the trial allowance

New self-service organisations receive a seven-day trial with up to 100,000 analysis rows. The allowance is shared across the organisation rather than multiplied by the number of invited team members. No card is required to start the advertised trial. Consult the current pricing page and account balance for the terms that apply when you sign up.

The trial is an opportunity to evaluate your workflow with representative evidence. It is not a promise that every survey format, manual clause or engineering question is automatically covered. Choose the relevant template and read the resulting coverage before drawing conclusions.

Prepare one useful evaluation file

Keep an untouched source export and choose a manageable file that represents the work you actually need to review. Confirm its format, units and identifiers against the selected check template. When project alignment matters, prepare the appropriate reference files and inspect their registration results.

Record the questions you want the trial to answer: can the export be interpreted correctly, can findings be traced to source rows, and can your reviewers follow the evidence? A deliberately controlled example is easier to evaluate than repeated uploads without a stated purpose.

Evaluate findings, not just the upload

Confirm receipt and analysis state, then read errors, warnings and skipped checks. Follow one finding to the affected source records and investigate the reason. Correct an export only when the original evidence supports that correction, and inspect the replacement result separately.

Invite the relevant colleagues through the normal team workflow and check their permissions. A person’s ability to view a file does not automatically make them eligible to co-sign or certify it. Test the review path with the independence requirements intact.

Decide what to continue after evaluation

After the trial, processing uses the platform’s prepaid-credit workflow. Review current pricing and the available account balance before further paid processing. Usage, pending holds and posted transactions should be read in their own context; a billing movement does not prove a survey passed.

Keep your evaluation notes and unresolved limitations. The best outcome is a clear understanding of which checks ran, what evidence the team can review and which engineering responsibilities remain outside the software. Use the onboarding library to build familiarity with the precise actions.

Sources and scope

This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.