Separate First Welcome Gifts from Replacement Requests

A recurring welcome-gift request can contain people awaiting their first gift, people asking for another, and people whose earlier issue is unclear. Before sending a quantity to purchasing, ask the programme owner to approve each request under the current welcome programme and identify its reason. A staff list or attendance count cannot make that decision on its own.

The useful result is a welcome-issue reason and authorization register. It tells the buyer which first issues and replacements the programme has approved. It does not set employment policy, create a legal entitlement or decide how many gifts to order from a supplier.

Define what this welcome programme actually covers

Start with the named programme, its current approved purpose and the gift it offers. Identify the qualifying programme event using the owner’s existing instructions. That event might be admission to a particular programme or attendance at an identified induction; the article prescribes neither. Joining another team or appearing on a new list should not silently trigger another welcome set.

Ask the owner to distinguish first issue, replacement and any separately approved repeat award. Keep the actual permitted circumstances and exceptions attached to the programme reference. If the instructions do not resolve a case, return that question to the owner instead of inventing a rule for procurement convenience.

Define the issue unit as well. A welcome box containing a notebook and tote is one set if that is the approved programme unit. A request to replace its notebook does not automatically authorize another whole box. Preserve the approved scope before translating a request into product quantities.

Read prior issue evidence for the same gift programme

Check whether the person has already received the relevant programme gift, using the authorized record and its known coverage. A record covering one office’s distribution cannot settle what happened at another location. An empty field may mean no issue, incomplete recording or a record that was never meant to capture this programme.

Ask the record owner to resolve ambiguous status. Keep “owner confirms no prior issue” distinct from “prior issue unknown.” Similarly, a prepared box, dispatch entry or booked collection does not alone establish recipient receipt. Use the event actually evidenced rather than promoting every movement to a completed issue.

This distinction matters when a recipient asks again. An unfulfilled original request may still belong to the first issue; a replacement follows an earlier issue under the programme’s authorized replacement decision. Link the new enquiry to its earlier case so two descriptions do not become two welcome awards. Do not decide product fault or a remedy merely from the request reason.

Record the decision without copying the personnel file

Use a programme-specific key to connect the request, relevant prior issue and owner decision. Keep the person-to-key relationship in its authorized record. A key is not automatically anonymous, and a purchasing summary usually needs approved gift quantities and variants rather than a copy of every recipient’s background.

Record the qualifying event, prior issue status, request reason and approving owner beside the procurement disposition. Use a brief reason such as “first issue awaiting confirmation” or “replacement requested.” Avoid personal explanations that the decision does not require. Identify the decision reference and date in the accompanying record so an old approval cannot drift into a later welcome cycle.

The ICO’s UK data-minimisation guidance relates the information held to its purpose and the amount needed. The page flags that it is under review. This is limited UK background; this worksheet establishes no lawful basis, retention period, disclosure permission or privacy compliance for a gift programme.

Work through fifteen fictional welcome requests

Assume a fictional programme receives twelve first-issue requests and three replacement requests. Every request in this example is for one of the same standard welcome sets. All keys, circumstances, decisions and quantities below are invented teaching inputs, not employee records or customer results. The first row groups ten individually reviewed cases solely to keep the table readable.

The owner has approved 10 first issues + 1 replacement = 11 requests. Four remain unresolved: two submitted as first issues and two as replacements. The three replacement requests do not become three additional first-time recipients. Nor does the presence of fifteen request records justify buying fifteen sets.

The result is an approved request count of eleven, separated by purpose. Available gifts, existing allocations and the supplier’s current offer have not been established, so eleven is not yet an order quantity. The example supplies no buffer, stock deduction or estimate for the next intake.

Resolve exceptions without rewriting their history

For W11, establish what the earlier distribution entry actually means. If it proves an earlier issue, ask the programme owner whether any replacement is approved; do not simply relabel the pending first issue as an approved replacement. If the original issue remains unfulfilled, preserve its connection to that original request.

For R02, record the owner’s eventual decision and exact gift scope. An unresolved request is neither an approval nor a refusal. If a refusal or withdrawal is later confirmed, retain that outcome distinctly. A later amendment should identify which request and decision it changes, including any purchasing instruction already based on the earlier version.

Hand purchasing the approved gift requirement

Provide the programme reference, approved first-issue and replacement counts, gift units and variants, decision references and unresolved cases. Use the custom promotional gifts guide for the wider order stages. The purchasing owner must separately establish usable stock, the current offer and authority for the next commitment.

For a gift quote enquiry, describe the approved gift and grouped quantities without sending a personnel list. The form supports product text, links and specified image references. Arrange any necessary recipient-record transfer separately with an authorized contact; the register does not create an employee integration or upload facility.