top of page
An illustration of computer screen with several SOPs.

Linda Spiller | Portfolio
Standards, SOPs, and SOWs

  • Project: Portfolio samples
  • Role: Technical Writer and Technical Editor
  • Type:  Sample technical documentation for LinkedIn and personal portfolio
  • Format: Online and PDF
  • Portfolio tools: Canva and Microsoft Word
    ​
  • Workplace tools for similar projects: Confluence, SharePoint, Office 365, and Miro​​​​​​

Overview

With a legal background and over a decade of experience representing clients before federal agencies, I bring a compliance-focused approach to creating SOPs, SOWs, guidelines, policies, and best practices. I’ve drafted privacy guidelines and translated complex requirements into clear statements. 

​

For more than eight years, I’ve led technical writing projects. To guide teams in both Agile and Waterfall environments, I've written internal style guides, procedures, and training materials with a strong emphasis on accessibility and clarity. 

​

 When product teams need to comply with legal and regulatory standards required for regulated industries, my legal experience will provide me with the research and analytical skills to quickly comply with industry standards and regulatory requirements. 

Website carousel for LinkedIn​

​

Key tasks I did:

  • Researched Good Documentation Practices (GDocP).

  • Organized research notes into an outline. 

  • Created a carousel in Canva.  

​​

What I learned: 

  • Learned about the latest GDocP practices. 

  • I updated my understanding of technical writing practices for the manufacturing, pharmaceutical, and regulated device industries.

  • Added to my design skillset and explored a new use for Canva. 

​​​

Impact: 

  • A scientist in pharmaceutical manufacturing and an FDA Regulatory and Compliance Officer reposted my post, leading to over 2,500 impressions. Many of the favorable responses were also from technical writers.  â€‹

Standard Operating Procedure portfolio sample​

​

Key tasks I did:

  • Researched topics suitable for a portfolio sample of a Standard Operating Procedure, since I can't share internal documents from my current or prior roles. 

  • Brainstormed ideas from past experiences and research. Asked Gemini and Copilot some targeted questions to expand the rationale and regulatory purposes of SOPs.

  • Prepared draft using Word (as a replacement for Confluence or other internal CMS).​

​

What I learned:

  • Learned more about recordkeeping and compliance tasks that I want to implement in future guidelines or SOPs for PII management.

​​

Impact: 

  • Created a sample SOP that I can add to my portfolio that follows a structure that is suitable for many workplaces. 

Statement of Work template​

​

Key tasks I did:

  • Researched typical formats and rationale for content in a Statement of Work, particularly those used for IT work. 

  • Researched possible topics for a future portfolio sample: loud services, managed services, systems integration, security services, IoT training, website design, or technical documentation content. 

  • Created an outline of topics and categories needed for a typical SOW. 

  • Created final draft of template to use for future projects using Word.

​

What I learned:

  • Learned that state and federal agencies often have templates or samples that follow their preferred formats. Templates used for non-governmental work vary depending on the type of SOW used. 

​​

Impact: 

  • Created a template that is suitable for a variety of IT projects. 

bottom of page