Weekly updates archive

Week of February 16, 2026

Weekly update: building trust through clearer support records

Last week was about trust as much as it was about progress. We strengthened how organizations are recognized in our system by introducing a single privacy-safe identity, so records can connect cleanly without exposing sensitive identifiers. That matters because people should not have to sort through duplicate or conflicting information when they are already carrying enough. Clearer records help create calmer, more confident decisions for everyone reviewing or publishing updates. We also clarified how publish and suppress decisions are made, so high-impact actions are permission-gated, reasoned, and explainable. This week, we’ll connect 990 enrichment work to the new identity model and begin implementing dashboard guardrails that keep review thoughtful and accountable.

• Created one privacy-safe organization identity so support records line up clearly without exposing raw EINs.
• Reduced duplicate and conflicting entries so people can move forward with more confidence.
• Strengthened record history safeguards so published information stays dependable over time.
• Clarified how publish and suppress decisions are made, so high-impact actions are transparent and accountable.
• Kept weekly updates fresh and aligned so our public trust signals remain steady and current.

Week of February 9, 2026

Making review decisions clearer and kinder to use

• Mapped review screens so teams can find the right place to act without guesswork.
• Finished permissions guidance so sensitive actions stay deliberate and accountable.
• Refined list behavior to reduce operator stress and avoid preventable mistakes.
• Defined publish dashboard expectations in plain language so outcomes are easier to understand.

Week of February 2, 2026

Keeping trust signals steady and understandable

• Turned weekly refresh into a reliable rhythm so public updates never feel stale.
• Kept config and landing payload aligned so what people read stays consistent everywhere.
• Refined trust-surface copy to be calmer, clearer, and easier to connect with.
• Protected deploy reliability while keeping freshness checks visible and accountable.

Week of January 26, 2026

Laying careful groundwork before moving faster

• Documented shared phase language so progress can be understood without insider terms.
• Strengthened TEOS foundations to reduce future rework and confusion.
• Set clear privacy-safe boundaries for aggregate insights before scaling up.
• Captured handoff details that make next steps easier for teams and reviewers to follow.

Week of January 19, 2026

Making discovery and review feel more dependable

• Improved directory foundations so verified organizations are easier to find and trust.
• Strengthened review and suppression guardrails to prevent avoidable errors.
• Clarified status flows so reviewers can make decisions with less friction.
• Kept privacy-by-design central as publishing surfaces continued to evolve.