Your score is not your file, and you cannot dispute a number

People say “my credit” and mean a number. The number is downstream of the thing that actually matters, and the dispute machinery does not touch it.

The statute treats them differently

Your file is what a consumer reporting agency holds about you. 15 U.S.C. § 1681g(a)(1) entitles you, on request, to disclosure of “[a]ll information in the consumer’s file at the time of the request,” subject to stated exceptions.

A score is a separate thing. Section 1681g(f) governs disclosure of credit scores, and the provision says in terms that

nothing in this paragraph shall be construed to require a consumer reporting agency to disclose to a consumer any information concerning credit scores or any other risk scores or predictors relating to the consumer.

Scores are addressed by a different subsection, on different terms, with an express statement that the general obligation does not reach them.

Practically: a score is a model’s output, calculated on demand from your file by a scoring company, for a particular purpose, at a particular moment. There is no single number sitting in a drawer.

Which is why there are several of them

If you have ever seen different scores from different sources and assumed one was wrong, neither was. Different models, different versions, different agencies’ files, different dates. A lender’s score for auto lending and a free app’s score are not attempting the same measurement.

Nothing here says scores are meaningless. It says the number is a derived quantity, and derived quantities are not the thing you dispute.

What a dispute actually operates on

The reinvestigation machinery under § 1681i is about information in your file — the tradeline, the balance, the status, the dates, the public record. Not the score.

A score changes when the underlying file changes and the model is next run. It is a consequence, not a target. This is why “dispute to raise my score” is the wrong frame and produces frustration:

• A dispute that succeeds may not move a score much. Removing a small collection from a file with several other serious delinquencies changes little.
• A dispute that fails may still have been right to file. Accuracy is worth pursuing independently of whether the number moves.
• A score can drop for reasons unrelated to any error — utilisation, a new account, an account closing and shortening your history.

The honest way to think about it: you are correcting a record about you. The score follows the record.

Where scores are genuinely useful

The key factors. When a score is disclosed, § 1681g(f)(1) provides for accompanying information including the range of possible scores, the key factors adversely affecting the score, the date it was created, and its source. Under § 1681m(a), a user taking adverse action based on a report must disclose the score used, if any, along with that information.

Those key factors are a pointer. They tell you what the model reacted to, which tells you where to look in the file. If a factor references derogatory public records and you know of none, you have learned something concrete.

As a change detector. A sudden unexplained drop is a reason to pull the file and find out why. That is the score doing its only genuinely useful diagnostic job — telling you to go read the actual document.

The practical version

1. Stop optimising the number. Get the file. Full disclosure under § 1681g(a), from each agency.
2. Read every line for accuracy — accounts, balances, statuses, dates, inquiries, public records.
3. Dispute what is wrong, because it is wrong.
4. Use score factors as a map, never as the target.
5. Expect the number to lag, and do not measure the dispute’s success by it.

We are not telling you what your score means, what it should be, or what any change would do for you. We are telling you which document the law lets you correct.