Keep the written version: a job-change record checklist for China

A proposed work change often begins with a quick meeting, a message, or a request to sign something. Before deciding what it means, it helps to preserve the written version of what was proposed. This is a practical record-keeping checklist, not legal advice or a prediction about any outcome.

1. Start with the original documents

Make a dated folder for the documents that describe the current arrangement: the offer, contract, signed amendments, job description, pay statements, benefits information, and any written instructions that matter to the change. Keep the originals intact. If a document is supplied only as an image or messaging attachment, save a copy with its date and source rather than retyping it from memory.

2. Record the proposal before the details blur

Write a short factual note after the conversation. Include the date, who was present, what change was described, when it was said to take effect, and which documents were mentioned. Separate direct quotations or written wording from your own questions. A simple timeline is easier to review later than a long narrative assembled after several conversations.

3. Compare versions, not assumptions

If a new contract, addendum, policy, or email arrives, keep it beside the version it may replace. Mark the date received and identify concrete differences: role, reporting line, workplace, hours, pay structure, leave, commission, benefits, or other terms. Avoid overwriting a file with a revised copy. A filename such as 2026-09-13-proposed-addendum-received.pdf makes the sequence clear without making a judgment about the proposal.

4. Ask specific questions in writing

When a change is unclear, focused questions are usually more useful than a broad request for reassurance. Ask what is changing, which document states it, when it would apply, whether another signature or approval is expected, and who can confirm the written version. If pay, work location, a work-permit-related process, or a document handover may be affected, ask how the proposal relates to those items rather than relying on an informal summary.

5. Keep a small follow-up log

For each follow-up, record the date sent, the question asked, the recipient, and the response or missing response. Save the message in its original format when possible. If a conversation happens by phone or in person, write a neutral note afterward that identifies the participants and the points you understood. This is not about building an argument; it is about retaining a reliable sequence of what was provided and what still needs confirmation.

6. Handle documents carefully

Do not alter screenshots, remove surrounding context, or annotate the only copy of an original document. Keep a working copy for notes and a separate source copy for reference. Where personal information is involved, use ordinary privacy precautions and share documents only with people who need them. A tidy source folder can make a later consultation or internal clarification much more efficient.

7. Review before you respond

Before replying to a request, read the written material once more and compare it with your timeline. Check that the date, the document version, and the question you are answering match. If release documentation becomes part of the discussion, the release-letter guidance offers a focused starting point for understanding why the written version matters.

A record does not settle a workplace issue by itself. It does, however, give you a calmer way to ask precise questions and retain the documents that shaped the discussion.