, 7 tweets, 2 min read
My Authors
Read all threads
With a huge assist from @tlowdon who let me use his data to fill in gaps I had missing for early June, I am putting together a multi-dimensional date of death chart which will show deaths by week occurred, publicly reported deaths by week and weeks when CDC updated the deaths.
Top row: Deaths reported publicly by week

West to East: Provisional death counts by CDC when death occurred, columns representing the week when CDC added them.

Color striping indicates a way to track trends based reporting week. First red = 1st week of data, Orange = 2nd, etc.
Most recent four week sum of deaths by reporting week:

July 11: 2,340
July 4: 2,868
June 27: 3,064
June 20: 5,226
June 13: 5,665
June 6: 6,809
May 30: 7,769
May 23: 10,960
May 16: 11,545
May 9: 9,387
May 2: 12,590
Did TES call it? These last couple weeks might be an indication.

This is what's happening:

1) States report new deaths. Regardless of when they happened. If they increase, media blows it up.

2) These deaths are reported to the CDC and lag a bit

3) When CDC updates numbers, we can see when those deaths were occurring the states had reported
By analyzing this data, we can see if states were changing prior deaths to "probable" or if they're backlogging. When we do this, we can combat the increasing deaths narrative. What we found this week is that the couple of spikes that were seen in 'public' numbers were not spikes
I hope this helps, I've included these notations to help explain how to read the chart:
Missing some Tweet in this thread? You can try to force a refresh.

Keep Current with Kyle Lamb

Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!