{"compare":false,"blog":false,"article":false,"page":{"title":"Requests and approvals","lead":"Requests and approvals give each internal request, such as leave, remote work, new equipment or a one-off decision, a person who decides, a recorded decision and a history. The point is that nothing is granted, or refused, without a record of who decided and why.","sections":[{"heading":"The steps","html":"
  1. Request: what is asked, by whom, for which dates, with any details.
  2. Decision: a manager approves or rejects it.
  3. Record: the decision stays with the request, and the requester can cancel it before it is decided.
  4. Effect: approved leave shows next to the person’s attendance, so plans can take it into account.
"},{"heading":"A worked example","html":"

An example. A designer asks to work remotely on Thursday and Friday. Her manager approves the request with a note that the Friday client call is still in the office. The decision and the note stay on the request.

"},{"heading":"How PLYNTUM handles it","html":"

Requests and approvals are on every plan. The request types are leave, sick leave, late arrival, absence explanation, remote work, equipment or admin, and a general approval. Each moves from submitted to approved, rejected or cancelled, and the decision is recorded. Client changes are not a request type: add an agreed client change to the project as its own task. See requests.

See also people and capacity, team capacity and all terms in the glossary.

"}]},"faq":[["What is the difference between a request and a task?","A request asks for a decision. A task is agreed work with an owner and a date."],["Can PLYNTUM run multi-step approval chains?","Not today. Each request gets one decision. Multi-stage automations with conditions and approvals are planned for Scale and above, with no release date."],["Can a client change be logged as a request?","No, there is no request type for it. Record the change as a task on the client’s project, with an estimate, so its hours are tracked."]]}