Once the tea gifts are on their way, the final task is to leave a record the next colleague can actually use. Put quantities, costs, dates and exceptions on one page, then link supporting documents in their approved storage location.
Start with the fields that explain the project
Record the project name, owner, purpose and period; planned and actual quantities; approved budget, confirmed charges and amounts awaiting reconciliation; key milestones; delivery status; exceptions; follow-up owner; and document location. Identify currency, date, tax treatment and source for each figure so that a “total” means the same thing to everyone.
Separate approved, incurred and paid costs
Start with the approved budget. List product, packaging, design, delivery and other confirmed costs, with approval details for additions. Invoiced, paid and awaiting confirmation describe different states: keep separate columns instead of asking the next colleague to solve a month-end mystery. Actual quotes, taxes and payment terms depend on the agreed documents.
Record the milestones that explain a change
Note actual dates for the initial request, specification confirmation, sample or design approval where applicable, final quantity, dispatch and receipt. Compare planned and actual dates and briefly explain relevant changes and owners. If the project did not involve a sample, mark that step not applicable rather than inventing a date.
Turn a delivery problem into an actionable record
Define planned, ordered, dispatched, confirmed delivered, remaining and unresolved quantities. For a damaged package, record when it was noticed, the quantity and batch, where photos are kept, the contact made and the agreed resolution. A case awaiting a response stays open with an owner and next date. Keep personal addresses and contact information in a properly controlled system rather than on a broadly shared summary.
Make the handover easy to use
Identify the approved specification, the final artwork, the location of any remaining gifts and the person responsible for outstanding items. Two concrete observations are more useful than a vague “improve communication”: for example, allow time to verify the recipient list before its final approval. Supplier and regional conditions can change, so confirm them again for a later project.
Common questions
Can a project be closed if not every recipient replies? Record completed delivery work as complete and keep unresolved confirmations in a separate follow-up list with an owner and date. Does staying within budget prove success? Cost is one measure; delivery, issue resolution and the original project objective deserve attention too.
A reusable one-page template
Project and period: ____; approved specification and quantity: ____; budget, confirmed costs and outstanding reconciliation: ____; planned and actual milestones: ____; deliveries and remaining stock: ____; issue, action, owner and due date: ____; approved document location: ____; what to retain and improve next time: ____. Fill in what is known, and give every open item a clear next step.
Work through one budget example
Imagine a project with an approved budget of 50,000 in the stated currency. The initial estimate allocates 40,000 to gifts and packaging and 5,000 to delivery, leaving 5,000 for other approved costs. After the event, compare orders, approved changes and invoices line by line. If the delivery charge is not final, record it as awaiting reconciliation rather than presenting an estimate as an invoice. These numbers illustrate a method; they are not a brand quote or recommended budget.
Columns can separate the original budget, approved changes, confirmed cost, outstanding amount and payment status. State currency and tax treatment. If a deposit and final payment are separate, track each. A design owner and a logistics owner can verify their respective documents before the project owner reconciles the combined figure. Approval, incurred cost and payment answer different questions; clear definitions save the finance team another guessing game.
Investigate quantity differences without guessing blame
Start with a common unit. If an order counts boxes and a shipping record counts cases, confirm the number of boxes per case. Then record ordered, dispatched, confirmed delivered, remaining and unresolved quantities with an as-of date. These fields do not necessarily add together: a dispatched count may already include delivered items. Explain the relationship before comparing totals.
For example, if 100 boxes were dispatched and 96 have confirmed delivery, record the four unresolved tracking references, last contact, owner and next check date. If two later return, record their return date and condition before deciding how to handle them. Do not assume returned food gifts are suitable for redistribution; check the packaging and storage condition with the supplier’s guidance. This is a hypothetical example, not a campaign result.
Keep facts, action and next steps distinct
For an exception, first record when it was observed, the relevant batch, quantity and what was seen. Next record contact, response and action. Finally list what remains unknown, who owns it and when it will be checked again. Store photos and delivery records with appropriate access controls; a summary can point to the document location without copying personal addresses into every version. If an external resolution is still being discussed, the status should say so.
A useful retrospective can include one practice to retain, one specific issue and one action for next time. “Have two owners independently check the final recipient list against the dispatch list” is more actionable than “communicate better.” If quantities, destinations, specifications or suppliers change, confirm the new conditions rather than treating an old project as a guarantee.
Give every line a status, owner and evidence link
A closeout sheet becomes useful when it distinguishes completed, confirmed, pending, disputed and not applicable. Add an owner and next review date to anything that is not complete. A delivery can be physically finished while an invoice, credit note or replacement remains open; calling the whole project “done” hides the one item most likely to return on a busy Monday.
Use a document link rather than pasting every invoice, address or photograph into the summary. Record the final approved specification, purchase order or quotation reference, delivery evidence, reconciliation file and exception log. The U.S. Federal Acquisition Regulation is written for government contracts, not private tea-gift campaigns, but its closeout structure offers a useful general lesson: evidence of receipt and final payment are separate records. Apply the principle, not its government deadlines, to an internal handover.
Protect recipient information during handover
The summary usually needs delivery counts, not a second copy of every recipient’s name, telephone number and address. Keep personal details in the authorised system, name the access owner and record the retention or deletion decision under the organisation’s policy. Taiwan’s Personal Data Protection Act requires collection, processing and use to stay within the necessary scope of a specific purpose; it also addresses correction and what happens when the purpose disappears or the retention period ends. The project owner should follow the organisation’s legal and information-security process rather than inventing a disposal period in the closeout sheet.
Use a three-minute handover test
Ask a colleague who did not run the project to read the page for three minutes. Can they identify the approved quantity, confirmed delivery, financial status, open exceptions, document location and next owner? If a field needs a private explanation, add the missing definition or link. The exercise is not an audit certificate; it is a practical way to discover whether the handover can stand without its original author hovering beside it.
| Closeout line | Status and evidence | Owner and next step |
|---|---|---|
| Specification and quantity | Approved version; ordered, dispatched, delivered, remaining and unresolved counts | Named owner; reconcile any difference by a stated date |
| Cost and payment | Budget, approved change, confirmed cost, invoice or credit status | Finance/procurement owner; next reconciliation date |
| Delivery and exceptions | Milestones, evidence location, facts and action taken | Service owner; open case and response date |
| Records and privacy | Authorised folder, access owner and applicable retention decision | Follow organisational policy and legal advice |
| Next project | One practice to keep, one issue and one specific improvement | Future project owner accepts the handover |
Explore next
Gift quantities · Budget planning
Sources
- Acquisition.gov: FAR Subpart 4.8, Government Contract Files
- Taiwan Laws & Regulations Database: Personal Data Protection Act
- Acquisition.gov: DFARS Subpart 204.8, Contract Files
Checked 12 November 2026. Government contract rules are used only as records-management references, not as deadlines for a private tea-gift project.

