04 — Platform
The workspace, object by object.
Everything an Adilm employee does happens inside one workspace: a roster, a queue of work, the checkpoints where it stops for you, and the record of what was done.
The workspace
Employees
Work
- Assigned via voice
- Read the thread and the delivery policy
- Reply drafted
- Stopped at a boundary and asked for approval
- Assigned via task
- Started work on the overnight queue
- 11 threads categorised, 3 flagged as billing
- Assigned via task
- Delivered Unresolved issues, week 21
ListUnresolved issues, week 21
Oversight
Waiting for you
Reply drafted to the customer asking about the delayed order
Record
Unresolved issues from last week listed with their owners
ListUnresolved issues, week 21
Everything above, named.
The roster
Every employee you have set up, with its role, its reference, and whether anything is waiting on you.
The work queue
Everything assigned to a role, in one list, each item carrying its own state. Work that needs you leads it.
Assignment
A task, a chat message or a spoken instruction. All three become the same object with the same record.
Schedules and recurring work
Work that runs to a cadence rather than waiting to be asked. It appears in the queue like anything else.
Connected tools
What an employee may reach, and at which level. Read is separate from act, and scope narrows both.
Approval boundaries
The actions that stop and wait for a person. The task changes state; the change is the notification.
Collaboration
One employee holds the outcome, others contribute, and every handoff is recorded with a from, a to and a what.
Deliverables
Named and typed in text. A document, a list, a draft, a schedule — with the role and reference that produced it.
The activity record
Append-only. A rejected action is recorded, not erased. This is what “keep the oversight” actually means.
Retained context
What an employee knows about your business, carried across assignments, so you do not brief it again each time.
Ten states. Each one says what happens next.
A task is always in exactly one of these. The marker shape carries the state, the label carries it again, and colour comes third — so the whole system stays legible in greyscale.
- Accepted, not started.
- Queued for a stated time.
- Being worked.
- More than one employee involved.
- Stopped — a person must supply something.
- Stopped — a person must decide.
- A system condition prevents progress.
- The person decided; work is back with the employee.
- Complete, record available.
- Ended by a person.
Classes of connection, not a logo wall.
An employee reaches a class of tool at a level you set. We name the class, never a third-party product, because the products you connect are yours to choose.
- the connected inbox
- the connected calendar
- the connected CRM
- the connected document store
- the connected helpdesk
- the connected billing system
- the business context you provide