Hello, this is Ryuta Hamamoto from TIMEWELL.
If you work in research promotion or risk management at one of Japan's national research and development agencies (national R&D agencies), the question in front of you right now is probably "How many sets of rules should we have?" The agency has had security export control rules for years. Now it has been asked to write research security rules. Should they be separate? Should they be bolted onto the existing rules? And what has to go round before the president signs? That is where things tend to stall.
My answer: one rulebook with common general provisions, a chapter for export control and a chapter for research security, and the source written down for each article. The information and the people involved overlap almost entirely. The legal strength of the sources and the timing of their revisions do not. And information the agency receives as a research funder goes into its own ledger.
The short version
- There are three sources, and they carry different weight. FEFTA and the compliance standards ordinance are legal obligations. METI's fifth-edition guidance for universities and research institutions explains how to implement them and offers model rules. The Cabinet Office's research security procedures manual is "guidelines to be complied with," and it adds steps when you apply to a Specified Research and Development Program.
- Keep only the outline of the system in the statement of operational procedures (Article 28 of the Act on General Rules for Incorporated Administrative Agencies). Put the substance of both sets of rules into internal rules adopted by the president, and put forms into detailed procedures. That way you avoid changes that need ministerial approval (my suggestion).
- Laid side by side, the definitions, the officer table, the screening record, reporting, training, and records and audit can be shared. Transaction review and risk assessment decisions, pledges and consent or declaration forms, and the bodies you report to are safer kept apart.
- Information received through funding work (Part II, Chapter 2 of the manual) differs from your own researchers' declarations in purpose and in starting date. Keep separate ledgers with separate access.
Two premises first. Being on a list is a regulatory designation; it is not a judgment about the merits of the listed organisation or person. The same goes for the "specified categories" used in Japan's deemed export controls. METI says that falling into a specified category "does not mean the person is regarded as a security concern"1. The procedures manual also says that, when judging whether a counterpart is a trustworthy partner, "there must be no discriminatory treatment on grounds of nationality, race, religion, culture or the like"2. Integrating the rules is about cutting duplicate checks. It is not about sorting researchers by country or origin.
The research security side of the work (the table of add-on steps and the 90-day plan) is covered in the national R&D agency section of How to build a research security system. A gap check of the export control rules themselves is in Reviewing a university's export control rules. This piece deals only with fitting the two into one framework.
Three sources, three different strengths
Start by ranking what each article of your rules rests on. If you merge the rules without doing this, nobody will later be able to say whether breaking a given article breaks the law or just misses a recommendation.
First, FEFTA and the Ministerial Ordinance on Export Compliance Standards (the compliance standards ordinance). Article 55-10(4) of FEFTA says that "exporters, etc. shall conduct exports, etc. in accordance with the export compliance standards." The Minister of Economy, Trade and Industry can give guidance and advice so that exports follow the standards (Article 55-11), can issue a recommendation if a breach continues, and can order compliance if the recommendation is ignored (Article 55-12). Violating that order is punishable by imprisonment of up to six months or a fine of up to 500,000 yen (Article 71, item 11)3. The fifth-edition guidance confirms that exporters, including universities and research institutions, must appoint an officer responsible for classification under the standards (p. 93)4.
Article 1 of the ordinance requires every exporter to appoint a classification officer (item 1(i)) and to brief staff on current law (item 1(ro)). Anyone handling listed goods or technology (specified important goods) must also do everything from appointing a general manager from among those who represent the organisation (item 2(i)) to reporting to the Minister when they have broken, or may have broken, the law (item 2(nu)). Of these, audit (he), training (to), guidance to subsidiaries (chi) and record keeping (ri) are written as "shall endeavour to," so they are duties of effort. Article 2 allows the same person to serve as both classification officer and general manager5.
Second, METI's "Guidance on Sensitive Technology Management for Security Trade Control (for Universities and Research Institutions)," fifth edition (September 2025). It explains how to implement the standards and "strongly recommends" that institutions adopt internal export control rules and manage accordingly (p. 96). The model rules in Chapter IX are written for "XX University / Research Institution." The centralised version (from p. 106, 27 articles) names the "university president / agency president" as chief officer in Article 5.
Watch the titles. The ordinance's "general manager" corresponds to the model rules' "chief officer." The model rules' "export control general manager" (vice president) is the operational lead, and note 107 on page 94 says explicitly not to confuse the two. The guidance also says that where listed technology is handled, a vice president or similar should be the general manager and the president or another person who represents the organisation should be the chief officer (p. 68)4.
Third, the "Procedures Manual for Ensuring Research Security" (December 2025), compiled by the Cabinet Office's expert panel. The manual describes itself as "guidelines to be complied with, not laws," and it separates "necessary" (the minimum measures) from "desirable" (measures not required at present) (Part I, 1-2). It applies to Specified Research and Development Programs, which the ministry in charge designates after consulting the funding agency. For research funded by other competitive grants, or by public money other than competitive funding such as operating grants for national university corporations, it says risk management "in line with this manual" is "desirable" (Part I, 2-2)2.
The detail I find most telling is a footnote. In explaining its framework, the manual says the fifth-edition guidance "should be referred to as appropriate" for preventing leaks of critical technology (Part I, 2-1, note 5). The two documents were written to be used together.
| Source | Nature | Applies to | Wording | If you do not comply |
|---|---|---|---|---|
| FEFTA and the compliance standards ordinance | Act and ministerial ordinance | Anyone exporting as a business. The fifth edition says this includes universities and research institutions (p. 93) | "Shall." Audit, training, guidance to subsidiaries and record keeping are duties of effort | Guidance and advice, recommendation, order. Violating an order is a criminal offence (FEFTA Art. 71(xi)) |
| Fifth-edition guidance | METI's explanation, model rules and model forms | Universities and research institutions | Distinguishes "necessary" from "recommended" | Pages 88 to 89 list the standards as items 1 to 12 and say they "must be complied with" |
| Research security procedures manual | Guidelines to be complied with | Government, funding agencies, research institutions and researchers involved in Specified Research and Development Programs | "Necessary" and "desirable" | For deliberate false or concealed declarations, measures such as restrictions on applying "could be" taken after the funding guidelines are amended (Part I, 2-6) |
To carry this difference into the rules, I suggest adding the source and its strength at the end of each article: "(FEFTA Art. 55-10(4); compliance standards ordinance Art. 1(ii)(ni))," "(Manual II 3-3(1), necessary)," "(Manual II 3-1(3), desirable)," "(our own practice)." Articles of different strength can then sit in the same rulebook without anyone mistaking one for another. It also tells the auditor (Article 19(4) of the Act on General Rules says the auditor audits the agency's operations) and internal audit exactly what to check, article by article6.
Splitting content between the statement of operational procedures and internal rules
Under the Act on General Rules, a national R&D agency is an incorporated administrative agency whose main business is research and development (Article 2(3)). The head of the agency represents it and presides over its business (Article 19(1)). The provision that matters most when deciding where rules live is Article 28, on the statement of operational procedures. Paragraph 1 says the agency must prepare the statement when it starts operating and obtain the competent minister's approval, and the same applies to any change. Paragraph 2 requires it to cover "matters concerning the development of systems to ensure that officers' (other than auditors') performance of duties complies with this Act, the individual Act or other laws and regulations, and other systems to ensure the proper conduct of the agency's operations." Under paragraph 3, the approved statement is published without delay6.
So the statement needs ministerial approval every time it changes, and it is public. Write research security procedures into it in detail and every revision of the manual becomes an approval exercise. The manual calls itself something "to be reviewed as needed" (Part I, 1-2(3)), and it has the Cabinet Office revisit the manual and checklists as needed (Part II, 1-5)2. The detail belongs at a level the agency can change itself.
Note too that the manual does not say which rules the research security measures should go into. The only place the word "rules" (kitei) appears in the manual is note 33, on information security. I read that as leaving the choice to each agency. Note 33 does, however, say that national government bodies, incorporated administrative agencies and designated corporations (the "agencies") need to check, against the information security policies and operating rules each has set based on the Common Standards for government information security, that the information on important technologies is secure; for other research institutions it says this is something to consider (p. 21).2 National R&D agencies are incorporated administrative agencies, so for them the check is necessary.
Here is the three-layer split I recommend.
| Layer | Who decides, and how | What goes there (my suggestion) | Source |
|---|---|---|---|
| Statement of operational procedures | Prepared by the agency and approved by the competent minister; published without delay once approved (Act on General Rules, Art. 28(1) and (3)) | A statement that the agency maintains systems for legal compliance and proper operations. No detail on export control or research security | Act on General Rules, Art. 28(2) |
| Rules (adopted by the president) | Under the agency's own rule-making procedure. In the model rules, the chief officer (president) adopts and amends the rules (Art. 5(2)) | Common general provisions, an export control chapter, a research security chapter, common procedures | Fifth-edition model rules; Manual Part II, Chapter 3 |
| Detailed procedures and forms | In the model rules, the export control general manager (a vice president, in the example) adopts and amends detailed operating procedures (Art. 6(2)); anything not in the rules goes into detailed procedures (Art. 27) | Pre-check sheet, review form, pledge, self-declaration, consent and declaration forms, due diligence ledger, contact list | Fifth-edition model rules |
The first job is to open your agency's published statement of operational procedures and read its internal control provisions. If the current wording already covers a research security system, you can leave the statement alone and simply adopt rules. If it does not, you need approval for a change, so build time for talks with the ministry into the schedule. Which case applies depends on the agency. I have not checked any individual agency's statement or the items each ministry's ordinance requires (the "other matters specified by ordinance of the competent ministry" in Article 28(2)).
You can also check from the export control side whether one rulebook is acceptable. In setting out who may apply for a bulk license, METI's Bulk License Handling Guidelines define internal export control rules as including "those made up of several sets of rules, and those that also cover matters other than export control" (Part I, 2(2)(ii))7. On that definition, putting a research security chapter in the same rulebook is not ruled out (METI still decides on acceptance of a notification and on bulk license applications).
I would leave the research integrity rules (conflicts of interest and of commitment) as they are. The manual defines research integrity as covering all research activity and research security as covering research that has been judged to need protection (Reference material (1)), and it treats collecting declarations based on the research integrity checklist as "necessary" (Part II, 3-1(1))2. Rules that apply to everyone and rules for a narrow set of procedures have different scopes. Have the research security chapter take research integrity declarations as its input rather than repeating them.
Replace siloed classification work with AI.
METI's FY2024 data shows 52% of foreign exchange law violations stem from classification errors. Download the TRAFEED product catalog covering features and rollout.
Article map (fifth-edition model rules, our 13-article draft, Annex 2)
The map below lists, from the left, the articles of the fifth edition's centralised model rules, our 13-article draft, and the questions in Annex 2 of the manual (the checklist for the lead institution), with our suggested treatment on the right. For the model rules and Annex 2 I list only what actually appears in the original; where nothing does, the cell says "none." The 13-article draft is copied from our Excel resource and our earlier article, and the manual references attached to it are our own mapping. In the decentralised model rules (from p. 111, 28 articles), Article 8 adds a department export control officer, so every article from 8 onward moves up by one4.
| Function | Fifth-edition model rules (centralised) | Our 13-article draft | Annex 2 (lead institution) | How to combine (my suggestion) |
|---|---|---|---|---|
| Purpose and scope | Art. 1 Purpose, Art. 3 Scope, Art. 4 Basic policy | Art. 1 Purpose (I 1-1) | None | State both purposes in the common general provisions. Set scope chapter by chapter (export control covers all technology transfers and exports; research security covers Specified R&D Programs and research handled in line with them) |
| Definitions | Art. 2 (19 terms, including technology transfer, transaction review, specified-category persons, and staff) | Art. 2 Definitions (Specified R&D Program, persons involved in running it, PI, Co-PI, participating researchers, due diligence, lists) | "0. Definitions" | One definitions article. The exception is "lists": the manual means METI's End User List and the US Consolidated Screening List, while Article 12 of the model rules names the End User List. Same word, different scope, so define it per chapter |
| Officers | Art. 5 Chief officer (president), Art. 6 Export control general manager (vice president), Art. 7 Export control manager | Art. 3 Responsible officer and department (II 3-1(2)) | None | One officer table, with export control roles and research security roles in separate columns. In the manual the word "responsible person" appears only in the definition of PI; it sets no institutional title |
| Committee | Art. 8 (deliberates on amendments, classification, exceptions, transaction review, training and audit) | None | None | Add research security to one committee's remit and review its name and members |
| Declarations and pooling information | Art. 17 Confirming specified-category persons (pledge on hiring, resubmitted when circumstances change) | Art. 4 Declaring and centrally managing research activity information (II 3-1(1)(2)) | None | One place for the information, with access split by purpose |
| Self-declaration, consent, declaration | Art. 17 (pledge) | Art. 6 Self-declaration, consent and declaration forms (II 3-3, reference) | 2. Handling of personal information | Keep the documents separate. The wording of the consent's purpose is discussed below |
| Persons involved in running the program | None | Art. 5 Designation and confidentiality (II 3-2 ① ②) | None | Research security chapter only |
| Checking the counterpart | Art. 9 Pre-check (concerns, non-resident or specified-category status, exceptions), Art. 11 End-use check, Art. 12 End-user check (including the End User List) | Art. 7 Due diligence and risk assessment (II 3-3(1)(2)) | 1(1) items 9 to 12; 1(3) item 2 | One screening record (list and version, date, who checked), referenced by both the pre-check and due diligence |
| Decisions | Art. 10 Classification, Art. 13 Transaction review (first review by the manager, second by the general manager), Art. 14 License application | Art. 7 (risk assessment), Art. 9 Risk mitigation (II 3-4) | 1(1); 3. Risk mitigation | Keep decision-makers and records separate. Transaction review decides whether a license is needed and whether to proceed; risk assessment decides the mitigation |
| Contracts | None (no contract article in the model rules) | Art. 8 Checking joint research contracts and agreements (II 3-3(1)(v), (2)(iii)) | 1(2) items 1 to 4 | Put the manual's four items and the export control checks side by side in the contract review form |
| Managing technology and information | Art. 15 Technology transfer control, Art. 16 Shipment control | Art. 9 (access control and the like) | 3. Risk mitigation | Keep access-control procedures in the information security rules and refer to them. A national R&D agency is one of the "agencies" in note 33 of the manual, so checking against information security policies and operating rules based on the Common Standards is described as "necessary" (for universities and other non-agencies, it is something to "consider") |
| After research starts | None | Art. 10 Follow-up after research starts (II 3-5) | 4(1) to (3) | Research security chapter only. When adding a participant, do the specified-category check and due diligence together |
| Reporting breaches and leaks | Art. 24 Reporting (general manager to chief officer; to the authorities without delay) | Art. 11 Emergency contact and response (II 3-2 ③, I 2-6) | None | One reporting entry point, two reporting destinations |
| Training | Art. 21 Guidance, Art. 22 Education | Art. 12 Training (II 3-1(4)) | None | One training plan, with the strength of each item noted |
| Records, audit, review | Art. 18 Records (at least seven years), Art. 19 Audit, Art. 20 Survey | Art. 13 Record keeping and review of rules and checklists (review: II 3-1(4); retention is our suggestion) | None | Add research security to the audit scope. The manual sets no retention period, so each agency decides |
| Other | Art. 23 Guidance to subsidiaries, Art. 25 Discipline, Art. 26 Office in charge, Art. 27 Miscellaneous | None | None | Subsidiary article stays in the export control chapter; discipline, office in charge and miscellaneous become common |
Once you build the map, the overlaps cluster in four places.
The first is definitions. Specified categories appear on both sides. Article 2(16) of the model rules defines specified-category persons by reference to items ① to ③ of section 1(3)(sa) of METI's services circular, and item 12 of the manual's due diligence points to that same circular and to METI's deemed export Q&A (Part II, 2-1, note 25)2. One definition is enough. "Lists" go the other way. The manual means two lists, METI's End User List and the US Consolidated Screening List, while Article 12 of the model rules names the End User List. Make that a shared definition and the export control pre-check starts to read as though screening against US lists were mandatory.
The second is pooling information. The fifth edition recommends gathering information on specified-category persons in the export control unit (p. 51)4. The manual calls a system in which relevant departments work together to collect risk management information and manage it centrally "desirable" (Part II, 3-1(2))2. The Cabinet Office Q&A says the unit handling leak prevention will mainly be the departments already doing security export control or research integrity (Part II, No. 9)8. Making the export control unit the place where information collects fits all three documents.
The scopes still differ, though. The fifth edition's pledge comes from staff employed by the institution (model rules Art. 2(17) and Art. 17). The manual's due diligence covers participating researchers including students, and Co-PIs at other institutions (Part II, 2-4 and 3-3(1)(i))2. Reusing the export control pledge on its own leaves students and Co-PIs out.
The third is the purpose stated in the consent form. The manual requires the consent form to include that "the researcher declares personal information to the research institution for the purpose of risk management to ensure research security, and the research institution uses it only for that purpose" (Part II, 3-3, reference)2. Because the purpose is limited, I would not reuse declarations gathered for research security as-is for specified-category checks. If you want them for both, either add export control to the stated purpose or take the pledge separately. Settle which with your agency's personal information staff. I have not checked which provisions of Japan's personal information protection law apply to national R&D agencies. For a starting draft, Research security self-declaration, consent and declaration forms (Word, in Japanese) sets out the 13 items in the manual's wording and the required content of the consent and declaration. Deciding on that form whether to add export control to the purpose speeds things up.
The fourth is reporting. When there is, or may be, a breach of FEFTA, you report to the Minister of Economy, Trade and Industry (compliance standards ordinance Art. 1(ii)(nu))5. When critical technology has leaked, or may have leaked, the Q&A says you must report as quickly as possible to the parties concerned, including the funding agency, whether or not the manual applies (Part I, No. 7)8. With two destinations, have one entry point for reports and set out both onward reports in the same article so neither is missed.
The contract row has no model-rule article behind it, so a form is the quickest fix. Joint and commissioned research checklist and clause examples (Excel, in Japanese) puts the manual's four items (scope of cooperation, access to research data, intellectual property, confidentiality) next to the classification and counterpart checks, with ten pre-contract checks, a record of counterpart screening and seven example clauses.
To apply the map to your own rules, use the "draft rule headings" sheet in the 90-day research security plan for national R&D agencies (Excel, in Japanese). For each of the 13 articles you can record where it sits (statement of operational procedures, internal rules adopted by the president, or a chapter added to existing rules) and its article number in your rules. A combined rulebook could be laid out like this (my draft).
| Chapter | Articles (my draft) |
|---|---|
| Chapter 1 General provisions | Purpose, definitions (shared terms and chapter-specific terms), scope, officer table, committee, office in charge |
| Chapter 2 Security export control | Pre-check, classification, end-use check, end-user check, transaction review, license application, technology transfer control, shipment control, confirming specified-category persons, guidance to subsidiaries |
| Chapter 3 Research security | Declarations and information management, designation and confidentiality of persons involved, self-declaration, consent and declaration, due diligence and risk assessment, checking contracts and agreements, risk mitigation, follow-up after research starts, a section on funding work (only where it applies) |
| Chapter 4 Common procedures | Reporting, training, record keeping, audit, review of rules and checklists, discipline |
The path to the president's approval
The manual does not describe an approval process. What the originals do support are five points: who adopts the rules (the president), who drafts them (the model rules' export control general manager), where they are discussed (the model rules' committee), how the statement of operational procedures is changed, and the conditions for reporting to METI. The table below is how I connect them.
| Step | What to do | Who (example) | Source in the original |
|---|---|---|---|
| 1 Draft | Use the map to place each article and prepare a comparison of old and new text | Export control staff and research promotion staff | Model rules Art. 6(2) (the export control general manager drafts amendments) |
| 2 Consultation | Circulate to legal, HR, information security, industry collaboration and personal information staff | Each department | My suggestion (to check the consent purpose, contract forms and the link to information security rules) |
| 3 Committee | Deliberate on the draft | Export control committee (rename and adjust membership if research security is added) | Model rules Art. 8(2)(i) (matters concerning drafting amendments) |
| 4 Check the statement | Decide whether the current statement covers it; if not, obtain approval for a change | Legal, corporate planning | Act on General Rules, Art. 28(1) and (2) |
| 5 Check METI procedures | If you hold bulk licenses or have notified internal rules, confirm whether a report is needed | Export control staff | Bulk License Handling Guidelines IX(2) and license conditions (p. 55 and elsewhere) |
| 6 Approval | The president adopts or amends the rules | President | Act on General Rules, Art. 19(1); model rules Art. 5(2) |
| 7 Detailed procedures and forms | Adopt detailed procedures and forms | Export control general manager (model rules' title) | Model rules Art. 6(2) and Art. 27 |
| 8 Announce and bring into force | The president communicates to all staff; forms are posted | Office in charge | Fifth edition p. 97 (it is effective for the head of the organisation to take the lead in communicating) |
Step 5 is the one export control teams most often forget. The Bulk License Handling Guidelines attach to the Special General Bulk License and others the condition: "When a change arises in the part of the internal export control rules relating to the FEFTA compliance items, report to the Minister of Economy, Trade and Industry within one month" (p. 55 and elsewhere). They also say that when a bulk license holder changes its internal export control rules, METI's Security Export Inspection Office may ask for the checklist filled in with the latest state of its efforts (IX(2))7. Adding a research security chapter alone may not touch the FEFTA compliance items. I have not confirmed whether a restructuring that renumbers articles counts as such a change. Agencies with bulk licenses should check with the Security Export Inspection Office before the rules take effect.
If step 4 shows no change to the statement is needed, everything from drafting to approval stays inside the agency. My rough estimate: two weeks to draft, two weeks for consultation, one committee meeting and a week for approval, so about two months. If the statement must change, add talks with the ministry. Writing the approval document along the lines below helps each consulted department find the points it cares about (my example).
Example (outline of the approval document) Subject: Partial amendment of the security export control rules (new chapter on research security)
- Purpose: To set out the measures based on the Cabinet Office research security procedures manual (December 2025) as one rulebook together with the existing security export control rules.
- Basis: FEFTA Art. 55-10(4) and compliance standards ordinance Art. 1; Manual Part II, Chapter 3 (and Chapter 2 if the agency funds research); the provision of the statement of operational procedures on systems ensuring proper operations.
- Main points: Common general provisions (definitions, officers, committee); new research security chapter; a single reporting route; separation of information from funding work.
- Change to the statement of operational procedures: Not required (reason: covered by the provision on developing systems in Article X).
- Report to METI: Whether the agency holds bulk licenses, and the outcome of checking with the Security Export Inspection Office.
- Date of effect and transitional measures: As in the supplementary provisions. Attachments: Comparison of old and new text, article map, record of consultation.
The supplementary provisions should give the date of effect and say what happens to matters already under way. The model rules' supplementary provision is a single sentence, "These rules come into force on [date]"4, so add transitional measures when you amend.
Example (supplementary provisions of the amended rules; my example, to be checked by your legal team)
- These rules come into force on [date].
- For research projects that have already applied to a Specified Research and Development Program when these rules come into force, the procedures under Chapter 3 shall be carried out by the deadline the funding agency sets in its call for proposals.
- Pledges submitted under the rules before amendment are deemed to be pledges under Article X of these rules.
Why the funding-agency ledger stays separate
Some national R&D agencies do not just receive research money; they also hand it out. The Cabinet Office's FY2025 follow-up survey counted 21 research funding agencies and similar bodies, five of them national R&D agencies with competitive funding programs in FY20259. The Cabinet Office lists the institutions selected for its support program for building funding agencies' risk management systems next to its notice on FY2026 registration, and five of the seven are national R&D agencies (Japan Agency for Medical Research and Development, Japan Science and Technology Agency, the Bio-oriented Technology Research Advancement Institution of the National Agriculture and Food Research Organization, National Institute of Information and Communications Technology, and Japan Aerospace Exploration Agency)10.
The manual puts funding agencies' measures in Part II, Chapter 2 and research institutions' measures in Chapter 3. A funding agency must set up an operating system for each program before the call opens, and one of the points to keep in mind is "formulating a policy for managing information, research data and the like obtained from the acceptance of applications onward" (Part II, 2-1(1) ③). When it commissions people who play an important role in running the program (such as externally recruited program directors and program officers), it carries out 13-item due diligence on the candidates (Part II, 2-1(2)). After applications arrive, it checks the financial position and list status of the lead institution and partner institutions (other than Japanese universities, national R&D agencies and similar), receives the institutions' risk management results, and decides with the ministry in charge whether the mitigation is enough (Part II, 2-2)2. The Q&A says "developing the system" for a funding agency means a system able to carry out what the manual describes, such as clarifying lines of responsibility within the agency (Part II, No. 2)8.
| Point | As a research institution (Part II, Chapter 3) | As a funding agency (Part II, Chapter 2) |
|---|---|---|
| Who is checked | Your own PIs and participating researchers (including students), and Co-PIs | Candidates who will play an important role in running the program; applying lead and partner institutions (other than Japanese universities, national R&D agencies and similar) |
| Start of the three-year window | Three years including the fiscal year of the application date | Three years including the fiscal year of the planned appointment date (in the Q&A example, an appointment on 1 June 2026 covers FY2024 to FY2026; Part II, No. 4) |
| Where information comes from | Researchers' self-declarations, with consent and declaration forms | Questionnaire answers from the lead institution; candidates' declarations |
| Where information goes | The funding agency and relevant government bodies (the third parties in the consent; also the lead institution when you collect as a partner institution) | The ministry in charge (checking due diligence results; judging mitigation) |
| What gets decided | The mitigation to put in place (in consultation with the funding agency) | Whether the mitigation is enough; if not, a request for more |
That table gives three reasons to keep the ledgers apart.
The first is the scope of consent. The consent form for declarations you collect as a research institution limits use to research security risk management and names the funding agency and relevant government bodies as third parties (Part II, 3-3, reference, and note 30). Information about other institutions' researchers that you receive as a funder is handled after the call for proposals names the bodies that will receive and use it (Part II, 2-1(3) ⑤)2. Put information that arrived by different routes, under different consents, in the same table and you will have to ask, row by row, whether this information may be used for this purpose.
The second is that the starting dates and the reasons for keeping records differ. The three-year window runs from the application date in one case and the planned appointment date in the other. You keep records as a researcher's employer to explain your own diligence, and as a funder to document a review.
The third is who can see what. In my view, research staff at the same agency being able to view the declarations of other institutions' applicants received through funding work invites suspicion of use beyond the stated purpose. The manual does not say this directly. Still, since Part II, 2-1(1) ③ asks the funding side for its own information management policy, keeping its records in a separate place with separate access makes that policy much easier to explain.
Once you decide to separate them, choose whether to set up a "funding work" section inside the research security chapter or to place it in your rules on funding operations. Training, version control of the lists used for screening (which dated version you checked against), and a store of anonymised cases can be shared without the purposes colliding. Funding agencies "must" collect and publish cases (Part II, 2-4(2)), and research institutions should provide them on request, which the manual calls "desirable" (Part II, 3-5)2. I would keep sharing to that range.
The research institution's ledger is least likely to have gaps if you build it from the Annex 2 self-check. Research security self-check and due diligence record kit (Excel, in Japanese) sets out the questions of all three Annex 2 checklists in the original wording and sends any row marked "partly" or "cannot" to the planning sheet. It also contains a 13-item due diligence ledger and a draft questionnaire sheet that works out the three fiscal years from the application date.
Wrap-up: what to do in the first 30 days
Half the work of merging the rules is done in the checks before you write a single article. In the first 30 days:
- Open your agency's published statement of operational procedures and check whether its internal control provisions already cover a research security system.
- List the articles of your current security export control rules in the left-hand column of the map above and mark where they overlap with the 13-article draft.
- Check whether you hold bulk licenses or have notified internal export control rules to METI, and if so, consult the Security Export Inspection Office before amending.
- Check whether you do funding work, and if so, decide first where the funding ledger lives and who can see it.
With that done, items 1 to 5 of the approval document are filled in. The point of one rulebook is not fewer pages. It is to stop asking the same researcher the same question twice, without ever confusing a legal obligation with a desirable practice under a guideline. Noting the source at the end of each article is, I think, the cheapest way to get there.
What I have not confirmed
As of 22 November 2026, when this piece was written, I had not confirmed the following:
- What individual national R&D agencies' statements of operational procedures say, and the items each ministry's ordinance requires in them
- The "latest changes (November and December)" document on the fifth-edition guidance page, and the Word versions of the model rules and forms (not obtained because METI's site refused access)
- The FEFTA compliance items in Annex 1 of the 2005 circular "On Notification of Internal Export Control Rules," and METI's current guidance on notifying and changing rules
- Whether restructuring chapters or renumbering articles counts as "a change in the part relating to the FEFTA compliance items" under the bulk license conditions
- Which provisions of Japan's personal information protection law apply to national R&D agencies, and whether the consent wording discussed above is appropriate
The rule wording and supplementary provisions here are my examples. Have them checked by your legal team and, where needed, outside specialists before use. The manual is revised as needed, and I will update this article map when it is.
Further reading
- How to build a research security system: the add-on table for national R&D agencies, the 90-day schedule, the 13 draft headings and the five-step emergency contact flow
- Reviewing a university's export control rules: a gap table against the fifth-edition model rules, and how the rules are adopted
- Ten checks before a joint or commissioned research contract with an overseas institution: clause examples that put the four contract items and the export control checks in one place
- Research security due diligence in practice: how to gather information for the 13 items
- Filling in the research security questionnaire: Annex 3 and the Cabinet Office Q&A answers
- A pre-application self-check with the research security checklist: the Annex 2 questions used in the map's right-hand column, one at a time
- Japan's export compliance standards explained: the compliance standards ordinance item by item
If you are looking at a system that keeps due diligence and list-screening records in one ledger, you can contact us about TRAFEED here.
Footnotes
-
METI Trade Control Department, Security Export Control Policy Division, "Clarifying the Operation of Deemed Export Controls" (in Japanese). Printed page 3: specified categories "simply group, by type, cases that need to be confirmed in individual review; falling into a specified category does not mean the person is regarded as a security concern." Checked against a copy of the original (obtained 21 November 2026, re-checked 22 November 2026). https://www.meti.go.jp/policy/anpo/law_document/minashi/meikakukanitsuite2.pdf ↩
-
Expert Panel on Ensuring Research Security and Research Integrity, "Procedures Manual for Ensuring Research Security," December 2025 (Cabinet Office, in Japanese). Part I 1-1(2) (no discriminatory treatment, p. 3), I 1-2 (status and nature, p. 4), I 2-1 and note 5 (p. 5), I 2-2 (p. 6), I 2-4 (p. 8), I 2-6 (p. 10), II 1-5 (p. 12), Part II Chapter 2 (2-1 to 2-4 and note 25, pp. 13 to 16), Part II Chapter 3 (3-1 to 3-5 and notes 30 and 33, pp. 17 to 21), Reference material (1) definitions (p. 23), Annex 2 checklist for lead institutions (pp. 29 to 31). Checked against a copy of the original on 22 November 2026. https://www8.cao.go.jp/cstp/kokusaiteki/integrity/yushikisha/guidelines_v1.pdf ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12
-
e-Gov, "Foreign Exchange and Foreign Trade Act" (Act No. 228 of 1949), Article 55-10(4), Article 55-11, Article 55-12 and Article 71, item 11 (in Japanese). Version in force from 12 August 2026, retrieved through the e-Gov Laws API (v2) on 22 November 2026. https://laws.e-gov.go.jp/law/324AC0000000228 ↩
-
METI Trade Control Department, "Guidance on Sensitive Technology Management for Security Trade Control (for Universities and Research Institutions)," fifth edition, September 2025, 150 pages (in Japanese). Page numbers are the printed numbers: p. 51 (pooling information on specified-category persons), p. 68 (who serves as general manager and chief officer), pp. 88 to 89 (the standards), p. 93 and note 105 (appointing the classification officer; organisational decisions), p. 94 and note 107 (general manager versus the model rules' titles), p. 96 (recommendation to adopt internal rules; example items), p. 97 (communication by senior leaders), p. 105 (Chapter IX, model rules and forms), pp. 106 to 110 (centralised model rules, Articles 1 to 27 and supplementary provision), pp. 111 to 112 (decentralised model rules, Article 8). Note 107 refers to the model rules as "see p. 97," but the model rules start on p. 106 in Chapter IX. Checked against a copy of the original (obtained 20 November 2026, re-checked 22 November 2026). https://www.meti.go.jp/policy/anpo/daigaku/guidance5.pdf ↩ ↩2 ↩3 ↩4 ↩5
-
e-Gov, "Ministerial Ordinance Prescribing the Export Compliance Standards" (METI Ordinance No. 60 of 2009), Articles 1 and 2 (in Japanese). Version in force from 9 October 2025, retrieved through the e-Gov Laws API (v2) on 22 November 2026. https://laws.e-gov.go.jp/law/421M60000400060 ↩ ↩2
-
e-Gov, "Act on General Rules for Incorporated Administrative Agencies" (Act No. 103 of 1999), Article 2(3), Article 19(1) and (4), Article 28(1) to (3) (in Japanese). Version in force from 1 June 2025, retrieved through the e-Gov Laws API (v2) on 22 November 2026. https://laws.e-gov.go.jp/law/411AC0000000103 ↩ ↩2
-
METI, "Bulk License Handling Guidelines" (last amended by Export Notice 2025 No. 27, published 14 November 2025, in force 14 February 2026; in Japanese). Part I 2(2)(ii) (definition of internal export control rules, p. 1), IX(1)(2) (where to submit documents; changes to internal export control rules, p. 44), conditions of the Special General Bulk License for exports and transactions (program use) and others (p. 55 and elsewhere). Checked against a copy of the original (obtained 20 November 2026, re-checked 22 November 2026). https://www.meti.go.jp/policy/anpo/law_document/tutatu/tutatu24fy/houkatu_toriatukaiyouryou.pdf ↩ ↩2
-
Cabinet Office, "Q&A on the Procedures Manual for Ensuring Research Security," last updated 26 August 2026 (in Japanese). Part I No. 7 (reporting a leak), Part II No. 2 (funding agencies' system), Part II No. 4 (counting the three years), Part II No. 9 (which unit handles leak prevention). Checked against a copy of the original on 22 November 2026. https://www8.cao.go.jp/cstp/kokusaiteki/integrity/security_qa_v1.pdf ↩ ↩2 ↩3
-
Cabinet Office, "Summary of the FY2025 Research Integrity Follow-up Survey," December 2025 (in Japanese). Survey population: 21 research funding agencies and similar bodies, including five national R&D agencies with competitive funding programs in FY2025. Checked against a copy of the original on 22 November 2026. https://www8.cao.go.jp/cstp/kokusaiteki/integrity/ri_follow-up_fy2025/ri_fu_fy2025_sum.pdf ↩
-
Cabinet Office, "List of institutions selected for the support program for building funding agencies' risk management systems for research security" (seven institutions; in Japanese). https://www8.cao.go.jp/cstp/kokusaiteki/integrity/r8_supportdecision.pdf . The list itself gives no fiscal year; the Cabinet Office research security page places it next to the program's notice on FY2026 registration. Both checked against copies of the originals on 22 November 2026. ↩






