Naming a Revised Contact Role in the Enquiry Log or the Handover Note

The problem: one change, two documents, no clear owner

A fictional enquiry sits in a procurement folder. It has an enquiry log entry and a handover note. Then one ordinary thing changes: the named contact for that enquiry is reassigned to a different role, or a different person takes over the role. Nothing about the material changes. No price, quantity or specification moves. Only the name attached to a role.

That small change creates a filing question. Should the enquiry log be edited, or should the handover note be rewritten? If both are edited, the two documents can drift apart. If neither is edited, the next reader works from a stale name. If one is edited and the other is silent, a reader who opens only the untouched document has no way to know a change happened.

This guide works through that single decision using a fictional enquiry. Nothing here describes a real enquiry, a real order, or a real person. The aim is a repeatable habit: pick one document as the place where the change is recorded, and make the other point to it with a short cross-reference line.

San Techno Pte Ltd is a Singapore-based company working across semiconductor and solar materials, silicon recovery, specialised power module development, and botanical extracts under the ST GREEN brand. That breadth is useful context for why a procurement folder can hold several kinds of enquiry at once, but the naming question below is administrative and applies to any of them.

Why the enquiry log is usually the better home for the change

An enquiry log is built to be the running record. It is the place where a reference number, a date, a material description and a named contact already sit side by side. When a contact role is reassigned, the log is the natural place to record it, because the log is the document a reader checks first when they want the current state of an enquiry.

A handover note is different. It is written at a moment in time, for a specific reader, to carry context across a gap. It explains what is happening and what the next person should do. Rewriting a handover note every time a contact role changes turns a snapshot into a moving target, and a moving target is hard to trust.

So the working rule for this fictional enquiry is: the enquiry log records the change; the handover note points to the log. The log carries the new role name and the date the change was recorded. The handover note keeps its original wording and gains one cross-reference line.

This is an author heuristic, not a standard. It is offered because it keeps one document authoritative and the other honest about where the current answer lives.

What the log entry should contain

A log entry that records a reassigned contact role needs four things, and no more than four, to stay readable.

First, the enquiry reference. The change belongs to a specific enquiry, not to the folder as a whole.

Second, the role that changed. Name the role, not just the person. A role survives a personnel change; a name does not. Writing the role first means the entry still makes sense after the next reassignment.

Third, the effective date. A reader needs to know when the new name started applying, because an earlier message may still carry the old one.

Fourth, a short note on what did not change. If the material description, the quantity under discussion or the technical context is untouched, say so in a few words. That sentence stops a reader from assuming the whole enquiry was reopened.

A fictional example of the shape, not the content: reference, role, effective date, and a line confirming the material description is unchanged. Keep it to one line per field so the log stays scannable.

What the handover note should contain instead

The handover note should not repeat the new name. It should point to where the new name is recorded. That is the whole point of the split.

A cross-reference line in a handover note does three jobs. It tells the reader that a change exists. It tells the reader which document holds the current version. And it tells the reader the date of the note, so they can judge whether the cross-reference is still fresh.

A fictional cross-reference line might read: contact role updated, see enquiry log entry for this reference, dated as shown there. That is enough. It does not restate the name, so it cannot fall out of step with the log.

One caution: a cross-reference is only useful if the reader can actually reach the log. If the handover note travels to someone outside the team that holds the log, the note needs a plain sentence saying who to ask. Do not put personal contact details in the note; name the team or the role instead.

Keeping the two documents from drifting apart

Drift happens when two documents both claim to hold the current answer. The split above prevents most of it, but a few habits keep it working.

Date every edit. An undated change is hard to place against earlier messages.

Do not delete the old name. Strike it through or mark it superseded, with the date. A reader tracing a message from last month needs to see why the old name appeared.

Keep the cross-reference line short and identical in wording each time. A consistent phrase is easier to search for than a paragraph.

Review the pair when the enquiry closes. At close, the log is the record and the handover note is history. A short closing line in the log saying the enquiry is closed, with the date, stops the pair from being reopened by accident.

These are suggested habits, not rules drawn from research. Treat them as a checklist you can adapt to your own filing conventions.

Where this fits in a real supplier relationship

The naming question above is administrative, but it sits inside a real relationship. A procurement team that keeps a clean enquiry log and an honest handover note can hand an enquiry to a colleague without losing the thread. That matters when the enquiry concerns semiconductor materials, solar grade silicon, silicon recovery or wafer reclaim, where the technical context is often carried in the same message as the commercial one.

San Techno's public materials describe recovery of non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities, and processing of those materials into reusable raw materials for solar wafers and cells. A procurement team documenting an enquiry in that area benefits from a log that names the role clearly and a note that points to it, because the technical context is the part most easily lost in a handover.

The same applies to power module enquiries. San Techno describes an AC-to-DC power module design offering and a development programme around an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format. Detailed architecture, materials, dimensions and assembly processes are described as confidential, which is another reason a handover note should point to the log rather than restate technical detail.

For readers who want the wider company context before filing an enquiry, the About page is the natural next stop.

A short worked example, kept fictional

Here is the whole decision in one fictional sequence, with no real names, references or materials.

Step one. An enquiry is logged with a reference, a material description and a named contact role.

Step two. The contact role is reassigned. The log gains a dated line: role changed, effective date, material description unchanged.

Step three. The handover note is not rewritten. It gains one line: contact role updated, see log entry for this reference.

Step four. A colleague opens the handover note, sees the cross-reference, opens the log, and finds the current role and date. No one has to guess which document is current.

Step five. The enquiry closes. The log gains a closing line with the date. The handover note is left as history.

That is the whole method. It is deliberately small, because the change it handles is small. The value is in the consistency, not in the length of the entry.

When to ask the supplier instead of guessing

Sometimes the naming question cannot be settled from the folder alone. If the reassignment came from a message that is ambiguous about which role now owns the enquiry, the right move is to ask rather than to infer. A short question to the supplier's team, naming the enquiry reference and the role in question, is cheaper than a misfiled handover.

San Techno's public contact material lists a Singapore base and a direct phone number, and its contact page invites enquirers to include their area of interest and technical context so the team can respond efficiently. That is a useful pattern for any supplier message: state the reference, state the role, state what you need confirmed.

Keep personal contact details out of the enquiry log and the handover note. Name the team or the role, and let the reader reach the right person through the channel your organisation already uses.