Technical Manuals, Validation Evidence, and Customer Documentation
Why technical documentation matters
Technical documentation helps customers understand what an assessment measures, how it was developed, how scores are calculated, what evidence supports interpretation, and what limitations apply.
The appropriate depth of documentation depends on the assessment type, maturity, intended use, and confidentiality requirements.
What documentation may be available?
Depending on the assessment, Testlify may provide or summarize:
- assessment purpose and intended population
- construct or competency definitions
- assessment blueprint
- content-development methodology
- subject matter expert review process
- scoring methodology
- proficiency levels or benchmarks
- reliability information
- validity evidence
- fairness considerations
- administration requirements
- accessibility considerations
- security controls
- version history
- result-interpretation guidance
- responsible-use limitations
Not every document is available publicly, and not every assessment has the same evidence package.
What is a technical manual?
A technical manual is a structured document describing the scientific and operational basis of an assessment.
It may include:
- Purpose and intended use.
- Construct model.
- Test design and content specifications.
- Development and review process.
- Scoring.
- Norms, benchmarks, or standards.
- Reliability.
- Validity.
- Fairness.
- Administration and security.
- Interpretation.
- Limitations.
- Version control.
Can customers request assessment evidence?
Yes. Customers can contact Testlify with:
- the assessment name
- intended role and use
- candidate population
- required evidence
- procurement or regulatory context
- deadline
- confidentiality requirements
Some documentation may require a confidentiality agreement or may be provided as a summary rather than a complete proprietary manual.
Why might evidence differ between assessments?
Testlify offers different assessment types and content families. Evidence maturity may vary based on:
- how long the assessment has been available
- sample size
- assessment stakes
- scoring model
- whether it is standardized or custom
- available outcome data
- frequency of content change
Customers should evaluate the evidence for the specific assessment they intend to use.
Frequently asked questions
Does Testlify have one technical manual for all assessments?
A platform-level methodology document may explain common practices, but each assessment family may require separate evidence.
Can customers receive item-level content?
Usually not. Item security and intellectual property may limit disclosure.
Can Testlify complete an RFP validation questionnaire?
Testlify can provide available information relevant to the assessment and procurement requirements.
Does the absence of a public manual mean no quality process exists?
Not necessarily. However, high-stakes customers should request enough evidence to evaluate the intended use.
Can customers conduct their own validation?
Yes. Customers may conduct local studies using job-performance or selection data, subject to privacy, legal, and contractual requirements.