Cn Ib Deck Qc

CN IB Deck QC

Review a deck as a banker preparing it for circulation. Treat automated hits as leads, not final conclusions.

Principles

1. Protect the client first: wrong entity, stale transaction terms, unsupported claims, and other-project residue are release blockers.
2. Reconcile facts before polishing layout.
3. Inspect both the editable file and rendered slides; XML or text extraction cannot prove visual correctness.
4. Preserve the user's template, slide geometry, and house style unless asked to redesign.
5. Report each issue with slide number, exact location, evidence, severity, and a concrete correction.
6. Separate confirmed defects from items that require professional judgment.

Workflow

1. Establish the review baseline

Confirm:

• intended audience and circulation status;
• client, transaction, valuation date, and reporting period;
• approved source documents and data cut-off date;
• governing template and any required disclaimers;
• whether the task is a full review or a delta review after refresh.

Do not assume that an old deck is the source of truth.

2. Scan the editable deck

Read references/deck-qc-checklist.md, then run:

bashCopy code
python3 scripts/scan_pptx.py input.pptx --output deck-issues.csv

To detect names or terms from another project, create a temporary text file with one forbidden term per line and run:

bashCopy code
python3 scripts/scan_pptx.py input.pptx --forbidden-terms forbidden.txt --output deck-issues.csv

The script checks text-accessible placeholders, unit case, duplicate punctuation, superlatives, small font settings, and supplied forbidden terms. It does not validate numbers against sources and does not replace rendering.

3. Reconcile high-risk content

Check every slide containing:

• transaction structure, timetable, valuation, fundraising, share capital, or ownership;
• historical or forecast financials;
• market share, ranking, growth, capacity, customers, or order backlog;
• legal, regulatory, tax, accounting, or eligibility conclusions;
• credentials, tombstones, league tables, or comparable transactions.

Trace figures and claims to a source with page, table, cell, period, unit, and calculation where applicable. Use cn-ib-source-verifier or cn-ib-cross-document-check when the task requires source re-performance or cross-document reconciliation.

4. Render and inspect every slide

Inspect thumbnails for the whole deck, then full-size slides for all exceptions. Check:

• clipping, overflow, overlap, missing glyphs, and broken charts;
• alignment, margins, spacing, type hierarchy, and inconsistent colors;
• chart axes, legends, labels, units, footnotes, and totals;
• low-resolution images, distorted logos, and stale screenshots;
• repeated slide titles, missing page numbers, and appendix navigation;
• density, readability, and whether the takeaway matches the evidence.

Review hidden slides, speaker notes, comments, embedded files, and document properties when circulation risk warrants it.

5. Classify and close issues

Use references/issue-severity.md. Maintain an issue log with:

textCopy code
issue_id, slide, location, severity, category, finding,
evidence, proposed_fix, owner, status, reviewer

Re-render changed slides and confirm closure. Do not mark an issue closed merely because the editable text changed.

Output contract

Deliver:

1. release recommendation: BLOCK, CONDITIONAL, or READY;
2. prioritized issue log, with P0/P1 items first;
3. cross-slide consistency findings;
4. source and freshness gaps;
5. visual-review findings;
6. scope limitations and checks not performed.

Never represent an automated scan as a complete deck review.