Learn how to use Luklak’s fixed Status Categories for system-wide consistency and how to embed step-by-step Workflow Guides directly into your processes.
STATUS
names for your workflow (like AWAITING REVIEW
or PENDING PAYMENT
), each one must be mapped to one of six fixed system Categories
. This simple requirement is the key to maintaining system-wide consistency.
STATUS
automatically inherits the color of its Category
. For example, all COMPLETED
statuses are green, and all CANCELLED
statuses are red. This provides instant, at-a-glance recognition of an Object's
state across the entire platform.Dashboards
and Filters
that report on the Category
level. You can easily find all ACTIVE
work across the entire company, even if different teams use unique status names like IN PROGRESS
, IN REVIEW
, or BEING WRITTEN
.Category | Color | Intended Meaning |
---|---|---|
OPEN | Light Gray | The work has been created but has not yet been acted upon. |
PLANNED | Sky Blue | The work is scheduled or planned for the future but is not yet active. |
ACTIVE | True Blue | The work is currently being actively processed or executed. |
COMPLETED | Green | The work has been successfully finished and achieved its goal. |
IDLE | Orange | The work is paused or waiting for external input to proceed. |
CANCELLED | Dark Gray | The work has been stopped and will not be completed. |
STATUS
of your workflow.
When a user is working on an Object
, the guide for the Object’s current STATUS
is prominently displayed. When the Object
transitions to the next STATUS
, the guide automatically updates to show the instructions for that new step.
IN REVIEW
status, clicking on the ‘Guide’ tab, and writing a checklist of review criteria. It would then show an end-user view where that guide is visible on an Object currently in the IN REVIEW
status.]