How to Attach Files to your Standard Operating Procedures

Standard operating procedures only work when they contain everything a team member needs to execute correctly. That means the SOP itself is rarely enough on its own. The supporting files, compliance forms, reference documents, training videos, and templates that sit alongside each procedure are what turn a static document into an executable, auditable process.

Attaching files directly to your SOPs eliminates the most common failure mode in process execution: someone following the steps but missing a critical resource because it lived in a different folder, a shared drive, or someone’s email inbox.

This guide covers why file attachments matter for SOPs, which file types you should attach, how to do it in Process Street, and best practices for keeping your attachments current and useful.

Why File Attachments Strengthen Your SOPs

An SOP without its supporting files is like a recipe without the ingredients list. The instructions might be clear, but the person executing them still has to hunt for what they need.

File attachments solve three problems at once:

• Compliance evidence stays attached to the procedure that requires it. Auditors can trace from policy to proof without chasing files across systems.
• Training materials live where they are needed. New team members find reference guides, videos, and examples inside the workflow they are running, not in a separate learning management system.
• Version control becomes automatic. When the attached file updates, everyone running that procedure gets the current version. No more outdated spreadsheets circulating through email threads.

Types of Files to Attach to Your SOPs

The files you attach depend on the procedure, but most SOPs benefit from one or more of these categories:

• Compliance forms and audit checklists that need to be completed as part of the process
• Training guides, walkthrough videos, and onboarding reference materials
• Policy documents, regulatory requirements, and internal standards
• Templates and standard forms (intake forms, report templates, approval request forms)
• Reference data such as pricing tables, product specs, or vendor contact lists
• Certificates, licenses, and audit evidence that prove completion or qualification

How to Attach Files in Process Street

Process Street makes file attachments a native part of your workflows. Here is how to add files:

1. Open an existing workflow or create a new one from your Process Street dashboard.
2. Select the task where you want to attach a file.
3. In the task editor, add a file upload field from the form fields menu. You can set it as required so the workflow cannot be completed without the attachment.
4. Upload the file directly by dragging it into the upload zone, or click to browse your files. Process Street accepts PDFs, spreadsheets, documents, images, and other common file formats.
5. Save the workflow. Every time someone runs this workflow, the attached file is available in the correct task.

You can also attach files at the workflow level (visible across all tasks) or within the content area of a task as an embedded reference.

Best Practices for SOP File Attachments

Attaching files is straightforward. Keeping those attachments useful over time requires a few practices:

• Review attachments during regular SOP reviews. A quarterly check ensures forms, templates, and reference documents are still current.
• Use descriptive file names. “Client_Onboarding_Checklist_v3.2.pdf” tells the user what they are opening. “Document1.pdf” does not.
• Set file fields as required when the attachment is critical to the process. This prevents someone from completing a workflow without uploading the necessary evidence.
• Keep one source of truth. Attach the file to the SOP rather than linking to a version in someone’s personal drive. This eliminates access issues and version drift.
• Use workflow permissions to control who can modify attachments versus who can only view them. This protects approved documents from accidental edits.

Frequently Asked Questions

What file types can I attach to SOPs in Process Street?

Process Street supports most common file types including PDFs, Word documents (DOCX), Excel spreadsheets (XLSX), images (PNG, JPG), videos, and compressed archives (ZIP). There is a file size limit per upload, but most standard business documents fall well within it.

Can I require file uploads as part of a workflow?

Yes. When you add a file upload field to a task in Process Street, you can toggle it as required. The workflow run cannot be marked complete until the required file is uploaded.

How do I update an attached file without breaking the SOP?

Upload the new version of the file to the same field in the workflow template. Future workflow runs will use the updated file. Completed runs retain the file that was attached at the time of execution, preserving your audit trail.

Can team members attach files during a workflow run?

Yes. File upload fields in Process Street allow team members to attach files as they work through the procedure. This is useful for collecting signed forms, inspection photos, completed checklists, or other evidence of task completion.