> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stage3.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding Forms to Guides

> Learn how to attach forms and templates to activity guides

## What Are Forms?

Forms are fillable documents or templates that team members complete as part of an activity. By attaching forms directly to your activity guides, you ensure people have the right forms at the right time.

Forms can include checklists, request forms, data collection templates, approval documents, or any other structured information that needs to be completed.

<Info>
  Forms complement your activity guides. The guide tells people what to do; the form gives them a structured way to capture information.
</Info>

## Why Attach Forms to Guides?

<CardGroup cols={2}>
  <Card title="Convenience" icon="hand-pointer">
    Team members find the form exactly when they need it, right in the activity instructions
  </Card>

  <Card title="Consistency" icon="equals">
    Everyone uses the same form version, ensuring consistent data collection
  </Card>

  <Card title="Completeness" icon="list-check">
    Forms with required fields ensure no critical information is missed
  </Card>

  <Card title="Version Control" icon="clock-rotate-left">
    Updated forms automatically appear in guides, no broken links or outdated versions
  </Card>
</CardGroup>

## Common Form Types

<Tabs>
  <Tab title="Request Forms">
    Forms for requesting approvals, resources, or actions

    **Examples:**

    * Budget approval request form
    * Time off request form
    * IT support request form
    * Purchase requisition form
    * Access request form
  </Tab>

  <Tab title="Checklists">
    Step-by-step checklists to ensure nothing is forgotten

    **Examples:**

    * New employee onboarding checklist
    * Pre-launch quality checklist
    * Monthly close checklist
    * Equipment setup checklist
    * Compliance verification checklist
  </Tab>

  <Tab title="Data Collection">
    Forms for gathering structured information

    **Examples:**

    * Customer intake form
    * Project kickoff questionnaire
    * Employee feedback survey
    * Incident report form
    * Sales qualification form
  </Tab>

  <Tab title="Evaluation Forms">
    Forms for assessments, scoring, or rating

    **Examples:**

    * Candidate interview scorecard
    * Performance review template
    * Vendor evaluation rubric
    * Project retrospective form
    * Quality audit form
  </Tab>
</Tabs>

## Adding Forms to Your Guide

<Warning>
  **Important:** You must create a guide SOP (Standard Operating Procedure) before you can add forms. The system will display a warning "Guide SOP Required: Create a guide SOP first before adding forms" until you create the SOP.
</Warning>

<Steps>
  <Step title="Create Your Guide Content First">
    Open your activity guide from the Guides column in the RACI tab.

    Write your guide content using the rich text editor.
  </Step>

  <Step title="Create the Guide SOP">
    Click **"Create SOP"** to save your guide content as a Standard Operating Procedure.

    This step is required before you can attach any forms.
  </Step>

  <Step title="Prepare Your Form">
    Create your form in the appropriate format:

    * **PDF forms** with fillable fields
    * **Word/Google Docs** templates
    * **Excel/Google Sheets** spreadsheets
    * **Online forms** (Google Forms, Typeform, etc.)

    Make sure the form includes:

    * Clear title
    * Instructions for completing it
    * Required field indicators (\*)
    * Submission instructions
  </Step>

  <Step title="Access the Forms Sidebar">
    After creating your SOP, look at the right sidebar of the guide editor.

    You'll see the **Forms** section with a button labeled **"+ Add New Form"**.
  </Step>

  <Step title="Add Your Form">
    Click **"+ Add New Form"** in the Forms sidebar.

    Upload your form file or provide a link to your online form.

    Add a descriptive name for the form so users know what it is.
  </Step>

  <Step title="Reference the Form in Instructions">
    In your step-by-step instructions, tell users when and how to complete the form.

    **Example:**

    > **Step 4: Complete the Budget Request Form**
    > Download and fill out the Budget Request Form (available in the Forms section). Complete all required fields marked with (\*). Save the completed form as: YourName\_BudgetRequest\_YYYY-MM-DD.pdf
  </Step>

  <Step title="Test the Form">
    Test the form to make sure it's accessible and all fields work correctly.

    Try filling it out to ensure instructions are clear.
  </Step>
</Steps>

## Form Best Practices

<AccordionGroup>
  <Accordion title="Keep Forms Simple" icon="minimize" defaultOpen>
    **Why:** Long, complex forms discourage completion and increase errors.

    **How:**

    * Only include necessary fields
    * Use dropdowns instead of text fields when possible
    * Group related fields into sections
    * Use clear, simple labels

    **Example:** Instead of "Please provide detailed information about your request including justification, expected outcomes, timeline, and budget implications," break this into separate, clearly labeled fields.
  </Accordion>

  <Accordion title="Mark Required Fields" icon="asterisk">
    **Why:** Users need to know what's mandatory vs. optional.

    **How:**

    * Use asterisks (\*) for required fields
    * Include a note at the top: "\* indicates required field"
    * Consider using form validation that prevents submission without required fields

    **Tip:** Only mark fields as required if they're truly necessary. Over-requiring creates frustration.
  </Accordion>

  <Accordion title="Provide Instructions" icon="circle-info">
    **Why:** Clear instructions reduce errors and questions.

    **How:**

    * Add brief instructions at the top of the form
    * Include field-level help text for complex fields
    * Provide examples for format-specific fields (dates, phone numbers)
    * Link to additional resources if needed

    **Example for a date field:** "Enter start date (format: MM/DD/YYYY, e.g., 06/15/2024)"
  </Accordion>

  <Accordion title="Use Consistent Formatting" icon="equals">
    **Why:** Consistency makes forms easier to scan and complete.

    **How:**

    * Use the same font and sizing throughout
    * Align fields consistently
    * Use consistent spacing
    * Match your company's document branding

    Create form templates that everyone uses to maintain consistency.
  </Accordion>

  <Accordion title="Include Submission Instructions" icon="paper-plane">
    **Why:** Users need to know what to do after completing the form.

    **How:**

    * State where to submit (email, portal, folder, etc.)
    * Specify who receives it
    * Mention any deadlines
    * Note what happens next

    **Example:** "Submit completed form to [approvals@company.com](mailto:approvals@company.com). Your manager will review within 2 business days. You'll receive an email when approved."
  </Accordion>
</AccordionGroup>

## Form Types and Tools

<CardGroup cols={3}>
  <Card title="PDF Forms" icon="file-pdf">
    **Best for:** Forms that need to be printed, signed, or archived

    **Tools:** Adobe Acrobat, PDFescape, Sejda
  </Card>

  <Card title="Word/Google Docs" icon="file-word">
    **Best for:** Templates that users customize with their own content

    **Tools:** Microsoft Word, Google Docs
  </Card>

  <Card title="Spreadsheets" icon="table">
    **Best for:** Forms with calculations, data tables, or financial info

    **Tools:** Excel, Google Sheets
  </Card>

  <Card title="Online Forms" icon="globe">
    **Best for:** Forms that collect data into a database automatically

    **Tools:** Google Forms, Typeform, Jotform, Microsoft Forms
  </Card>

  <Card title="System Forms" icon="window-maximize">
    **Best for:** Forms within your existing software platforms

    **Examples:** Salesforce forms, ServiceNow requests
  </Card>

  <Card title="Checklists" icon="list-check">
    **Best for:** Simple yes/no or checkbox completion tracking

    **Tools:** Plain documents, Monday.com, Asana
  </Card>
</CardGroup>

## Creating Effective Forms

<Steps>
  <Step title="Define the Purpose">
    What information do you need to collect? Why?

    Write down the specific data points required and why each one matters.
  </Step>

  <Step title="Design the Form Structure">
    Organize fields into logical sections:

    * Group related information together
    * Put most important fields first
    * End with submission information

    **Example structure for a budget request:**

    1. Requestor Information (name, dept, date)
    2. Request Details (amount, category, purpose)
    3. Justification (why needed, expected outcomes)
    4. Approvals (manager signature, date)
  </Step>

  <Step title="Choose Field Types">
    Select the appropriate input type for each field:

    * **Text fields:** For names, descriptions
    * **Dropdowns:** For predefined options
    * **Radio buttons:** For single choice from options
    * **Checkboxes:** For multiple selections
    * **Date pickers:** For dates
    * **Number fields:** For amounts

    Use constrained inputs (dropdowns, radio buttons) when possible to ensure data consistency.
  </Step>

  <Step title="Add Validation">
    If using online forms, add validation rules:

    * Required fields can't be blank
    * Email fields must contain "@"
    * Number fields only accept numbers
    * Dates must be valid formats

    Validation prevents submission of incomplete or incorrect data.
  </Step>

  <Step title="Test the Form">
    Fill out the form yourself from a user's perspective:

    * Are any questions confusing?
    * Are there too many required fields?
    * Is anything missing?
    * Does it take too long to complete?

    Get feedback from team members before finalizing.
  </Step>
</Steps>

## Form Integration Examples

<AccordionGroup>
  <Accordion title="Example 1: Candidate Interview Scorecard" icon="clipboard" defaultOpen>
    **Activity:** Conduct Final Interview

    **Guide Instructions:**

    > **Step 5: Complete Interview Scorecard**
    > During or immediately after the interview, fill out the Interview Scorecard (available in the Forms section).
    >
    > **Scoring:**
    >
    > * Rate each criterion on a 1-5 scale
    > * 1 = Does not meet expectations
    > * 5 = Exceeds expectations
    > * Add comments for scores below 3 or above 4
    >
    > **Submission:**
    > Save completed scorecard as: CandidateName\_Interview\_YourName\_Date.pdf
    > Upload to the candidate's folder in Google Drive within 24 hours

    **Form:** Interview Scorecard PDF with sections for:

    * Candidate information
    * Technical skills (5 criteria)
    * Soft skills (5 criteria)
    * Culture fit (3 criteria)
    * Overall recommendation
    * Comments section
  </Accordion>

  <Accordion title="Example 2: IT Equipment Request" icon="laptop">
    **Activity:** Request Equipment for New Hire

    **Guide Instructions:**

    > **Step 2: Submit Equipment Request**
    > Fill out the IT Equipment Request Form (available in the Forms section) at least 2 weeks before the new hire's start date.
    >
    > **Required Information:**
    >
    > * New hire's name and start date
    > * Department and role
    > * Equipment needed (laptop, monitor, etc.)
    > * Software licenses required
    > * Shipping address
    >
    > **After Submission:**
    > IT will email you a confirmation within 1 business day. Equipment typically arrives 1 week before start date.

    **Form:** Google Form that:

    * Collects required info via dropdown menus
    * Automatically emails IT team
    * Creates ticket in IT system
    * Sends confirmation to requestor
  </Accordion>

  <Accordion title="Example 3: Monthly Expense Report" icon="receipt">
    **Activity:** Submit Monthly Expenses

    **Guide Instructions:**

    > **Step 3: Complete Expense Report**
    > Download the Expense Report Template (Excel file in Forms section) and complete all tabs:
    >
    > **Tab 1: Summary**
    >
    > * Auto-calculates from detail tabs
    > * Verify totals match your receipts
    >
    > **Tab 2: Details**
    >
    > * One row per expense
    > * Attach receipts for expenses over \$25
    > * Use category codes (see Reference tab)
    >
    > **Tab 3: Reference**
    >
    > * Category codes and guidelines
    > * Do not edit this tab
    >
    > **Submission:**
    > Save as: YourName\_Expenses\_YYYY-MM.xlsx
    > Email to [accounting@company.com](mailto:accounting@company.com) by the 5th of each month

    **Form:** Excel template with:

    * Auto-calculating summary tab
    * Data validation on category fields
    * Built-in formulas for totals
    * Reference tab with guidelines
  </Accordion>
</AccordionGroup>

## Form Naming Conventions

Use clear, consistent naming for forms:

<CardGroup cols={2}>
  <Card title="Form Files" icon="file">
    **Pattern:** FormPurpose\_Version\_Date

    **Examples:**

    * BudgetRequest\_v2.0\_2024-06.pdf
    * InterviewScorecard\_v1.3\_2024-01.xlsx
    * OnboardingChecklist\_v3.0\_2024-03.docx
  </Card>

  <Card title="Completed Forms" icon="file-check">
    **Pattern:** YourName\_FormType\_Date

    **Examples:**

    * SarahJ\_BudgetRequest\_2024-06-15.pdf
    * MikeC\_ExpenseReport\_2024-06.xlsx
    * Project\_Alpha\_Kickoff\_2024-06-10.docx
  </Card>
</CardGroup>

## Version Control for Forms

Forms evolve over time. Track versions properly:

<Steps>
  <Step title="Version Number">
    Include version number in the form itself (header or footer).

    Use semantic versioning: v1.0, v1.1 (minor changes), v2.0 (major changes)
  </Step>

  <Step title="Update Date">
    Show when the form was last updated.

    Format: "Last updated: June 2024" or "Version 2.0 - June 2024"
  </Step>

  <Step title="Update the Attached Form">
    When you update a form, replace the old version in all guides that use it.

    Check where the form is used before updating to avoid breaking workflows in progress.
  </Step>

  <Step title="Notify Users">
    When you make significant changes, notify team members who use the form.

    Explain what changed and why in a brief email or message.
  </Step>
</Steps>

<Warning>
  **Don't create multiple versions of the same form.** If you have BudgetRequest\_v1.pdf and BudgetRequest\_v2.pdf both active, people will use the wrong version. Retire old versions when you update forms.
</Warning>

## Use Cases by Department

<Tabs>
  <Tab title="HR">
    * New hire information form
    * Performance review template
    * Time off request form
    * Disciplinary action form
    * Exit interview questionnaire
  </Tab>

  <Tab title="Sales">
    * Lead qualification form
    * Sales opportunity form
    * Proposal request form
    * Contract review checklist
    * Customer feedback form
  </Tab>

  <Tab title="Operations">
    * Incident report form
    * Quality audit checklist
    * Equipment maintenance log
    * Inventory count sheet
    * Process improvement suggestion form
  </Tab>

  <Tab title="Finance">
    * Purchase requisition form
    * Expense report template
    * Budget request form
    * Invoice approval form
    * Vendor payment authorization
  </Tab>

  <Tab title="IT">
    * Access request form
    * Equipment request form
    * Support ticket template
    * Change request form
    * System setup checklist
  </Tab>
</Tabs>

## Troubleshooting Form Issues

<AccordionGroup>
  <Accordion title="Cannot Add Forms to Guide" icon="circle-exclamation" defaultOpen>
    **Problem:** The "+ Add New Form" button is not available or shows a warning.

    **Solution:** You must create a guide SOP first. Click "Create SOP" to save your guide content, then the Forms section will become available.
  </Accordion>

  <Accordion title="Form Link Is Broken" icon="link-slash">
    **Problem:** Users click the form link and get an error.

    **Solutions:**

    * Check if the file was moved or deleted
    * Verify link permissions (anyone with link can view?)
    * Re-upload the form if necessary
    * Update the link in all guides that reference it
  </Accordion>

  <Accordion title="Form Won't Open or Download" icon="file-circle-xmark">
    **Problem:** Form doesn't open or download button doesn't work.

    **Solutions:**

    * Check file format compatibility
    * Verify file isn't corrupted (re-upload clean version)
    * Ensure file size isn't too large (compress if needed)
    * Try a different file hosting method
  </Accordion>

  <Accordion title="Users Complete Wrong Form Version" icon="files">
    **Problem:** People are using an outdated version of the form.

    **Solutions:**

    * Remove all old versions from shared locations
    * Update the attached form in all guides
    * Send announcement about the new version
    * Include version number prominently on the form
  </Accordion>

  <Accordion title="Form Data Gets Lost" icon="triangle-exclamation">
    **Problem:** Completed forms aren't reaching their destination.

    **Solutions:**

    * Clarify submission instructions in the guide
    * Use online forms that auto-submit to a database
    * Set up email rules to organize form submissions
    * Implement a tracking system for form status
  </Accordion>
</AccordionGroup>

## Tips for Success

<CardGroup cols={2}>
  <Card title="Start Simple" icon="seedling">
    Begin with a basic form and add fields as needed. Overcomplicating forms reduces completion rates.
  </Card>

  <Card title="Test with Users" icon="users">
    Have team members test your form before deploying. They'll catch issues you missed.
  </Card>

  <Card title="Make Forms Optional When Possible" icon="circle-check">
    Only require forms when absolutely necessary. Optional forms get higher quality responses.
  </Card>

  <Card title="Provide Examples" icon="lightbulb">
    Include a filled-out sample form to show what good completion looks like.
  </Card>
</CardGroup>

## Form Checklist

Before attaching a form to your guide:

* [ ] Guide SOP has been created
* [ ] Form has a clear, descriptive title
* [ ] All fields are clearly labeled
* [ ] Required fields are marked with (\*)
* [ ] Instructions for completion are included
* [ ] Submission instructions are clear
* [ ] Version number and date are visible
* [ ] Form has been tested with actual users
* [ ] File format is compatible with your team's tools
* [ ] Form is properly attached in Forms sidebar
* [ ] Guide instructions reference the form clearly

## Next Steps

<CardGroup cols={3}>
  <Card title="Creating Guides" icon="book" href="/processes/creating-guides">
    Learn how to create activity guides that use forms
  </Card>

  <Card title="Sharing Processes" icon="share-nodes" href="/processes/sharing-processes">
    Share your guides and forms with team members
  </Card>

  <Card title="Collaboration Best Practices" icon="handshake" href="/processes/collaboration-best-practices">
    Learn how to collaborate effectively on documentation
  </Card>
</CardGroup>