Many people confuse two very different things: the system’s ability to build a model and calculate its scores, and your facility’s right to use a published psychometric. The first is a technical matter provided by the system, and the second is a matter of licensing and rights that no provider can grant you.
This confusion puts centers in a difficult situation: protected standards are built into the system without authorization, and then the matter is discovered at the first review or dispute.
Why is this requirement included in the purchasing decision?
Because it specifies what is written in the offer and what remains your responsibility. A supplier who says “famous standards are built into the system” makes a promise that requires scrutiny: Are they licensed? Who obtained the license? Who does it apply to – his or yours?
More precisely, the clause should be written like this: The system provides model building and calculation and comparison rules, and your facility is responsible for the rights to use any protected tool you choose to enter.
What should the scope cover?
What the system provides (technical capability):
- Building models with different question types and conditional logic.
- The rules for calculating scores and subdomains are as you specify.
- Send the form to the right respondent at the right time.
- Save versions and compare over time.
- Controlling what appears to the client and what remains to the specialist.
What remains on your facility (right and use):
- Obtaining a license to use any published standard protected by copyright.
- Adherence to the rules for applying and interpreting the tool as determined by its publisher and professional authority.
- Choosing the right tools for your services and categories — a professional, not a technical, decision.
- Ensure the qualifications of those who apply and interpret the tool.
Checklist in demo
- Ask: Are there built-in metrics? What is its exact legal status?
- Ask to build one of your models in front of you: How long did it take? Can your team build it later?
- Test a composite calculation rule: subdomains and overall score.
- Test conditional logic: A question that appears based on a previous answer.
- Ask who is responsible for inserting a protected device: Ask for the answer to be written in the presentation.
The practical question that resolves this file: Who will build the models after operation? If your team can build and modify it themselves, you’re independent. If every modification requires a request to the provider, your improvements will be postponed and accumulated — experience this yourself in the demo, not just ask for it.
Limits that need to be adopted
- No automatic explanation: The system calculates the score and does not translate it into a case description or classification.
- Licensing Responsibility: It is expressly written in the contract so that it is not assumed by either party.
- Internal tools: If you build a tool specific to your center, its professional status and authority are your responsibility — it is not treated as a standard tool.
- Professional Review: Any model built into the system is approved by your specialist before using it with clients.
The next step is to document the requirements
In your requirements, write two separate items: modeling capabilities, and responsibility for tool licenses. And review Evaluation page.
Request a system demo
We build one of your models in front of you with its calculation rules and conditional logic — and we explicitly state the limits of our and your liability in the tool licenses.