G

Georgina Weston

Refuge In Literacy UK Position Profile

Marketing and PR Director Position Profile at Refuge In Literacy UK

This profile documents the responsibilities, decision frameworks, systems, and practices associated with my Marketing and PR Director position within a literacy-focused community interest company. It provides structured context around public-facing platform stewardship, content governance, accessibility-led delivery, and stakeholder coordination within a volunteer-supported environment.

The content is factual, stable, and intended for consistent reference across communications, platform, and governance discussions rather than as a chronological narrative of activity.

Marketing and PR Director Position Overview

Position
Marketing and PR Director

Organisation
Refuge In Literacy UK C.I.C.

Dates
August 2024 to Present

Position Type
Volunteer / Director-Level, Remote

Domain
Communications systems, literacy resources, non-profit platforms, public-facing web systems

Marketing and PR Director Position Summary

As Marketing and PR Director, I am responsible for communications systems, public-facing platforms, content governance, and online representation for a literacy-focused community interest company. My responsibilities include website architecture, content systems, accessibility-led design, stakeholder coordination, platform tooling, documentation, and ongoing system stewardship.

I operate within a remote, volunteer-supported environment serving educators, refuge centres, and community partners, with a strong emphasis on accessibility, trust, and consistency of public information.

Platform and Delivery Context

My work supports public-facing systems used by educators, refuge centres, volunteers, directors, and community partners. The delivery context is remote and volunteer-supported, with strong emphasis on accessibility, clarity, governance, and trust across platforms that require regular updates, consistent messaging, and practical long-term stewardship.

Digital Platform Architecture and Structure

Area Summary

  • This area focuses on how public-facing platforms are structured, organised, and maintained.
  • It covers website architecture, navigation, layouts, templates, and resource organisation.
  • It supports diverse users, including non-technical contributors and low-confidence users.
  • It requires accessibility-led thinking across structure as well as presentation.
  • It balances clarity and discoverability with long-term maintainability.
  • It often operates within CMS, hosting, and volunteer capacity constraints.
  • It treats site structure as a practical system for public use, not just visual presentation.
  • It prioritises sustainable platform foundations over unnecessary complexity.

Responsibilities

  • I design website architecture to support clarity, accessibility, and long-term use.
  • I structure navigation around user needs, literacy resources, and public information pathways.
  • I organise layouts and templates so content remains clear and consistent across pages.
  • I configure the CMS to support safe and manageable use by non-technical contributors.
  • I review structural decisions against accessibility expectations and usage patterns.
  • I organise literacy resources into repeatable sections that are easier to maintain.
  • I document platform structure and behavioural expectations for continuity.
  • I review and refine architecture over time as platform needs grow or change.

Decision Criteria

  • Accessibility for diverse user groups, including low-confidence and assisted users
  • Clarity of information hierarchy for educators and community partners
  • Ease of use for non-technical contributors
  • Scalability of platform structure as resources expand
  • Compliance with accessibility standards
  • Discoverability of literacy resources
  • Consistency of navigation and layout
  • Maintainability of site architecture over time

Constraints

  • Non-profit budget limitations
  • Volunteer contributor capacity
  • Existing hosting and CMS capabilities
  • Accessibility compliance requirements
  • Content approval and safeguarding processes
  • Remote coordination limitations
  • Wide device and browser diversity
  • Ongoing update requirements

Trade-Offs

  • Custom development versus CMS flexibility
  • Visual richness versus accessibility clarity
  • Structural depth versus navigation simplicity
  • Immediate publishing versus review cycles
  • Feature expansion versus stability
  • Platform consolidation versus tool diversity
  • Manual updates versus systemisation
  • Short-term fixes versus long-term structure

Prioritisation Thresholds

  • Accessibility before visual enhancement
  • Clarity before expansion
  • Maintainability over customisation
  • Resource discoverability before feature growth
  • Stability before optimisation
  • Contributor usability before complexity
  • Documentation before delegation
  • Compliance before experimentation

Delivery Alignment

  • I designed website architecture for clarity and accessibility.
  • I structured navigation around user needs and usage patterns.
  • I embedded accessibility considerations into layouts and templates.
  • I configured the CMS for safe use by non-technical contributors.
  • I organised literacy resources into clear, repeatable sections.
  • I documented platform behaviour.
  • I reviewed updates for consistency and compliance.
  • I reviewed structure periodically.

Tools and Systems

  • WordPress supports public-facing CMS delivery and structured content management.
  • Structured CMS workflows support repeatable publishing and page maintenance.
  • HTML5 supports accessible content structure and semantic page hierarchy.
  • CSS3 supports layout consistency and responsive presentation.
  • JavaScript supports practical interaction where appropriate.
  • Managed hosting services shape platform stability and update behaviour.
  • Organised content libraries support repeatable resource management.
  • Accessibility-led templates support consistent public-facing delivery.

Content Systems and Information Governance

Area Summary

  • This area focuses on how information is created, organised, reviewed, and maintained.
  • It covers templates, publishing rules, editorial consistency, and governance standards.
  • It supports volunteers who need clear structures for accurate content updates.
  • It balances readability, search visibility, and organisational consistency.
  • It requires sensitivity in language, structure, and public information handling.
  • It often depends on practical governance rather than heavy process overhead.
  • It treats content as a system that must remain usable, trustworthy, and maintainable.
  • It prioritises accuracy and clarity before scale or expansion.

Responsibilities

  • I define and apply content templates to support consistent publishing standards.
  • I maintain editorial structure across pages, resources, and public-facing updates.
  • I review language for accessibility, sensitivity, and clarity.
  • I organise literacy resources so they remain easy to locate and maintain.
  • I document publishing processes to support repeatable and safer updates.
  • I apply content changes systematically rather than through fragmented edits.
  • I maintain version consistency across related pages and references.
  • I uphold governance standards in how information is reviewed and represented.

Decision Criteria

  • Accuracy of published information
  • Consistency of messaging across channels
  • Ease of updating content by volunteers
  • Reusability of literacy resources
  • Alignment with organisational objectives
  • Accessibility of language and tone
  • Search visibility for public resources
  • Version control clarity

Constraints

  • Contributor technical confidence
  • Content review capacity
  • CMS taxonomy limitations
  • Approval and safeguarding workflows
  • Time availability
  • SEO tooling constraints
  • Language sensitivity requirements
  • Platform publishing permissions

Trade-Offs

  • Detailed guidance versus concise content
  • Centralised governance versus contributor autonomy
  • Immediate updates versus controlled review
  • SEO optimisation versus readability
  • Content depth versus navigation simplicity
  • Structured templates versus flexible layouts
  • Manual oversight versus trust-based publishing
  • Expansion versus maintainability

Prioritisation Thresholds

  • Accuracy before publication
  • Accessibility before optimisation
  • Consistent structure before volume
  • Clear ownership before delegation
  • Reusable templates before bespoke pages
  • Discoverability before expansion
  • Documentation before onboarding
  • Maintainability before scale

Delivery Alignment

  • I defined and applied content templates consistently.
  • I maintained editorial structure across pages.
  • I reviewed language for accessibility and clarity.
  • I organised literacy resources consistently.
  • I documented publishing processes.
  • I applied updates systematically.
  • I maintained version consistency.
  • I upheld governance standards.

Tools and Systems

  • Content templates support consistent public-facing publishing.
  • Editorial guidelines support language clarity and structural consistency.
  • WordPress supports content governance through structured page management.
  • CMS taxonomy supports resource grouping and discovery.
  • SEO-aware publishing practices support discoverability of public resources.
  • Shared review processes support safer content approval.
  • Version-aware references support continuity across related materials.
  • Organised documentation supports governance continuity over time.

End-User Support and Enablement

Area Summary

  • This area focuses on helping non-technical users and volunteers use platforms confidently.
  • It covers walkthroughs, guidance, documentation, and handover support.
  • It supports contributors with a wide range of technical confidence and experience.
  • It balances clarity and accessibility with practical time and support limits.
  • It aims to reduce avoidable dependency on technical intervention.
  • It treats support as part of long-term sustainability, not only reactive help.
  • It requires guidance that reflects real usage rather than abstract instructions.
  • It prioritises confidence and understanding before autonomy.

Responsibilities

  • I deliver walkthroughs where practical to support platform understanding.
  • I create and maintain guidance materials for recurring tasks and processes.
  • I answer questions and clarify platform usage for contributors and volunteers.
  • I update support materials as systems, workflows, or expectations change.
  • I assess contributor confidence before increasing independence or access.
  • I define support boundaries so responsibilities remain clear and practical.
  • I adapt explanations to suit different levels of technical confidence.
  • I review enablement outcomes to identify where further support is needed.

Decision Criteria

  • Confidence of non-technical users and volunteers
  • Clarity of guidance materials
  • Reduction of dependency on technical support
  • Ease of routine updates
  • Responsiveness to user questions
  • Transferability of knowledge
  • Alignment with actual platform usage
  • Long-term sustainability

Constraints

  • Volunteer availability
  • Wide user technical range
  • Communication channels
  • Documentation formats
  • Platform learning curves
  • Time limitations
  • Access permissions
  • Ongoing update frequency

Trade-Offs

  • Live walkthroughs versus written guides
  • Comprehensive training versus focused instruction
  • Immediate assistance versus scheduled support
  • Simplicity versus completeness
  • Standard guidance versus tailored explanations
  • Central support versus peer enablement
  • Speed versus confidence
  • Depth versus usability

Prioritisation Thresholds

  • User understanding before autonomy
  • Clear documentation before handover
  • Core platform knowledge before advanced features
  • Accessibility before thoroughness
  • Confidence before independence
  • Sustainability before expansion
  • Stability before delegation
  • Clarity before efficiency

Delivery Alignment

  • I delivered walkthroughs where appropriate.
  • I created and maintained guidance materials.
  • I addressed questions promptly.
  • I shared and updated documentation.
  • I assessed contributor confidence.
  • I defined support boundaries.
  • I clarified platform usage.
  • I reviewed enablement outcomes.

Tools and Systems

  • Shared guides support repeatable contributor enablement.
  • Templates support clearer step-by-step task guidance.
  • Google Workspace supports shared access to training materials and references.
  • WordPress admin pathways shape how contributors interact with the platform.
  • Remote communication tools support clarification and ongoing support.
  • Access controls support phased contributor independence.
  • Documentation formats support different learning preferences and confidence levels.
  • Structured support records support continuity across recurring questions.

Stakeholder Coordination and Communication

Area Summary

  • This area focuses on maintaining alignment across directors, volunteers, and partners.
  • It covers communication, expectation-setting, updates, and documented decisions.
  • It supports coordinated delivery in a remote environment with varied availability.
  • It balances responsiveness with clarity, predictability, and governance.
  • It often depends on asynchronous communication rather than live discussion alone.
  • It requires visibility of priorities, ownership, and agreed actions.
  • It treats communication as an operational system, not just an informal activity.
  • It prioritises shared understanding before acceleration.

Responsibilities

  • I maintain regular communication with directors, volunteers, and relevant partners.
  • I share updates clearly so priorities, changes, and expectations remain visible.
  • I document decisions to reduce ambiguity and preserve continuity.
  • I incorporate feedback appropriately within organisational and safeguarding boundaries.
  • I align communications with current priorities and delivery constraints.
  • I clarify expectations around ownership, timelines, and next steps.
  • I support coordination across remote contributors and organisational stakeholders.
  • I review communication outcomes to maintain trust and delivery confidence.

Decision Criteria

  • Alignment with organisational priorities
  • Clarity and tone of communication
  • Responsiveness to feedback
  • Transparency of decisions
  • Coordination across directors and partners
  • Predictability of updates
  • Documentation of agreements
  • Conflict mitigation

Constraints

  • Remote communication reliance
  • Director and volunteer availability
  • Decision-making timelines
  • Communication tooling
  • Capacity for synchronous meetings
  • Feedback turnaround
  • External partner dependencies
  • Safeguarding considerations

Trade-Offs

  • Synchronous meetings versus asynchronous updates
  • Speed versus alignment
  • Formal documentation versus informal agreement
  • Centralised decision-making versus shared input
  • Predictability versus flexibility
  • Detailed reporting versus concise summaries
  • Immediate resolution versus consultation
  • Autonomy versus oversight

Prioritisation Thresholds

  • Alignment before action
  • Documented decisions before implementation
  • Consistency before iteration
  • Clear ownership before delivery
  • Transparency before optimisation
  • Communication before acceleration
  • Predictability before flexibility
  • Shared understanding before expansion

Delivery Alignment

  • I maintained regular communication.
  • I shared updates clearly with stakeholders.
  • I documented decisions.
  • I incorporated feedback appropriately.
  • I aligned priorities.
  • I clarified expectations.
  • I supported delivery through coordination.
  • I maintained stakeholder confidence.

Tools and Systems

  • Google Workspace supports shared communication, notes, and coordination.
  • Remote communication tools support distributed discussion and updates.
  • Shared documents support recorded decisions and agreed actions.
  • Structured update formats support predictability across communication.
  • Director-level coordination practices support organisational alignment.
  • Access-controlled resources support appropriate information sharing.
  • Shared planning references support ownership and delivery visibility.
  • Documentation records support continuity across stakeholder discussions.

Digital Tooling and Brand Consistency

Area Summary

  • This area focuses on maintaining consistent visual and public-facing representation.
  • It covers templates, brand assets, platform suitability, and practical reuse.
  • It supports consistency across channels without overcomplicating production.
  • It balances clarity and accessibility with quality and recognition.
  • It often operates within volunteer design capacity and lightweight tooling constraints.
  • It prioritises reusable systems rather than one-off asset creation.
  • It treats brand consistency as part of trust and public reliability.
  • It supports long-term stewardship across multiple communication formats.

Responsibilities

  • I create and apply visual templates for repeatable use across public channels.
  • I follow brand guidelines consistently to protect recognition and cohesion.
  • I optimise assets for platform suitability, accessibility, and performance.
  • I consider accessibility in visual presentation and design decisions.
  • I maintain consistency across web, platform, and wider communications outputs.
  • I organise asset libraries so materials remain easier to find and reuse.
  • I document usage guidance for templates, assets, and design conventions.
  • I review assets periodically to keep materials current and aligned.

Decision Criteria

  • Consistency of visual identity
  • Ease of reuse across channels
  • Accessibility of assets
  • Alignment with organisational values
  • Efficiency of production
  • Maintainability of templates
  • Platform compatibility
  • Longevity of materials

Constraints

  • Existing brand assets
  • Tooling availability
  • Volunteer design capacity
  • Platform specifications
  • File size and performance limits
  • Approval processes
  • Storage constraints
  • Update frequency

Trade-Offs

  • Custom assets versus templates
  • Visual complexity versus clarity
  • Platform-specific designs versus reuse
  • Speed versus polish
  • Flexibility versus consistency
  • Centralised assets versus local copies
  • Expansion versus cohesion
  • Novelty versus recognition

Prioritisation Thresholds

  • Brand consistency before variation
  • Accessibility before enhancement
  • Reusable templates before bespoke designs
  • Clarity before detail
  • Performance before decoration
  • Maintainability before expansion
  • Recognition before novelty
  • Documentation before distribution

Delivery Alignment

  • I created and applied visual templates.
  • I followed brand guidelines consistently.
  • I optimised assets for platforms.
  • I considered accessibility in design.
  • I maintained consistency across channels.
  • I organised libraries.
  • I documented usage guidance.
  • I reviewed assets periodically.

Tools and Systems

  • Adobe Creative Suite supports visual asset development and refinement.
  • Canva supports efficient template-based design and collaborative asset creation.
  • Brand guidelines support consistency across public-facing outputs.
  • Shared media libraries support reusable and organised asset management.
  • Platform specifications shape format, size, and performance decisions.
  • Accessibility-led design practices support clearer visual communication.
  • Template systems support repeatable production across channels.
  • Usage guidance supports more consistent application by volunteers and collaborators.

System Maintenance and Reliability

Area Summary

  • This area focuses on keeping public-facing systems accurate, available, and dependable.
  • It covers updates, issue resolution, compliance checks, and maintenance routines.
  • It supports platforms that require frequent content changes and practical ongoing stewardship.
  • It balances visibility and improvement with stability and controlled change.
  • It often operates with limited monitoring tooling and volunteer maintenance capacity.
  • It prioritises reliability and accessibility over rapid feature expansion.
  • It treats maintenance as an essential operational practice rather than background admin.
  • It supports trust in public information through predictable platform care.

Responsibilities

  • I apply platform updates responsibly to reduce avoidable instability.
  • I review public content accuracy as part of ongoing maintenance activity.
  • I check accessibility compliance when updates or changes affect user experience.
  • I resolve issues promptly where they affect platform clarity, trust, or usability.
  • I document maintenance actions to preserve continuity and shared understanding.
  • I monitor system behaviour within the limits of available tooling and access.
  • I communicate relevant updates where platform changes affect wider use or expectations.
  • I review recurring issues to reduce preventable disruption over time.

Decision Criteria

  • Accuracy of public information
  • Availability of platforms
  • Security of systems
  • Compliance with accessibility standards
  • Predictability of updates
  • Ease of maintenance
  • Error visibility
  • Long-term sustainability

Constraints

  • Hosting provider capabilities
  • CMS update cycles
  • Volunteer maintenance capacity
  • Limited monitoring tooling
  • Access permissions
  • Time availability
  • Platform dependencies
  • External service reliability

Trade-Offs

  • Immediate updates versus scheduled maintenance
  • Feature additions versus stability
  • Manual checks versus automated alerts
  • Platform updates versus compatibility
  • Monitoring depth versus overhead
  • Centralised control versus shared access
  • Prevention versus remediation
  • Expansion versus reliability

Prioritisation Thresholds

  • Accuracy before visibility
  • Stability before enhancement
  • Accessibility compliance before optimisation
  • Core functionality before expansion
  • Error resolution before new changes
  • Maintainability before complexity
  • Reliability before experimentation
  • Documentation before updates

Delivery Alignment

  • I applied platform updates responsibly.
  • I reviewed content accuracy.
  • I checked accessibility compliance.
  • I resolved issues promptly.
  • I documented maintenance activities.
  • I monitored system behaviour.
  • I preserved reliability.
  • I communicated updates.

Tools and Systems

  • Managed hosting services shape maintenance processes and support boundaries.
  • WordPress update cycles shape timing and compatibility considerations.
  • CMS admin tooling supports direct maintenance and issue resolution.
  • Accessibility checks support compliance-led review during changes.
  • Shared maintenance records support continuity over time.
  • Platform dependencies shape update risk and sequencing.
  • Limited monitoring tooling requires practical manual oversight.
  • Access permissions shape who can maintain, review, and update systems.

Documentation and Knowledge Continuity

Area Summary

  • This area focuses on preserving useful knowledge across systems, contributors, and change.
  • It covers guides, templates, references, onboarding materials, and process continuity.
  • It supports non-technical audiences who need accessible and dependable documentation.
  • It balances clarity with completeness and accuracy with practical usability.
  • It often requires adapting explanations to different audiences and responsibilities.
  • It prioritises reusable materials over isolated one-off notes.
  • It treats documentation as part of continuity, governance, and sustainability.
  • It supports ongoing stewardship beyond any single contributor or change cycle.

Responsibilities

  • I produce and share guides that explain systems and processes clearly.
  • I document practical workflows so recurring tasks can be repeated with confidence.
  • I create templates that can be reused across common delivery needs.
  • I update documentation as systems, structures, and platform behaviour evolve.
  • I structure materials so they remain easy to navigate and reference.
  • I support onboarding through clear references and practical documentation.
  • I maintain shared materials to reduce avoidable knowledge loss.
  • I review documentation continuity so guidance remains aligned over time.

Decision Criteria

  • Clarity for non-technical audiences
  • Ease of reference
  • Alignment with live systems
  • Maintainability over time
  • Accuracy of instructions
  • Support for onboarding
  • Reusability of materials
  • Consistency across documentation

Constraints

  • Documentation tooling
  • Contributor access
  • Time availability
  • Update frequency
  • Platform-specific terminology
  • Review capacity
  • Version control practices
  • Audience diversity

Trade-Offs

  • Detail versus simplicity
  • Precision versus accessibility
  • Bespoke guides versus reusable templates
  • Immediate updates versus scheduled reviews
  • Centralised documentation versus distributed notes
  • Formal structure versus usability
  • Expansion versus maintenance
  • Speed versus accuracy

Prioritisation Thresholds

  • Clarity before completeness
  • Accessibility before formality
  • Accuracy before speed
  • Reusable templates before bespoke guides
  • Documentation before onboarding
  • Maintainability before expansion
  • Consistency before refinement
  • Knowledge continuity before optimisation

Delivery Alignment

  • I produced and shared guides.
  • I documented processes.
  • I created templates.
  • I applied updates as systems evolved.
  • I structured documentation clearly.
  • I supported onboarding.
  • I maintained references.
  • I ensured continuity.

Tools and Systems

  • Google Workspace supports shared documentation and collaborative references.
  • Shared guides and templates support repeatable organisational use.
  • Process documentation supports continuity across volunteers and directors.
  • Structured file organisation supports easier access and maintenance.
  • Onboarding materials support contributor confidence and practical handover.
  • Version-aware documentation practices support consistency over time.
  • Accessibility-led language supports broader usability of guidance materials.
  • Shared references support continuity beyond individual contributors.

Communications Systems, Tools, and Platforms

My core systems, tools, and platforms include WordPress and structured CMS workflows; HTML5, CSS3, and JavaScript; Adobe Creative Suite and Canva; Google Workspace; WCAG-informed practices; managed hosting services; organised content libraries; and shared guides, templates, and documentation resources that support accessible, consistent public-facing delivery.

Position Scope and Operating Environment

This position sits within a remote, volunteer-supported environment serving educators, refuge centres, community users, directors, and partners across non-profit public-facing platforms. The work depends on accessibility, clarity, governance, trust, and ongoing stewardship of systems that require regular content updates, consistent communication, and sustainable operational maintenance.