Picking Up a GHK-Cu Enquiry Mid-Flight? What a Handover Must Say
A folder of emails, screenshots and a report is not a handover. Here is how to pass on a GHK-Cu enquiry so the next person knows what is done, what is open and who owns it.

A GHK-Cu enquiry handover goes wrong when the outgoing person passes over a folder and assumes the contents speak for themselves. They rarely do. The incoming colleague opens it to find a product page capture, a supplier email, an attached report and a half-finished spreadsheet, with no way of telling which items have been assessed and which merely arrived.
A good handover note takes about ten minutes to write and saves days of repeated questions. It says what the enquiry is for, how far each strand has got, who supplied each statement, and what happens next. The example here concerns CLOVA's GHK-Cu listing, but the structure works for any single-product enquiry.
Say what the enquiry is for
Start with the research requirement that justified looking at this item at all. A shortened label such as "the copper peptide one" should never replace it. If the project changes, the next person needs to judge whether the earlier work still applies.
Then name the candidate precisely, using the wording on the product page, and state whether any alternative came up. If a supplier suggested a different listing during correspondence, flag it as mentioned or assessed. Otherwise a later colleague may assume the original conclusion covers an item nobody actually reviewed.
Show how far each stage got
An enquiry has three strands that move at different speeds, and each needs its own status.
- Source identification. Is the product page the reference, and is a dated copy or link saved?
- Commercial clarification. Which questions went to the supplier, which were answered, and which are still open?
- Technical interpretation. Has the responsible researcher read the documents against the brief, or has nobody done so yet?
"Complete" is not a status. A file holding several documents has not been assessed just because the documents are in it. Say which strand each one belongs to.
Record who said what
Keep three voices apart: the supplier's replies, the original analytical records and your organisation's own interpretation. When the file is later shortened for an approval summary, those roles must still be visible.
A common trap: purchasing receives a report and files it, but nobody in research has read it against the brief. If the note does not say so, the arrival of the attachment quietly turns into a finished technical judgement at the moment the enquiry changes hands. Reports are published on the COAs page where one is available, and the batch number on the label should be matched against the report. Record whether that matching has been done.
Handover checklist
- One sentence stating the requirement behind the enquiry.
- The exact product name and page, with the date it was viewed.
- Questions sent, with dates, and the status of each: answered, partly answered or open.
- Each open question paired with what it stops you deciding.
- Attachments listed with who supplied them and whether anyone has reviewed them.
- Any internal correction labelled as internal, so it is not mistaken for a supplier change.
- The reason any earlier question was closed.
- One named person and one next action.
Keep corrections and closed questions honest
If you fixed a transcription error in the spreadsheet, say that it was your correction. Without that line, the next reviewer may suspect the supplier changed something, and an invented dispute can sour a perfectly good enquiry.
Closed questions need the same care. Suppose the supplier's reply cleared up a naming ambiguity. That settles the name, nothing more. Write down exactly what was resolved, so a finished administrative task does not grow into a broader assurance as the note is passed along and shortened.
End with one next action
Finish the note with the single decision waiting for attention and who is placed to make it under your organisation's process. "Follow up on documentation" is too loose. "Ask the supplier which report corresponds to the batch on the label; owner: purchasing" is something a person can do on Monday morning. The material is supplied for laboratory research use only, so the note should stay on records and purchasing, not on anything beyond them.
Frequently asked questions
How long should a handover note be?
One page is enough. If it runs longer, the detail probably belongs in the file, with the note pointing to it.
Do I need to explain work that was closed weeks ago?
Briefly, yes. State what was closed and why. Otherwise the new owner may reopen it, or worse, stretch the result to cover something it never addressed.
Who should sign off the technical reading?
The responsible researcher, not purchasing. Purchasing can organise the paperwork, but interpreting what a document means for your brief is a research decision.


