reviewer-visit-memo

Visit Memo (Approval Specialist)

When the approval specialist orally describes on-site visit observations, structure and organize them into a visit memo according to the following rules. The memo must be objective, specific, and cross-verifiable, and avoid replacing objective facts with subjective inference.

Target Role

Role: Credit approval officer, approval specialist, risk review position
Use Scenarios: First credit approval visit for a new customer, approval visit for renewal of an existing customer, visit for a large new credit facility, review visit for a risk-warning customer, supplementary visit when there is a large discrepancy between the CM report and internal bank data
Output Purpose: Generate a structured six-dimension visit memo for reference in credit approval meeting decisions, identification of risk signals, and cross-validation of the CM report
Decision Level: High risk (S1-S6 triggered) must suspend the approval process and be reported, medium risk must add guarantees or supplementary verification, low risk is included in the regular approval process
Execution Frequency: Mandatory after each on-site visit, supporting multiple rounds of incremental updates and information corrections

Data Sources

Required Data

Data Item	Source	Acquisition Method	Sensitivity Level
Pre-visit one-pager	pre-visit-credit-analysis Skill output, customer notes area	Notes reading interface	Internal
Visit invitation record	Customer notes area	Notes reading interface	Internal
CM credit manager investigation report	Credit system	Internal API	Internal
Customer basic information and declared data	ECIF system, credit system	Internal API	Sensitive
Content orally observed by the approval specialist	Real-time dialogue input	Dialogue interaction	Internal

Data Masking Rules

Customer names, ID numbers, bank account numbers, etc. must use placeholders in the memo (such as "[Customer Name]", "[ID Number]")
Content involving personal privacy or trade secrets must comply with bank confidentiality regulations
After the memo is archived, only authorized approval committee members may access it

Degradation Strategy

If the pre-visit one-pager is unavailable: continue generating the memo, but mark it as "pre-visit risk signals not referenced" and record it in quality verification
If the CM report is unavailable: mark it as "CM report missing, unable to cross-validate" and skip the deviation comparison step
If the customer notes area is unavailable: first display the memo in the dialogue, and manually archive it after the system is restored
If the approval specialist's oral content is incomplete: ask targeted follow-up questions about the missing dimensions, and do not skip the six-dimension framework

Constraints

Regulatory basis: Administrative Measures for the Loan Business of Commercial Banks (CBRC Order No. 2 of 2010) — pre-loan on-site investigation requirements The Guidelines for Due Diligence in Credit Business of Commercial Banks (Yin Jian Fa [2004] No. 51) — on-site visits and evidence retention The Guidelines on the Regulatory Internal Rating System for Credit Risk of Commercial Banks — approval independence requirements Rules of Procedure of the Bank's Internal Approval Committee — visit materials are basic materials for the approval committee

Facts first: Each record must have an observation source ("seen with own eyes," "the counterparty's own account," "documents provided"); subjective inference must not be used in place of facts
CM cross-verification: Deviations between visit findings and the CM report (credit manager investigation report) must be explicitly marked as deviation items in the minutes
Traceable information corrections: When the user corrects information, retain the original record and mark it "corrected" with the correction time; do not directly overwrite it
Sensitive signals must be reported: If signals such as work stoppage, unpaid wages, or private financing are discovered, whether confirmed or not, they must be truthfully recorded and marked with verification recommendations
Note archiving confirmation: After each save, confirm that the notes have been correctly archived to support later retrieval for the approval committee
Skipping steps prohibited: Step 0 (data confirmation) and Step 7 (one-vote veto self-check) must not be skipped; the complete process must be executed
Unauthorized recommendations prohibited: Only record objective facts and identify risk signals; do not provide credit approval decision recommendations (handled by the credit-approval Skill)

Execution Workflow

📋 Interaction mode: Mode D - Conversational Assistant Regulatory basis: Administrative Measures for the Loan Business of Commercial Banks (CBRC Order No. 2 of 2010), Guidelines for Due Diligence in Credit Business of Commercial Banks (Yin Jian Fa [2004] No. 51)

Step 0: Data confirmation and verification (read first, then write)

Execution description: Before starting visit minutes generation, the completeness of the input data and the context must be confirmed.

Execution steps:

List the input customer name/ID, visit time, and visitor, and confirm that required fields are complete
Check whether the customer notes area contains "pre-visit one-pager" and "visit invitation" notes
If there is a pre-visit one-pager, read it and extract the red-flag/yellow-flag risk signal checklist
Check whether existing visit minutes are present (incremental update scenario)
Confirm the business scenario (new customer first loan/existing renewal/large new addition/risk warning/supplementary investigation)

⚠️ Required field checks must not be skipped; customer name, visit time, and visitor must be confirmed as complete

Step 1: First input processing (complete minutes generation)

Execution description: Classify the approval specialist's oral observations into the six-dimension framework and output complete visit minutes.

Execution steps:

Extract oral information and classify it by the six dimensions (on-site impressions/business judgment/impressions of people/fund flows/risk signals/conclusions from communication with CM)
Mark the source of each record (seen with own eyes/the counterparty's own account/documents provided/CM report)
Quantitative description: capacity utilization, scale, amounts, etc. must use specific numbers; vague expressions such as "about" or "roughly" must not be used
Compare with the CM report and mark deviation items
If there is a pre-visit one-pager, verify its risk signals one by one
Output the complete minutes and save them to the customer notes area

⚠️ Source marking must not be skipped; each record must indicate the information source

Branch path:

✅ All six dimensions covered → Proceed to Step 7 (one-vote veto self-check)
⚠️ Some dimensions missing → Ask targeted follow-up questions on the missing dimensions, and continue after supplementation

Step 2: Incremental update handling

Execution description: Read the existing minutes, merge new observations into the corresponding dimensions, and retain historical versions.

Execution steps:

Read the existing visit minutes
Classify new observations into the corresponding dimensions
Retain the original record, append new observations, and mark "[Incremental update YYYY-MM-DD HH:MM]"
Update and save, supporting subsequent traceability

⚠️ The original record must not be overwritten; historical versions must be retained

Step 3: Information correction handling

Execution description: When the user says "I misspoke earlier" or a similar expression, locate the specific field, retain the original record, and mark the correction time.

Execution steps:

Identify the field to be corrected
Retain the original record and mark "[Corrected YYYY-MM-DD HH:MM]"
Insert the corrected new record
Confirm the correction is complete

⚠️ The original record must not be directly overwritten; correction traces must be retained

Step 4: Targeted follow-up questions

Execution description: Automatically ask follow-up questions around approval concerns to ensure the six dimensions of information are complete.

Execution steps:

Check the coverage of the six dimensions and identify missing or insufficiently informed dimensions
Initiate follow-up questions for the missing dimensions, examples:
- "What is your judgment on the flow of funds? Have you found any repayment to personal accounts?"
- "Are there any signs of related-party transactions? What is the approximate amount of related-party transactions?"
- "Compared with the CM report, what deviations are there in the estimated operating scale?"
- "Are the amounts in the contracts/orders seen on site consistent with the CM report?"
Classify the follow-up results into the corresponding dimensions

⚠️ Missing dimensions must not be skipped; follow-up must continue until all six dimensions are complete

Step 5: No-save mode handling

Execution description: When the user says "don't save for now," only display the minutes in the conversation and do not perform the save operation.

Execution steps:

Generate the complete minutes
Display them in the conversation
Mark "[Not saved - display only]"
Do not perform the note archiving operation

Step 6: Natural exit

Execution description: Respond normally when the user changes the topic, and do not force completion of the minutes.

Execution steps:

Detect whether the user has changed the topic
If changed, save the current minutes status (if authorized)
Respond normally to the user's new topic

Step 7: One-vote veto self-check (gating step)

Execution description: Before generating the minutes, compare the one-vote veto signals S1-S6 one by one; if triggered, mark them in red at the top.

Execution steps:

Check the triggering status of S1-S6 one by one:
- S1: The business premises are false or have been sealed, seriously inconsistent with the declaration
- S2: It is found that the enterprise has effectively suspended operations for more than 30 days, and there is no reasonable recovery plan
- S3: The actual use of funds is seriously inconsistent with the applied use (e.g., working capital loan used for home purchase/stock trading)
- S4: Obvious signs of private financing/illegal fundraising are found, and the amount is relatively large
- S5: The actual controller is unreachable or refuses to meet, and cannot provide a reasonable explanation
- S6: Major environmental/safety hazards found on site, ordered by government authorities to rectify
If any condition is triggered, mark in red at the top of the minutes: [Veto-SX: Trigger Reason]
Recommend suspending the approval process and reporting upward

Branch Path:

❌ Any of S1-S6 triggered → mark in red, recommend suspending approval, output minutes
✅ None triggered → output minutes normally

Structured Dimensions

📋 The six dimensions are the core framework; each dimension must include specific factual descriptions (including time, location, quantity, source), and must not merely list headings. 📋 For complete content such as detailed inspection items, recording points, deviation markers, cross-verification, risk signals, and execution points, please refer to references/visit-memo-dimensions.md。

1. On-site Impression

Actual visit confirmation, authenticity of business premises, production/operating activity level, environment and management standards, deviations from the CM report
The operating rate must be estimated as a specific percentage; vague descriptions such as "basically normal" must not be used
Detailed inspection items and deviation markers: refer to references/visit-memo-dimensions.md Section 1

2. Business Judgment

Actual operating scale, authenticity of main business, order/contract evidence, reasonableness of inventory, industry prosperity
For contract verification, prioritize originals or stamped copies; orally claimed contract amounts must be marked as "self-reported by the other party, original not verified"
Detailed inspection items and cross-verification: refer to references/visit-memo-dimensions.md Section 2

3. Impressions of Individuals

Interview with actual controller/legal representative, interview with finance personnel, signs of avoidance and leading, assessment of cooperativeness
"Cooperativeness" is not better the higher it is: excessive cooperativeness may be a signal of prior staging and must be recorded objectively
Detailed inspection items and risk signals: refer to references/visit-memo-dimensions.md Section 3

4. Fund Flow

Main repayment methods, payment recipients and methods, signs of off-book circulation, judgment of related-party transactions, consistency of fund use
For fund flow verification, prioritize original bank statements or online banking screenshots; oral descriptions must be marked with their source
Detailed inspection items and risk thresholds: refer to references/visit-memo-dimensions.md Section 4

5. Risk Signals

Explicit risks (work stoppage/wage arrears/seizure/environmental penalties), hidden risks (information avoidance/data contradictions/excessive cooperativeness), private financing, actual controller risk, compliance risk
Detailed categories, typical signals and handling requirements: refer to references/visit-memo-dimensions.md Section 5

6. Conclusions from Communication with CM

CM's judgment of the client, additional information from CM, points of disagreement, CM's commitments for follow-up
Points of disagreement must be specific (e.g., "CM report revenue 50 million, visit estimate about 20 million"), and must not vaguely state "data has deviations"
Detailed recording items and content requirements: refer to references/visit-memo-dimensions.md Section 6

Veto Signals

If any of the following situations is found during the visit, it must be marked in red at the top of the minutes, and it is recommended to suspend the approval process and report upward.

No.	Trigger Condition
S1	The business premises are false or have been seized, seriously inconsistent with the declaration
S2	The enterprise is found to have substantially ceased operations for more than 30 days, and there is no reasonable recovery plan
S3	The actual use of funds is seriously inconsistent with the applied use (e.g., working capital loan used to buy a house/speculate in stocks)
S4	Obvious signs of private financing/illegal fundraising are found, and the amount is relatively large
S5	The actual controller is out of contact or refuses to meet, and cannot provide a reasonable explanation
S6	On-site discovery of major environmental protection/safety hazards, ordered by a government department to rectify

Output Format

Output a structured visit summary containing the following sections:

Section	Content	Data Type
Basic Report Information	Visit time, visitor, customer address, one-vote veto annotation (if triggered)	Table
I. On-Site Impressions	Actual visit confirmation, authenticity of the business premises, production/operating activity level, environment and management standards, deviations from the CM report	Table
II. Business Assessment	Actual operating scale, authenticity of the main business, order/contract evidence, reasonableness of inventory, industry prosperity level	Table
III. Impressions of Key Individuals	Interview with actual controller/legal representative, interview with finance personnel, signs of evasion and leading, assessment of cooperativeness	Table
IV. Fund Flows	Payment collection methods and cycles, payment recipients and methods, signs of off-balance-sheet circulation, related-party transactions, consistency of fund usage	Table
V. Risk Signals	Red flags (major risks), yellow flags (potential risks), positive signals (factors supporting credit granting)	List
VI. Conclusions from Communication with CM	CM judgment, supplementary information, points of disagreement, CM commitments to follow up	List
Approval Focus Points	Matters requiring further verification (to-do list)	List
Dimensions to Be Supplemented	Key dimensions not covered or with insufficient information in this visit	List
Data Sources and Record Notes	Information items, sources (seen firsthand/self-reported by the other party/provided documents/CM report), record time	Table

Downstream Compatibility: This output can be parsed and used by the credit-approval Skill as a reference for credit approval committee decision-making.

Disclaimer: This summary does not constitute a recommendation for credit approval decisions and is for reference only. The final approval decision must be comprehensively judged by the credit approval committee based on complete materials. Quoting the shared/disclaimer-template.md template.

Interaction Pattern

📋 Mode D - Conversational Assistant

Dialogue Stage

Starting Stage:

Confirm customer name, visit time, and visitor
Check the pre-visit one-pager and visit invitation records
Guide the approval specialist to begin verbalizing observations

Middle Stage:

Structure the verbal content in real time into the six-dimension framework
Ask targeted follow-up questions on missing dimensions
Support incremental updates and information corrections
When the user says "do not save for now", only display without saving

Ending Stage:

Perform the one-vote veto self-check (S1-S6)
Generate the complete summary
Confirm saving to the customer notes area (if authorized by the user)
Provide a list of approval focus points and dimensions to be supplemented

Context Management

Context Accumulation Rules

Continuously accumulate six-dimension information across multiple dialogue turns
During incremental updates, read existing meeting notes and merge new observations
When correcting information, retain the original record and annotate the correction time
When the user changes topics, save the current state without losing recorded information

Context Cleanup Rules

When the user explicitly says "start over", clear the current meeting notes and regenerate them
For drafts not updated for more than 24 hours, prompt the user to confirm whether to continue

Audit Trail

Generate an audit log recording operation information:

{
  "skill_name": "reviewer-visit-memo",
  "skill_version": "2.0.0",
  "execution_time": "2026-05-05T14:00:00+08:00",
  "customer_name": "[客户名称]",
  "visit_time": "YYYY-MM-DD HH:MM",
  "reviewer_name": "[审批专员姓名]",
  "operation_mode": "首次记录/增量更新/信息修正/仅展示",
  "data_sources": {
    "pre_visit_paper": true,
    "visit_invitation": true,
    "cm_report": true,
    "customer_data": true
  },
  "six_dimensions_coverage": {
    "site_observation": true,
    "business_assessment": true,
    "personnel_impression": true,
    "cash_flow": true,
    "risk_signals": true,
    "cm_communication": true
  },
  "veto_trigger": {
    "triggered": false,
    "signal": null,
    "reason": null
  },
  "red_flags_count": 0,
  "yellow_flags_count": 0,
  "save_status": "已保存/未保存"
}

Audit Log Retention Period: At least 3 years.

Gotchas

#1: Subjective inference replacing objective facts

Symptom: Conclusions without sources such as "poor business conditions" and "possible problems" appear in the meeting notes
Cause: The approval specialist mixed subjective judgments into their oral account, and the model did not strictly distinguish facts from inferences
Solution: Each record must indicate its source (seen firsthand/self-reported by the other party/provided documents/CM report), and subjective inferences must be separately marked as "[Inference]" with the basis explained

#2: Incremental updates overwriting original records

Symptom: After the meeting notes are updated, historical versions are lost and the correction process cannot be traced
Cause: The original record was directly overwritten, with no trace of corrections retained
Solution: Incremental updates must retain the original record, append new observations, and mark them as "[Incremental update YYYY-MM-DD HH:MM]"; information corrections must be marked as "[Corrected YYYY-MM-DD HH:MM]"

#3: CM report deviations not explicitly marked

Symptom: Differences found during the visit compared with the CM report were not clearly marked in the meeting notes
Cause: The model did not compare key data in the CM report one by one
Solution: Each item must be compared in the "Deviations from CM report" checklist, and major deviations must be listed separately (e.g., "CM report revenue 50 million, visit estimate about 20 million")

#4: Missed veto signals

Symptom: S1-S6 veto conditions were triggered, but they were not marked in red at the top of the meeting notes
Cause: The veto self-check was not performed before generating the meeting notes
Solution: Step 7 mandatorily performs the veto self-check; if triggered, mark it in red at the top of the meeting notes as [Veto-SX: trigger reason] and recommend suspending approval

Examples

Example 1: Visit for approval of a new customer's first credit line

User input:

客户名称: XX制造有限公司
走访时间: 2026-05-05 10:00
走访人: 张审批
走访目的: 新客户首笔授信

口述内容: 今天去了XX制造有限公司,地址是北京市朝阳区XX路123号,跟营业执照一致。厂房大概5000平米,目测开工率约60%,设备运转正常。实控人李总接待的,对经营数据很熟悉。看了几份销售合同,金额大概2000万。资金流主要是对公账户回款,没发现异常。跟CM报告基本一致,但CM报告说营收5000万,我估算大概3000万左右。

Skill execution flow:

Step 0: Confirm that the customer name/visit time/visitor are complete, and check the pre-visit one-pager and CM report
Step 1: Extract the oral information, categorize it into the six dimensions, and mark the source (seen firsthand/self-reported by the other party/provided documents)
Step 4: Ask follow-up questions for missing dimensions (person impressions - interview with finance personnel, risk signals, conclusions of communication with CM)
Step 7: Veto self-check (S1-S6 not triggered)
Output the complete visit meeting notes and save them to the customer notes area

Output key points:

Complete coverage of the six dimensions, with each item's source marked
Mark deviations from the CM report (revenue estimate difference)
No veto triggered

Example 2: Follow-up visit for a risk-warning customer

User input:

客户名称: XX贸易有限公司
走访时间: 2026-05-05 14:00
走访人: 李审批
走访目的: 风险预警复核

口述内容: 这家企业有点问题,厂房门口贴着法院查封公告,说涉及诉讼。车间基本停工了,只有几个工人在收拾东西。实控人电话打不通,财务说老板出差了。问了工人,说已经两个月没发工资了。这情况是不是得暂停审批?

Skill execution flow:

Step 0: Confirm customer information and read the pre-visit one-pager (if there are risk warning signals)
Step 1: Extract oral information and identify major risk signals (seizure notices, work stoppage, unpaid wages, actual controller unreachable)
Step 7: One-vote veto self-check → trigger S1 (business premises seized), S2 (work stoppage exceeding 30 days), S5 (actual controller unreachable)
Mark in red at the top of the minutes: [One-vote veto - S1/S2/S5: Trigger reason]
Recommend suspending the approval process and reporting upward

Output points:

Mark one-vote veto signals in red (S1/S2/S5)
Recommend suspending approval and reporting upward
Objectively record facts, and do not provide approval decision recommendations

Out of Scope

This skill is not responsible for credit approval decisions (it only provides visit minutes; approval decisions are handled by the credit-approval Skill)
This skill does not generate the CM credit manager investigation report (it is only used for cross-verification)
This skill does not handle post-loan risk classification adjustments or non-performing asset disposal
This skill does not replace on-site visits (it only organizes oral observations into structured minutes)
If the user requests the above, clearly inform them and recommend contacting the relevant department or using an appropriate tool

About this skill

Target Role

Data Sources

Required Data

Data Masking Rules

Degradation Strategy

Constraints

Execution Workflow

Step 0: Data confirmation and verification (read first, then write)

Step 1: First input processing (complete minutes generation)

Step 2: Incremental update handling

Step 3: Information correction handling

Step 4: Targeted follow-up questions

Step 5: No-save mode handling

Step 6: Natural exit

Step 7: One-vote veto self-check (gating step)

Structured Dimensions

1. On-site Impression

2. Business Judgment

3. Impressions of Individuals

4. Fund Flow

5. Risk Signals

6. Conclusions from Communication with CM

Veto Signals

Output Format

Interaction Pattern

Dialogue Stage

Context Management

Context Accumulation Rules

Context Cleanup Rules

Audit Trail

Gotchas

#1: Subjective inference replacing objective facts

#2: Incremental updates overwriting original records

#3: CM report deviations not explicitly marked

#4: Missed veto signals

Examples

Example 1: Visit for approval of a new customer's first credit line

Example 2: Follow-up visit for a risk-warning customer

Out of Scope