← Week 6 portalMaster file in the engagement folder:
my-work/week-6/fund-level/library/process/engagement-playbook-v1.md

Engagement playbook: climate disclosure for a PE manager (v1)

Status: draft from the blank-shell scout, not reviewed. The library is the product; the draft is a byproduct. This file says how an engagement runs, what the client gives at each stage, and where the harness does the work versus the human.

1. The split

The harness carriesThe human carries
Framework mapping (register and requirement files)Scope and materiality cuts
Drafting against the register and data tableConversations with ESG leads, CFOs, operations
Interview prep packs (from register gaps)Interpretation of what the evidence means
Documentation (content index, methodology notes)Sign-off and the client relationship
QA execution (qa/run_qa.py, logged every run)Judgment on anything QA flags as NA or FAIL

2. Lifecycle, stage by stage

#StageClient givesHarness doesOutputGate
1IntakeLP list and the requests they sent; fund and company list with sector, size, revenue, locations; the entity facts the screen needs; any existing reportsConverts the facts into entity-facts-v1.json, runs engine/run_applicability.py, drafts the scope note from its resultScope note; applicability result; settings file (report date, period, declared year_status, any earlier partial disclosures)Owner signs scope
2MaterialityThe prior materiality assessment (it exists; do not redo it)Converts it to concept ids in settings.material_topics; flags register concepts it does not coverMaterial-topic list; gap listOwner signs the cut
3ReferencesNothing (Year 1 build) / nothing new (Year 2)Year 1: confirm framework files are current (re-check-by dates). Year 2: re-verify each file past its dateLibrary at a known versionCheck: no framework past its re-check date
4DataEmissions inventory, revenue, physical-risk model output, transition and initiatives view, governance documents (charters, minutes)Converts each into data-table rows with source, factor version and grade; recomputes register statusData table; filled register; coverage matrix and gap listQA Q01, Q02, Q18 pass
5InterviewsTime with ESG lead, CFO, operations per companyengine/build_prep_packs.py writes one pack per company: material gaps first, then gaps a framework that applies to that company needs, then grade C figures to upgrade, then missing applicability facts; each with question, who to ask and whyInterview notes, turned into rows or narrative inputsEach gap closed or recorded as a disclosed gap
6DraftQualification sentence; any authorisation to name a companyWrites narrative sections with figure tokens only; runs the engineLP report skeleton; content index per frameworkQA full run
7QANothingRuns all checks; logs every run to qa/qa-log-v1.jsonlQA result fileAll PASS or explained NA
8Sign-offNamed reviewers at the GP and every portfolio companyBuilds the sign-off list from settings; checks every company contact is on itSigned report; frozen filesOwner and client sign

3. Drafting conventions

4. QA protocol

5. Version discipline

6. Hours per stage: estimate, Year 1 and Year 2

These are the scout's estimates for a GP with about ten companies, unverified: from model knowledge; no engagement has been timed against them.

StageYear 1 (hours)Year 2 (hours)Why it shrinks, or does not
Intake63Applicability rules exist; only changes in LP list or thresholds need work
Materiality62Re-confirm the prior cut; change only if the portfolio changed
References206Year 1 builds and verifies framework files; Year 2 re-verifies past their re-check date. Does not reach zero: regulation moves
Data3018Data-table shape and source mapping are known; new and exited companies still cost full effort; prior-year reconciliation is new work
Interviews2014Prep packs come from the gap list; conversations themselves do not get shorter
Draft168Year 2 starts from last year's narrative and the same tokens
QA63Checks are scripts; time goes on judging FAILs. Year 2 adds two live prior-year checks
Sign-off87People time; barely shrinks
Total11261About 45% less, mostly from references, drafting and QA

7. Re-run note

Next year: copy last year's case folder; save last year's published data table as prior-published-v1.csv; update settings-v1.json (report date, period, factor version, and prior_report with the published file, its period end, explanations for changes over 10% and any restatement reasons); add this year's rows and keep last year's as comparatives (make_year2_cases.py shows the shape); re-check every framework file past its re-check date; run outputs/run-all.sh; resolve every FAIL before drafting further.

Portfolio edition: Kith Climate cohort case, fictional client.