User Manual

Executive Advisor Board – WordPress Plugin

1. Overview and Purpose

What Is the Executive Advisor Board Plugin?

The Executive Advisor Board is an AI-powered WordPress plugin that simulates a comprehensive executive evaluation of business proposals. It provides feedback from eight different C-suite perspectives to help you prepare for real-world Board of Directors meetings.

Key Features

• Eight Executive Perspectives – Get feedback from CEO, CFO, CHRO, CMO, COO, CTO, General Counsel, and Independent Board Member
• Comprehensive Proposal Form – 60+ structured fields across 12 categories
• Real-time Processing – Watch as each agent evaluates your proposal
• Consolidated Summary – Automatic synthesis highlighting agreements and conflicts
• Interactive Chat – Ask follow-up questions about the evaluation
• PDF Export – Download formatted reports for sharing
• Secure Storage – Encrypted data storage with configurable retention

Who Should Use This Plugin?

User Type	Use Cases
Directors & Senior Managers	Prepare proposals for executive leadership or board presentations
Product Managers	Develop business cases for new products or features
Entrepreneurs	Refine investor presentations and business proposals
Strategy Professionals	Test strategic initiatives before formal review
Anyone Learning Executive Thinking	Understand how C-suite executives evaluate proposals

2. Accessing the Plugin

Prerequisites

1. WordPress Account – You must have a user account on the WordPress site
2. Login Credentials – Your username and password
3. Web Browser – Modern browser (Chrome, Firefox, Safari, Edge)

Accessing the Evaluation Page

Objective: Navigate to the Executive Advisory Board evaluation interface

Steps:

1. Open your web browser
2. Navigate to: https://it-influentials.com/virtual-board-of-directors/
3. If you see a login prompt:
   • Click the Log In button
   • Enter your username and password
   • Click Submit
   • You’ll be redirected back to the evaluation page

Expected Result: You see the Executive Advisory Board interface with eight executive agent badges displayed at the top and the proposal form below.

3. The Proposal Form

Form Overview

The proposal form is organized into 12 thematic sections covering all aspects of a business proposal. Each section contains multiple fields related to its theme.

Form Navigation

The form uses a tabbed navigation system at the top that allows you to move between sections:

• Click any section tab to jump to that section
• The active section is highlighted
• You can navigate in any order – sections don’t need to be completed sequentially
• All entries are preserved as you navigate between sections

Field Types and Behavior

All fields in the form are:

• Text areas – Multi-line input fields that expand as you type
• Optional – Marked with “(optional)” label
• Described – Each has a description explaining what to include
• Preserved – Your entries are saved as you navigate sections

Understanding Field Labels and Descriptions

Each field has three components:

1. Label – The name of the information requested (e.g., “Proposal Summary”)
2. Optional indicator – All fields show “(optional)”
3. Description – Guidance on what to include (appears as placeholder and below field)

4. Understanding Form Sections

The form is divided into 12 sections. This reference explains what each section covers and what information to include.

Section 1: Proposal Basics

Purpose: Establish the fundamental “what” and “why” of your proposal

Key Fields:

Field	What to Include
Proposal Summary	2-3 sentence overview of what you’re proposing and why
Proposal Owner	Name and role of the person responsible for this initiative
Contributors	Names and roles of key team members or collaborators
Decision Needed	Specific approval or decision being requested (e.g., “Approve $500K budget for Q2 launch”)
Problem / Opportunity	The business problem you’re solving or opportunity you’re capturing
Time Horizon	Timeline for the initiative (e.g., “6-month project with 12-month payback”)

Section 2: Strategic Context

Purpose: Connect your proposal to broader business strategy and priorities

Key Fields:

• Strategic Priority Mapping – How this aligns with company’s top 3-5 priorities
• Success Metrics – Concrete, measurable targets that define success
• Customer / Stakeholder Impact – Who benefits and how (be specific)
• Alternatives Considered – Other options evaluated, including doing nothing
• Opportunity Cost – What you won’t be able to do if you pursue this

Section 3: Financial Model

Purpose: Demonstrate financial viability and return on investment

Key Fields:

Field	What CFOs Look For
Cost Breakdown	One-time vs. recurring costs, broken down by category (labor, technology, etc.)
Headcount Plan	Number of people, roles, fully-loaded costs (salary + benefits + overhead)
Revenue / Savings Drivers	How you’ll make or save money, with unit economics if applicable
Adoption Assumptions	Expected uptake rates, growth curves, conversion funnels
Cash Flow Timing	When money goes out (costs) and when it comes in (benefits)
Payback Period	How long until cumulative benefits exceed cumulative costs
ROI / NPV / IRR	Return on investment metrics (percentage), net present value, internal rate of return
Budget Request	Specific dollar amount and funding source being requested

Section 4: Customer & Market

Purpose: Validate customer need and market opportunity

Key Fields:

• Target Segments – Specific customer personas or market segments
• Customer Problem / JTBD – The job-to-be-done from customer perspective
• Customer Evidence – Data from interviews, surveys, usage analytics, etc.
• Market Context – Market size, growth rate, category dynamics
• Competitive Landscape – Direct competitors, substitutes, and the status quo
• Value Proposition – One-sentence differentiation statement
• Differentiation – Why customers would choose you; why now is the right time
• Proof Points – Credible claims you can make (awards, testimonials, metrics, etc.)

Section 5: Execution Plan

Purpose: Demonstrate you can actually deliver this proposal

Key Fields:

• Scope (In) – What is explicitly included in this initiative
• Scope (Out) – What is explicitly NOT included (very important!)
• Plan + Milestones – Key deliverables with dates and owners
• Timeline – Overall duration and critical dates
• Critical Path – The dependencies that determine your timeline
• Resourcing – People, time allocation, budget, vendors/partners
• Go/No-Go Gates – Decision points where you assess progress and decide whether to continue

Section 6: Technical Considerations

Purpose: Address technical feasibility and architecture

Key Fields:

Field	What CTOs Evaluate
Current State	Existing systems, infrastructure, and technical capabilities
Proposed Solution	High-level technical approach and architecture
Build vs Buy	Rationale for building custom vs. purchasing/integrating existing solutions
Dependencies / Integrations	APIs, data sources, third-party services, internal systems
Data Considerations	Data quality, access controls, migration needs, retention policies
Security / Privacy / Compliance	Security controls, privacy requirements, regulatory compliance
Reliability / SLOs	Service level objectives, availability targets, failure modes
Scalability	Expected load, growth assumptions, scaling strategy
Tech Debt Impact	Does this create or reduce technical debt?

Section 7: Legal & Compliance

Purpose: Identify legal risks and compliance requirements

Key Fields:

• Jurisdictions – Geographic regions where this applies (matters for regulations)
• Regulated Areas – Industries or activities with regulatory requirements
• Data Flow – How data is collected, stored, processed, shared
• Third Parties – Vendors, partners, subprocessors involved
• Contracts Impacted – Customer, vendor, or partner agreements affected
• New Agreements Needed – MSAs, DPAs, SOWs, or other contracts required
• IP Considerations – Open source licenses, content rights, patents
• Approvals Needed – Sign-offs from Procurement, Security, Privacy, Board, etc.

Section 8: Organization & Talent

Purpose: Address people, skills, and organizational readiness

Key Fields:

• Teams Impacted – Which groups will experience change in their work
• Hiring Plan – New roles needed, timeline for hiring, role definitions
• Capacity Plan – What current work stops or slows to make room for this
• Skills Gaps – Difference between current capabilities and what’s needed
• Enablement Plan – Training, coaching, or upskilling approach
• Leadership Readiness – Who leads this? Do they have the capability?

Section 9: Operating Model

Purpose: Define how work gets done and who’s accountable

Key Fields:

• Decision Rights – Who decides what? (Use RACI framework if helpful)
• Process Changes – How current workflows, approvals, or procedures change
• Systems / Tools Changes – Technology or tool changes required
• Support Model – Who provides ongoing support? What are SLAs?
• Performance Measures – How success shows up in individual/team performance

Section 10: Change Management

Purpose: Plan for organizational adoption and transition

Key Fields:

• Change Narrative – The story you’ll tell employees about why this change is happening
• Communications Plan – Who hears what message, through what channel, at what time
• Adoption Plan – How you’ll drive usage/adoption (training, incentives, measurement)
• Employee Experience Impact – Effects on workload, morale, engagement, culture

Section 11: Risk & Support

Purpose: Identify risks and mitigation strategies

Key Fields:

• Risks + Mitigations – Top 3-5 risks across all dimensions with specific mitigation plans
• Support Needed – What help you need from HR, leadership, legal, finance, engineering, etc.
• Kill / Pivot Criteria – Conditions that would cause you to stop or significantly change direction

Section 12: Board Considerations

Purpose: Address governance-level questions

Key Fields:

• Context – Additional background for board-level understanding
• Strategic Intent – The larger strategic purpose this serves
• Expected Upside – Best-case scenario outcomes
• Reversibility – How easy/hard is it to reverse this decision?
• Benchmarks – Industry comparisons or precedents
• Ownership – Who owns ongoing execution after approval?
• Reporting Plan – How you’ll report progress to leadership/board

5. Submitting Your Proposal

Pre-Submission Checklist

Before submitting, verify:

1. ✓ At least one field is filled in (though more is better)
2. ✓ Key fields like Proposal Summary and Decision Needed are complete
3. ✓ Financial information includes specific numbers where applicable
4. ✓ You’ve reviewed the GDPR privacy notice
5. ✓ You’re ready to wait 3-5 minutes for results

Submission Process

Objective: Submit your proposal for AI evaluation

Prerequisites:

• You are logged in
• You have filled in at least one field
• You understand your data will be processed by AI

Steps:

1. Scroll to the bottom of the form
2. Read the GDPR privacy notice
3. Check the consent checkbox:
   • This confirms you consent to AI processing of your data
   • Submission is not possible without checking this box
4. Click the Submit for Evaluation button
5. The button will show a loading state (“Processing…”)
6. The form will disappear and the progress screen will appear

Expected Result: The progress screen displays showing the status of each executive agent.

What Happens After Submission

1. Data Encryption – Your proposal is encrypted and stored securely
2. Agent Queue – Each of the 8 executive agents is queued for processing
3. Sequential Processing – Agents process your proposal one at a time
4. Result Storage – Each evaluation is saved as it completes
5. Consolidation – After all agents finish, a summary is generated
6. Display – Results appear on your screen automatically

6. The Evaluation Process

Understanding the Progress Screen

After submission, you’ll see a progress screen with:

• Progress Bar – Visual indicator of overall completion percentage
• Agent Status List – Each executive agent with current status:
  • Pending – Waiting to start
  • Processing – Currently evaluating your proposal
  • Complete – Evaluation finished
  • Failed – Error occurred (rare)
• Status Messages – Text updates about current activity

Processing Time Expectations

Scenario	Typical Duration
Short proposal (few fields filled)	2-3 minutes
Medium proposal (half the fields)	3-4 minutes
Comprehensive proposal (most fields)	4-6 minutes
High system load	Add 1-2 minutes

Troubleshooting Processing Issues

If processing seems stuck:

1. Wait a bit longer – Some evaluations take up to 10 minutes on complex proposals
2. Check your internet connection – Lost connection may prevent updates
3. Refresh the page – Results may be ready even if not displayed
4. Check back later – Processing continues even if you close the page
5. Clear browser cache – See Troubleshooting Guide for instructions

7. Understanding the Executive Agents

Each agent represents a different C-suite executive perspective. Understanding what each role cares about helps you interpret their feedback.

CEO – Chief Executive Officer

Primary Focus: Strategic alignment, overall viability, company priorities

Key Questions CEOs Ask:

• Does this advance our top strategic priorities?
• Why now? What changes if we wait?
• What’s the opportunity cost?
• Do we have the resources and capability to execute?
• Is this the best use of our time and capital?

CEO Decision Framework:

• Approve – Clearly aligned with strategy, well-resourced, strong ROI
• Approve with Modifications – Good idea but needs adjustments to scope, timeline, or approach
• Revise and Resubmit – Interesting but needs more development, data, or refinement
• Decline – Wrong priority, wrong timing, or insufficient return

CFO – Chief Financial Officer

Primary Focus: Financial analysis, ROI, budget impact, cash flow

Key Questions CFOs Ask:

• What’s the total cost (one-time and recurring)?
• What’s the expected return and over what period?
• Are the financial assumptions realistic?
• How does this impact our budget and cash position?
• What are the financial risks?

What CFOs Look For:

• Specific numbers backed by credible assumptions
• Clear understanding of unit economics
• Realistic revenue or savings projections
• Consideration of downside scenarios
• Appropriate payback periods and ROI hurdle rates

CHRO – Chief Human Resources Officer

Primary Focus: People implications, organizational readiness, talent needs

Key Questions CHROs Ask:

• Do we have the right people and skills?
• How will this affect employees?
• What’s the change management plan?
• Are managers ready to lead this?
• What’s the impact on culture and engagement?

What CHROs Care About:

• Realistic assessment of organizational capacity
• Clear hiring plans with timelines
• Thoughtful change management approach
• Training and enablement programs
• Impact on employee experience

CMO – Chief Marketing Officer

Primary Focus: Customer validation, market positioning, competitive landscape

Key Questions CMOs Ask:

• Is there real customer demand for this?
• How do we differentiate from competitors?
• What’s our go-to-market strategy?
• Do we have evidence this will resonate with customers?
• How does this strengthen our brand?

What CMOs Look For:

• Direct customer evidence (interviews, surveys, tests)
• Clear value proposition
• Understanding of competitive alternatives
• Realistic adoption assumptions
• Strong go-to-market plan

COO – Chief Operating Officer

Primary Focus: Operational feasibility, execution planning, resource allocation

Key Questions COOs Ask:

• Can we actually execute this?
• Is the timeline realistic?
• Are dependencies and risks managed?
• Do we have the operational capacity?
• What’s the operational support model?

What COOs Care About:

• Detailed execution plans with clear milestones
• Realistic timelines considering dependencies
• Clear accountability and decision rights
• Process definitions and operating model
• Risk mitigation strategies

CTO – Chief Technology Officer

Primary Focus: Technical assessment, architecture, technology decisions

Key Questions CTOs Ask:

• Is this technically feasible?
• Are we making sound technology choices?
• How does this affect our tech stack and architecture?
• What are the security and scalability implications?
• Does this create or reduce technical debt?

What CTOs Look For:

• Sound technical approach and architecture
• Consideration of build vs. buy tradeoffs
• Clear dependency mapping
• Security and compliance requirements addressed
• Scalability and reliability planning

GC – General Counsel

Primary Focus: Legal, regulatory, and compliance considerations

Key Questions GCs Ask:

• What are the legal risks?
• Are we compliant with applicable regulations?
• Do we have appropriate contracts in place?
• How is data being handled?
• What intellectual property issues exist?

What GCs Care About:

• Clear understanding of regulatory landscape
• Appropriate data handling and privacy controls
• Contract requirements and approvals
• IP ownership and licensing clarity
• Risk mitigation for legal exposures

Board – Independent Board Member

Primary Focus: Strategic governance, risk evaluation, oversight

Key Questions Board Members Ask:

• Is this aligned with our long-term strategy?
• Are we taking appropriate risks?
• Is management capable of executing this?
• How does this create shareholder value?
• What oversight and reporting is needed?

What Board Members Look For:

• Strategic thinking and long-term perspective
• Appropriate balance of risk and reward
• Strong executive sponsorship
• Clear metrics and reporting plan
• Consideration of stakeholder interests

8. Reviewing Your Results

Results Screen Overview

When all evaluations are complete, the results screen displays four main components:

1. Executive Summary – Consolidated view synthesizing all feedback
2. Decision Overview – Grid showing each executive’s decision
3. Detailed Agent Evaluations – Full text of each agent’s analysis
4. Action Buttons – Options to copy, download, chat, or start new evaluation

Understanding the Executive Summary

The Executive Summary is automatically generated after all agents complete. It includes:

Overall Assessment

High-level view of whether the proposal is ready for approval, needs work, or should be reconsidered.

Consensus Points

Areas where all or most executives agree. These represent the strongest or weakest aspects of your proposal.

Decision Conflicts

Where executives disagree. These are particularly valuable because they highlight:

• Important tradeoffs you need to address
• Different perspectives on risk
• Areas needing more detail or clarity

Critical Concerns

The most important issues raised across all evaluations. These are typically:

• Blockers that prevent approval
• Major risks without clear mitigation
• Missing information executives need

Key Recommendations

Specific, actionable suggestions for improving the proposal.

Overall Recommendation

Aggregate view with confidence level.

Interpreting the Decision Overview

The Decision Overview shows each executive’s verdict at a glance:

Decision	What It Means	Next Steps
Approve	Executive supports moving forward as proposed	Read their feedback for any additional suggestions
Approve with Modifications	Supportive but has specific changes to request	Review their recommendations carefully – these are usually important
Revise and Resubmit	Needs significant changes before they can approve	This is major feedback – you likely need to rework portions of the proposal
Decline	Does not support the proposal	Read carefully to understand if this is fixable or a fundamental problem

Reading Detailed Agent Evaluations

Click on any agent to expand their full evaluation. Each typically includes:

Section 1: Decision and Rationale

Their verdict with key reasoning points specific to their role perspective.

Section 2: Strengths

What you did well. This reinforces strong thinking and shows what to preserve in revisions.

Section 3: Concerns

Issues, gaps, or risks they identified. This is critical feedback to address.

Section 4: Recommendations

Specific suggestions for improvement, often with examples or specifics.

Section 5: Questions

Things that need clarification or more information.

Identifying Patterns in Feedback

As you review multiple agent evaluations, look for:

• Repeated themes – If multiple agents mention the same concern, it’s critical
• Unique insights – Sometimes one agent spots something others missed
• Conflicting advice – Competing concerns that require balancing
• Quick wins – Easy-to-address issues multiple agents noted
• Fundamental problems – Deep issues that require rethinking the approach

9. Using the Advisory Chat

When to Use Chat

The Advisory Chat feature allows you to ask follow-up questions after receiving your evaluation. Use it to:

• Clarify feedback you don’t fully understand
• Explore “what if” scenarios and modifications
• Get more detail on specific recommendations
• Understand how to resolve conflicting advice
• Test potential solutions to concerns raised

Accessing the Chat

Objective: Start a conversation about your evaluation results

Steps:

1. After viewing your results, look for the chat panel (typically in the lower right)
2. If collapsed, click to expand it
3. You’ll see a welcome message
4. Type your question in the input field at the bottom
5. Click the send button or press Enter
6. The AI will respond based on all the evaluation context

Expected Result: You receive a conversational response that references the evaluation feedback.

Effective Chat Questions

Good Questions:

• “The CFO and COO disagreed on timeline feasibility. How can I address both concerns?”
• “Can you elaborate on the CMO’s concern about customer evidence?”
• “If I added a pilot phase, how would that affect the CEO’s decision?”
• “What would be the top 3 changes to make this more likely to be approved?”
• “The GC mentioned data flow concerns. Can you be more specific about what information is needed?”

Less Effective Questions:

• “What did the CEO say?” (Just re-read the evaluation)
• “Is this a good proposal?” (Too vague)
• “Tell me about my proposal” (You already have the evaluations)
• “What should I do?” (Too broad – be specific about what you want to understand)

Chat Limitations

The chat feature:

• Cannot access information outside your evaluation – It only knows what was in your proposal and the agent feedback
• Cannot provide company-specific guidance – It doesn’t know your company’s internal context, politics, or culture
• Cannot guarantee outcomes – Following chat suggestions doesn’t ensure approval from real executives
• Has session limits – After many back-and-forth messages, you may need to start a new evaluation

10. Exporting and Saving Results

Copying Results to Clipboard

Objective: Copy all evaluation text for pasting into another document

Steps:

1. From the results screen, locate the action buttons near the top
2. Click the Copy button (clipboard icon)
3. You’ll see a confirmation message
4. The entire evaluation (summary + all agent feedback) is now in your clipboard
5. Paste into your preferred application (Word, Google Docs, email, etc.)

Expected Result: Plain text version of all results is copied to your clipboard.

Downloading PDF Report

Objective: Generate and download a formatted PDF of your evaluation

Steps:

1. From the results screen, click the Download PDF button
2. Wait a few seconds while the PDF is generated
3. Your browser will prompt you to save the file
4. Choose a location and save

Expected Result: A formatted PDF file containing your entire evaluation report.

PDF Contents Include:

• Title page with submission date and ID
• Executive Summary
• Decision Overview table
• Each agent’s full evaluation with formatting
• Page numbers and headers for easy navigation

Retaining Access to Results

Your evaluation results are stored on the server for a limited time based on the site’s retention policy (typically 7-30 days). After this period, results are automatically deleted for privacy and storage management.

To preserve your results long-term:

• Download the PDF immediately after evaluation
• Copy the text to a local document
• Take screenshots of key findings
• Save the PDF to your company’s document management system

11. Best Practices

Writing Effective Proposals

Be Specific and Concrete

Instead of vague statements, provide concrete details:

• ❌ “This will improve revenue”
• ✅ “This will increase revenue by $2.3M annually (15% improvement) based on pilot results”

Show Your Work

Explain how you arrived at numbers and conclusions:

• ❌ “ROI: 200%”
• ✅ “ROI: 200% (Investment: $500K, 3-year benefit: $1.5M calculated from 15% efficiency gain across 200-person department at average $150K loaded cost)”

Acknowledge Uncertainty

Executives appreciate honest assessment of what you know and don’t know:

• ❌ Pretending you have all the answers
• ✅ “Customer demand is validated through 15 interviews. We’re less certain about competitive response, which is a key risk we’ll monitor.”

Address the “Why Now?” Question

Explain urgency and timing:

• ❌ “We should do this”
• ✅ “We should do this now because: (1) competitor launched similar feature in Q4, (2) we have a 6-month technical head start window, (3) sales team reports this as #2 customer request in last quarter”

Interpreting Feedback

Look for Themes Across Multiple Agents

If 3+ agents mention the same concern, it’s critical. If only one agent mentions it, consider their unique perspective.

Understand the Difference Between Fatal Flaws and Improvement Areas

• Fatal Flaws: Fundamental problems that prevent approval (e.g., “This violates regulatory requirements”)
• Improvement Areas: Things that would strengthen the proposal (e.g., “Consider adding a pilot phase”)

Pay Attention to Questions

When executives ask questions, they’re often indicating gaps in your proposal. These questions tell you what information you need to add.

Iterating on Your Proposal

Prioritize Critical Feedback

1. Address fatal flaws first (things that prevent approval)
2. Resolve concerns mentioned by multiple executives
3. Add missing information executives requested
4. Incorporate improvement suggestions
5. Refine based on individual agent recommendations

Document Your Changes

When revising, track what changed and why:

• Keep a “Version History” section noting major changes
• Reference which executive feedback prompted each change
• Note any tradeoffs you made

Re-Evaluate After Major Revisions

If you make substantial changes, submit the revised proposal for a new evaluation to ensure you’ve addressed concerns effectively.

Using Results for Real Board Presentations

Prepare for Anticipated Questions

Use agent questions and concerns to prepare your FAQ and anticipate board member questions.

Strengthen Weak Areas

Where agents identified concerns, gather additional data or develop stronger arguments before the real presentation.

Highlight Consensus Points

If all agents agreed something was strong, emphasize it in your real presentation.

Prepare for Conflicts

Where agents disagreed, prepare to address both perspectives and explain your reasoning for the tradeoffs you made.

Learning Over Time

Compare Evaluations

If you submit multiple proposals, compare them to identify patterns in your strengths and areas for improvement.

Study Different Executive Perspectives

Over time, you’ll develop intuition for how different roles think about problems. This makes you a more effective communicator.

Build a Personal Checklist

Create your own proposal checklist based on feedback you’ve received repeatedly.

12. Privacy and Security

How Your Data Is Used

When you submit a proposal:

1. Encryption – Your data is encrypted using AES-256 encryption before storage
2. Processing – Your proposal is sent to Claude AI (Anthropic) for evaluation
3. Storage – Results are stored in the WordPress database with encryption
4. Access – Only you and site administrators can access your submissions
5. Retention – Data is automatically deleted after the retention period (typically 7-30 days)

Third-Party Services

Anthropic Claude AI

Your proposal text is sent to Anthropic’s Claude AI service for evaluation. Anthropic’s data handling:

• Processes your data to generate evaluations
• Does not use your data to train their AI models
• Maintains security and privacy protections
• Subject to Anthropic’s terms of service and privacy policy

Review Anthropic’s policies at: https://www.anthropic.com/legal/privacy

What Data Is Collected

The plugin collects and stores:

• Proposal Content – All text you enter in the form
• User Information – Your WordPress user ID and username
• Evaluation Results – All agent feedback and consolidated summary
• Chat History – Messages you exchange with the advisory chat
• Metadata – Timestamps, processing times, token usage
• Audit Logs – Actions taken (submission, access, etc.)

Data Retention and Deletion

Automatic Deletion

Based on site configuration (typically 7-30 days), old submissions are automatically deleted including:

• Proposal data
• All evaluation results
• Chat history
• Associated files

Manual Deletion

If you want your data deleted before the automatic retention period:

1. Contact the site administrator
2. Provide your submission ID
3. Request deletion
4. Deletion typically occurs within 48 hours

Security Best Practices

For End Users:

• Don’t include highly sensitive information (trade secrets, personal data of individuals, confidential financial details) in proposals
• Use generic examples if discussing sensitive topics
• Log out when finished, especially on shared computers
• Download and delete results when no longer needed
• Don’t share your login credentials

Your Rights

As a user, you have the right to:

• Access – View all your submitted proposals and evaluations
• Export – Download your data in portable formats (PDF, text)
• Deletion – Request deletion of your data at any time
• Correction – Submit revised proposals if information was incorrect

Contact for Privacy Concerns

If you have privacy or security questions:

Email: peter@it-influentials.com
Subject: Executive Advisor Privacy Inquiry

Include:

• Your username
• Submission ID (if applicable)
• Specific concern or request

---

Additional Resources

• Getting Started Guide – Quick introduction for new users
• Troubleshooting Guide – Solutions to common problems
• FAQ – Frequently asked questions
• Glossary – Definitions of terms used in this documentation

---

Document Version: 1.0 | Last Updated: January 3, 2026
Plugin Version: 1.0.0
Support: peter@it-influentials.com