Abstract enquiry preparation file for product liability matters

Enquiry preparation · browser-only

Prepare the right high-level facts before opening a secure enquiry.

Organise a short, non-sensitive product-incident briefing before opening the existing secure enquiry path. Nothing selected here is submitted, stored, or sent to a lawyer.

Prepare my enquiry → What not to share ↗

03 preparation stages 05 briefing prompts ER–PL preparation companion

01 Starting point

Keep the context you already built

Carry forward the useful context from the guide, directory, or city page before entering the secure enquiry.

This companion helps you organise a concise first conversation. It does not replace the existing intake, consent, conflict, privacy, or engagement process.

Starting point

Product liability guide or counsel directory

Keep the substantive product guide and lawyer directory as the primary places for orientation and counsel discovery.

Briefing scope

Product safety / claim / recall context

Prepare only a high-level description of the product category, party role, city and event type—without incident files or confidential technical data.

Next step

Existing guided secure enquiry

The handoff opens the established enquiry experience with route context only. Your checklist selections do not transfer.

02 Prepare

Choose where you are in the process

Choose the high-level stage that best describes your situation. The prompts then show what can be prepared safely without entering a confidential matter history.

These choices help frame an initial professional conversation. They do not assess suitability, urgency, legal merits, or lawyer availability.

Current stage

Planning product compliance or market placement

Use a high-level product category, party role, and timing frame—without attaching specs or certification packs.

✓ A high-level route frame is different from a legal conclusion or a document review.

03 Briefing checklist

Prepare only high-level context

Prepare the basic facts that can be stated safely at a high level.

Use the checklist as a private prompt for yourself. Your selections are not stored, submitted, or transmitted by this companion.

I can describe the product category in plain, non-sensitive language. Example: consumer electronics, food, cosmetics, or industrial components—not formulas, source code, or batch-level trade secrets. I can state the high-level supply-chain role. Use brand, manufacturer, distributor, platform, or insurer; do not provide company numbers or personal identifiers. I can identify the relevant city or market context. A city or market is enough; do not provide plant addresses or customer delivery details. I can name the timing in general terms. Use planning, recent complaint, or recall-review stage; do not upload timelines, notices, or evidence packs. I can name the main question to organise for a first conversation. For example: compliance pathway, incident response, recall readiness, insurance notice, or claims orientation.

04 Privacy boundary

What not to enter here

Keep confidential material, identity data, documents, and detailed legal issues out of this browser-only preparation step.

Do not add

Document or evidence file

Keep agreements, drafts, correspondence, regulator notices, schedules, and other files for an appropriate secure process.

Do not add

Identifier or contact record

Do not use this companion for names, passports, company numbers, banking data, emails, telephone numbers, or employee information.

Do not add

Conclusion or case assessment

Do not treat the page as a way to establish access, solve a transaction question, judge a deadline, or obtain advice.

Incident photos, medical records, lab reports, recall packs, credentials, or images Customer or employee identifiers, contact information, or confidential technical specifications Legal conclusions, regulator allegations, settlement terms, or a full confidential chronology

05 Secure handoff

Continue to the existing secure enquiry

When ready, open the existing guided enquiry with only the Product Liability route context attached.

The existing intake should present its own consent, privacy, conflict, scope, and secure contact process. This companion does not bypass those controls.

Continue to secure enquiry ↗ Browse product lawyers →

What the handoff carries

Practice contextProduct Liability

Operating stancePlanning product compliance or market placement

Checklist progress0 / 5

✓ No selected fields, documents, contact details, or narrative are included in the route transfer.

06 Other useful routes

Need more context first?

Go back to the relevant guide, location page, or lawyer directory if you need more context.

Read the product liability guide

Return to national product safety, recall and claims orientation.

Check consumer-protection context

Use the consumer route when platform, advertising or consumer-claim questions also matter.

Browse product lawyers

Compare practice-side discovery records before entering a professional handoff.

07 Common questions

Before you continue

Common questions before moving into the secure enquiry process.

Does this readiness companion send my selections to China Legal Portal or a lawyer?

No. The controls operate in the current browser view only. The handoff link carries only its controlled route context, not selected fields, documents, contact details, or a narrative.

Can I use this page to submit documents or explain a confidential issue?

No. The companion is intentionally limited to high-level preparation. Do not upload or paste confidential material until a secure channel, engagement scope, and appropriate professional process are confirmed.

Does opening the guided enquiry create a lawyer-client relationship?

No. The existing enquiry route should present its own consent, conflict, scope, and engagement boundaries. A route selection or enquiry does not establish representation.