Make the support explanation shorter.

[kathigg]

• Support should be shorter.
• Add an explanation on the bill---"based on the status on the bill, it's unlikely that a representative has taken a stance yet."
• Most recent bills in chamber. Direct people to things that are actually being votes on---the most crucial time period is when they're actually voting on something.
• Take Action Organizations aren't changing per bill.

[kathigg]

Bug finder link to GitHub. Find a bug? Add it to the GitHub?

[kathigg]

• Having a page to see what your Representative or Senator HAS said.
• Information on what it means when the bill is in committee.
• Not a lot of information on what it actually means. What is the process?

[kathigg]

"How long do the steps take? Bills spend 60 weeks here and 90% of them die."

AI generated summaries are good.
The language of the website is fairly good.

Percentage chance the bill gets to the next step.
"Textual predictions of bill survival in congressional committee."
Build a model in the backend that predicts based on markers in previous bills and surface that in the website.
Alter the messaging based on the predictions.
If there is a low chance of success but you really care, say "hey reach out to your representative!"
Oh if it does't look like it has a high chance of success, then you maybe don't want to spend the time to reach out.
Compiling a data set that could be interesting in terms of predictor data sets. It's collecting data over time. Predictors for the legislation. We are compiling a real-time dataset.
Throw up another tab on the website that's like, "hey, researchers, check out our dataset! You can use this to look at Congressional bill data!"