Boards that forget.
Comments and checklists look real until you refresh. Harmoni Flow writes them to the database.
Harmoni Flow
A calm board for projects and tasks, with grid and timeline when you need them. The people on the cards are the same people Organo already shows. Leave is on the same ledger.
| Task | Owner | Column |
|---|---|---|
| Payroll export API | Soren | In progress |
| Onboarding Nadia checklist | Nadia | QC |
| Leave policy copy | Kai | Delivered |

HF-142 · In progress

Open My board on Sprint 14
Comments and checklists look real until you refresh. Harmoni Flow writes them to the database.
Portfolios, risks and automations matter, but they should not bury the board. They live under More.
Capacity that does not know who is on leave, and hire cascades that never become tracked work.
Inside the workspace
This is My board and the project board, not a dark window stacked under See it working. Capacity reads the leave ledger. Cascades write real cards.
The columns
Five named columns. Soft WIP. No sixth column you invent on a Friday.
How Flow fixes it
One record. Nothing entered twice.
Flow uses people and departments from Employee Management, capacity from Leave, goals from Perform, cascades from Recruit and resignation, tasks from Learn and Connect, and calendar due dates across the platform.
Inside Flow
Projects and tasks on a real board, with hire and leave cascades, automations and reports that read live Flow data.
Why teams switch
Open Flow and you see My board or a project board. Portfolios and automations live under More. They do not bury the work.
A checklist, a comment and a due date write to the database. A refresh does not invent a blank card.
A person on approved leave is not a free pair of hands on the sprint. The board reads the same leave ledger Organo does.
A Connect message can become a Flow task in one click. The person and the thread stay on it. Nobody retypes the chat into a ticket.
Already connected
Accepting an offer raises onboarding work. A resignation raises offboarding work. A Connect message can become a task. None of that is a template you paste by hand each time.
Who it is for

Delivery
Elena looks at Needs attention, not a wall of green. Overdue and blocked rise first.

The maker
Felix opens the drawer, ticks the checklist, logs time. The board updates for everyone else without a refresh meeting.

People
Offer accept already opened the onboarding project. She does not build it again from a doc.

A teammate on leave
Approved leave takes them out of capacity. Assigning them a due date this week is a choice you can see, not a surprise.
Keep reading
PlaybookHR approval workflowsA request that becomes tracked work, not a chat that went quiet.
GuideEmployee offboarding checklistResignation already raises the Flow project. This is what that project has to finish.
ProductDue dates on the company calendarA Flow due date is a real day on Company Calendar, not a private reminder.You can rename the five stages and set a WIP limit on each. A sixth freeform column is not in the product yet, and the screen says so.
Yes. Offer accept raises an onboarding project. Resignation raises offboarding work. Both are real Flow projects with tasks, not a toast.
Project membership and role-aware access. A board is not open to the whole company just because Flow is on.
No. Assignees are employees. Capacity reads approved leave. There is no shadow org inside the board.
Flow pricing
No tiers to decode and no sales call to get a number. Slide to your size and see exactly what Flow costs.
Every workspace starts from the connected employee record. Add Flow the moment your team needs it, with no re-import and no separate setup.