Hi Hudu Community,
We’ve been rebuilding a big part of Hudu — Processes — from the inside out. This update has been a long time coming, and it changes how processes work at a pretty fundamental level.
The short version: processes are now more structured, faster, and a lot more flexible. You can break work down with subtasks, assign multiple technicians, and track everything through “runs.”
This is one of those features where early feedback really helps, so we wanted to open it up for community thoughts before we finalize things.
What’s staying the same
A few important things haven’t changed — just gotten clearer:
Global Process Templates still exist. These are perfect for defining standardized workflows that apply to multiple or all companies.
You can still create company-level processes from global templates (or start blank if you prefer).
Onboarding Processes still work as before, but will be getting a rename. As a reminder, these are global templates that can be "featured", automatically creating them at the company level.
Those concepts are solid — we didn’t want to reinvent them, just make them more intuitive.
What’s new
→ Runs
Company processes now have “runs.” A run represents a single execution of a process — the part you actually complete. The process itself is where you build and refine the workflow; runs are where the work happens.
Runs can be tied to assets or not, and they track progress, assignees, and completion over time.
→ Subtasks
Each process step can have subtasks. These help clarify detailed work without turning a single task into a wall of text.
→ Multiple Assignees
You can now assign tasks and subtasks to multiple team members. Collaboration finally fits the way teams actually operate day to day.
→ Optional Tasks
Tasks (and subtasks) can be flagged as 'optional'. If a subtask isn’t marked optional, it must be completed before its parent can be checked off — giving you both structure and flexibility.
→ Performance Upgrades
The entire process system is faster — large workflows load smoother, and navigation between tasks feels much lighter.
→ Process Run Dashboard
We added a dashboard where you can track total runs, completion rates, and overall performance for each process. It’s a small addition that makes it easier to measure consistency across clients.
A quick look
Process View (what you edit)
Editing a Task
Run View (what you complete)
Runs Dashboard (progress across runs)
Use-cases for V1
Run client onboarding workflows from a single shared process template
Assign different steps to multiple team members simultaneously
Track completion rates and performance over time
Manage recurring internal processes (security audits, employee onboarding, quarterly reviews, etc.)
What else do we have planned?
What we've listed above is just the first phase of this overhaul. Processes will be a large area of expansion for us in upcoming releases as well.
Recurring Processes: Ability to set up a schedule for when a Process Run should be created
Propagation from Global Process Template: If a process is created from a GPT, changes made to the GPT will cascade down to the company level
This will not affect already-created Runs.
Company Processes will have the option to be "detached" — meaning they will no longer update when their parent GPT changes (non-reversible)
Help us shape it
This is still in motion, and there’s plenty of room to adjust how it feels and functions.
We’d love to know:
How does the “runs” model fit with how your team works?
Anything missing from the subtask or assignment system?
What would make the dashboard genuinely useful for you?
Drop thoughts, screenshots, or just unfiltered opinions below — everything helps.
Let’s build this one together.