Consultation Plan Template Word

DOCUMENT CONTROL BLOCK

• Document ID: SOP-TR-OPS-409
• Effective Date: October 24, 2023
• Version: 3.2.1
• Review Cadence: Annual
• Classification: Internal Operations / Institutional Standard

---

1. Executive Summary & Scope

1.1 Purpose

This Standard Operating Procedure (SOP) defines the mandatory protocol for sourcing, drafting, validating, and deploying the Consultation Plan Template Word (.docx) across Template Registry operations. The objective is to eliminate structural drift, enforce typographic and semantic hierarchy, ensure WCAG 2.1 AA accessibility compliance, and guarantee seamless data integration with downstream project management ecosystems.

1.2 Scope

This procedure applies to all operational architects, client-success leads, technical writers, and administrative personnel tasked with generating, modifying, or distributing client consultation frameworks. Adherence to this SOP is mandatory for all external-facing and internal advisory documentation originating from Template Registry.

---

2. Prerequisites & Required Tools

2.1 Software & Hardware Requirements

• Word Processing Engine: Microsoft Word for Microsoft 365 (Version 2308 or later) or LibreOffice Writer (v7.6+ strictly for fallback conversions).
• Format Baseline: Microsoft Word OpenXML Spreadsheet/Document format (.docx). Legacy .doc formats are strictly prohibited.
• Accessibility Engine: Built-in Microsoft Accessibility Checker.
• Version Control: Git-based template repository (git.templateregistry.internal/ops/consultation-plans).

2.2 Compliance & Governance Standards

• ISO/IEC 27001 Information Security Management (for client data placeholders).
• WCAG 2.1 Level AA Accessibility Guidelines (applied to document structure, contrast ratios, and alternative text).
• Template Registry Style Guide v4.0 (Typography: Arial/Calibri pairing, 1.15 line spacing, 6pt post-paragraph spacing).

---

3. Roles & Responsibilities (RACI Matrix)

• Responsible (R): The role that performs the activity.
• Accountable (A): The role with final approval authority.
• Consulted (C): The role providing advisory input.
• Informed (I): The role notified of status changes.

---

4. Step-by-Step Procedure

Phase 1: Repository Retrieval & Environment Preparation

• 1.1 Authenticate to the Template Registry internal version control system using enterprise SSO credentials.
• 1.2 Navigate to the baseline repository: git.templateregistry.internal/ops/consultation-plans.
• 1.3 Execute a pull command to retrieve the latest master .docx build artifact (Consultation_Plan_Master_v3.2.docx).
• 1.4 Move the retrieved file to your local working directory and rename it using the institutional naming convention: YYYYMMDD_[ClientName]_Consultation_Plan.docx.
• 1.5 Open the file in Microsoft Word, navigate to File > Options > Save, and verify that "Embed fonts in the file" is checked.

Phase 2: Metadata & Variable Injection

• 2.1 Open the Document Properties panel via File > Info > Properties > Advanced Properties.
• 2.2 Populate the Title field with the precise engagement title.
• 2.3 Populate the Manager field with the designated Accountable (A) resource identifier.
• 2.4 Locate all programmatic XML/Content Control tags within the document body (indicated by gray bracketed fields such as {{Client_Name}}, {{Effective_Date}}, and {{Scope_Summary}}).
• 2.5 Overwrite default token strings with verified project parameters sourced from the CRM master record. Ensure no raw bracket syntax remains uncompiled.

Phase 3: Structural & Semantic Assembly

• 3.1 Verify the presence and integrity of the mandatory sections: Executive Summary, Stakeholder Matrix, Discovery Milestones, Risk Mitigation, and Sign-off Block.
• 3.2 Highlight all headings and ensure they are assigned native Word Styles (Heading 1, Heading 2, Heading 3) rather than manual font sizing and bolding.
• 3.3 Format all tabular data utilizing the native Word table style Table Grid Accent 1. Ensure table headers include the "Repeat as header row at the top of each page" property.
• 3.4 Insert institutional callout boxes for operational warnings using single-cell borderless tables shaded in 5% light neutral tint with a 3pt left border in primary brand hex (#003366).

Phase 4: Quality Verification & Accessibility Audit

• 4.1 Execute the Microsoft Accessibility Checker via Review > Check Accessibility. Resolve all errors and warnings related to missing alt text, irregular heading sequences, or low-contrast text.
• 4.2 Run the built-in Spelling and Grammar utility (F7) and ensure zero unresolved flags.
• 4.3 Verify that all hyperlinks use descriptive anchor text (e.g., "Access the Client Portal" instead of "Click Here" or raw URLs).
• 4.4 Save the finalized document state and prepare for formal validation.

---

5. Quality Assurance & Verification

5.1 Key Metric Thresholds

• Accessibility Score: 100% compliance verified via Word Accessibility Checker.
• Stylistic Drift: 0% deviation from Template Registry Typography and Color Palette specs.
• Metadata Completeness: 100% of Content Control fields mapped and verified against CRM source.

5.2 Common Pitfalls

• Pitfall 1: Using manual bolding and font size adjustments for headers instead of native Paragraph Styles, which breaks automated table-of-contents generation and screen reader navigation.
• Pitfall 2: Failing to embed custom fonts, causing layout shifts and character substitution when opened on external client endpoints.
• Pitfall 3: Leaving placeholder tags ({{...}}) uncompiled, resulting in acute professional leakage during client delivery.

5.3 Audit Checklist

• Document properties completely filled out.
• Native heading styles utilized exclusively.
• Zero uncompiled placeholder tags remaining.
• Accessibility checker reports zero errors.
• File saved in .docx format with fonts embedded.

---

6. Troubleshooting FAQ

Q1: The document accessibility checker flags "No Table Header Row Specified" for a complex multi-tier matrix table. How do I resolve this?

A: Right-click the top row of the table, select Table Properties, navigate to the Row tab, and ensure the checkbox for "Repeat as header row at the top of each page" is selected. Additionally, ensure the first row is explicitly designated as a header row in the table design ribbon to satisfy screen reader semantics.

Q2: Content Control fields ({{...}}) fail to update automatically when generating multiple consultation plans from the master template. What is the root cause?

A: This occurs when Content Controls are instantiated as static text rather than mapped XML nodes. To remediate, access the Developer tab, open the XML Mapping Pane, locate the Template Registry schema, and bind the specific document nodes to the corresponding content controls prior to distribution.

Q3: Client endpoints report missing custom typography elements, causing text wrapping errors upon file receipt. How is this prevented?

A: The document was saved without font embedding enabled. Re-open the source file, navigate to File > Options > Save, check the box for "Embed fonts in the file", select "Embed only the characters used in the document" to control file size, and re-export the master .docx artifact.