A card that carries the procedure
Attach SOPs, maps, checklist runs and KPIs right inside the card.
Run personal, team, department and org work on boards where every card carries the SOP, process map, checklist run or KPI it is actually about.
In a standalone task tool, "follow the returns procedure" is a sentence someone typed, and the procedure itself is somewhere else and one version behind. Wikidoc puts the SOP, the process, the checklist run and the KPI inside the card, because it already owns them.
Pick who it is for, and name the columns the work actually moves through.
Owner, due date, priority, tags, and the SOP or KPI it is about, linked rather than described.
Assignment emails straight away, and a status change waits for the dragging to settle.
Attach SOPs, maps, checklist runs and KPIs right inside the card.
Personal, team, department or org. A personal board is yours alone.
Description, dates, people, priority, tags, comments and a full history.
Share a card link in a message or notice and it navigates people on that card.
Notifications that stay useful, so nobody mutes them.
Everything assigned to or watched by you, sorted by due date.
Opening a second site is forty tasks with an order to them, and each one carries the SOP it follows, so the second opening runs the way the first one did.
A checklist item that fails at open becomes a card with an owner and a deadline, still pointing at the run it came out of so nobody has to re-explain it.
Each new client is a board walked left to right, with the intake SOP on the first card and the engagement letter attached to the last one.
Servicing, calibration and stock reorders sit on a department board with real due dates, and each card names the KPI it protects.
Every card can come from a checklist run, carry the SOP it follows, and feed the KPI it serves. Same org, same source of truth.
The recurring runs whose failures become cards, with the run still linked.
The SOPs a card carries, so whoever picks the work up reads the current version.
The KPIs a task serves, and the review where finished work arrives as evidence.
Five: personal, shared, team, department and org. The kind is fixed when the board is created and cannot be converted, so if the work needs a different audience it is a different board.
Yes, and it is the one rule above all the others. A personal board has an audience of exactly one, its creator, with no admin override, no invitations, no assignees and no email.
No. Assignment emails immediately, because being handed work is news. A status change waits for the dragging to settle and is filtered for meaning, so a triage session is one message rather than thirty.
Every board and every card has a permalink, with a copy button on both. It is a link, not a grant: someone outside the board gets a page offering to request access, never a preview.
A description, dates, an author and assignees, a status, a priority, tags, watchers, threaded comments, subtasks, attachments and an append-only activity trail plus the Wikidoc artefacts and KPI it links to.
Yes. Every move has a keyboard and a menu path alongside the drag, and those same paths are what the mobile board uses. Drag-only would be an accessibility failure.