Tool Purpose
Use this tool to decide whether a remote-first China entry model is reasonable for the next milestone. It is not a legal conclusion. The company must still check customs, tax, product, data, contract and sector rules for the actual activity.
Inputs
| Input | Question | Record |
|---|---|---|
| Goods | Will goods enter or leave China? | Product, HS classification and customs route |
| Service | Will the company provide services into China? | Service type, customer and delivery location |
| Partner | Will a distributor, agent or supplier perform local work? | Legal entity, authority and contract controls |
| Data | Will China personal or operational data be accessed overseas? | Data type, system, recipient and volume |
| People | Will employees or individuals work in China? | Employer, location and role |
| Milestone | What event would trigger local setup? | Sales, staffing, inventory or license threshold |
Scoring Logic
Mark each input as low, medium or high complexity. A high result means that the company should add specialist review before relying on a remote model. A remote model does not mean “outside regulation”; it changes which rules and authorities must be checked.
| Result | Suggested action |
|---|---|
| Low complexity | Document the cross-border route, contract owner and customs or data checks. |
| Mixed complexity | Add partner due diligence, product review, tax analysis and a launch checkpoint. |
| High complexity | Pause the commitment or obtain local professional confirmation before launch. |
Official Checks
- The Customs Law governs declaration and customs obligations for goods entering or leaving China.
- The CAC cross-border data rules must be checked when China personal or important data is transferred or accessed overseas.
- The Foreign Investment Law and access lists must be reviewed if the activity becomes an investment or local operating entity.
- Sector licensing and tax rules must be checked even when a local entity is not created.
Go-or-No-Go Checklist
- Describe the remote activity and counterparties.
- Confirm the customs, tax, product and data route.
- Verify the partner’s authority and evidence.
- Define the trigger for local setup.
- Record the decision, owner and review date.
How to Read the Result
A remote-first route is strongest when the activity is genuinely cross-border, the counterparties are controlled, the product and data route are documented and the company has a clear test milestone. It is weak when the company is effectively operating locally while treating the absence of a local entity as the only control.
Conclusion
Use remote entry as a controlled test, not as a way to avoid compliance. Review the official route again when sales, staffing, inventory, data, local support or licensing needs change.
Sources and Review Date
- Customs Law of the People’s Republic of China – customs and declaration framework
- Provisions on Promoting and Regulating Cross-Border Data Flows – data-transfer routes and exemptions
- Foreign Investment Law of the People’s Republic of China – foreign-investment and local-entity framework
Last reviewed: 2026-07-14
Management and Implementation Framework
A remote china entry decision tool: what to check before local setup should not produce a single number that management treats as a quotation. Inputs need a stated date, city, entity type, employee or transaction assumptions, and clear inclusions and exclusions. The useful result is a base case, a downside case and a list of variables that require confirmation. Before approval, the decision tool owner should reconcile the output to current contracts, official requirements and provider quotations.
Validate inputs before relying on the result
Ownership of each input should be explicit. Legal confirms entity and authority assumptions; finance confirms tax and cash assumptions; HR or operations confirms headcount and operating needs. Any field based on an estimate should be marked as such. A decision log should record the version used, the reviewer, unresolved questions and the point at which the estimate must be refreshed.
Control ownership and evidence
Management control depends on assigning decisions before deadlines become urgent. For remote china entry decision tool: what to check before local setup, the accountable group normally includes the decision owner, finance and legal reviewers, operating lead and approving executive. Responsibility should be divided between preparation, approval and independent checking. The core file should contain decision question, criteria, weightings, input evidence, option scores, sensitivity analysis and signed recommendation. Evidence should be dated, attributable to a named owner and linked to the decision or filing it supports. Verbal confirmation is not a substitute for a retained authority notice, counterparty response or approved internal record.
The control calendar should reflect the decision framing, evidence collection, option scoring, management review and post-decision validation. Dependencies and cut-off dates need to be visible to every function that supplies data. Any external provider should receive a written scope, required inputs, response timetable and escalation route. The company remains responsible for reviewing outputs even when execution is outsourced. Known failure modes include biased criteria, unsupported inputs, hidden trade-offs, false precision and failure to record why an option was rejected; each should have a preventive check and a named reviewer.
Management review and escalation
The review meeting should focus on exceptions and unresolved assumptions. The status pack should show the decision required, facts confirmed, assumptions still open, monetary or operational exposure, next deadline and responsible owner. Items that depend on local discretion should be labelled clearly. Escalation should occur when an authority rejects a filing, a counterparty requests materially different evidence, a cost or timing threshold is exceeded, or actual operations no longer match the approved setup.
Before go-live, the responsible executive should confirm that legal form, contracts, system configuration, payment authority and record retention are aligned. A short post-implementation review after the first operating cycle should compare planned and actual time, cost and exceptions. That review is where recurring controls are corrected and where lessons become part of the company standard rather than remaining with an individual adviser.
Practical completion checklist
- State the business decision, scope, city, entity and target date.
- Confirm the current official rule and any local implementation requirement.
- Assign preparation, approval and independent review to named owners.
- Retain the documents, calculations and correspondence supporting the decision.
- Test cost, timing and operational assumptions against a downside case.
- Record unresolved issues and the threshold for management escalation.
- Verify the first completed operating cycle and update the control calendar.
Execution Record and Handover
The final record for remote china entry decision tool: what to check before local setup should allow another manager to understand what was decided, which evidence was relied on and which obligations remain open. The handover pack should identify the current operating assumption, the approving executive, the external authority or counterparty involved, the effective date and the next mandatory review. It should also explain any local interpretation, exception or temporary workaround so that it is not mistaken for a permanent rule.
For decision tool, continuity depends on preserving decision question, criteria, weightings, input evidence, option scores, sensitivity analysis and signed recommendation. Files should use a consistent naming convention and access should follow the company’s authority matrix. Critical dates belong in a controlled calendar rather than an individual’s inbox. Where a provider holds original submissions or account credentials, the contract and exit plan should guarantee prompt return of records in a usable format.
A quarterly control check should sample one completed transaction or employee cycle, reconcile it to the approved process and record exceptions. Material deviations should be assigned to an owner with a due date; repeated deviations should trigger a process redesign rather than another informal reminder. This creates a defensible link between policy, daily execution and management oversight while keeping the control proportionate to the actual China operation.
