AI won't follow our document template

You're going to build my company's DOCUMENT STRUCTURE BLOCK: a reusable instruction block I'll paste into any AI chat that drafts our documents, so the AI follows our house structure without being reminded.

Interview me first, one question at a time. Where I don't know, propose a sensible default and move on:
1. Which 3 to 5 document types do we produce most, and what is each one for (proposals, client reports, SOWs, board memos)?
2. For each type, what sections do readers expect, in what exact order? Paste an example document if you have one and infer the skeleton from it.
3. How does each document open: straight in, or a summary first? What do we call that opening section?
4. What is mandatory in every document of that type (a scope note, pricing terms, a legal line, next steps) and what is optional?
5. What does the AI most often get wrong about our structure today: reorders sections, drops parts, invents headings, over-explains?

Then output my DOCUMENT STRUCTURE BLOCK as one copy-paste block containing: (a) one line of company context, (b) for each document type, its ordered skeleton with the exact section names, (c) the opening convention and the mandatory elements per type, (d) hard rules: never reorder sections, never invent a heading, never drop a mandatory section, and ask if a required input is missing rather than inventing it, (e) a closing self-audit that checks the draft against the correct skeleton before output and appends "Structure check: pass" or lists what is out of order or missing.

Keep it under 400 words so it fits any project-instructions field. After you output it, name the three ways the AI is most likely to still drift from our structure and how the block prevents each.

CONTEXT: Fenwick & Cole is a boutique management consultancy. Documents we produce: client proposals, engagement reports, statements of work, board memos.

SKELETONS (follow the exact order; never reorder, never invent a heading):
- Proposal: In short, Context, Approach, Team, Timeline, Commercials, Next steps.
- Engagement report: In short, Context, Findings, Recommendations, Next steps, Appendices.
- Statement of work: Summary, Scope, Deliverables, Timeline, Fees, Assumptions, Sign-off.
- Board memo: Recommendation, Background, Options, Risks, Ask.

OPENING: every client-facing document opens with a one-paragraph summary under its first heading ("In short" or "Summary"). Board memos open with the recommendation, not the background.

MANDATORY: proposals and SOWs always carry a Commercials/Fees section and a Next steps/Sign-off section. Reports always carry numbered Recommendations. Never drop a mandatory section; if you lack the input for one, ask me rather than inventing it.

SELF-AUDIT: before output, check the draft against the correct skeleton for its type. Append one line: "Structure check: pass", or list any section that is out of order, missing, or invented.