How do you translate a WIPO Digital Access Service (DAS) patent priority document notice without confusing an access code with an application number, or a document made available for retrieval with an accepted priority claim? Accurate international patent translation preserves the office of first filing, earlier filing date, application type, DAS access code, later office, retrieval request, correspondence history and each deadline. A single altered character or upgraded status verb can make a cross-border filing record unreliable.
This world-facing guide explains how to translate WIPO DAS priority document correspondence, first-filing confirmations, retrieval requests, patent office deficiency notices, certified copy statements and international application references into precise educational English. The Digital Access Service allows participating intellectual property offices to exchange priority documents through a secure system. It does not itself grant a patent, establish that a claim is legally valid, or replace the rules of an office of second filing.
Start by distinguishing the earlier filing from the later application. Copy both application numbers and all filing dates exactly, preserve access codes confidentially, and check whether the second office requested, received or merely could retrieve the priority document. Under the Paris Convention, the general priority period is twelve months for patents and utility models and six months for industrial designs and trademarks; confirm the actual deadline and any procedural exception with the competent office or a qualified patent adviser.
- Separate earlier and later applications, their offices and filing dates.
- Do not equate DAS registration with priority claim acceptance.
- Keep access codes and certified copies confidential and accurately labelled.
- Use WIPO and the relevant office’s current procedural guidance.
- Translate pending, available, received, retrieved and approved as different states.
Why priority documents are easy to misunderstand
The reader normally sees several stages in one folder: the first office’s original application, a later filing referencing it, a system permission to access the document, an office request to retrieve it and possibly another letter questioning formal compliance. These stages belong to one procedural story, but they are not interchangeable. A good translation keeps the relationships clear enough for a patent specialist to verify each step.
The WIPO mechanism addresses document exchange. It is not an examination of inventive step or novelty. A translation should therefore avoid promising a patent grant or legal effectiveness merely because a document has been uploaded to a secure database. When the file contains multiple national or regional offices, identify who is speaking in each record and whether its instruction is binding for the case at hand.
Read the complete filing chain before translating one sentence
Begin with the earliest source date and original application identifier. Then locate the later application and claimed priority statement, depositing office, DAS registration message, access code, retrieval request, retrieval status and any unresolved deficiency notice. This chronology helps distinguish filing acts, documentary evidence and official decisions. Where a source is incomplete, ask the responsible person to supply the missing record instead of guessing.
Use a verification table with columns for source term, translated term, number or date, issuing authority, supporting document and unresolved question. That structure is particularly useful for multilingual firms handling several applications and multiple countries. A translator can write natural English while retaining the underlying evidence and legal status exactly.
1. Office of first filing
The office receiving the earlier application is the original source of the priority document and is often the depositing office in DAS. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
Do not call that office the later examining office or assume it has granted a patent just because an application exists. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
An inventor first files in a national office and later seeks to use the original filing as the basis for a claim abroad. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Retain the formal office name, jurisdiction, earlier application number and distinct role in the document exchange. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
2. Office of second filing
The later patent office receives an application claiming priority from an earlier filing and may retrieve the evidence through DAS. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A subsequent office is not automatically the depositing office, nor does it approve priority by merely downloading a document. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
A regional office is asked to obtain an earlier national filing through the secure exchange mechanism. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Keep the receiving office, request date, legal role and retrieval status clearly separated. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
3. First application identifier
The original application number identifies the earlier filing, commonly with country, year and other office-specific components. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
A publication number, patent grant number, internal attorney code or DAS access code must not be substituted for the application number. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
A legal file includes multiple similar-looking codes under different headings, each used for a different purpose. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Copy digits and letters exactly, retain punctuation when meaningful and label the identifier according to the source. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
4. Later application identifier
The subsequent application has its own number and filing date even if it claims benefit of a previous application. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
Saying both applications have the same number can make an office unable to match a retrieval request. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
A subsequent PCT application cites an earlier domestic filing, and the covering letter contains both references. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Place the earlier and later identifiers in different fields and check the office prefix against the actual record. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
5. Priority date
A priority date identifies an earlier qualifying filing relied on for an applicable priority claim. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A translator must not calculate a new priority date from a publication date, office response date or DAS upload timestamp. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
A source records an early-January first filing but a spring DAS registration; those are separate procedural dates. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Render calendar dates unambiguously and preserve the originally claimed priority relationship without implying validation. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
6. Later filing date
The later application filing date identifies when the subsequent application was submitted in its own jurisdiction or route. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
Moving this date back to the earlier priority date conceals the separate event and can distort deadlines. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
A later international application is filed months after the national application whose priority it claims. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Keep both dates visibly distinct, retain timezone or receipt qualification if present, and check the source form. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
7. Priority claim itself
A claim of priority is a formal assertion by the later applicant seeking the benefit of the earlier filing under relevant law. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
DAS registration by itself is not a priority claim, and a claimed right is not automatically an accepted right. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
An applicant includes the earlier office, date and number on a later application form requesting priority treatment. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Translate the claim as a claim, avoiding phrases that state legal entitlement was finally established. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
Reading application identifiers and DAS access
8. Priority document
A certified copy of the original filing is documentary evidence used to support applicable priority formalities. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
An ordinary abstract, public search result or translated summary is not inherently the same thing as a certified priority document. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
An office makes the application as originally filed available for electronic retrieval. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Identify precisely whether the document is a certified copy, supporting extract, portal status screen or correspondence. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
9. DAS access code
The access code authorises an office to retrieve a particular document made available through the WIPO Digital Access Service. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
It is not a patent number or public identifier, and the translator should not put real confidential codes into a public example. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
An applicant receives a code after the original office makes a priority document available for participating offices. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Copy the code accurately only within an authorised confidential workflow, verify the associated first application and do not translate its characters. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
10. Registration in DAS
Registration or availability means the earlier document has been made accessible in the relevant system under defined procedures. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
The word registered should not become patent registered, patent granted or finally accepted priority. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
A depositing office sends an electronic notice that a first application is now accessible in DAS. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Translate this as a document-access event and preserve which subsequent retrieval action remains outstanding. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
11. Depositing office notice
A depositing office may issue a notification indicating the original filing document has been prepared or made available. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A receipt from that office is not proof the second office requested the document or accepted a claim. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
An electronic message identifies the first filing and states when its certified copy entered the exchange service. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Preserve sender, office reference, document type, exact time and any warning about incomplete details. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
12. Applicant authorisation
The applicant or an authorised person enables retrieval by providing the correct priority details and access code. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
A code copied into a draft but never submitted to the later office does not show the office can retrieve the file. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
An attorney completes a form for the later office and includes the first filing’s identifier and DAS code. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Keep the requesting person, legal role, destination and method of authorisation clear. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
13. Retrieval request
The later office may be asked to retrieve the original document using DAS rather than waiting for a paper copy. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
A filed retrieval request is not proof of successful retrieval, and a promised future request is not a completed action. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
A PCT request form contains a box asking the International Bureau to obtain an earlier application. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Translate the exact imperative or requested action and preserve the request date and target document. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
14. Retrieval completed status
A successful retrieval means the receiving office obtained access to the specified earlier document. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
It does not conclusively establish compliance with every formal priority requirement or validity of the claimed priority date. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
A portal shows received or retrieved while an examiner may still raise a separate legal or procedural question. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Report the actual system event, time, version and recipient; do not extend the statement into substantive approval. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
Separating legal rights, office actions and deadlines
15. Retrieval failed status
A failed retrieval may follow an incorrect identifier, missing deposit, wrong access code or mismatch in participating-office support. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
The error should not be translated as proof that the patent application is fake or that the invention lacks novelty. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
A later office cannot locate a filing because the country prefix differs from the deposit record. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Preserve the exact error code, unsuccessful action and remedy instructions, referring unresolved discrepancies back to the responsible office. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
16. Patent versus utility model
Different forms of intellectual property have different legal definitions even when they relate to technical inventions. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
A utility model filing should not be renamed a granted patent merely because the source uses an unfamiliar local term. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
An applicant has an earlier utility model application and must accurately identify its type in a subsequent request. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Keep the underlying right type, the applicable office classification and the stated priority basis. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
17. Design versus patent
Industrial designs and patents may both use priority-document mechanisms in participating offices, but they cover different forms of protection. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
Treating a design document as a patent filing can make the translated form invoke the wrong period or procedure. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
One law firm handles ornamental design filings and technical patent applications in parallel. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Translate the particular intellectual property class shown in the filing and refrain from merging unlike applications. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
18. Paris Convention timing
The Paris Convention sets standard priority periods, generally twelve months for patents and utility models and six months for industrial designs and marks. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
A generic claim that every DAS-related document has twelve months is wrong and dangerous for time-sensitive filings. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
A client prepares a patent filing and a trademark filing based on earlier applications signed on the same date. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Retain the right type, source date and applicable rule; ask a qualified docketing expert to verify deadlines and exceptions. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
19. PCT international application
The Patent Cooperation Treaty offers a procedural route for international patent applications that may claim priority from an earlier national filing. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
Calling a PCT filing an international patent grant creates legal rights the source did not establish. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
An applicant files through a receiving office and requests DAS access to an earlier application as a priority document. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Keep PCT filing, international publication and national or regional procedures distinct. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
20. Participating offices and scope
WIPO DAS operates between participating intellectual property offices, but each office may support particular document categories or functions. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A country’s appearance on a public list does not guarantee every office service or filing type is supported. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
A later office can retrieve some document categories while the earlier office deposits a narrower set. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Check WIPO’s current participating-office details and preserve support limitations in the translation. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
21. Certified copy versus screenshot
The official certified priority document serves a different evidentiary purpose from a screenshot of a dashboard status. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
An availability confirmation displayed on a computer should not be called the certified copy of the entire original filing. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
A project manager attaches a portal screenshot to an email while the certified file remains available only through office exchange. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Label the material accurately and preserve its evidential role without inventing a seal, certification or endorsement. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
Handling missing documents, corrections and release
22. Document language and translation
A receiving office may specify requirements for translating a priority document or parts of it into an accepted language. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
It would be misleading to state all international applications require a complete translation at the same stage. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
An office requests a translation of selected supporting passages following a formalities notice. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Preserve the exact requested languages, scope, certification standard and relevant time limit. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
23. Formal deficiency notice
An office notice may identify a missing code, unavailable priority document, data inconsistency or other formal issue. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A correctable formality should not automatically be described as a substantive rejection of the patent application. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
The examiner asks for an amended reference after detecting inconsistent priority data. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Translate who must act, which defect was found, the deadline and the stated consequences. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
24. Request for correction
A correction request changes how an applicant should respond to incomplete or inaccurate priority details. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
A proposal to correct is not proof that the office has already accepted the amendment. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
The applicant discovers a transposed digit in the earlier filing number after submitting the later form. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Retain the previous and new values, amendment history, date and office response. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
25. Applicant and representative
The named applicant and an appointed patent attorney or agent may have distinct roles in sending office requests. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
The person preparing a translation or correspondence is not automatically authorised to make a legal declaration. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
A law firm manages filings on behalf of a company that remains the named applicant. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Translate formal capacity, signer identity and the scope of the appointment as recorded. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
26. Office acknowledgement
An electronic acknowledgement can confirm receipt of a message, file or response without promising a final decision. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A general receipt notice must not become an approval, grant, completed retrieval or valid priority claim. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
A system issues an automated receipt for a DAS-related request while substantive processing continues. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Carry the precise received status, office, case reference and acknowledgement timestamp into the target text. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
27. Confidentiality and access control
DAS is designed for controlled transfer of documents that may not yet be public, including unpublished applications. Short status messages often do the most work in a patent file. A word such as received, pending, available, retrieved or corrected identifies an event rather than a general positive impression. Translate the event, not an optimistic interpretation of the whole case.
Putting the real access code or unpublished filing contents in an open translation sample can compromise confidentiality. A copied sentence can become a dangerous statement when its context is removed. Keep nearby references, jurisdiction, date, application type and form name. Where instructions are conditional, preserve the condition and the consequence instead of turning them into an unconditional order.
An applicant is asked to send a code to a named receiving office but not circulate it to unrelated external recipients. The safest bilingual layout often preserves the source value in one column and the target explanation in another. This makes contradictions visible, prevents accidental replacement of identifiers and helps applicants communicate with offices that may use different procedural terminology.
Preserve secure-sharing instructions and limit disclosure of sensitive application material. Before release, trace every claim back to a document: the filing receipt, certified copy, DAS notification or later office response. A translator may flag a problem and ask for legal review; the translation itself must not pretend to resolve a contested priority claim.
28. Versioned document records
Translations can be revised as filing numbers, office notices and retrieval statuses change during the case. This is an evidence question as much as a vocabulary question. A translation should let another reader identify the same record without relying on the translator’s memory or assumptions. Keep the term consistent in headings, correspondence and attachments, but do not flatten two legally different actions into one everyday word.
An old translation describing a failed retrieval must not be presented as the newest status after a later correction. A smooth translation may still mislead when it changes timing, legal status or who has authority. Re-read negations, modal verbs and qualifications in the source. If two offices use different naming conventions, retain both names with a short explanation rather than replacing one with the other.
The first attempt fails, a corrected application number is submitted, and a later log shows successful retrieval. The example demonstrates how an apparently small language change can interrupt an international workflow. A person using the translated document should know what has happened, what has not happened and the next action required. If that cannot be determined, ask for clarification instead of inventing the answer.
Mark each translation by source version and date, keeping earlier evidence rather than overwriting history. A careful reviewer can test the final sentence by locating its source field, checking its date and tracing its legal or administrative role. Keep a glossary and discrepancy log. Never claim that a filing is valid, a patent is granted or a document is received unless the actual record says so.
29. Office-specific filing procedure
A national or regional office may prescribe forms, accepted languages, portals, deadlines and evidence beyond the DAS mechanism. Each technical or administrative label belongs to a particular step. A source might refer to a filing, certified copy, permission to access, electronic retrieval or office determination. Good language work makes those steps easier to understand without changing their order or their legal effect.
A general online guide cannot override the actual instructions applicable to a particular filing. The temptation is to choose the most familiar English word and move on. Yet a familiar term may suggest an approval, guarantee or entitlement never made by the issuer. Compare the wording with the relevant office guidance and preserve the document’s degree of certainty.
A later office requires the DAS code in a specific form field while another accepts a different workflow. In an international patent workflow, several teams may use the same email thread. They need stable identifiers and clear procedural verbs, not a literary paraphrase. Translate the source evidence so that any receiving team can match it with the correct office file.
Identify the competent office, reproduce the operative instruction and flag any local rule requiring confirmation. Finish with a two-person check where possible: one reviewer verifies the legal or technical record and another verifies clarity in the target language. Record unresolved questions, and do not silently repair a discrepancy in a scanned copy or online portal.
Worked case 1: a DAS code is translated as the filing number
The original letter has two fields: an application number issued by a national office and an access code issued for the DAS workflow. A translation places the code under the heading ‘patent number’. A receiving office cannot reliably match the record. Correct the labels, confirm the source strings and separate the access credential from the official application reference.
An internal quality checklist should be applied to the corrected letter before it is sent again. Verify the sending office, first filing date, application type, applicant identity, target office and exact response deadline. Do not present the corrected translation as proof of accepted priority; it establishes only that the documentary labels now accurately reflect the source.
Worked case 2: registered becomes accepted
A message states that a certified document has been made available in DAS. A machine translation says ‘your patent priority has been accepted’. That sentence goes beyond the source. The accurate message should identify the document-access status and say nothing about final legal recognition. If the later office requires a separate retrieval request, communicate that step clearly without implying completion.
Worked case 3: a generic deadline is copied to the wrong right type
A filing team uses the same bilingual template for patent and trademark documents. It leaves the patent priority period in a trademark letter. The error could distort docketing decisions. The correct process identifies the relevant right category, keeps the earlier filing date and applicable period distinct, and asks the patent or trademark practitioner to validate the deadline under the receiving office’s procedure.
Five passes for a publishable and usable translation
Document identity
Verify every original and subsequent filing number, office name, access code, right type and correspondence reference. Keep leading zeroes, punctuation and letter case if meaningful. A correct noun is not enough when the accompanying identifier points to the wrong file. A second reviewer should reconstruct the event from the translated version alone, then compare it with the source. Where a sentence would cause a reader to file the wrong reference, miss an explicit step, or assume approval without evidence, it must be revised before release.
Date and deadline
Check written date format and distinguish filing, deposit, retrieval, notice and response dates. Do not import a jurisdiction’s deadline from another case. A translated date should be readable without ambiguity about day and month order. A second reviewer should reconstruct the event from the translated version alone, then compare it with the source. Where a sentence would cause a reader to file the wrong reference, miss an explicit step, or assume approval without evidence, it must be revised before release.
Status and legal effect
Read requested, submitted, available, received, retrieved, accepted, refused and corrected as distinct events. A procedural acknowledgement does not normally settle the substantive validity of a priority claim. Avoid adding certainty to tentative office language. A second reviewer should reconstruct the event from the translated version alone, then compare it with the source. Where a sentence would cause a reader to file the wrong reference, miss an explicit step, or assume approval without evidence, it must be revised before release.
Confidentiality and distribution
Keep unpublished documents and access credentials inside authorised channels. Redact real codes from teaching examples and public summaries. Check the intended addressee rather than automatically copying confidential information to every participant in an email chain. A second reviewer should reconstruct the event from the translated version alone, then compare it with the source. Where a sentence would cause a reader to file the wrong reference, miss an explicit step, or assume approval without evidence, it must be revised before release.
Final human validation
Review the target against original PDFs or reliable records, inspect attachment order, note any conflicts, and obtain legal review for disputed formalities. The goal is a faithful, actionable description of a document, not an invented legal conclusion. A second reviewer should reconstruct the event from the translated version alone, then compare it with the source. Where a sentence would cause a reader to file the wrong reference, miss an explicit step, or assume approval without evidence, it must be revised before release.
Frequently asked questions
Does WIPO DAS grant patents?
No. It supports secure exchange of priority documents among participating offices. Patent examination, grant and enforceability depend on separate laws and procedures. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Is a DAS code the same as a patent application number?
No. It is an access credential associated with a priority document. The earlier application and later application each retain their own identifying numbers. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Does a retrieved document mean the priority claim is valid?
No. Retrieval is a document-access event, not a final determination of the legal claim’s validity. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Can the first filing date and later filing date be the same?
They may coincide in some circumstances, but they are conceptually distinct filing events. Translate the dates actually recorded and do not assume identity. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Are all priority periods twelve months?
No. The Paris Convention distinguishes categories of intellectual property. Patent and utility model priority generally uses twelve months, while designs and trademarks generally use six months. Exceptions and receiving-office procedures need expert checking. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Can access codes be included in a published translation example?
Use invented examples. Real access codes can expose non-public filing documents and should be protected according to the case’s access and confidentiality requirements. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
What if the first office has uploaded the document but the later office cannot retrieve it?
Translate the status and error exactly, verify the application reference and code, check office participation and consult the relevant office’s troubleshooting instructions. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Can a translator decide whether an applicant missed a filing deadline?
A translator should flag conflicting dates or deadlines but should not substitute for qualified legal docketing advice or an official decision. Where instructions or jurisdiction-specific requirements are unclear, preserve the issuer’s wording and seek authoritative clarification before relying on a translated operational statement.
Authoritative references
WIPO Digital Access Service: official overview
WIPO Paris Convention: treaty overview
Related eduKate learning routes
The Master Art of Translation remains the canonical owner of broad translation method. The Vocabulary Learning Hub develops accurate understanding of words such as claim, certified, received and available, while How English Works explains the conditions, temporal expressions and administrative language that determine what a sentence actually commits someone to do. This article covers only patent priority-document notices and their translation risks.
A reliable translation of a WIPO DAS notice preserves original application identity, corresponding office, exact dates and codes, evidential status, retrieval step and any outstanding action. It never creates a patent grant or accepted priority claim by changing a verb. The best result is a document whose reader can determine exactly what happened and what remains to be confirmed.