“Did anyone approve this?”
A request gets buried in chat. Work starts before the right person sees it, and the decision has no clear record.
The next step becomes clear.
Give requests a named owner and a clear review status. Keep the decision alongside the work it affects.
See the next connection
Workspace / Website launchNWebsite launch
Clear owners. Visible progress.
What stays connected.
The details behind the workflow, including what is available and what is still planned.
THE CONNECTION
An incoming request needs a clear decision before it becomes a commitment. Record what is needed, who should review it and what was approved. When a request moves into delivery, the team can refer to the original details and decision history instead of asking the same questions again.
Follow approved work Explore team collaboration
An accountable owner
Make the request, its priority and the person responsible for its next decision clear.
An explicit decision
Retain the approval and its supporting details with the request.
A route into delivery
Keep the client, files and agreement attached when an accepted request becomes a task.
Also in the system
Client requests, leave, operational intake, decisions and follow-up.
How a request becomes a decision
A request is not yet a commitment. PLYNTUM records who asked, who decides and what was approved before the work starts.
Capture the request
Record what is needed, for which client or team, and how urgent it is.
Name the decision owner
Every request has one person responsible for the next decision.
Record the decision
Keep the approval and its supporting details with the request.
Move it into delivery
An accepted request becomes a task with the client, files and agreement still attached.
Who uses it
- Account leads
- Log client asks in one place instead of personal inboxes.
- Managers
- Decide with the context in front of them and leave a record the team can understand.
- Employees
- Request leave or raise an operational need and see the answer.
Available today and in development
| Client requests and operational intakeAll plans | Available |
|---|---|
| Approvals with decision history | Available |
| Leave requests | Available |
| An accepted request becomes a task | Available |
| AI flags for late approvals and scope changes | Planned |
What it replaces
Requests arrive by email, chat and phone. Without one place to land, they are either lost or started without a decision. In PLYNTUM each request has an owner and a record.
- Requests in personal inboxes
- Approvals given in chat
- Leave forms
Your first week
- Choose one type of request, for example client changes or leave.
- Name who decides for that type.
- For two weeks, route new requests of that type into PLYNTUM and review what was decided.
Connected areas
Common questions
Start with the work that keeps getting stuck.
Bring one project into a connected workspace. See the work, the people and the cost together.