{"compare":false,"blog":false,"article":false,"page":{"title":"Give every request a clear destination.","lead":"Keep leave, remote work, equipment and other team requests in one place, each with a recorded decision.","sections":[{"heading":"What it brings to your business.","html":"<p class=\"content-eyebrow\">THE CONNECTION</p><p>A team request needs a clear decision before anyone acts on it. Record what is needed and for which dates; a manager approves or rejects it, and the decision stays with the request, so nobody has to ask twice what was agreed. </p><p class=\"content-links\"><a href=\"{{route:platform/work}}\">See how work is planned </a><a href=\"{{route:operations}}\">Explore team collaboration </a></p><h3>A clear request </h3><p>Choose the type (leave, sick leave, late arrival, absence explanation, remote work, equipment or admin, or a general approval) and add the dates and details. </p><h3>An explicit decision </h3><p>A manager approves or rejects the request, and the decision stays with it. The person who asked can cancel it until it is decided. </p><h3>A record for later </h3><p>Every request, its decision and any cancellation stay on record for the person and their manager. Before approving leave, check the minimum days, notice and carry-over rules in our guide to <a href=\"{{route:guide/leave-rules-georgia}}\">leave under Georgia’s Labour Code</a>. </p><h3>Also in the system </h3><p>Leave, sick leave, late arrival, absence explanations, remote work, equipment and general approvals. Client change requests are not a request type: add an agreed client change as a task on its project. </p>"}]}}