Approve an open delivery request
Check an open request, assign its delivery arrangements and accept it with an optional message.
Use Accept when you are ready to approve an open delivery request. You must be signed in as a manager assigned to its project, or as an administrator. Acceptance changes the request to accepted; submitting a delivery request alone does not produce that status.
Before deciding, inspect the request summary and compare the proposed arrangements with the project calendar. Pay particular attention to the delivery window and shared handling resources.
Accept the request
- Open Requests for the correct project and find the open request. On a phone, tap Menu first; Requests is also one of the two quick links in the top bar.
- Use Show to open the request page and read the contacts, delivery information, destination and requested resources.
- Select the green Accept button at the top of the request page. You can also select Accept in the request's row in the list. The dialog asks, Are you sure you want to accept this request?
- Review the fields below. Keep the proposed values or adjust the delivery arrangements you intend to approve.
- If useful, enter a Message to requester (marked (optional)) explaining instructions or changed arrangements.
- Inspect any conflict feedback. The Conflict warning lists overlapping requests and events, for example Request ID # 2: 14.01.2030 09:00 - 10:00, with the conflicting items. Where Send a message to requestors of the conflicting requests is offered, use it to explain the impact on affected accepted requests.
- Select Accept in the dialog. Use Close instead if you are not ready to submit the decision.
- Check for Request was successfully approved. You return to the page where you started. On the request page, the status is now accepted and the buttons are Change and Refuse. If you started in the list, the request can disappear from the open list: the list then says This list is filtered by: with the active filters; select Show all requests, or change Status to accepted or all.
Fields you can adjust
| Field | How to use it |
|---|---|
| Building, Floor, Sector | Select the destination offered for the project; lower-level choices depend on the preceding selection. |
| Area | Offered when area selection is enabled for you and the request has no building. Complete it when shown; the other path offers the project’s Building, Floor and Sector choices. |
| Date, Start time, End time | Set the delivery date and the intended delivery window. Start time and End time are lists in 15-minute steps. As a manager you can choose any time of the day; the opening hours of the site do not limit you. End times at or before the Start time are greyed out. If you choose a later Start time than the current End time, End time is cleared (Choose time) and you pick a new one. |
| Duration | Complete this when the option is enabled and shown. |
| Assigned 'drop off area' | Review the project’s drop-off zone selections. |
| Assigned 'drop off tool' | Review the assigned offload tools; the own-tools option is labelled Own offload tools where shown. |
| Message to requester | Add an optional explanation accompanying the decision. |
The dialog displays Delivery Info for reference when present; it is not a full edit form for requester contacts, goods or vehicle details. Available resource feedback can vary with operating dates and configured restrictions. Recheck destination choices after changing a building or floor. A request needs selected tools or the own-tools option; leaving both unset can fail validation.
Outcomes and problems
A successful approval records the decision and schedules approval notifications. If delivery details were changed, the notification can describe approval with amendments. A separately supplied conflict message concerns requestors of conflicting accepted requests. The notification path also copies request subscribers and project watchers and BCCs active administrators. Neither notification scheduling nor a success banner guarantees that an email reached its recipient.
Only open requests can be approved. If another manager has already acted, reopen the current request and check its status before deciding what to do next. Validation failures keep the approval dialog open. A red summary at the top of the dialog says how many entries to check, for example Please check 1 entry, and lists each problem as a link to its field, for example End time: Please fill in. The dialog moves focus to this summary. The message also appears under the field concerned. A problem that belongs to no field is shown as one red message at the top. Correct the indicated fields and submit again only after checking the arrangements.
Do not treat a successful manager decision as proof that all overlaps have disappeared. Use scheduling conflicts to inspect them. To change an already accepted delivery, use Change as described in amend an accepted request.
Check the current selection before saving
In Accept and Change, the compact check status describes the date, time and resources currently selected in the dialog:
| Check status | What to do |
|---|---|
| Checking this selection… | Wait for the current selection to be checked. |
| Conflicts remain for this selection | Inspect the overlapping Accepted requests, Open requests and Events, their links and conflicting items. |
| No conflicts found for this selection | No overlaps were detected by this check for the selected time and resources. This check does not save the selection. |
| Complete the date, time and required selections to check conflicts. | Complete the date, time and required destination selections; End time must be later than Start time. Select an unloading tool or Own offload tools, and enter a numeric Duration when shown. The form automatically checks the updated selection. |
| The conflict check is unavailable. Please try again. | The check failed; this is not a clear result. Select the Check again link. |
When conflicts remain, the short hint links to the existing time controls. It can additionally link to an affected unloading area, unloading tool, building, floor or sector when those controls are present. Change the selection using the indicated controls, then let it be checked again. The hint disappears when the check finds no conflicts. It does not find a free slot or choose an alternative for you; all existing fields stay directly editable.
The notice Changes are not saved yet. remains separate from the conflict result. Select Accept or Save to submit the decision, then check the actual success message and saved request. A successful acceptance or amendment can still retain overlaps; inspect its saved conflict result and coordinate the arrangements when needed. Managers may deliberately retain a coordinated overlap. A clear draft does not confirm that anything has been saved, and a successful save does not prove that the schedule is conflict-free.
The existing Message to requester and separate message to requesters of conflicting accepted requests keep their different audiences. See conflict communication before sending either message.
If saving reports Saving could not be confirmed. Check the request before trying again., the dialog stays open with your entered values. A failed response or network interruption does not establish whether the server saved the decision. Select Close, then reload or reopen the request to get its current status and details before submitting again; the page behind the dialog may still show the earlier state. Do not immediately repeat the decision. This save warning is separate from a failed conflict check. A response with validation errors can display a new form without this warning. Its disappearance does not tell you whether the earlier decision was saved; still reload or reopen the request before submitting again.
A successful acceptance, or a changed amendment, also includes the saved conflict result after its success sentence: Conflicts remain for this booking. or No conflicts found when saving. Read that suffix as well as the success sentence. An amendment with no changed details and no added messages returns without a success notice.
Element availability
Approval checks every assigned element at the selected arrival time, even when you keep the requested date. A saved request summary can show that an element is no longer available and link to its editor. For an archived element, ask an administrator to review it; managers without administrator access cannot open its editor. In the approval form, replace or remove unavailable selections before accepting. These availability errors are separate from overlap warnings; confirming a conflict does not waive them. Refusing a request without changing its date or selections remains possible without correcting retained unavailable elements.
Approve a request
These images show the English RERA interface, captured on 13 November 2026 UTC in a synthetic local project. Example project dates use a synthetic January 2030 clock. The GIF presents selected actual steps. Options depend on the project and your role.
