tear-sheet
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseFinancial Tear Sheet Generator
财务摘要生成工具
Generate audience-specific company tear sheets by pulling live data from S&P Capital IQ via the S&P Global MCP tools and formatting the result as a professional Word document.
通过S&P Global MCP工具从S&P Capital IQ获取实时数据,生成针对特定受众的公司财务摘要,并将结果格式化为专业的Word文档。
Style Configuration
样式配置
These are sensible defaults. To customize for your firm's brand, modify this section — common changes include swapping the color palette, changing the font (Calibri is standard at many banks), and updating the disclaimer text.
Colors:
- Primary (header banner background, section header text): #1F3864
- Accent (signature section highlights): #2E75B6
- Table header row fill: #D6E4F0
- Table alternating row fill: #F2F2F2
- Table borders: #CCCCCC
- Header banner text: #FFFFFF
Typography (sizes in half-points for docx-js):
- Font family: Arial
- Company name: 18pt bold (size: 36)
- Section headers: 11pt bold (size: 22), Primary color
- Body text: 9pt (size: 18)
- Table text: 8.5pt (size: 17)
- Footer/disclaimer: 7pt italic (size: 14)
- Per-template overrides are specified in each reference file's Formatting Notes.
Company Header Banner:
- The header is a navy (#1F3864) banner spanning the full page width with company name in white.
- Below the banner, key-value pairs MUST be rendered in a two-column borderless table spanning the full page width. Left column: company identifiers (ticker, HQ, founded, employees, sector). Right column: financial identifiers (market cap, EV, stock price, shares outstanding). Each cell contains a bold label and regular-weight value on the same line (e.g., "Market Cap $124.7B"). Do not left-justify all fields in a single column — this wastes horizontal space and looks unprofessional. The two-column spread is the single most important visual signal that distinguishes a professional tear sheet from a default document.
- Implementation: Create a 2-column table with and
borders: noneon all cells. Set column widths to 50% each. Place left-column fields (ticker, HQ, founded, employees) as separate paragraphs in the left cell. Place right-column fields (market cap, EV, stock price, shares outstanding) in the right cell. Each field is a single paragraph: bold run for the label, regular run for the value.shading: none - The specific fields in each column vary by audience — see the reference file's header spec. The principle is always: spread across the page, not clumped left.
- Implementation: Create a 2-column table with
- Do not use a bordered table for the header key-value block. Bordered tables are reserved for financial data only.
- Key metrics in the header (market cap, EV, stock price) should be displayed as inline key-value pairs, not in a separate bordered table.
Section Headers:
- Each section header gets a horizontal rule (thin line, #CCCCCC, 0.5pt) directly beneath it to create clean visual separation between sections.
- Render the rule as a bottom border on the header paragraph itself — do not insert a separate paragraph element for the rule. A separate paragraph adds its own before/after spacing and causes excessive whitespace below section titles.
- Implementation: In docx-js, apply a bottom border to the section header paragraph via . Do not use
paragraph.borders.bottom = { style: BorderStyle.SINGLE, size: 1, color: "CCCCCC" }with a separate horizontal rule element. Do not usedoc.addParagraph(). The border must be on the heading paragraph itself with 0pt spacing after, so the rule sits tight against the header text.thematicBreak - Spacing: 12pt before the header paragraph, 0pt after the header paragraph, 4pt before the next content element.
Bullet Formatting:
- Use a single bullet character (•) for all bulleted content across all tear sheet types. Do not mix •, -, ▸, or numbered lists within or across tear sheets.
- Synthesis/analysis bullets (Earnings Highlights, Strategic Fit, Integration Considerations, Conversation Starters): indented block-style formatting with left indent 360 DXA (0.25") and a hanging indent for the bullet character. These should be visually offset from body text — they're interpretive content and should look distinct from data tables and prose paragraphs.
- Informational bullets within relationship sections: standard body indent (180 DXA), no hanging indent.
- Do not apply left-border accents to any bullet sections. Left-border styling renders inconsistently in docx-js and creates visual artifacts. Use indentation and text size differentiation to distinguish signature sections instead.
Tables (financial data only):
- Header row: Table Header Fill (#D6E4F0) with bold dark text
- Body rows: alternating white / Table Alternating Fill (#F2F2F2)
- Borders: Table Border color (#CCCCCC), thin (BorderStyle.SINGLE, size 1)
- Cell padding: top/bottom 40 DXA, left/right 80 DXA
- Right-align all numeric columns
- Always use ShadingType.CLEAR (never SOLID — SOLID causes black backgrounds)
Layout:
- US Letter portrait, 0.75" margins (1080 DXA all sides)
Number formatting:
- Currency: USD. Use millions unless company revenue > $50B (then billions, one decimal). Label units in column headers (e.g., "Revenue ($M)"), not in individual cells.
- Table cells: plain numbers with commas, no dollar signs. Example: a revenue cell shows "4,916" not "$4,916". The column header carries the unit.
- Fiscal years: actual years (FY2022, FY2023, FY2024), never relative labels (FY-2, FY-1).
- Negatives: parentheses, e.g., (2.3%)
- Percentages: one decimal place
- Large numbers: commas as thousands separators
Footer (document footer, not inline):
Place the source attribution and disclaimer in the actual document footer (repeated on every page), not as inline body text at the bottom. The footer is exactly two lines, centered, on every page:
- Line 1: "Data: S&P Capital IQ via Kensho | Analysis: AI-generated | [Month Day, Year]"
- Line 2: "For informational purposes only. Not investment advice."
- Style: 7pt italic, centered, #666666 text color
- This footer text must be identical across all tear sheet types for the same company. Do not vary the wording by audience.
- This footer is required on every tear sheet, every audience type, every page. Do not omit it.
以下是合理的默认设置。如需为贵公司品牌定制,请修改此部分——常见修改包括更换调色板、更改字体(Calibri是许多银行的标准字体)以及更新免责声明文本。
颜色设置:
- 主色调(页眉横幅背景、章节标题文本):#1F3864
- 强调色(重点区域高亮):#2E75B6
- 表格表头填充色:#D6E4F0
- 表格交替行填充色:#F2F2F2
- 表格边框颜色:#CCCCCC
- 页眉横幅文本颜色:#FFFFFF
排版设置(docx-js中使用半磅为单位):
- 字体家族:Arial
- 公司名称:18号粗体(size参数:36)
- 章节标题:11号粗体(size参数:22),主色调
- 正文字体:9号(size参数:18)
- 表格字体:8.5号(size参数:17)
- 页脚/免责声明:7号斜体(size参数:14)
- 各模板的自定义设置详见对应参考文件的格式说明。
公司页眉横幅:
- 页眉为深蓝色(#1F3864)横幅,横跨整个页面宽度,公司名称为白色字体。
- 横幅下方的键值对必须以无边框双列表格形式呈现,横跨整个页面宽度。 左列:公司标识信息(股票代码、总部所在地、成立时间、员工人数、行业板块)。右列:财务标识信息(市值、企业价值、股价、已发行股份数)。每个单元格包含粗体标签和常规字体的数值,位于同一行(例如:"市值 $1247亿")。请勿将所有字段左对齐放在单列中——这会浪费横向空间且显得不够专业。双列布局是区分专业财务摘要与普通文档的核心视觉特征。
- 实现方式: 创建一个且
borders: none的双列表格,每列宽度占比50%。将左列字段(股票代码、总部、成立时间、员工人数)作为独立段落放在左单元格中,右列字段(市值、企业价值、股价、已发行股份数)放在右单元格中。每个字段为单独段落:标签使用粗体文本,数值使用常规文本。shading: none - 每类受众对应的列中具体字段会有所不同——详见参考文件的页眉规范。核心原则始终是:内容横向分布,而非左对齐堆叠。
- 实现方式: 创建一个
- **页眉的键值对区块请勿使用带边框的表格。**带边框表格仅用于财务数据展示。
- 页眉中的关键指标(市值、企业价值、股价)应以内联键值对形式展示,而非放在单独的带边框表格中。
章节标题:
- 每个章节标题下方需添加一条水平分隔线(细线条,#CCCCCC,0.5磅),以清晰区分不同章节。
- 将分隔线作为标题段落的下边框实现——请勿插入单独的段落元素作为分隔线。单独的段落会自带前后间距,导致章节标题下方出现过多空白。
- 实现方式: 在docx-js中,通过为章节标题段落添加下边框。请勿使用
paragraph.borders.bottom = { style: BorderStyle.SINGLE, size: 1, color: "CCCCCC" }插入单独的水平分隔线元素,也请勿使用doc.addParagraph()。边框必须直接应用于标题段落本身,且段落的后间距设为0磅,使分隔线紧贴标题文本。thematicBreak - 间距设置:标题段落前间距12磅,后间距0磅,下一个内容元素前间距4磅。
项目符号格式:
- 所有类型财务摘要中的项目符号内容统一使用•符号。请勿在同一或不同财务摘要中混合使用•、-、▸或编号列表。
- 分析性项目符号(收益亮点、战略契合度、整合注意事项、对话切入点):采用缩进块式格式,左缩进360 DXA(0.25英寸),项目符号使用悬挂缩进。此类内容应与正文视觉区分开——它们属于解读性内容,需与数据表格和普通段落明显区分。
- 信息性项目符号(关联方章节内):使用标准正文缩进(180 DXA),无悬挂缩进。
- 请勿为任何项目符号章节添加左侧边框高亮。 左侧边框样式在docx-js中渲染效果不一致,会产生视觉瑕疵。请改用缩进和文本大小差异来区分重点章节。
表格(仅用于财务数据):
- 表头行:使用表格表头填充色(#D6E4F0),搭配深色粗体文本
- 数据行:交替使用白色和表格交替行填充色(#F2F2F2)
- 边框:表格边框颜色(#CCCCCC),细线条(BorderStyle.SINGLE,size为1)
- 单元格内边距:上下40 DXA,左右80 DXA
- 所有数值列右对齐
- 始终使用(绝不使用SOLID——SOLID会导致黑色背景)
ShadingType.CLEAR
页面布局:
- 美国信纸尺寸,纵向排版,边距0.75英寸(所有边距为1080 DXA)
数字格式:
- 货币:美元。默认以百万为单位,除非公司收入超过500亿美元(此时以十亿为单位,保留一位小数)。在列标题中标注单位(例如:"收入(百万美元)"),请勿在单个单元格中重复标注。
- 表格单元格: 仅显示带千分位分隔符的纯数字。示例:收入单元格显示"4,916"而非"$4,916",单位由列标题说明。
- 财年:使用实际年份(FY2022、FY2023、FY2024),绝不使用相对标签(FY-2、FY-1)。
- 负数:使用括号标注,例如:(2.3%)
- 百分比:保留一位小数
- 大数:使用千分位分隔符
页脚(文档页脚,非内联):
将来源说明和免责声明放在实际文档页脚中(每页重复显示),而非正文末尾的内联文本。页脚共两行,居中对齐,显示在每一页:
- 第一行:"Data: S&P Capital IQ via Kensho | Analysis: AI-generated | [Month Day, Year]"
- 第二行:"For informational purposes only. Not investment advice."
- 样式:7号斜体,居中对齐,文本颜色#666666
- 同一公司的所有类型财务摘要的页脚文本必须完全一致,请勿根据受众类型修改措辞。
- 所有财务摘要的每一页都必须包含此页脚,不得省略。
Component Functions
组件函数
You MUST use these exact functions to create document elements. Do NOT write custom docx-js styling code. Copy these functions into your generated Node script and call them. The Style Configuration prose above remains as documentation; these functions are the enforcement mechanism.
javascript
const docx = require("docx");
const {
Document, Paragraph, TextRun, Table, TableRow, TableCell,
WidthType, AlignmentType, BorderStyle, ShadingType,
Header, Footer, PageNumber, HeadingLevel, TableLayoutType,
convertInchesToTwip
} = docx;
// ── Color constants ──
const COLORS = {
PRIMARY: "1F3864",
ACCENT: "2E75B6",
TABLE_HEADER_FILL: "D6E4F0",
TABLE_ALT_ROW: "F2F2F2",
TABLE_BORDER: "CCCCCC",
HEADER_TEXT: "FFFFFF",
FOOTER_TEXT: "666666",
};
const FONT = "Arial";
// ── 1. createHeaderBanner ──
// Returns an array of docx elements: [banner paragraph, key-value table]
function createHeaderBanner(companyName, leftFields, rightFields) {
// leftFields / rightFields: arrays of { label: string, value: string }
const banner = new Paragraph({
children: [
new TextRun({
text: companyName,
bold: true,
size: 36, // 18pt
color: COLORS.HEADER_TEXT,
font: FONT,
}),
],
shading: { type: ShadingType.CLEAR, color: "auto", fill: COLORS.PRIMARY },
spacing: { after: 0 },
alignment: AlignmentType.LEFT,
});
function buildCellParagraphs(fields) {
return fields.map(
(f) =>
new Paragraph({
children: [
new TextRun({ text: f.label + " ", bold: true, size: 18, font: FONT }),
new TextRun({ text: f.value, size: 18, font: FONT }),
],
spacing: { after: 40 },
})
);
}
const noBorder = { style: BorderStyle.NONE, size: 0, color: "FFFFFF" };
const noBorders = { top: noBorder, bottom: noBorder, left: noBorder, right: noBorder };
const noShading = { type: ShadingType.CLEAR, color: "auto", fill: "FFFFFF" };
const kvTable = new Table({
rows: [
new TableRow({
children: [
new TableCell({
children: buildCellParagraphs(leftFields),
width: { size: 50, type: WidthType.PERCENTAGE },
borders: noBorders,
shading: noShading,
}),
new TableCell({
children: buildCellParagraphs(rightFields),
width: { size: 50, type: WidthType.PERCENTAGE },
borders: noBorders,
shading: noShading,
}),
],
}),
],
width: { size: 100, type: WidthType.PERCENTAGE },
});
return [banner, kvTable];
}
// ── 2. createSectionHeader ──
// Returns a single Paragraph with bottom border rule
function createSectionHeader(text) {
return new Paragraph({
children: [
new TextRun({
text: text,
bold: true,
size: 22, // 11pt
color: COLORS.PRIMARY,
font: FONT,
}),
],
spacing: { before: 240, after: 0 }, // 12pt before, 0pt after
border: {
bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
},
});
}
// ── 3. createTable ──
// headers: string[], rows: string[][], options: { accentHeader?, fontSize? }
function createTable(headers, rows, options = {}) {
const fontSize = options.fontSize || 17; // 8.5pt default
const headerFill = options.accentHeader ? COLORS.ACCENT : COLORS.TABLE_HEADER_FILL;
const headerTextColor = options.accentHeader ? COLORS.HEADER_TEXT : "000000";
const cellBorders = {
top: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
left: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
right: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
};
const cellMargins = { top: 40, bottom: 40, left: 80, right: 80 };
function isNumeric(val) {
if (typeof val !== "string") return false;
const cleaned = val.replace(/[,$%()]/g, "").trim();
return cleaned !== "" && !isNaN(cleaned);
}
// Header row
const headerRow = new TableRow({
children: headers.map(
(h) =>
new TableCell({
children: [
new Paragraph({
children: [
new TextRun({
text: h,
bold: true,
size: fontSize,
color: headerTextColor,
font: FONT,
}),
],
}),
],
shading: { type: ShadingType.CLEAR, color: "auto", fill: headerFill },
borders: cellBorders,
margins: cellMargins,
})
),
});
// Data rows with alternating shading
const dataRows = rows.map((row, rowIdx) => {
const fill = rowIdx % 2 === 1 ? COLORS.TABLE_ALT_ROW : "FFFFFF";
return new TableRow({
children: row.map((cell, colIdx) => {
const align = colIdx > 0 && isNumeric(cell)
? AlignmentType.RIGHT
: AlignmentType.LEFT;
return new TableCell({
children: [
new Paragraph({
children: [
new TextRun({ text: cell, size: fontSize, font: FONT }),
],
alignment: align,
}),
],
shading: { type: ShadingType.CLEAR, color: "auto", fill: fill },
borders: cellBorders,
margins: cellMargins,
});
}),
});
});
return new Table({
rows: [headerRow, ...dataRows],
width: { size: 100, type: WidthType.PERCENTAGE },
});
}
// ── 4. createBulletList ──
// items: string[], style: "synthesis" | "informational"
function createBulletList(items, style = "synthesis") {
const indent =
style === "synthesis"
? { left: 360, hanging: 180 } // 360 DXA left, hanging indent for bullet
: { left: 180 }; // 180 DXA, no hanging
return items.map(
(item) =>
new Paragraph({
children: [
new TextRun({ text: "• ", font: FONT, size: 18 }),
new TextRun({ text: item, font: FONT, size: 18 }),
],
indent: indent,
spacing: { after: 60 },
})
);
}
// ── 5. createFooter ──
// date: string (e.g., "February 23, 2026")
function createFooter(date) {
return new Footer({
children: [
new Paragraph({
children: [
new TextRun({
text: `Data: S&P Capital IQ via Kensho | Analysis: AI-generated | ${date}`,
italics: true,
size: 14, // 7pt
color: COLORS.FOOTER_TEXT,
font: FONT,
}),
],
alignment: AlignmentType.CENTER,
}),
new Paragraph({
children: [
new TextRun({
text: "For informational purposes only. Not investment advice.",
italics: true,
size: 14,
color: COLORS.FOOTER_TEXT,
font: FONT,
}),
],
alignment: AlignmentType.CENTER,
}),
],
});
}Usage in generated scripts:
- Copy all functions and constants above into the generated Node.js script
- Call instead of manually building banner paragraphs and tables
createHeaderBanner(...) - Call for every section title — never manually set paragraph borders
createSectionHeader(...) - Call for all tabular data — financial summaries, trading comps, M&A activity, relationship tables, funding history, etc. Pass
createTable(...)for M&A activity tables (IB/M&A template). For non-numeric tables (e.g., relationships, ownership), the function still works correctly — it only right-aligns cells that contain numeric values.{ accentHeader: true } - Call for earnings highlights, strategic fit, integration considerations, and conversation starters
createBulletList(items, "synthesis") - Call for relationship entries
createBulletList(items, "informational") - Pass to the Document constructor's
createFooter(date)propertyfooters.default
What these functions eliminate:
- Black background tables (enforces everywhere)
ShadingType.CLEAR - Separate horizontal rule paragraphs under section headers (enforces on the paragraph itself)
border.bottom - Bordered key-value tables in headers (enforces )
borders: none - Inconsistent bullet styles (enforces character only)
• - Missing footers (provides the exact footer structure)
必须使用以下指定函数创建文档元素,禁止编写自定义docx-js样式代码。 将这些函数复制到生成的Node脚本中并调用。上述样式配置说明仅作为文档参考,这些函数是强制执行样式的机制。
javascript
const docx = require("docx");
const {
Document, Paragraph, TextRun, Table, TableRow, TableCell,
WidthType, AlignmentType, BorderStyle, ShadingType,
Header, Footer, PageNumber, HeadingLevel, TableLayoutType,
convertInchesToTwip
} = docx;
// ── Color constants ──
const COLORS = {
PRIMARY: "1F3864",
ACCENT: "2E75B6",
TABLE_HEADER_FILL: "D6E4F0",
TABLE_ALT_ROW: "F2F2F2",
TABLE_BORDER: "CCCCCC",
HEADER_TEXT: "FFFFFF",
FOOTER_TEXT: "666666",
};
const FONT = "Arial";
// ── 1. createHeaderBanner ──
// Returns an array of docx elements: [banner paragraph, key-value table]
function createHeaderBanner(companyName, leftFields, rightFields) {
// leftFields / rightFields: arrays of { label: string, value: string }
const banner = new Paragraph({
children: [
new TextRun({
text: companyName,
bold: true,
size: 36, // 18pt
color: COLORS.HEADER_TEXT,
font: FONT,
}),
],
shading: { type: ShadingType.CLEAR, color: "auto", fill: COLORS.PRIMARY },
spacing: { after: 0 },
alignment: AlignmentType.LEFT,
});
function buildCellParagraphs(fields) {
return fields.map(
(f) =>
new Paragraph({
children: [
new TextRun({ text: f.label + " ", bold: true, size: 18, font: FONT }),
new TextRun({ text: f.value, size: 18, font: FONT }),
],
spacing: { after: 40 },
})
);
}
const noBorder = { style: BorderStyle.NONE, size: 0, color: "FFFFFF" };
const noBorders = { top: noBorder, bottom: noBorder, left: noBorder, right: noBorder };
const noShading = { type: ShadingType.CLEAR, color: "auto", fill: "FFFFFF" };
const kvTable = new Table({
rows: [
new TableRow({
children: [
new TableCell({
children: buildCellParagraphs(leftFields),
width: { size: 50, type: WidthType.PERCENTAGE },
borders: noBorders,
shading: noShading,
}),
new TableCell({
children: buildCellParagraphs(rightFields),
width: { size: 50, type: WidthType.PERCENTAGE },
borders: noBorders,
shading: noShading,
}),
],
}),
],
width: { size: 100, type: WidthType.PERCENTAGE },
});
return [banner, kvTable];
}
// ── 2. createSectionHeader ──
// Returns a single Paragraph with bottom border rule
function createSectionHeader(text) {
return new Paragraph({
children: [
new TextRun({
text: text,
bold: true,
size: 22, // 11pt
color: COLORS.PRIMARY,
font: FONT,
}),
],
spacing: { before: 240, after: 0 }, // 12pt before, 0pt after
border: {
bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
},
});
}
// ── 3. createTable ──
// headers: string[], rows: string[][], options: { accentHeader?, fontSize? }
function createTable(headers, rows, options = {}) {
const fontSize = options.fontSize || 17; // 8.5pt default
const headerFill = options.accentHeader ? COLORS.ACCENT : COLORS.TABLE_HEADER_FILL;
const headerTextColor = options.accentHeader ? COLORS.HEADER_TEXT : "000000";
const cellBorders = {
top: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
bottom: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
left: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
right: { style: BorderStyle.SINGLE, size: 1, color: COLORS.TABLE_BORDER },
};
const cellMargins = { top: 40, bottom: 40, left: 80, right: 80 };
function isNumeric(val) {
if (typeof val !== "string") return false;
const cleaned = val.replace(/[,$%()]/g, "").trim();
return cleaned !== "" && !isNaN(cleaned);
}
// Header row
const headerRow = new TableRow({
children: headers.map(
(h) =>
new TableCell({
children: [
new Paragraph({
children: [
new TextRun({
text: h,
bold: true,
size: fontSize,
color: headerTextColor,
font: FONT,
}),
],
}),
],
shading: { type: ShadingType.CLEAR, color: "auto", fill: headerFill },
borders: cellBorders,
margins: cellMargins,
})
),
});
// Data rows with alternating shading
const dataRows = rows.map((row, rowIdx) => {
const fill = rowIdx % 2 === 1 ? COLORS.TABLE_ALT_ROW : "FFFFFF";
return new TableRow({
children: row.map((cell, colIdx) => {
const align = colIdx > 0 && isNumeric(cell)
? AlignmentType.RIGHT
: AlignmentType.LEFT;
return new TableCell({
children: [
new Paragraph({
children: [
new TextRun({ text: cell, size: fontSize, font: FONT }),
],
alignment: align,
}),
],
shading: { type: ShadingType.CLEAR, color: "auto", fill: fill },
borders: cellBorders,
margins: cellMargins,
});
}),
});
});
return new Table({
rows: [headerRow, ...dataRows],
width: { size: 100, type: WidthType.PERCENTAGE },
});
}
// ── 4. createBulletList ──
// items: string[], style: "synthesis" | "informational"
function createBulletList(items, style = "synthesis") {
const indent =
style === "synthesis"
? { left: 360, hanging: 180 } // 360 DXA left, hanging indent for bullet
: { left: 180 }; // 180 DXA, no hanging
return items.map(
(item) =>
new Paragraph({
children: [
new TextRun({ text: "• ", font: FONT, size: 18 }),
new TextRun({ text: item, font: FONT, size: 18 }),
],
indent: indent,
spacing: { after: 60 },
})
);
}
// ── 5. createFooter ──
// date: string (e.g., "February 23, 2026")
function createFooter(date) {
return new Footer({
children: [
new Paragraph({
children: [
new TextRun({
text: `Data: S&P Capital IQ via Kensho | Analysis: AI-generated | ${date}`,
italics: true,
size: 14, // 7pt
color: COLORS.FOOTER_TEXT,
font: FONT,
}),
],
alignment: AlignmentType.CENTER,
}),
new Paragraph({
children: [
new TextRun({
text: "For informational purposes only. Not investment advice.",
italics: true,
size: 14,
color: COLORS.FOOTER_TEXT,
font: FONT,
}),
],
alignment: AlignmentType.CENTER,
}),
],
});
}在生成脚本中的使用方法:
- 将上述所有函数和常量复制到生成的Node.js脚本中
- 调用创建横幅段落和表格,替代手动构建
createHeaderBanner(...) - 每个章节标题都调用——绝不手动设置段落边框
createSectionHeader(...) - 所有表格数据(财务摘要、可比公司分析、并购活动、关联方表格、融资历史等)都调用。对于并购活动表格(IB/M&A模板),传入
createTable(...)。对于非数值表格(例如关联方、股权结构),该函数依然可以正常工作——仅会对包含数值的单元格进行右对齐处理。{ accentHeader: true } - 收益亮点、战略契合度、整合注意事项和对话切入点等内容调用
createBulletList(items, "synthesis") - 关联方条目调用
createBulletList(items, "informational") - 将传入Document构造函数的
createFooter(date)属性footers.default
这些函数解决的问题:
- 黑色背景表格(强制所有场景使用)
ShadingType.CLEAR - 章节标题下方的独立分隔线段落(强制将分隔线作为段落的属性)
border.bottom - 页眉中带边框的键值对表格(强制设置)
borders: none - 不一致的项目符号样式(仅允许使用符号)
• - 缺失页脚(提供标准页脚结构)
Workflow
工作流程
Step 1: Identify Inputs
步骤1:确定输入信息
Gather up to four things before proceeding:
- Company — name or ticker. If only a ticker, resolve the full company name with an initial query (e.g., use the company info tool).
- Audience — one of four types:
- Equity Research — for buy-side/sell-side analysts evaluating an investment
- IB / M&A — for bankers profiling a company in transaction context
- Corp Dev — for internal strategic teams evaluating an acquisition target
- Sales / BD — for commercial teams preparing for a client meeting
- Comparable companies (optional) — if the user has specific comps in mind, note them. Otherwise the skill will identify peers from S&P Global data. This matters for Equity Research, IB/M&A, and Corp Dev tear sheets.
- Page length preference (optional) — defaults vary by audience (see below), but the user can override.
If the user doesn't specify an audience, ask.
开始前收集最多四类信息:
- 公司——名称或股票代码。如果仅提供股票代码,需先通过初始查询(例如使用公司信息工具)获取完整公司名称。
- 受众——以下四类之一:
- 股票研究——用于买方/卖方分析师评估投资标的
- IB / 并购——用于银行家在交易场景中分析公司
- 企业发展——用于内部战略团队评估收购目标
- 销售 / 业务发展——用于商务团队准备客户会议
- 可比公司(可选)——如果用户指定了特定可比公司,请记录下来。否则,技能将从S&P Global数据中识别同行公司。这对股票研究、IB/并购和企业发展类财务摘要至关重要。
- 页面长度偏好(可选)——默认长度因受众类型而异(详见下文),但用户可自定义。
如果用户未指定受众类型,请主动询问。
Step 2: Read the Audience-Specific Reference
步骤2:阅读特定受众的参考文档
Read the corresponding reference file from this skill's directory:
- Equity Research →
references/equity-research.md - IB / M&A →
references/ib-ma.md - Corp Dev →
references/corp-dev.md - Sales / BD →
references/sales-bd.md
Each reference defines sections, a query plan, formatting guidance, and page length defaults.
从本技能的目录中读取对应参考文件:
- 股票研究 →
references/equity-research.md - IB / 并购 →
references/ib-ma.md - 企业发展 →
references/corp-dev.md - 销售 / 业务发展 →
references/sales-bd.md
每个参考文件定义了章节结构、查询计划、格式指南和默认页面长度。
Step 3: Pull Data via S&P Global MCP
步骤3:通过S&P Global MCP获取数据
First: Create the intermediate file directory:
bash
mkdir -p /tmp/tear-sheet/Use the S&P Global MCP tools (also known as the Kensho LLM-ready API). Claude will have access to structured tools for financial data, company information, market data, consensus estimates, earnings transcripts, M&A transactions, and business relationships. The query plans in each reference file describe what data to retrieve for each section — map these to the appropriate S&P Global tools available in the conversation.
After each query step, immediately write the retrieved data to the intermediate file(s) specified in the reference file's query plan. Do not defer writes — data written to disk is protected from context degradation in long conversations.
Query strategy:
Each reference file includes a query plan with 4-6 data retrieval steps. These are starting points, not rigid constraints. Prioritize data completeness over minimizing calls:
- Always pull 4 fiscal years of financial data, even though only 3 years are displayed. The fourth (earliest) year is needed to compute YoY revenue growth for the first displayed year. Without it, the earliest year's growth rate will show "N/A" — which looks like missing data, not a design choice.
- Execute the query plan as written, using whichever S&P Global tools match the data needed.
- If a tool call returns incomplete results, try alternative tools or narrower queries. For example, if company summary doesn't include segment detail, try the segments tool directly.
- If a data point isn't returned after a targeted retry, move on — label it "N/A" or "Not disclosed."
- Never fabricate data. If the tools don't return a number, do not estimate from training knowledge.
User-specified comps: If the user provided comparable companies, query financials and multiples for each comp explicitly. If no comps were provided, use whatever peer data the tools return, or identify peers from the company's sector using the competitors tool.
Optional context from the user: Listen for additional context the user provides naturally. If they mention who the acquirer is ("we're looking at this for our platform"), what they sell ("we sell data analytics to banks"), or who the likely buyers are ("this would be interesting to Salesforce or Microsoft"), incorporate that context into the relevant synthesis sections (Strategic Fit, Conversation Starters, Deal Angle). Don't prompt for this information — just use it if offered.
Private company handling:
CIQ includes private company data, so query the same way. However, expect sparser results. When generating for a private company:
- Skip: stock price, 52-week range, beta, stock performance, consensus estimates, trading comps
- Lean into: business overview, relationships, ownership structure, whatever financials are available
- Note "Private Company" prominently in the header
第一步: 创建中间文件目录:
bash
mkdir -p /tmp/tear-sheet/使用S&P Global MCP工具(也称为Kensho LLM-ready API)。Claude可访问用于获取财务数据、公司信息、市场数据、一致预期、收益会议记录、并购活动和业务关联方的结构化工具。每个参考文件的查询计划描述了各章节所需获取的数据——请将其映射到对话中可用的S&P Global工具。
每次查询完成后,立即将获取的数据写入参考文件查询计划中指定的中间文件。 请勿延迟写入——写入磁盘的数据可避免长对话中的上下文丢失问题。
查询策略:
每个参考文件包含4-6个数据检索步骤的查询计划,这些是起点而非严格约束。优先保证数据完整性,而非减少调用次数:
- 始终获取4个财年的财务数据,尽管仅展示3年的数据。第四年(最早年份)的数据用于计算第一个展示年份的同比收入增长率。如果缺失该数据,最早年份的增长率将显示为"N/A"——这会被视为数据缺失,而非设计选择。
- 严格按照查询计划执行,使用匹配数据需求的S&P Global工具。
- 如果工具调用返回不完整结果,尝试使用替代工具或更精准的查询。例如,如果公司摘要未包含业务板块详情,可直接调用板块工具。
- 如果经过针对性重试仍未获取到数据点,可跳过——标注为"N/A"或"未披露"。
- 绝不编造数据。如果工具未返回数值,请勿通过训练知识估算。
用户指定的可比公司: 如果用户提供了可比公司,请明确查询每家公司的财务数据和估值倍数。如果未提供可比公司,使用工具返回的同行数据,或通过竞争对手工具从公司所属行业中识别同行。
用户提供的可选上下文: 留意用户主动提供的额外上下文。如果他们提到收购方("我们正在为平台评估此标的")、自身业务("我们为银行提供数据分析服务")或潜在买家("Salesforce或Microsoft可能对此感兴趣"),请将这些上下文融入相关分析章节(战略契合度、对话切入点、交易角度)。无需主动询问此类信息——如果用户提供则直接使用。
私营公司处理方式:
CIQ包含私营公司数据,因此查询方式与上市公司相同。但预期结果会更简略。为私营公司生成财务摘要时:
- 跳过:股价、52周区间、贝塔系数、股票表现、一致预期、可比公司交易分析
- 重点展示:业务概述、关联方、股权结构、可获取的财务数据
- 在页眉中显著标注"私营公司"
Step 3b: Calculate Derived Metrics
步骤3b:计算衍生指标
After all data collection is complete and intermediate files are written, compute all derived metrics in a single dedicated pass. This is a calculation-only step — no new MCP queries.
Read all intermediate files back into context, then compute:
- Margins: Gross Margin %, EBITDA Margin %, FCF Margin %, Operating Margin %
- Growth rates: YoY revenue growth, YoY segment revenue growth, YoY EPS growth
- Efficiency ratios: FCF Conversion (FCF/EBITDA), R&D as % of Revenue, Capex as % of Revenue
- Capital structure: Net Debt (Total Debt − Cash & Equivalents), Net Debt / EBITDA
- Segment mix: Each segment's revenue as % of consolidated total revenue (use consolidated revenue as denominator per Data Integrity Rule 8)
Validation (moved from Arithmetic Validation): During this calculation pass, enforce all arithmetic checks:
- Margin calculations: Verify EBITDA Margin = EBITDA / Revenue, Gross Margin = Gross Profit / Revenue, etc. If the computed margin doesn't match the raw numbers, use the computation from raw components.
- Growth rates: Verify YoY growth = (Current − Prior) / Prior. Don't rely on pre-computed growth rates if you have the underlying values.
- Segment totals: If showing revenue by segment, verify segments sum to total revenue (within rounding tolerance). If they don't, omit the total row rather than publishing inconsistent math.
- Percentage columns: Verify "% of Total" columns sum to ~100%.
- Valuation cross-checks: If you show both EV and EV/Revenue, verify EV / Revenue ≈ the stated multiple.
If a validation fails: attempt recalculation from raw data. If still inconsistent, flag the metric as "N/A" rather than publishing incorrect numbers. Quiet math errors in a tear sheet destroy credibility.
Write results to with columns:
/tmp/tear-sheet/calculations.csvmetric,value,formula,componentsExample rows:
metric,value,formula,components
gross_margin_fy2024,72.4%,gross_profit/revenue,"9524/13159"
revenue_growth_fy2024,12.3%,(current-prior)/prior,"13159/11716"
net_debt_fy2024,2150,total_debt-cash,"4200-2050"完成所有数据收集并写入中间文件后,单独执行一次衍生指标计算流程。此步骤仅进行计算——不发起新的MCP查询。
将所有中间文件读入上下文,然后计算:
- 利润率: 毛利率%、EBITDA利润率%、自由现金流利润率%、营业利润率%
- 增长率: 收入同比增长率、板块收入同比增长率、每股收益同比增长率
- 效率比率: 自由现金流转换率(自由现金流/EBITDA)、研发费用占收入比、资本支出占收入比
- 资本结构: 净债务(总债务−现金及等价物)、净债务/EBITDA
- 板块占比: 各板块收入占合并总收入的比例(根据数据完整性规则8,使用合并收入作为分母)
验证(从算术验证部分迁移至此): 在计算过程中,强制执行所有算术检查:
- 利润率计算: 验证EBITDA利润率 = EBITDA / 收入,毛利率 = 毛利润 / 收入等。如果计算出的利润率与原始数据不符,使用原始数据重新计算。
- 增长率: 验证同比增长率 = (当期值−上期值)/上期值。如果已有基础数据,绝不依赖预计算的增长率。
- 板块总计: 如果展示板块收入,验证板块收入之和与合并收入是否一致(在四舍五入误差范围内)。如果不一致,省略总计行,避免发布不一致数据。
- 百分比列: 验证"占总计比例"列之和约为100%。
- 估值交叉验证: 如果同时展示企业价值和企业价值/收入倍数,验证企业价值 / 收入 ≈ 标注的倍数。
如果验证失败:尝试使用原始数据重新计算。如果仍然不一致,将该指标标注为"N/A",避免发布错误数据。财务摘要中的隐性计算错误会严重损害可信度。
将结果写入 ,列名:
/tmp/tear-sheet/calculations.csvmetric,value,formula,components示例行:
metric,value,formula,components
gross_margin_fy2024,72.4%,gross_profit/revenue,"9524/13159"
revenue_growth_fy2024,12.3%,(current-prior)/prior,"13159/11716"
net_debt_fy2024,2150,total_debt-cash,"4200-2050"Step 3c: Verify Data Files
步骤3c:验证数据文件
Before generating the document, verify that all intermediate files are present and populated.
Read each intermediate file via separate read operations and print a verification summary:
=== Tear Sheet Data Verification ===
company-profile.txt: ✓ (12 fields)
financials.csv: ✓ (36 rows)
segments.csv: ✓ (8 rows)
valuation.csv: ✓ (5 rows)
calculations.csv: ✓ (18 rows)
earnings.txt: ✓ (populated)
relationships.txt: ⚠ MISSING
peer-comps.csv: ✓ (12 rows)
================================Soft gate: If any file expected for the current audience type is missing or empty, print a warning but continue. The tear sheet handles missing data gracefully with "N/A" and section skipping. However, the warning ensures visibility into what data was lost.
Critical rule: The files — not your memory of earlier conversation — are the single source of truth for every number in the document. When generating the DOCX in Step 4, read values from the intermediate files. Do not rely on conversation context for financial data.
生成文档前,验证所有中间文件是否存在且已填充数据。
通过单独的读取操作读取每个中间文件,并打印验证摘要:
=== 财务摘要数据验证 ===
company-profile.txt: ✓ (12个字段)
financials.csv: ✓ (36行)
segments.csv: ✓ (8行)
valuation.csv: ✓ (5行)
calculations.csv: ✓ (18行)
earnings.txt: ✓ (已填充)
relationships.txt: ⚠ 缺失
peer-comps.csv: ✓ (12行)
================================软限制: 如果当前受众类型所需的任何文件缺失或为空,打印警告但继续执行。财务摘要可通过"N/A"和跳过章节的方式优雅处理缺失数据。但警告可确保团队了解哪些数据丢失。
核心规则:文件——而非对话上下文记忆——是文档中所有数据的唯一来源。 在步骤4生成DOCX文档时,从中间文件中读取数据,绝不依赖对话上下文获取财务数据。
Step 4: Format as DOCX
步骤4:格式化为DOCX文档
Read for docx creation mechanics (docx-js via Node). Apply the Style Configuration above plus the section-specific formatting in the reference file.
/mnt/skills/public/docx/SKILL.mdPage length defaults (user can override):
- Equity Research: 1 page (density is the convention)
- IB / M&A: 1-2 pages
- Corp Dev: 1-2 pages
- Sales / BD: 1-2 pages
If content exceeds the target, each reference file specifies which sections to cut first.
Output filename:
Example:
[CompanyName]_TearSheet_[Audience]_[YYYYMMDD].docxNvidia_TearSheet_CorpDev_20260220.docxSave to and present to the user.
/mnt/user-data/outputs/阅读了解docx创建机制(通过Node.js使用docx-js)。应用上述样式配置以及参考文件中的章节特定格式。
/mnt/skills/public/docx/SKILL.md默认页面长度(用户可自定义):
- 股票研究:1页(行业惯例为高密度内容)
- IB / 并购:1-2页
- 企业发展:1-2页
- 销售 / 业务发展:1-2页
如果内容超过目标长度,每个参考文件指定了优先删减顺序。按照指定顺序删减内容——绝不将字体大小或边距缩小到模板最小值以下。删减顺序为严格的优先级:完全删减第1个章节后再考虑删减第2个章节。
输出文件名:
示例:
[CompanyName]_TearSheet_[Audience]_[YYYYMMDD].docxNvidia_TearSheet_CorpDev_20260220.docx保存到并交付给用户。
/mnt/user-data/outputs/Data Integrity Rules
数据完整性规则
These override everything else:
- S&P Global tools are the only source for financial data. Do not fill gaps with training knowledge — it may be stale or wrong.
- Label what you can't find. Use "N/A" or "Not disclosed" rather than omitting a row silently.
- Dates matter. Note the fiscal year end or reporting period. Don't assume calendar year = fiscal year. Market data (stock prices, market cap) should include an "as of" date.
- Don't mix reporting periods. If you have FY2023 revenue and LTM EBITDA, label them distinctly.
- Prefer MCP-returned fields over manual computation. If the S&P Global tools return a pre-computed field (e.g., net debt, EBITDA, FCF), use that value directly rather than computing it from components. Only compute derived metrics manually when the tools do not return the field. This reduces discrepancies.
- Ensure consistency across tear sheet types. If generating multiple tear sheets for the same company (e.g., equity research and IB/M&A in the same session), the same underlying data points must produce identical values across all outputs. Net debt, revenue, EBITDA, margins, and growth rates must match exactly. Do not re-query or re-compute independently per report — reuse the same retrieved values.
- Never downgrade known transaction values. If the M&A tools return a deal value for a transaction, that value must appear in the output. Do not replace a known deal value with "Undisclosed." Use "Undisclosed" only when the tools genuinely return no value for a transaction.
- Use consolidated revenue as the denominator for segment percentages. When computing "% of Total" for segment tables, divide each segment's revenue by consolidated total revenue (as reported on the income statement), not by the sum of segment revenues. The sum of segments often exceeds consolidated revenue due to intersegment eliminations. Using consolidated revenue ensures percentages align with the total revenue figure shown elsewhere in the document.
- Always include forward (NTM) multiples when available. If the tools return both trailing and forward valuation multiples, both must appear in the output. Forward multiples are the primary valuation reference for equity research, IB/M&A, and corp dev audiences. Never show only trailing multiples when forward data is available.
- No S&P Global tool returns executive or management data. Do not populate management names, titles, or biographical details from training data — this violates Rule 1 and produces stale information. If a management section appears in a template, omit it entirely. Ownership structure (institutional holders, insider %, PE sponsor) may be included only if returned by the tools — gate with "data permitting."
以下规则优先级高于所有其他设置:
- 仅可从S&P Global工具获取财务数据。 绝不通过训练知识填补数据缺口——训练知识可能过时或错误。
- 标注无法获取的数据。 使用"N/A"或"未披露"标注,而非静默省略行。
- 日期至关重要。 标注财年结束日期或报告期。请勿假设日历年等同于财年。市场数据(股价、市值)需标注"截至日期"。
- 请勿混合报告期。 如果同时拥有FY2023收入和LTM EBITDA,需明确标注差异。
- 优先使用MCP返回的字段,而非手动计算。 如果S&P Global工具返回预计算字段(例如净债务、EBITDA、自由现金流),直接使用该值,而非通过组件计算。仅当工具未返回该字段时,才手动计算衍生指标。这可减少数据差异。
- 确保不同类型财务摘要的一致性。 如果为同一公司生成多个财务摘要(例如同一会话中生成股票研究和IB/并购类摘要),相同基础数据点在所有输出中必须完全一致。净债务、收入、EBITDA、利润率和增长率必须完全匹配。请勿为每份报告独立重新查询或计算——复用已获取的数据。
- 绝不降低已知交易价值的展示优先级。 如果并购工具返回某交易的价值,该值必须显示在输出中。绝不将已知交易价值替换为"未披露"。仅当工具确实未返回交易价值时,才使用"未披露"。
- 计算板块占比时使用合并收入作为分母。 计算板块表格的"占总计比例"时,将各板块收入除以合并总收入(根据利润表数据),而非板块收入之和。由于板块间抵消,板块收入之和通常会超过合并收入。使用合并收入可确保百分比与文档中其他位置展示的总收入一致。
- 如果有数据,务必包含远期(NTM)估值倍数。 如果工具同时返回历史和远期估值倍数,两者必须都显示在输出中。远期估值倍数是股票研究、IB/并购和企业发展受众的主要估值参考。当有远期数据时,绝不仅展示历史倍数。
- S&P Global工具不返回高管或管理层数据。 绝不通过训练数据填充管理层姓名、职位或传记信息——这违反规则1且信息可能过时。如果模板包含管理层章节,需完全省略。股权结构(机构持股、内部人持股比例、PE投资方)仅当工具返回数据时才可包含——需标注"视数据情况而定"。
Intermediate File Rule
中间文件规则
All data retrieved from MCP tools must be persisted to structured intermediate files before document generation. These files — not conversation context — are the single source of truth for every number in the document.
Setup: At the start of Step 3, create the working directory:
mkdir -p /tmp/tear-sheet/Write-after-query mandate: After each MCP query step completes, immediately write the retrieved data to the appropriate intermediate file(s). Do not wait until all queries finish. Each reference file's query plan specifies which file(s) to write after each step.
File schemas:
| File | Format | Columns / Structure | Used By |
|---|---|---|---|
| Key-value text | name, ticker, exchange, HQ, sector, industry, founded, employees, market_cap, enterprise_value, stock_price, 52wk_high, 52wk_low, shares_outstanding, beta, ownership | All |
| CSV | | All |
| CSV | | ER, IB, CD |
| CSV | | ER, IB, CD |
| CSV | | ER |
| Structured text | Quarter, date, key quotes, guidance, key drivers | ER, IB, Sales |
| Structured text | Customers, suppliers, partners, competitors — each with descriptors | IB, CD, Sales |
| CSV | | ER, IB, CD |
| CSV | | IB, CD |
| CSV | | All (written in Step 3b) |
Abbreviations: ER = Equity Research, IB = IB/M&A, CD = Corp Dev, Sales = Sales/BD.
Not every audience type uses every file — the reference files define which query steps apply. Files not relevant to the current audience type need not be created.
Raw values only. Intermediate files store raw values as returned by the tools. Do not pre-compute margins, growth rates, or other derived metrics in these files — that happens in Step 3b.
Page budget enforcement: Each reference file specifies a default page length and a numbered cut order. If the rendered document exceeds the target, apply cuts in the order specified — do not attempt to shrink font sizes or margins below the template minimums. The cut order is a strict priority stack: cut section 1 completely before touching section 2.
从MCP工具获取的所有数据必须先保存到结构化中间文件,再生成文档。这些文件——而非对话上下文——是文档中所有数据的唯一来源。
设置: 在步骤3开始时创建工作目录:
mkdir -p /tmp/tear-sheet/查询后立即写入规则: 每次MCP查询完成后,立即将获取的数据写入对应的中间文件。请勿等待所有查询完成后再写入。每个参考文件的查询计划指定了每次查询后应写入的文件。
文件结构:
| 文件 | 格式 | 列 / 结构 | 使用受众 |
|---|---|---|---|
| 键值对文本 | name, ticker, exchange, HQ, sector, industry, founded, employees, market_cap, enterprise_value, stock_price, 52wk_high, 52wk_low, shares_outstanding, beta, ownership | 所有 |
| CSV | | 所有 |
| CSV | | 股票研究、IB、企业发展 |
| CSV | | 股票研究、IB、企业发展 |
| CSV | | 股票研究 |
| 结构化文本 | Quarter, date, key quotes, guidance, key drivers | 股票研究、IB、销售 |
| 结构化文本 | Customers, suppliers, partners, competitors — 每个类别包含描述信息 | IB、企业发展、销售 |
| CSV | | 股票研究、IB、企业发展 |
| CSV | | IB、企业发展 |
| CSV | | 所有(在步骤3b中写入) |
缩写: 股票研究 = ER, IB = IB/并购, 企业发展 = CD, 销售 = 销售/BD。
并非所有受众类型都需要所有文件——参考文件定义了适用的查询步骤。与当前受众类型无关的文件无需创建。
仅存储原始值。 中间文件仅存储工具返回的原始值。请勿在这些文件中预先计算利润率、增长率或其他衍生指标——这些计算在步骤3b中执行。
页面长度限制执行: 每个参考文件指定了默认页面长度和编号删减顺序。如果生成的文档超过目标长度,按照指定顺序删减内容——绝不将字体大小或边距缩小到模板最小值以下。删减顺序为严格的优先级队列:完全删减第1个章节后再考虑删减第2个章节。
Content Quality Rules
内容质量规则
- Rewrite every narrative section for the audience. The CIQ company summary is an input, not an output. Each audience type needs a different description: concise and thesis-oriented for equity research, pitchbook prose for IB, product-focused for Corp Dev, plain language for Sales/BD. Never paste the CIQ summary verbatim into any tear sheet.
- Differentiate earnings highlights by audience. The same earnings call produces different takeaways for different readers. Equity research wants segment-level performance and consensus beat/miss. IB wants margin trajectory and strategic commentary. Sales/BD wants strategic themes that create conversation angles. Do not reuse the same bullets across tear sheet types.
- Synthesis sections are the differentiator. Strategic Fit Analysis, Integration Considerations, Conversation Starters, and Business Overview paragraphs are where the tear sheet earns its value. These sections require analytical reasoning that connects data points into a narrative — listing company names without context is not synthesis.
- Flag pending divestitures in segment tables. If a company has announced a pending divestiture of a segment or business unit, add a footnote or parenthetical to the segment table noting the pending transaction (e.g., "Mobility* — *Pending divestiture, expected mid-2026"). For Corp Dev and IB/M&A tear sheets, include a one-line note below the segment table showing pro-forma revenue and revenue mix excluding the divested segment. This helps the reader evaluate the "go-forward" business without doing the math themselves.
- 针对受众重写所有叙述性章节。 CIQ公司摘要仅作为输入,而非输出。每类受众需要不同的描述:股票研究需简洁且突出核心论点,IB需符合推介文档风格,企业发展需聚焦产品,销售/业务发展需使用通俗易懂的语言。绝不直接将CIQ摘要复制到任何财务摘要中。
- 针对受众区分收益亮点。 同一场收益会议对不同读者的价值点不同。股票研究关注板块表现和是否符合一致预期,IB关注利润率趋势和战略评论,销售/业务发展关注可用于对话的战略主题。绝不在不同类型的财务摘要中复用相同的项目符号内容。
- 分析章节是核心价值所在。 战略契合度分析、整合注意事项、对话切入点和业务概述段落是财务摘要的核心价值体现。这些章节需要分析推理能力,将数据点整合为连贯的叙述——仅列出公司名称而无上下文不属于分析。
- 在板块表格中标注待剥离业务。 如果公司已宣布将剥离某业务板块或部门,需在板块表格中添加脚注或括号标注待剥离交易(例如:"Mobility* — *待剥离,预计2026年中期完成")。对于企业发展和IB/并购类财务摘要,需在板块表格下方添加一行说明,展示剥离后的预计收入和收入结构。这可帮助读者无需自行计算即可评估"未来业务"情况。
Arithmetic Validation
算术验证
→ Arithmetic validation is now enforced in Step 3b (Calculate Derived Metrics). All margin calculations, growth rates, segment totals, percentage columns, and valuation cross-checks are validated during the dedicated calculation pass, before document generation begins. See Step 3b for the full validation checklist.
→ 算术验证现在在步骤3b(计算衍生指标)中强制执行。 所有利润率计算、增长率、板块总计、百分比列和估值交叉验证都在文档生成前的专门计算步骤中完成。完整验证清单详见步骤3b。",