RDAS relationship adjustment report
{{ totalScore }}/69
{{ severityName }} range · {{ cutoffNarrativeShort }}
{{ badge.label }}

Brief 14-item relationship check-in for agreement, satisfaction, and cohesion over the last six months.

  • Answer each item using its original RDAS response scale.
  • The finished report keeps the overall cutoff view and the weaker relationship domain on one page.
  • Your responses stay in this browser unless you choose to export them.
{{ progressPercent }}%
{{ uxProgressLabel }}
  • {{ question.id }}. {{ question.text }}
/69
{{ card.label }}
{{ card.value }}
{{ card.note }}
Relationship Adjustment Dial

Shows the total RDAS score against the published 48-point distressed versus non-distressed cutoff.

What this result suggests

{{ interpretationLead }}

{{ cutoffNarrative }}

{{ trendNarrative }}

Top priorities
  1. {{ step }}
Practical adjustments
  • {{ step }}
What to bring into follow-up
  • {{ prompt }}

{{ whenToSeekSupport }}

Current score lane
Total Band Follow-up focus
{{ row.rangeLabel }} {{ row.label }} {{ row.shortAction }}
Domain read

{{ domainGuideLead }}

Consensus reflects agreement on decisions and values, satisfaction reflects conflict strain and stability, and cohesion reflects shared activity, discussion, and teamwork.

{{ domain.label }}
{{ domain.summary }}
{{ domain.total }}/{{ domain.max }}
{{ domain.percent }}% of domain maximum · {{ domain.levelLabel }}

{{ domain.note }}

Relationship Domain Radar

Plots consensus, satisfaction, and cohesion on their published domain maximums so the widest gap is obvious at a glance.

Higher and lower scored items

Higher rows show the parts of the relationship that are currently doing more stabilizing work. Lower rows show the items that are making the total feel thinner.

# Higher-scored anchor Lower-scored burden point
{{ row.id }} {{ row.highLabel }} ({{ row.highScore }})
{{ row.highDomain }}
{{ row.lowLabel }} ({{ row.lowScore }})
{{ row.lowDomain }}
# Item Response Score Item max Domain
{{ row.id }} {{ row.text }} {{ row.answer }} {{ row.score }} {{ row.max }} {{ row.domainLabel }}

Scoring note: Item 11 keeps its published 0 to 4 scale, which is why the RDAS total tops out at 69 rather than 70.


                
:

Relationship adjustment describes how two partners are managing agreement, closeness, and strain across ordinary life together. Those patterns matter because couples can feel stable in one area and unsettled in another long before they have clear language for what is changing.

This assessment turns that broad picture into a short structured snapshot. You answer fourteen prompts, and the page summarizes the result with a Total score plus separate Consensus, Satisfaction, and Cohesion subscores.

That kind of split view is useful when the problem is not simply “good” or “bad.” A couple may agree on major decisions yet quarrel more often, or still enjoy time together while feeling less secure about the relationship overall. The subscales help separate those situations instead of flattening them into one vague impression.

The output is most useful as a conversation aid and a repeatable self-check. It can help someone notice patterns, prepare for a counselling discussion, or compare two points in time, but it does not explain causes and it does not replace a full clinical assessment.

There is also a privacy detail worth knowing up front. Scoring happens in the browser and the page does not post answers to a server, but the response state can live in the page link when it is restored or shared, so the address bar itself can expose the answer pattern.

Everyday Use & Decision Guide:

The most reliable first pass is to answer the fourteen items in one sitting and keep the time frame consistent with the page instruction for the past six months. Use the first response that feels broadly true rather than trying to average every good week and bad week into one perfect answer.

This screen is a good fit when you want a structured check-in, a starting point for discussion, or a simple way to compare two snapshots taken under similar circumstances. It is a poor fit for crisis decisions, for judging whether a relationship is safe, or for settling an argument by treating the score as objective proof.

  • Read Total as the broad signal, then move immediately to Consensus, Satisfaction, and Cohesion for the real pressure points.
  • If the result lands near the cutoff, slow down and read the low-scoring items in Your Answers before acting on the band label.
  • If you plan to compare two runs, keep the same six-month frame and avoid taking the assessment right after an unusually intense conflict unless that event is exactly what you want to capture.
  • If a partner will see your result, use the export or link only when you are comfortable with the privacy tradeoff.

The most common misread is assuming that a Non-Distressed band means nothing is wrong. A relationship can clear the cutoff and still show a weaker domain or a cluster of low item scores that deserves attention. The page becomes far more useful when you treat the band as a starting label and the subscores as the real map.

Technical Details:

The Revised Dyadic Adjustment Scale, or RDAS, is a 14-item relationship screen organized around three domains: agreement, satisfaction, and shared connection. The page keeps that three-part structure and computes a total from all answered items, then adds domain-specific guidance by comparing each subscore with its maximum.

Four items are reverse-scored: discussion of divorce or separation, frequency of quarrelling, regret about being together, and getting on each other’s nerves. In other words, a larger raw response on those prompts becomes a smaller positive score before the total is summed. That reversal is what allows the page to keep one direction throughout the result: higher adjusted values indicate better adjustment.

The package then adds two interpretation layers of its own. First, it labels the overall band as Distressed when Total <= 48 and Non-Distressed when Total > 48. Second, it labels each domain as low, moderate, or high by comparing the subscore with one-third and two-thirds of that domain maximum. The “focus” guidance is based on the lowest normalized domain rather than the raw total alone.

Published RDAS scoring is usually described on a 0 to 69 scale. This screen keeps that cutoff language and draws the gauge to 69, but it also applies one shared 0 to 5 response scale to all fourteen items. Because of that package choice, the raw badge can mathematically reach 70 even though the gauge tops out at 69. If you ever see that edge case, trust the item pattern and subscores first rather than the gauge alone.

Formula Core

The page converts each raw response into a positive score, sums those adjusted item scores, and then breaks the result into three domain totals.

s_i = { x_i for non-reversed items 5x_i for items 7 to 10 }
Total = i=1 14 s_i , Consensus = (s_1 to s_6) , Satisfaction = (s_7 to s_10) , Cohesion = (s_11 to s_14)
RDAS domains and ranges
Output Items Nominal range What it reflects
Consensus 1 to 6 0 to 30 Agreement on values, affection, and major decisions
Satisfaction 7 to 10 0 to 20 Conflict climate and regret-related tension after reversal
Cohesion 11 to 14 0 to 20 Shared activity, laughter, discussion, and teamwork
Total All 14 adjusted items Cutoff framed at 0 to 69 Overall relationship adjustment signal used for the band label
RDAS interpretation thresholds
Field Boundary Meaning in this page
Total <= 48 Distressed
Total > 48 Non-Distressed
Each domain label <= 33%, <= 66%, > 66% of the domain maximum low, moderate, or high

The page does not store answers on a server, but it does preserve state through a compact response string. The link parameter must contain exactly 14 characters made of digits 0 to 5 or hyphens for blanks; invalid strings are ignored, and the full result view stays locked until all fourteen items are answered.

A final comparability note matters for repeat use. The score is a self-report snapshot, so trends only mean something when the same person answers under a similar time window and similar level of reflection. A one-point shift in a single item can be enough to move the total near the cutoff, which is why the item table and domain profile deserve as much attention as the headline band.

Responsible Use Note:

This screen is informational and not a diagnosis. It is not a safety assessment, and it should not be used to decide whether fear, coercion, abuse, or severe instability is present.

If relationship distress overlaps with safety concerns, depression, escalating conflict, or disruption to work or daily life, step away from the score and seek qualified support instead.

Step-by-Step Guide:

The page works best when you move from completion to interpretation in a deliberate order.

  1. Select Start Assessment, then read the first prompt with the page instruction in mind: answer for the past six months rather than for a single difficult day.
  2. Choose one radio answer for each item and use the question list to jump around if needed. The progress bar and the x/14 answered label should move with every response.
  3. Finish all fourteen items before trying to interpret anything. Until every answer is present, the page will not show the final Total badge, gauge, or guidance cards.
  4. Read the summary box first: it displays the Total band and the main result label. Then check the overview cards for completion, primary score, and band confirmation.
  5. Move next to the domain outputs. Compare Consensus, Satisfaction, and Cohesion, then read the guidance block and the low-scoring items in Your Answers to see where the band is being driven.
  6. If a shared link fails to restore the page correctly, check that the response string contains exactly 14 characters using only digits 0 to 5 or hyphens. After a complete run, copy or download the answer table only if you actually need a record for later discussion.

Interpreting Results:

The first boundary that matters is explicit: Total <= 48 is labeled Distressed, while Total > 48 is labeled Non-Distressed. That band is useful as a summary cue, but it should never be read by itself.

  • A Non-Distressed result does not mean the relationship is without strain. Verify the weakest of Consensus, Satisfaction, or Cohesion and read the related items before assuming everything is fine.
  • A Distressed result does not diagnose a cause. It tells you that this page’s scoring rule places the current answers on the concern side of the cutoff.
  • Scores near 48 deserve a slower read than scores far from it. When the total sits on or just above the boundary, use the domain profile and item table as the tie-breakers for what needs attention first.

A practical next step is to pair the band with one focused conversation or one professional follow-up question. If the result points to weaker Satisfaction, talk about conflict patterns; if it points to weaker Cohesion, look at shared time and teamwork; if it points to weaker Consensus, start with areas where agreement repeatedly breaks down.

Worked Examples:

A generally stable relationship with one softer domain

The response string 54434322214433 yields Total = 50, Consensus = 23, Satisfaction = 13, and Cohesion = 14. The page labels that profile Non-Distressed, but the lowest normalized domain is Satisfaction, so the narrative guidance leans toward conflict-repair habits rather than assuming the relationship needs no work.

A boundary result that lands on the cutoff

The response string 54334312214233 produces Total = 48, Consensus = 22, Satisfaction = 14, and Cohesion = 12. Because the rule is inclusive, that exact total is labeled Distressed. This is a good example of why the domain profile matters: the page points toward Cohesion as the first area to discuss, not just the headline band.

A link that does not restore because the state is malformed

If someone shares a link with a broken state such as r=5433431221423, the page ignores it because the response string is only 13 characters long. The assessment opens without a restored Total, the gauge does not appear, and the practical fix is to use a 14-character string or answer the missing items directly in the questionnaire.

FAQ:

Is this a diagnosis?

No. The page is a structured relationship screen, not a clinical diagnosis. It summarizes your answers into a band and three domains, but it cannot explain causes or replace professional assessment.

What does the cutoff of 48 actually mean here?

It is the page’s band rule: Total <= 48 becomes Distressed, and anything above 48 becomes Non-Distressed. Scores close to that boundary should be read together with the domain scores and item pattern.

Are my answers stored anywhere?

The scoring happens in the browser and the page does not submit answers to a server. The privacy caveat is the link itself: the response state can appear in the URL, so sharing or saving that link can expose the answer pattern.

Why can the page talk about 0 to 69 if the raw badge could reach 70?

The gauge and explanatory text follow the usual RDAS framing of 0 to 69. This package also uses a uniform 0 to 5 answer scale across all items, so a mathematically perfect response pattern can push the raw Total badge to 70 even though the gauge stops at 69.

Why do I see no result yet?

Results only appear after all fourteen items are answered. If you are using a shared link, the state string must contain exactly 14 digits or hyphens; otherwise the page starts without restored answers.

Can two partners compare their scores?

They can, but the comparison is still between two self-reports. Use the same six-month frame, compare the three domain scores rather than only the band, and treat differences as discussion prompts rather than verdicts.

Glossary:

RDAS
A 14-item relationship adjustment screen.
Consensus
The agreement-related domain built from items 1 to 6.
Satisfaction
The conflict and regret domain built from items 7 to 10.
Cohesion
The shared-activity domain built from items 11 to 14.
Reverse-scored item
A response where a higher raw answer becomes a lower adjusted score.

References: