Research history

Current published edition

Scale, neglectedness and tractability

As recorded by . This is a dated public record of drafts, changes, sources and review declarations. A page, checksum or merged pull request does not establish a scientific result or independent review.

Edition
edition:2026-11-07-encyclopedia
Edition checksum
e146b1666792c4b20504af099ca65663d0f70fea584397f38cb5eda241137bde
Projection checksum
a017dac8fb17a969a8d72ae660365d8c9a3840125e29cb258e797f50a27552ed
Period
inclusive to exclusive.
Starting baseline
Unknown before the recorded capture. Present states are not backdated to January.

JSON retains the complete pinned edition. CSV covers every recorded event in this edition; view filters do not change either download.

Recorded activity and qualification

  • 69Stable records
  • 71Subject versions
  • 69Recorded events
  • 0Review declarations
  • 0Subjects with qualifying source review
  • 0Peer-reviewed manuscripts
  • 0Qualifying research results
  • 1Editorial correction artifacts
  • 2Changed claim subjects
  • 23Open problems
  • 0Partially resolved problems
  • 0Solved problems
  • 0Problems under review
  • 0Unresolved challenges

Qualification follows the exact recorded public declarations. The ledger cannot establish identity, independence, source reading or truth by itself. Editorial corrections, proposed methods and software checks are separate from qualifying research results.

Coverage and limits

66 source entries are covered by this edition. Claim-level records cover only their selected wording and context; they do not qualify a whole manuscript. Source-derived case labels describe the published summaries, not Charitology fieldwork or charity ratings.

Entry links open the present site. The separate pinned source text retains this edition’s exact archived bytes.

Scale, neglectedness and tractability · Encyclopedia entry · version 1
Source review: draft

concept:scale-neglectedness-tractability

Qualification follows the exact recorded public declarations. The ledger cannot establish identity, independence, source reading or truth by itself.

Versions and exact subjects

Version entries 1–1

Version 1: Scale, neglectedness and tractability

Current subject in this edition

Subject checksum
1207f518054314422f9a4b8af8d8d426bca8b69efe97bb262d0c1f25a53dc928
Version checksum
d424a4007b06e0ea5dde0627ca8562cab42843e648bd9d4d2c6afac44cc1e87e
Authorship declaration
unknown; completeness unknown.
aliases
[
  "SNT framework",
  "ITN framework",
  "importance, neglectedness and tractability",
  "scale, neglectedness and solvability"
]
conditions
[
  {
    "collection": "conditions",
    "id": "single-lens"
  },
  {
    "collection": "conditions",
    "id": "symptom-trap"
  }
]
related
[
  "/record/encyclopedia/neglectedness/",
  "/record/encyclopedia/effective-altruism/",
  "/open-problems/the-exchange-rate-problem/",
  "/tools/values-compass/",
  "/record/lexicon/#tractability"
]
summary
A framework for comparing problems by how big they are, how few resources already go to them and how much extra effort would achieve. It grew out of GiveWell Labs and 80,000 Hours and is widely used in effective altruism.
Exact archived Markdown body

Inert source text, including its original formatting. It is not executed as page markup.

The **scale, neglectedness and tractability** framework asks three questions about a problem before asking which charity to fund. In the version 80,000 Hours publishes:

- **Scale:** If we solved the problem, how good would it be?
- **Neglectedness:** How many people, or dollars, are currently working on it? See [neglectedness](/record/encyclopedia/neglectedness/).
- **Solvability**, often called **tractability:** If we doubled the effort going into it, what fraction of what remains would we expect to solve?

Multiplied together, the three give an estimate of how much good an extra unit of money or work would do. Because the scores are logarithmic, 80,000 Hours adds them instead of multiplying.

## Where it came from

GiveWell Labs, the project that became the Open Philanthropy Project (later Open Philanthropy, and since 2025 Coefficient Giving), compared causes by importance, tractability and how crowded they were. A 2014 post used those three criteria to narrow down U.S. policy areas. In December 2013 Benjamin Todd of 80,000 Hours proposed a cause-selection framework of importance, tractability and uncrowdedness, crediting GiveWell Labs for the names. Robert Wiblin’s 2016 article for 80,000 Hours turned it into the formal version still in use.

## Cautions from its own authors

80,000 Hours lists the limits plainly. The scores are imprecise, and adding them adds uncertainty. Narrowly defined problems tend to score better than broad ones. Trade-offs between the yardsticks rest on contested value judgments. Solvability is the hardest factor to score, and the true differences between problems are probably smaller than the scores suggest. Wiblin also warns that the factors overlap: a problem can stay important because it is neglected, so the same fact can be counted twice.

## How Charitology uses it

Charitology treats the framework as a good tool that needs one more input: a moral framework. *Scale* needs a unit, such as lives, wellbeing, rights secured or species protected, and choosing the unit is a moral choice. A problem can rank first under one lens and last under another. So Charitology asks the questions once per framework. Its frameworks data, used by the [Values Compass](/tools/values-compass/), sketches how each framework tends to rank causes, so a giver can see where the rankings agree. Where they cannot be put on one scale at all is [Open Problem 2, the Exchange Rate Problem](/open-problems/the-exchange-rate-problem/).

The framework scores problems, not the depth of the work. A problem can be crowded at the relief level and neglected at the source level. Charitology’s working hypothesis is that this pattern is common, which is the [Symptom Trap](/diagnosis/symptom-trap/). This project has not established that pattern.
Cited evidence
Pinned source capture
Exact version fields and declaration references
{
  "adapterVersion": "research-encyclopedia-v1",
  "authorship": {
    "actorIds": [],
    "complete": false,
    "refs": [],
    "state": "unknown"
  },
  "hash": "d424a4007b06e0ea5dde0627ca8562cab42843e648bd9d4d2c6afac44cc1e87e",
  "id": "version:concept-scale-neglectedness-tractability-v1",
  "previousId": null,
  "recordId": "concept:scale-neglectedness-tractability",
  "sources": [
    {
      "selector": {
        "kind": "entry"
      },
      "sourceId": "source:encyclopedia-scale-neglectedness-tractability-v1"
    }
  ],
  "subject": {
    "body": "\nThe **scale, neglectedness and tractability** framework asks three questions about a problem before asking which charity to fund. In the version 80,000 Hours publishes:\n\n- **Scale:** If we solved the problem, how good would it be?\n- **Neglectedness:** How many people, or dollars, are currently working on it? See [neglectedness](/record/encyclopedia/neglectedness/).\n- **Solvability**, often called **tractability:** If we doubled the effort going into it, what fraction of what remains would we expect to solve?\n\nMultiplied together, the three give an estimate of how much good an extra unit of money or work would do. Because the scores are logarithmic, 80,000 Hours adds them instead of multiplying.\n\n## Where it came from\n\nGiveWell Labs, the project that became the Open Philanthropy Project (later Open Philanthropy, and since 2025 Coefficient Giving), compared causes by importance, tractability and how crowded they were. A 2014 post used those three criteria to narrow down U.S. policy areas. In December 2013 Benjamin Todd of 80,000 Hours proposed a cause-selection framework of importance, tractability and uncrowdedness, crediting GiveWell Labs for the names. Robert Wiblin’s 2016 article for 80,000 Hours turned it into the formal version still in use.\n\n## Cautions from its own authors\n\n80,000 Hours lists the limits plainly. The scores are imprecise, and adding them adds uncertainty. Narrowly defined problems tend to score better than broad ones. Trade-offs between the yardsticks rest on contested value judgments. Solvability is the hardest factor to score, and the true differences between problems are probably smaller than the scores suggest. Wiblin also warns that the factors overlap: a problem can stay important because it is neglected, so the same fact can be counted twice.\n\n## How Charitology uses it\n\nCharitology treats the framework as a good tool that needs one more input: a moral framework. *Scale* needs a unit, such as lives, wellbeing, rights secured or species protected, and choosing the unit is a moral choice. A problem can rank first under one lens and last under another. So Charitology asks the questions once per framework. Its frameworks data, used by the [Values Compass](/tools/values-compass/), sketches how each framework tends to rank causes, so a giver can see where the rankings agree. Where they cannot be put on one scale at all is [Open Problem 2, the Exchange Rate Problem](/open-problems/the-exchange-rate-problem/).\n\nThe framework scores problems, not the depth of the work. A problem can be crowded at the relief level and neglected at the source level. Charitology’s working hypothesis is that this pattern is common, which is the [Symptom Trap](/diagnosis/symptom-trap/). This project has not established that pattern.\n",
    "collection": "encyclopedia",
    "frontmatter": {
      "aliases": [
        "SNT framework",
        "ITN framework",
        "importance, neglectedness and tractability",
        "scale, neglectedness and solvability"
      ],
      "conditions": [
        {
          "collection": "conditions",
          "id": "single-lens"
        },
        {
          "collection": "conditions",
          "id": "symptom-trap"
        }
      ],
      "related": [
        "/record/encyclopedia/neglectedness/",
        "/record/encyclopedia/effective-altruism/",
        "/open-problems/the-exchange-rate-problem/",
        "/tools/values-compass/",
        "/record/lexicon/#tractability"
      ],
      "sources": [
        {
          "note": "First published in 2016 and last updated in December 2025.",
          "publisher": "Robert Wiblin, 80,000 Hours",
          "title": "A framework for comparing global problems in terms of expected impact",
          "url": "https://80000hours.org/articles/problem-framework/",
          "year": 2016
        },
        {
          "note": null,
          "publisher": "Benjamin Todd, 80,000 Hours",
          "title": "A framework for strategically selecting a cause",
          "url": "https://80000hours.org/2013/12/a-framework-for-strategically-selecting-a-cause/",
          "year": 2013
        },
        {
          "note": null,
          "publisher": "Holden Karnofsky, The GiveWell Blog",
          "title": "Narrowing down U.S. policy areas",
          "url": "https://blog.givewell.org/2014/05/22/narrowing-down-u-s-policy-areas/",
          "year": 2014
        },
        {
          "note": null,
          "publisher": "Robert Wiblin, Effective Altruism Forum",
          "title": "The Important/Neglected/Tractable framework needs to be applied with care",
          "url": "https://forum.effectivealtruism.org/posts/74oJS32C6CZRC4Zp5/the-important-neglected-tractable-framework-needs-to-be",
          "year": 2016
        },
        {
          "note": null,
          "publisher": "Effective Altruism Forum",
          "title": "Open Philanthropy Is Now Coefficient Giving",
          "url": "https://forum.effectivealtruism.org/posts/vkvtu6xbvfkHPhJkC/open-philanthropy-is-now-coefficient-giving",
          "year": 2025
        }
      ],
      "summary": "A framework for comparing problems by how big they are, how few resources already go to them and how much extra effort would achieve. It grew out of GiveWell Labs and 80,000 Hours and is widely used in effective altruism.",
      "title": "Scale, neglectedness and tractability"
    },
    "type": "entry"
  },
  "subjectHash": "1207f518054314422f9a4b8af8d8d426bca8b69efe97bb262d0c1f25a53dc928",
  "version": 1
}

Timeline in recorded order

Public occurrence time and ledger recording time are different. A coverage baseline records what was present at capture; it does not invent an earlier history.

Events 1–1

Coverage baseline

Recorded order
64; sequence 1 for this record.
Public occurrence
Undated / no earlier occurrence asserted · undated
Recorded in ledger

Additional exact-source encyclopedia coverage. Earlier authorship, source reading, independent review and historical event dates remain unknown.

Observed baseline: version 1.

Exact event fields
{
  "actorIds": [],
  "hash": "7cd9c6d14108f951009a6651c31e9bc1ba67b819bd1dc9674a087950da9c0792",
  "id": "event:concept-scale-neglectedness-tractability-1",
  "initialProblemState": null,
  "observationIds": [],
  "occurredAt": null,
  "ordinal": 64,
  "previousHash": null,
  "previousId": null,
  "reason": "Additional exact-source encyclopedia coverage. Earlier authorship, source reading, independent review and historical event dates remain unknown.",
  "recordId": "concept:scale-neglectedness-tractability",
  "recordedAt": "2026-11-07T23:20:18.679Z",
  "refs": [],
  "sequence": 1,
  "timeBasis": "undated",
  "type": "baseline",
  "version": {
    "recordId": "concept:scale-neglectedness-tractability",
    "subjectHash": "1207f518054314422f9a4b8af8d8d426bca8b69efe97bb262d0c1f25a53dc928",
    "version": 1
  }
}

Review declarations

No public review declaration is recorded for this subject in this edition.

Dated public metadata observations

These observations record only the displayed metadata at inspection. A merge, closed issue or empty review list does not establish research or independent review.

github-pull-request · 2026-10-27T08:20:16.587Z

Observed public object

{
  "base": "975bbbbbd198d4b3c4e1777013d0410588a838b3",
  "draft": false,
  "head": "3653d41717a86db2933b02664d7026a329350a66",
  "mergeCommit": "8df2d0ddbc6d91b9841c6bbb94dbde1fc7c00137",
  "mergedAt": "2026-10-27T08:10:57.000Z",
  "number": 15,
  "state": "closed"
}

be39e645f9291ea3931584665b011df77bfa8340e4d32f36562eb526f8e62396

github-pull-request · 2026-10-27T08:20:16.587Z

Observed public object

{
  "base": "905bdd27bb5f16027c3b3ad3c0f5ee3fc18e3e45",
  "draft": false,
  "head": "510320528e89f45caa9c42eb5a6eda3d6ad1bede",
  "mergeCommit": "3a57d24acc6efd4eb3ae60c59da36ea17c023fb9",
  "mergedAt": "2026-10-26T05:24:43.000Z",
  "number": 3,
  "state": "closed"
}

1ec26b57bd6ef466311b11958d47e9d144ec150ea5689838ae8036eb363aacbf

github-review-list · 2026-10-27T08:20:16.587Z

Observed public object

{
  "prNumber": 3,
  "reviewIds": []
}

3b7b719dbdd25b9937ba6c640f7234921611db30818b5675db41b9fa3534d926

github-issue · 2026-10-27T08:20:16.587Z

Observed public object

{
  "commentCount": 0,
  "number": 1,
  "state": "open"
}

b411d756f95b7434bc8a2a73dd5599f751afe621b2ab673c0e2e7b056d37bb14

Corrections stay public

This ledger reads checked-in public evidence. It does not read private browser registers, publish a local result, assign reviewers or rate charities. New evidence and corrections enter through the repository’s public contribution process.

How to contribute or challenge a claim