How to Read Hogan HPI Subscales When the Main Score Is Average

What does an average HPI percentile establish?

An average HPI percentile is a broad comparison, not a complete description of the profile. A percentile rank tells you what percentage of scores in a specified distribution fall below a given score. A norm group is the reference population represented by that distribution. The NCME Assessment Glossary defines these terms in relation to a specified population or score distribution; neither means that the person has a corresponding percentage of a personality trait. The percentile is meaningful only with its report’s comparison frame and category key. “Average” names a band used by that report, not a claim that every response or narrower theme sits at the midpoint. Keep the primary-scale percentile as the summary of that broad scale. Hogan’s 2013 Interpreting HPI Subscales guide says primary scales are often presented as percentiles in relation to the general workforce, while subscale results are raw scores. It argues that narrower results can add nuance and distinguish people whose main-scale scores are similar. That supports looking more closely when the broad result leaves a relevant question unresolved; it does not turn a subscale into another percentile or establish a separate verdict. The displays answer different questions: the primary percentile locates the broad score in its comparison, while subscale detail may point to distinctions within that result. An average primary percentile and a noticeable subscale entry are not inherently contradictory. The average remains the anchor; the subscale may refine what to ask, provided its metric and meaning are clear. Neither output predicts an action from the number alone. If the narrower entry seems striking, first identify what the report displays and how it should be read. This keeps “average” from being mistaken for a featureless profile, while preventing one detail from overruling the broad result before its format is understood.

Sources: Assessment Glossary; Interpreting HPI Subscales

Why can an average scale contain a noticeable subscale contrast?

A broad HPI scale can sit near the middle of its comparison group while a narrower subscale appears more distinctive because the displays summarize responses at different levels. The primary scale gathers a wider domain; subscales separate some themes within it. The contrast is not necessarily a contradiction. It may mean the broad summary leaves a pattern worth asking about, while remaining the main score to interpret. Hogan’s 2015 ‘FAQ Blog Series: The Hogan Personality Inventory (HPI)’ describes Homogenous Item Composites, or HICs, as related sub-themes within the seven primary dimensions. Its Adjustment example names themes such as worry, regret, complaints, patience, and irritability. The FAQ says these item themes clustered during development and that Hogan refined the composites through item development, empirical and theoretical refinement, and factor analyses. This explains the architecture: a broad scale represents a domain, while a subscale groups narrower content. It does not make each theme a self-contained measure of a separate personality quality. In a purely illustrative pattern, imagine a report with an average primary-scale percentile and one attention-catching subscale. The broad result still summarizes the primary scale against its norm group. The narrower result may indicate that responses within one theme differ from the broader pattern. It does not turn that subscale into a second primary-scale percentile or establish how someone will behave in every setting. The useful question is smaller: what, if anything, does this theme add to the broad description? That possibility is the point of Hogan’s 2013 ‘Interpreting HPI Subscales.’ The publisher says subscales can distinguish people with similar main-scale scores, including average scores, and presents them as added nuance. This is a reason to inspect the detail, not independent proof that any difference is precise, important, or useful for every reader. The source supports a narrower claim: subscales may help an interpreter notice distinctions not shown by a broad score alone. The published subscale structure should not be treated as timeless. Hogan’s 2015 FAQ states a set of 41 HICs across seven primary scales, while its 2013 article discusses interpretation without establishing that the same count or report format applies to every later assessment. These pages describe particular publisher materials and dates. They do not establish that every report contains an identical inventory, uses the same display, or presents a subscale in the same metric. An average main-scale percentile and a noticeable subscale can therefore coexist without either canceling the other. Keep the primary score as the broad, norm-referenced summary. Let a subscale sharpen the question only after checking what the report labels: it might show a raw count, a normed category, or another field. The contrast can guide focused reflection, rather than serve as an independent verdict.

Sources: FAQ Blog Series: The Hogan Personality Inventory (HPI); Interpreting HPI Subscales

Is the subscale a raw count, a brick, or an invalid display?

Before interpreting a mark beside an HPI subscale, identify what kind of mark the report uses. Hogan’s *Subscale Interpretive Guide HPI* describes a newer bar display in which shaded “bricks” place a subscale score into one of four quartiles, based on cumulative frequencies in a comparison population. That is a categorized, norm-referenced display. It is not the primary scale’s percentile, and it is not a count of how many items the respondent endorsed. An older report may instead show a raw fraction such as “2/5,” meaning two endorsed items out of five in that particular subscale. The same-looking small number can therefore mean something different depending on the report format. The distinction matters because the raw count does not translate into a brick by simple proportion. The guide compares two legacy subscales: for Not Anxious, raw counts from zero to four map one-for-one to zero through four bricks. For No Guilt, which has six items, counts from one through three all fall in the lowest brick, while four maps to the second, five to the third, and six to the fourth. Hogan explains that skewed score distributions make some conversions nonlinear: a count that looks numerically small may be uncommon in the comparison population, while another subscale’s counts may be more evenly distributed. These examples illustrate the guide’s older format; they are not a universal conversion table for every report or scoring version. The guide explicitly says it cannot provide a general conversion chart. So do not turn a fraction into a percentile by dividing endorsed items by total items, or infer that a raw count of three means the same relative standing on every subscale. Such arithmetic describes the fraction of items endorsed, not where the score falls in Hogan’s reference distribution. A quartile or brick already represents a grouped comparison; it does not reveal a precise percentile within that group. The report’s own key and administrator’s documentation should govern the interpretation. A four-brick HPI presentation also has two special cases that should not be collapsed into “low.” In the guide, no shaded boxes means zero items were endorsed and is labeled the minimum possible score for that subscale. A dashed line means the subscale could not be scored, for example because too few items were answered. The guide says this invalid display does not itself indicate inconsistent or dishonest responding; it means there is no valid subscale score to interpret. Hogan’s *Subscale Brick Format Scoring Updates* FAQ likewise distinguishes zero bricks for no endorsed HPI items from a dashed line when too few responses prevent scoring. A minimum score is still a score; a dashed line is missing score information. Neither should be silently converted into an extreme trait judgment. Check the report itself before drawing a conclusion. Note its title and date, whether the subscale is shown as a raw fraction or bricks, the legend’s definitions, and whether the display is a score or an unscorable indicator. Hogan’s FAQ dates the brick format to reports generated from May 2, 2016, while the guide describes newer bar charts replacing earlier raw-score indicators. Those dates document format changes, not a guarantee that every report in circulation follows one layout. If the key is absent or the display is unclear, ask the report administrator which scoring format applies and whether the subscale produced a valid score. Only then decide whether a particular subscale stands out against the main-scale summary.

Sources: Subscale Interpretive Guide HPI; Subscale Brick Format Scoring Updates

Why do report date and norm matter before interpreting a difference?

Because scoring format and norms change what a displayed number is compared with. Hogan documents a transition from two response options to four for newer HPI data and a 2023 norm update. Before comparing values, identify the report date, response format, norm, and any local or custom scoring. A report’s date is a clue, not proof of its scoring basis: Hogan says the update applied to many off-the-shelf reports from June 1, 2023, while some custom scoring followed a separate process. The sequence matters. A response format determines which answers a person can give and, in turn, the raw responses available for scoring. Hogan’s “2023 Scoring/Norm Launch FAQ” says HPI and HDS data collection moved from True/False responses to four options—Strongly Agree, Agree, Disagree, and Strongly Disagree—beginning in September 2018. A norm is a reference distribution: Hogan describes using norm data to convert raw scores into percentile scores that compare a person with others in that norm. Thus, a percentile is not a free-standing property of a response. It depends on the scoring process and comparison group that produced it. This also explains why a report date cannot tell the whole story. The FAQ says new norm data were collected beginning in 2018, finalized in late 2022, and put in place for many off-the-shelf reports in June 2023. It also notes that some custom reports were affected differently, local norms were updated, and web-service users should confirm the norm identifier. Hogan’s “Global Norm Update” page describes an earlier update, effective in 2019, and says administrators could check the norm used in Hogan’s administrative portal. These documents show that “Hogan norm” is not a sufficient description: a report may use a global, local, or custom basis. Hogan says the newer response options and norm were intended to make scoring more precise and improve representation. Those are the publisher’s stated aims, not independent proof that a particular subscale difference is precise or meaningful for an individual. The public update pages do not identify the norm, response format, or custom scoring in any one reader’s report. If the report does not state its version and norm clearly, ask the administrator or qualified feedback provider: Which response format was used? Which norm and scoring version produced these percentiles and subscale displays? Was local or custom scoring applied? Hogan recommends using the same norm to compare people; some four-option assessments scored on True/False norms may be eligible for rescoring. Confirm that with the administrator rather than assuming a score shift reflects a change in the person. Compare the primary percentile and subscale output only in their documented metrics; do not treat differences across norms or retakes as evidence of behavioral change until the scoring basis is confirmed.

Sources: 2023 Scoring/Norm Launch FAQ; Global Norm Update

When does subscale detail genuinely add information?

Subscale detail earns a place when it makes the broad result more specific without replacing it. Hogan’s “Interpreting HPI Subscales” says narrower themes can distinguish people whose primary-scale results look similar, including people whose scale scores fall in an average range. This describes the intended interpretive value of added detail: broad summaries may conceal different response patterns. It does not mean every visible difference is reliable, consequential, or useful for every reader. A primary scale and its subscales answer questions at different levels. The primary percentile gives a broad comparison with the report’s norm group. A subscale can point toward one component theme that may help explain what the broad result leaves unspecified. The outputs need not match in apparent intensity. An average primary percentile can coexist with a subscale display that draws attention, without either canceling the other. The main score remains the anchor; the subscale is a possible refinement whose value must be established in context. A useful threshold has three parts. First, the display must be understood: the reader should know whether the mark is a raw count or a normed category, and what the report’s key says it represents. Second, the contrast must be interpretable alongside the broader scale rather than treated as a free-standing label. Third, it must help form a bounded question about observable behavior relevant to the reader. If any part is missing, the detail may be striking but not informative. This is a practical reading rule, not a Hogan cutoff or a separate precision test. The “Subscale Interpretive Guide HPI” supports using subscale material to add nuance while keeping interpretation centered on the primary scale. Read together, the Hogan sources justify a measured conclusion: detail can differentiate profiles, but the report’s presentation alone does not establish whether a particular distinction is stable or decision-relevant. These public materials describe the publisher’s intended use; they do not independently show that each subscale contrast improves a coaching, work, or selection decision. Selective interpretation creates another risk. If a reader scans several subscales and chooses only one that confirms an existing self-description, the report can seem more certain without adding dependable evidence. A less selective approach is to choose the clearest documented contrast, translate it into one neutral question, and look for examples and counterexamples in relevant situations. For instance, ask whether a response pattern appears repeatedly in a defined kind of interaction. The question should not assume the answer, and the subscale is not proof that behavior occurred or why. If no contrast survives the format, context, and relevance checks, keep the average primary-scale interpretation. There is no need to make a narrow story from ambiguous detail. When one contrast does survive, use it to guide focused reflection or coaching, then let observed patterns and alternative explanations shape the conclusion. The useful result is not a more dramatic label; it is a clearer question the broad percentile alone could not answer.

Sources: Interpreting HPI Subscales; Subscale Interpretive Guide HPI

What can reliability and validity evidence tell you about a subscale?

Reliability and validity answer different questions about a score. Reliability, or precision, concerns how consistently scores are produced and how much random measurement error may affect them. Validity concerns whether evidence and theory support a particular interpretation for a particular use. The National Council on Measurement in Education’s Assessment Glossary defines reliability/precision in terms of consistency across repeated applications and freedom from random error; it defines validity as support for a specific score interpretation for a given use. That distinction matters when a report prints a narrow HPI subscale alongside a broad primary scale. The presence of a subscale label does not show that its score is sufficiently precise for every interpretation, and evidence about an overall scale does not automatically transfer to each component. Broad scales and subscales may differ in content, scoring, and intended interpretation. A claim about the HPI overall therefore cannot establish how dependable one particular subscale result is for this report version. Hogan’s 2017 article, “A Quick and Dirty Guide to Validity and Reliability,” reports publisher figures for HPI scales: short-term test-retest reliability of .81 and average internal consistency of .76. These are the article’s stated scale-level figures. It does not establish that the same coefficients apply to every HPI subscale, scoring format, or reader’s report. A reliability coefficient also cannot answer whether a subscale interpretation is useful for a given purpose. The article is publisher material, so treat it as a description of Hogan’s claims, not independent confirmation. For validity, ask what evidence supports the interpretation being considered. A claim that a subscale helps describe a recurring tendency differs from a claim that it predicts a work outcome or should guide a consequential decision. Each inference needs evidence suited to that use. The NCME Assessment Glossary’s definition makes validity interpretation-specific: support for one conclusion does not automatically establish another. Similarly, evidence for a broad scale does not prove that every narrower result carries equal meaning. A headline coefficient, without its measure, population, method, and intended outcome, cannot settle the reader’s question. If you need more than low-stakes reflection, ask the qualified report administrator or feedback provider for technical evidence tied to the exact HPI version, named subscale, relevant population and norm, and proposed interpretation. Ask whether evidence concerns the broad scale or that subscale, how precision was evaluated, and what use the validity evidence supports. If available documentation answers only the scale-level question, keep that boundary visible. Until more specific evidence is available, a subscale can prompt a question to examine; its printed presence and a general reliability figure do not make it a stand-alone verdict.

Sources: Assessment Glossary; A Quick and Dirty Guide to Validity and Reliability

How can you test a subscale reading against behavior?

A subscale reading becomes useful when it helps you ask a better question about behavior, not when it supplies a label to defend. Translate the report’s wording into a neutral, observable prompt. If the theme concerns responding to pressure, ask: “When a deadline changes, what do I usually do next?” This is an illustrative question, not a claim about what an HPI result means for a particular person. Keep the prompt close to an action another person could notice, such as asking for clarification, changing a plan, or waiting for information. Avoid turning it into a judgment about character or motive. Choose a recurring setting that matters to the question: a weekly handoff, a decision with incomplete information, or a disagreement about priorities. Recall more than one instance if possible, and describe the sequence: what was happening, what you did or said, and what followed. The point is not to prove the report correct. It is to see whether the description helps organize specific examples or remains too broad to distinguish one response from another. Hogan’s “Interpreting HPI Subscales” presents subscales as added detail around a primary scale. That intended role can guide a question, but it does not make a label a record of observed behavior. Then deliberately look for a counterexample. If examples suggest that you prefer to settle a plan early, ask when you tolerated an open decision or changed course readily. A counterexample does not automatically disprove a tendency; it may show that the pattern depends on the task, people involved, or consequences. Consider alternatives before attributing an action to personality: a tight deadline, unclear authority, limited experience, workload, incentives, or timing may have shaped what happened. These are possibilities to check, not explanations established by a subscale. A practical note can separate three things: the report’s exact term, behavior you can describe, and the context in which it occurred. Add a counterexample and any unresolved alternative. This keeps interpretation revisable. A percentile or other score is a comparison within a defined distribution, as the National Council on Measurement in Education glossary explains; it is not direct observation of a person in every setting. The same caution applies to a subscale description: agreement with familiar wording is not independent confirmation. If examples point in different directions, preserve that uncertainty rather than forcing one story. Ask a trusted colleague or coach: “When the plan changed, what did you notice me do, and what else might have influenced it?” Keep the discussion focused on an action and its setting, not whether someone fits a type. This reflection can support self-understanding, while remaining short of proving a cause, predicting conduct, or deciding job fit.

Sources: Interpreting HPI Subscales; Assessment Glossary

What can an average result or subscale not decide for you?

Neither an average HPI percentile nor a subscale description diagnoses a condition, explains why a behavior occurred, or determines whether someone is suited to a job. These outputs describe scores under a particular assessment and comparison frame. Moving from a score to a claim about a person, then to a consequential decision, requires evidence at each step. In reflection or coaching, a subscale can suggest a question to examine; it cannot establish a cause or settle the answer.

The distinction matters when a report is used beyond reflection. The 2018 Principles for the Validation and Use of Personnel Selection Procedures, adopted as American Psychological Association policy, frame selection around the accuracy of inferences supporting personnel decisions. Evidence that a measure relates to a broad personality construct would not by itself show that one subscale should decide who is hired, promoted, paid, or judged as a performer. Evidence must fit the specific interpretation and decision context. The Principles are professional guidance, not an evaluation of this report or a finding about a particular HPI subscale.

A credible, though bounded, challenge to self-report tests in high-stakes selection appears in Reconsidering the Use of Personality Tests in Personnel Selection Contexts, published in 2007. It summarizes a panel discussion held at a 2004 professional conference. The five former journal editors argued that operational use raised substantial problems and that published self-report tests’ use in important selection decisions should be reconsidered. They also allowed that personality constructs may have value for selection and called for research into alternatives to self-report measures. This is a critique of the broader selection debate, not an HPI-subscale study or an assessment of your report. It does show why a printed subscale is not a ready-made employment verdict.

For a consequential decision, ask what evidence supports the exact inference in the relevant work setting,. An average percentile cannot rule someone in or out; a contrasting subscale cannot supply that justification. Keep the result for a bounded reflection question, and do not use it alone for hiring, promotion, compensation, performance management, or clinical judgment. Ask the report administrator or qualified assessor: “What evidence supports using this specific score for the decision we are considering?”

Sources: Principles for the Validation and Use of Personnel Selection Procedures; Reconsidering the Use of Personality Tests in Personnel Selection Contexts

What is the next useful step with your HPI report?

The useful next step is a bounded check, not a second verdict. Keep the primary-scale percentile beside the norm group named in the report. Record the subscale label, whether its display is a raw count or normed category, and the report date or scoring version. Hogan’s scoring and norm FAQ describes changes in response format and norms, so a number detached from its scoring basis is hard to compare. If that basis is absent, ask the administrator which version and norm apply. Choose one clear subscale distinction and translate it into a question about a recurring situation. What could another person observe? What example supports that reading, and what counterexample complicates it? Consider whether the situation’s demands, incentives, workload, or timing offer another explanation. This is reflection, not score confirmation: the NCME Glossary defines validity in relation to evidence for a particular interpretation and use. If no repeated pattern emerges, the average primary-scale result remains the useful summary. If the scoring question is settled but you still want to examine how you approach decisions or collaboration, the [Work Pattern Report](/assessment) offers a low-stakes self-report across work-pattern continuums. It does not interpret Hogan results, supply norms or selection scores, or recommend a career. For more on assessment outputs, continue to [Personality Report topics](/topics). The verdict is conditional: let a verified contrast sharpen one bounded reflection question; do not let it displace the average percentile. Ask a coach: “What situation should I observe to see whether this pattern is useful?”

Sources: Assessment Glossary

Questions readers ask