Before You Say Yes FAQ | 50 Overseas Offer Risk Questions

Most people lose protection when a promise stays conversational. For "visa sponsorship", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "salary", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "probation", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "relocation", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "family support", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "verbal promise", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "visa rejection", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "start date", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "bonus", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "one-sided interpretation", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "career path", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "tax", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "job scope", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "overtime", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "travel reimbursement", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "equity", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "insurance", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "location", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "conditional offer", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "termination", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "non-compete", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "remote work", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "currency", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "dependents", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "tax promise", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "change flow", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "onboarding", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "document consistency", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "performance threshold", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "dependent documents", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "housing deposit", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "hidden tools fee", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "travel frequency", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "permit renewal", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "visa category", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "jurisdiction", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "leave", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "deductions", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "background check", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "email evidence", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "fallback role", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "salary reduction", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "rent reimbursement", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "second confirmation", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "relocation penalty", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "immigration profile", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "interpretation balance", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "offer checklist", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "time zone", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Most people lose protection when a promise stays conversational. For "amendment objection", turn the answer into four testable fields before signing: document, owner, deadline, and consequence. Compare the offer letter or contract, any company policy or appendix, and the HR/immigration/payroll email trail. If the same promise appears differently across documents, ask HR to identify the controlling version and confirm it in writing. Use this follow-up: "My understanding is: [condition], owner [name/team], deadline [date], fallback if delayed [fallback]. Could you confirm this in writing or share the policy that applies to my offer?" Until you have that confirmation, treat the item as an open signing risk.

Although rare, offer retractions do happen. First, immediately request in writing the specific reason and legal basis for the retraction. Second, check whether your offer letter or contract has an at-will clause or specific retraction terms. Third, if the contract does not allow unconditional retraction, you may claim reliance damages (visa fees, medical exams, flight tickets already paid). Fourth, consult a local employment lawyer about potential breach of contract. In future offers, consider requesting an "irrevocable after acceptance" clause.

This depends on the clawback clause in your relocation agreement. First, check the repayment terms carefully before signing — typically, if you leave or are terminated within X months of joining, you need to repay relocation costs on a pro-rata basis. Second, confirm whether a layoff counts as "involuntary termination without cause" which may have different terms. Third, even with a clawback clause, negotiate for a reduction, especially in company-initiated layoffs. Fourth, keep all relocation receipts and records for any repayment negotiation.

Whether your offer survives an acquisition depends on the acquisition type and contract terms. First, check if it is a stock purchase (offer usually continues) or asset purchase (new company not obligated). Second, contact HR or the acquirer for written confirmation of your offer status. Third, check for a change-of-control clause in your offer letter specifying the process. Fourth, if the acquisition cancels your offer, negotiate for severance or compensation for visa/relocation expenses already incurred.

Being fired during probation does not mean you have no rights. First, check local labor law — many countries require a valid reason and specific notice period even during probation. Second, review your contract probation clause for termination conditions and notice requirements. Third, even if terminated, you may be entitled to wages earned, unused vacation payout, and notice period salary. Fourth, if you believe termination was unfair, file a claim with the local labor court. Keep all performance feedback records.

Verbally promised bonuses have weak legal standing but are not entirely void. First, immediately send a confirmation email. Second, collect supporting evidence: interview notes, chat records. Third, check if the bonus is mentioned in your contract — if so, the verbal promise can serve as supplementary context. Fourth, in most jurisdictions, bonuses need to be in writing to be enforceable; verbal promises may only support an estoppel argument.

Chat promises on WeChat/WhatsApp can be used as evidence under certain conditions, but legal weight varies by jurisdiction. First, take complete screenshots including contact info, timestamps, and full context. Second, keep all chat records intact. Third, note that many courts require notarization or authentication — screenshots alone have limited probative value. Fourth, the safest approach is to forward key promises to HR and request email confirmation. Chat records generally serve as supplementary evidence only.

When interviewer promises do not match the offer letter, address this in writing before signing. First, list all key promises made during interviews and compare with the offer letter. Second, ask HR in writing which version is final for each discrepancy. Third, request that confirmed terms be added to the offer letter or contract appendix. Fourth, if HR cannot confirm the interviewer promises, treat them as unreliable and rely on the written offer.

When verbal promises conflict with contract terms, written contracts almost always prevail. First, check for an "entire agreement" clause that overrides prior verbal discussions. Second, if you discover conflicts before signing, insist on amending the contract or adding an appendix preserving the verbal terms. Third, if already signed, you may try estoppel but success is uncertain. Key: resolve all discrepancies before signing.

If the main visa is approved but the dependent is denied, act quickly. First, read the refusal letter for the exact reason. Second, consult the company immigration team about reapplying or administrative review. Third, ask if the company can adjust the visa type for family inclusion. Fourth, if dependents cannot join within a reasonable timeframe, consider delaying your start date. Fifth, ask about company policies for denied dependent visas — remote work options, additional fee coverage, etc.

Spouse work permits usually require a separate application. First, check the target country rules — some grant open work permits, others require separate authorization. Second, ask HR or immigration about the process, timeline, and costs. Third, confirm if the company offers application support or fee reimbursement. Fourth, prepare the spouse education and work documents in advance.

Prepare school enrollment documents during the visa stage as some require notarization and translation. First, contact international schools for a complete checklist. Common requirements: birth certificate (notarized + translated), vaccination records, report cards, passport copy, visa/residence permit. Second, be aware of enrollment deadlines. Third, check with your company about education assistance. Budget 3-6 months for school preparation in your relocation timeline.

Dependent visa processing takes 1-6 months depending on the country. First, ask the company immigration team for the standard timeline. Second, confirm if applications can be simultaneous or must be sequential. Third, if the timeline exceeds expectations, ask about short-term visitor visa support or remote work. Fourth, address this during the offer stage with sufficient buffer in your relocation schedule.

Exchange rate fluctuations directly affect your take-home pay. First, confirm the payment currency — if local currency, you bear all FX risk. Second, ask about company FX protection like annual fixed-rate conversion. Third, open a multi-currency account and convert in batches. Fourth, budget a 5-10% FX buffer in volatile environments and consider forward contracts for large transfers.

Sending money home involves exchange rates, fees, and regulations. First, compare Wise, Revolut, and PayPal against bank wires. Second, be aware of your home country remittance limits and keep payslips/tax documents for compliance. Third, send regular smaller amounts to manage FX risk. Fourth, check local remittance restrictions. Ask your payroll team about preferred remittance services.

Whether the company pays in local currency or USD affects income stability and tax. First, confirm payment currency and FX methodology in the offer. Second, check local tax treatment of foreign-currency salaries. Third, if you can choose, assess local spending needs vs savings to send home. Fourth, confirm with HR if the currency clause is adjustable and what FX benchmark applies.

Cross-border transfer costs include fees, FX spreads, intermediary charges, and receiving fees. First, compare total costs across providers — Wise offers best rates, bank wires suit large amounts. Second, check your home country annual remittance quota. Third, some countries require reporting above certain transfer amounts. Fourth, send in batches and keep payslips/tax documents. Your payroll team may offer bulk FX services.

Remote work offers require checking several dimensions. First, confirm payment currency, tax treatment, and payroll entity. Second, clarify timezone requirements — fixed core hours or flexible? Third, confirm equipment provision and expense coverage. Fourth, check visa requirements — remote work may need a work visa. Fifth, determine applicable labor law and social security. Sixth, clarify termination terms for remote workers.

Starting remotely before obtaining a visa carries some risk. First, clarify tax arrangements during the remote period. Second, confirm contract terms match post-visa terms. Third, establish a contingency plan if the visa is denied. Fourth, confirm equipment and timezone arrangements. Fifth, include a visa contingency clause in the contract: expected timeline, denial consequences, and maximum remote duration.

Cross-timezone contracts should address several elements. First, define core hours and flexible windows. Second, include a meeting rotation policy. Third, clarify overtime calculation for timezone-related extra hours. Fourth, set response time expectations and on-call allowance. Fifth, include periodic in-person travel clauses and wellness protections to prevent burnout.