Can staff manage their own to-do lists in 613OS?
Yes. Every team member has a personal task list — each task with a title, due date, and the family or project it belongs to — and tasks created by automations land there too: the day-12 tuition call, an expiring certification, a reference to chase. The office opens one list instead of six sticky notes.
Does 613OS have kanban-style project boards?
Yes. Project boards run as visual columns — To Do, In Progress, Waiting, Done — with cards assigned to staff, dragged between stages, and automations firing on movement: assign a card and the owner gets a WhatsApp ping; a card stuck in Waiting for five days alerts the menahel. Honest scope: this is built for how an office and a committee work, not a replacement for dedicated construction-grade project software with subtasks and dependency charts.
How does event planning work with project boards?
The big events run on autopilot: eight weeks before the dinner, the full prep card set generates itself — book the caterer, open journal sales, confirm the honoree, print the seating chart — each card assigned and dated. The dinner committee gets a shared board instead of a group chat with 400 unread messages.
What makes this different from Trello or a to-do app?
Connection. A task about the Cohen family sits on the Cohen record with their whole history attached, and the platform's automations create tasks on their own — a failed payment, an incomplete form, a certification about to lapse — so the to-do list writes itself from what's actually happening in the school.