# Render review checklist — for a machine with Microsoft Office (2026-10-11)

Purpose: the only check no seat here could run. Package integrity is already measured and filed; this is the visual opening. Do not edit the files; record what you see and send the filled table back.

## Files under review
| file | md5 |
|---|---|
| `DRAFT_Makki_Company_Portal_Deck_v3.1_v36-b11.pptx` | `0cb53c66cc48cea4221828d0323ce93a` |
| `DRAFT_Makki_One-Hour_Walkthrough_v3_v36-b11.docx` | `450a81b1ed5f9a448ad0987e19ff6d29` |
| rendering of record for the deck: `DRAFT_Makki_Company_Portal_Deck_v3_v36-b11.pdf` (30 pages, md5 `a9181f29ee55da28f6a2d8e5f78b2997`, in the 2026-10-10_2236 delivery) | |
| rendering of record for the guide: `DRAFT_Makki_One-Hour_Walkthrough_v3_v36-b11.pdf` (12 pages, md5 `51c5f1647d32f236479bf1ec2ba65abf`, same delivery) | |

## Step 0 — confirm the bytes, then the package (2 minutes)
1. Check the md5 of each file against the table above.
2. Run the validator (Python 3, standard library only, nothing to install):
   ```
   python3 office_package_check.py DRAFT_Makki_Company_Portal_Deck_v3.1_v36-b11.pptx
   python3 office_package_check.py DRAFT_Makki_One-Hour_Walkthrough_v3_v36-b11.docx
   ```
   Expected: output identical to `office_package_check_v3.1.out` and `office_package_check_docx.out`, last line `PKG_VERDICT ok`, exit code 0. If it differs, stop and report the difference; the file did not arrive intact.

## Step 1 — open the PPTX in PowerPoint (10 minutes)
| # | check | record |
|---|---|---|
| 1.1 | File opens with **no** "PowerPoint found a problem / repair" prompt | yes / no, and the prompt text if any |
| 1.2 | Slide count is 30; Notes pane shows text on every slide | counts |
| 1.3 | Fonts: no substitution warning; title and body fonts look like the PDF | yes / no, font names if substituted |
| 1.4 | Images: every slide that carries a screenshot in the PDF shows it here; none shows a red X or blank box | list any slide number with a missing image |
| 1.5 | Slide 16: the enlarged screenshot is legible when projected (labels readable at the back of a room) | yes / no |
| 1.6 | Text overflow: no text box runs off its slide; compare the reworded slides 4, 6, 7, 16, 23, 26, 28, 29, 30 against the same PDF pages | list slide numbers that differ |
| 1.7 | Slide Show view: step through all 30; no slide looks different from its PDF page beyond font rendering | list differences |
| 1.8 | Optional control: open the original `DRAFT_Makki_Company_Portal_Deck_v3_v36-b11.pptx` (md5 `66ffe827f7f6d3dd4cbe5a3f99e1b5e3`) the same way. Does PowerPoint prompt to repair it? | yes / no. This tells us whether the 29 dangling declarations ever mattered to Office |

## Step 2 — open the DOCX in Word (5 minutes)
| # | check | record |
|---|---|---|
| 2.1 | File opens with no repair prompt | yes / no |
| 2.2 | Headings, the six-role sections and the tables render; page count close to the 12-page PDF | page count |
| 2.3 | Wording spot-check: pages 10 and 12 of the PDF (the security limits and the QuickBooks "owner authorises, never shares credentials" wording) read the same in the DOCX | yes / no |

## Step 3 — report
- Send back this file with the "record" column filled, plus the PowerPoint and Word version used, and screenshots of anything that differs from the PDF.
- If any check in 1.1, 1.4, 1.6 or 2.1 fails, the PDFs remain the rendering of record and the editable file goes back for a versioned repair (v3.2 PPTX or v3.1 DOCX); the delivered files are never edited in place.
- If everything passes, the limitation "Office rendering unverified" is closed with this report as the evidence, dated and attributed to the person who ran it.