One place for everything that needs attention in Hypha.
Role: Member of Technical Staff, full-stack · Design: Sara Duval · Status: partly built, live with a customer for missing documents
The old way
Three places, three systems
Before Tasks, the app had no real way to track work. There was a separate notification center, a different place to review newly ingested data, and yet another spot that showed activity. The app also needed to tell people about many kinds of to-dos: new documents a loan might need, documents a covenant test was waiting on, data to review, financials to check, and so on. None of these shared the same underlying system.
The hard part
Agreeing on what a task is
The hardest part wasn’t the screens. It was agreeing on what all these to-dos had in common: what actions people should be able to take, which parts of the app should be allowed to create tasks, and how each task actually gets done and closed.
What a task is
Six parts, every time
In the end, every task came down to the same few parts: a description, a due date, an action to take, what created it, its current state, and a record of how it was updated along the way.
Closing the loop
Tasks that close themselves
Tasks close themselves. When the thing a task is waiting for shows up, like the missing document getting uploaded, the task resolves on its own, and anyone can reopen it if needed. We also designed it so agents could eventually pick up tasks and handle them, starting with scheduling covenant tests. That part wasn’t built, but the foundation is there for it.
What we built
One queue, grouped by deal
Tasks is the app-wide hub that collects all the work in flight across the platform (reviews, checks, and assignments) into a single queue. Tasks are grouped by deal, and each one carries its own comments and a full history of what raised it, so analysts can see what needs attention and why. People can update the status, assignee, and due date of one task or many at once, and saved views like Missing Docs focus on one kind of work.
Feeding into covenants
From a missing number to the right next step
This work fed straight into Covenant Compliance. When the covenant agent needs approved financials, it creates a task that takes you right to the next step: uploading the document, or reviewing the financials.
Where it is today
Partly built, already in use
Tasks is partly built. The core is in place (the walkthrough above shows it working), and the rest was in code review. It’s already deployed to a customer for tracking missing documents, and Covenant Compliance tests create tasks too.
What I learned
Find the middle ground
I learned that some ideas are so general they can mean anything, so you have to find a middle ground between too general and too detailed. It also taught me to step back now and then and look at the existing parts of an app to see what could be brought together in one place.
Covenant Compliance case study →
Cost Optimizations case study →