An English product page says a protective cover “can be removed before operation.” The source instruction meant that the operator was permitted to remove it for a particular inspection, under stated conditions. The English sentence now reads as a statement of capability. A fluent translation has changed the kind of information being supplied.
Industrial content contains requirements, recommendations, permissions and descriptions of what equipment can do. Before translating those sentences, identify their function and the document that authorizes them. A modal verb is one clue, but the surrounding condition, actor, prohibition and source revision are just as important.
This matters to overseas buyer research. An AI-generated comparison may compress a qualified instruction into “supports operation without a cover” or treat an optional feature as a standard delivery obligation. The manufacturer's English source should make the authorized meaning easier to recover.
Use the standard's own language convention
ISO explains the verbal forms used in its documents: shall expresses a requirement, should a recommendation, may permission, and can possibility or capability. The explanation appears in ISO's supplementary information for standards users. That convention helps readers interpret the kind of provision they are reading.
It is a convention for those documents, not a universal rule that every company's manual, contract and website already follows. Read the governing source. A manufacturer's house style may use direct instructions or another controlled vocabulary. A marketing writer cannot change that convention by replacing all occurrences of one word with another.
ISO's house-style guidance also places clarity in the context of international readers. Clear wording is useful, but shorter wording is not automatically equivalent wording. Deleting a condition can make a sentence easier to read while making it wrong for the product.
Separate the sentence's function from its grammar
Consider four invented supplier statements. They illustrate semantic differences; they are not operating instructions for real equipment.
| Intended function | Illustrative statement | Question the reviewer must settle |
|---|---|---|
| Product requirement | The inspection record shall identify the drawing revision. | Is this required by the applicable document and within its scope? |
| Recommendation | The supplier should retain a copy with the shipment record. | Is deviation permitted, and who decides? |
| Permission | The buyer may request a second language version. | Who grants permission, and under which commercial terms? |
| Capability | The viewer can display the approved STEP model. | What tested function and file conditions support that claim? |
The table is deliberately about records and publishing. A website team can review those statements without creating new machine-safety instructions. When the source concerns installation, protective equipment or hazardous operation, the technical owner must approve the meaning. Copy editing does not supply that approval.
The same word can also serve ordinary grammatical functions outside a normative provision. A sentence such as “the operator may encounter condensation” expresses a possibility in ordinary usage. A reviewer should read the document's definitions and context rather than applying a blind dictionary substitution.
Keep the actor and object attached
“May be supplied” can conceal who makes the choice. Does the manufacturer decide what to ship? Can the buyer order an option? Is a distributor allowed to substitute a component? The modal alone does not answer those questions.
A buyer-facing page can often be improved by naming the responsible actor and the relevant commercial step. For example, an invented feature description might say: “A stainless-steel bracket is an order option for model AX-2; confirm the option code in the quotation.” That gives the buyer a verification task without inventing a universal promise about stock or compatibility.
Likewise, “supports remote access” leaves open whether the capability is standard hardware, a licensed module, a future feature or a service the integrator must configure. Those distinctions belong in the product record before an English writer chooses a polished sentence.
For each important sentence, preserve the actor, action, object, condition and source. If one field is unknown, mark it for the product owner instead of letting English fluency conceal the gap.
Treat negation and exceptions as controlled content
A prohibition is easy to weaken accidentally. “Shall not,” “not recommended,” “not supplied” and “not possible” do different work. One concerns a requirement, another advice, another delivery scope and another capability. They should not be normalized into a single negative phrase.
Exceptions need the same care. “Except during inspection,” “unless ordered separately” and “only with revision C” can determine whether a claim applies. Moving an exception into a distant footnote makes it easier to lose when a page is summarized or a product table is copied.
An editorial review should compare the condition at the sentence and row level. If the table says “included” but its linked manual says “optional,” do not resolve the conflict by choosing the more attractive word. Identify the exact model, date and delivery configuration, then obtain a controlled correction from the owner of that information.
Build a requirement register for the release
For a modest English website project, a spreadsheet is often enough. Give each important instruction or delivery claim an identifier. Record its source document, revision, section, product applicability, semantic function, approved Chinese text, approved English text and approver.
The register is especially useful when the same statement appears in a product page, downloadable manual, FAQ, quotation template and distributor feed. A correction can then be traced to each affected occurrence instead of relying on someone remembering where a phrase was copied.
This register is an editorial control. It does not turn a website team into the authority for equipment safety or a conformity assessment. The authorized engineering or contractual source still determines what the company can state.
Use a status such as “technical meaning awaiting approval” when that review is incomplete. A translation can be linguistically reviewed and still be unapproved for release. Keep the two decisions separate.
Review summaries by asking for a decision
A useful content acceptance exercise asks a reviewer to answer a concrete question from the English page. Is the buyer required to submit a drawing revision? Is the bracket included? Can a distributor supply a local replacement without approval? Which instruction applies to the product being ordered?
Compare the answer with the authorized source. A paraphrase that merely repeats the same modal is less revealing than a decision about what a real buyer or supplier may do.
An AI summary can be one additional test surface, but its answer does not approve the source text. Save the exact question, complete answer, cited passage and source revision. A correct response once does not establish how every assistant will interpret the document. A wrong response should be investigated at the passage and context level before attributing it to a model's general language ability.
Google's guidance for AI features in Search does not offer a special wording formula that guarantees inclusion. The practical value of preserving semantic function is that both people and systems have a better source to consult. A recommendation or citation still needs to be observed directly.
Keep the publishing assignment within its scope
Xindar's manufacturing content work can support an English supplier website and buyer-facing content. A sensible brief asks for source-linked claims, visible applicability and a human approval route. It should name who supplies technical decisions and who authorizes the English release.
The work should not silently expand into an engineering certification, legal interpretation or automated sales commitment. In particular, an inquiry path with human handoff does not establish that a system can automatically approve technical exceptions or promise a delivery configuration.
When a source requirement changes, update the approved English text and its affected representations together. Preserve the original publication history and record the actual modification date. An unchanged URL does not mean its instruction has remained unchanged.
Questions that expose a weak translation brief
Should every Chinese instruction use “shall” in English?
No. First identify the source's function and governing writing convention. A requirement, recommendation, permission and capability statement need different treatment. Direct procedural instructions may also be appropriate under the applicable style and technical approval.
Is “can” always the wrong word on a product page?
No. It is useful for a supported capability. The problem is using capability wording where the source grants permission, defines an order option or imposes a requirement. The writer needs the underlying fact before choosing the sentence.
Can a terminology glossary solve the problem?
A glossary helps with recurring terms, but it cannot establish the actor, condition or current applicability of a whole provision. Pair terminology control with sentence-level source and approval records.
Before releasing the next English manual or product page, review ten sentences that contain obligations, permissions, options or prohibitions. For each, write the buyer's resulting decision in plain language and compare it with the authorized source. That small exercise can reveal a changed commitment that a fluency check would miss.