{{ item.short }}
{{ item.guidance }}
These items are carrying the least loneliness weight right now. They are the anchors worth protecting and repeating.
{{ item.guidance }}
These items are carrying the most loneliness weight right now. They usually offer the clearest starting point for the next small adjustment.
{{ item.guidance }}
{{ interpretationLead }}
| # | Item | Response | Scored point | Lens | Read | Reverse-coded |
|---|---|---|---|---|---|---|
| {{ row.id }} | {{ row.text }} | {{ row.answer }} | {{ row.scoreLabel }} | {{ row.lensLabel }} | {{ row.readLabel }} | {{ row.reverseLabel }} |
Loneliness is the felt gap between the connection you want and the connection you experience. A person can be surrounded by classmates, co-workers, or family and still feel cut off, which is why structured loneliness measures focus on subjective experience rather than a simple count of social contacts.
This package turns that experience into a 20-item snapshot using the UCLA Loneliness Scale-20 format implemented in the tool. Once every item is answered, it shows a Total score from 20 to 80, a four-band summary, a gauge, and supporting views that make the result easier to read than a raw list of answers.
That is useful when you want more than a vague sense that something feels off. A student settling into a new city, a remote worker whose routine has grown socially thin, or a caregiver whose days have narrowed can all use the score as a structured check of the past month instead of relying on memory alone.
The package also goes beyond the headline badge. It separates responses into an Isolation subscore and a reverse-coded Connection (rev) subscore, highlights higher-scored and lower-scored items, and summarizes the current pattern so you can see which questions are pushing the result.
What this does not do is diagnose depression, anxiety, or any other condition. It is a reflection tool. If the score stays high, keeps rising, or matches clear distress in daily life, the next useful step is a conversation with a qualified clinician or counselor, not a single number taken in isolation.
For a clean first pass, answer the 20 statements in one sitting and keep the same "past month" window in mind all the way through. If half your answers reflect this week and the rest reflect a much longer stretch, the Total score still computes correctly, but it stops being a reliable snapshot of one period.
The best comparison is usually with yourself, not with other people. If you repeat the assessment later, keep the same time window and then compare Total, Isolation, Connection (rev), and the top driver items instead of asking only whether the badge color changed.
The scoring model is straightforward. Each of the 20 statements is answered on a four-point scale from Never to Rarely, Sometimes, and Often, mapped in code to 1 through 4. Ten items are scored directly because they describe loneliness or social disconnection, while ten positively worded items are reverse-coded so higher scored values always point in the same direction.
The package sums the 20 scored responses into one Total score. Because every item contributes at least 1 point and at most 4 points, the range is 20 to 80. The result band is determined by explicit boundaries in the script: Low for 20-34, Moderate for 35-49, High for 50-64, and Very High for 65-80.
It also builds two internal 10-item subtotals. Isolation adds the directly scored items. Connection (rev) adds the reverse-coded items after flipping them, so a higher value there means more loneliness-related strain showing up in the positively worded questions, not stronger connection. The package then derives an average scored item, counts the number of items at the top and bottom of the scale, and adds a short pattern note based on how far the two subtotals diverge.
The mechanism is simple enough to state formally. The set of reverse-coded items is fixed in the package and uses item IDs 1, 4, 5, 6, 9, 10, 13, 14, 17, and 20.
| Symbol | Meaning | Range or type | Source |
|---|---|---|---|
r_i |
Raw response for item i | integer 1-4 | Input |
R |
Reverse-coded item set | 10 item IDs | Package rule |
x_i |
Scored value after direct or reverse coding | integer 1-4 | Derived |
T |
Total score shown in the summary badge and gauge | 20-80 | Derived |
I |
Isolation subtotal for directly scored items | 10-40 | Derived |
C |
Connection (rev) subtotal after reverse coding | 10-40 | Derived |
| Output | What it represents | How to read it |
|---|---|---|
| Total | Sum of all 20 scored items | The main summary number. Higher means more loneliness-related responding. |
| Low, Moderate, High, Very High | Package-defined result bands | Useful as shorthand, but the exact Total matters most near boundaries. |
| Isolation | Subtotal from directly scored loneliness items | Higher values mean more loneliness signal in the negatively worded items. |
| Connection (rev) | Subtotal from reverse-coded positively worded items | Higher values still mean more loneliness signal. It is not a positive support score. |
| Drivers & strengths | Highest-scored and lowest-scored items | Use this to see which statements are shaping the score, not just how high it is. |
This tool does not call a package-specific backend and does not submit answers to a server in the bundle. The scoring happens in the browser. However, the answer string is synchronized into the query parameter r, using digits for answered items and hyphens for blanks, so shared links and browser history should be treated as sensitive. For repeat checks, keep the same timeframe and interpret changes in the exact Total and item pattern rather than assuming a different band always means a large real-world shift.
The flow is short, but each stage has a clear output cue.
Start with Total and the band, then move immediately to the supporting detail. A score of 58 and a score of 50 are both labeled High, but the higher value tells a different story about frequency and concentration of loneliness-related responses. The Isolation and Connection (rev) subtotals help you see whether the total is being driven more by explicit disconnection items or by reverse-coded connection items.
A high result does not prove a disorder or crisis. Verify it against the item pattern, your recent circumstances, and daily functioning. If the same themes keep appearing on repeat checks, use the item export and seek qualified support.
Suppose the positively worded items such as feeling in tune with people are mostly answered Sometimes, while the more direct loneliness items such as lacking companionship are mostly answered Rarely. After direct and reverse coding, each item contributes 2 points, producing Total 40.
The output would show a Moderate band, Isolation 20/40, and Connection (rev) 20/40. That is a useful example of a score that is clearly elevated above the minimum without one item family dominating the pattern.
Imagine a completed run sitting at Total 49. The band still reads Moderate. If one directly scored item such as feeling left out changes from Rarely to Sometimes, the total rises by 1 point to 50.
The badge then changes to High, and the gauge moves into the next band. Nothing magical happened at that exact point. It simply shows why edge scores should be read with item context rather than label alone.
A common failure path is stopping at 19/20 answered. In that state, the progress bar moves, but Your ULS-20 Result, the gauge, and the export actions do not appear because the package only renders results after the final answer is set.
Use the question list to locate the unanswered item, select one option, and the summary appears immediately. If the content is sensitive, clear or avoid sharing the resulting URL afterward because the current response string is stored in r.
No. The package summarizes self-reported loneliness-related responses over the past month. It does not diagnose depression, anxiety, or any other condition.
It is a subtotal built from the positively worded items after reverse coding. Higher values still point toward more loneliness-related responding, not better social connection.
The tool bundle does not show package-specific network submission for scoring. The main privacy caveat is local URL storage: your current response string is written into the page query parameter so reloads and shared links can preserve state.
Every item must be answered. If the progress display is below 20/20 answered, the summary, gauge, and exports stay hidden until the last item is filled in.
Yes, but keep the same timeframe and answer style. Compare the exact Total, the two subtotals, and the higher-scored items, not just the band label.