Microsoft Word Forms: Creating Fillable Documents Without Adobe

Why Word Forms Are Underrated

When people think of fillable electronic forms, they often think first of Adobe Acrobat — not Microsoft Word. Yet Word’s form capabilities, particularly its content controls, are powerful enough to create professional fillable documents that can be distributed as standard .docx files, completed within Word itself, and submitted without any additional software. The advantages over PDF forms include native Office compatibility, full Word formatting and style support, easier modification, and no dependency on Adobe software on the recipient’s device.

This guide covers Word’s content controls — the building blocks of fillable forms — along with form protection, data extraction, and practical design patterns for common form types. These features are fully available in Office 2024 Professional Plus, Office 2021 Professional Plus, and Office 2019 Professional Plus.

Enabling the Developer Tab

Word’s form tools live in the Developer tab, which is hidden by default:

1. Go to File > Options > Customise Ribbon.
2. In the right-hand column (Main Tabs), tick Developer.
3. Click OK.

The Developer tab now appears between the View tab and the Add-ins tab in the ribbon. The Controls group within it contains all the content control types you will use to build forms.

Content Controls: The Building Blocks

Content controls are structured placeholders that can be inserted into any part of a Word document. Each type is designed for a specific kind of user input. Here are the available types:

Rich Text Content Control

Allows the user to enter formatted text — bold, italic, different font sizes, multiple paragraphs. Use this when free-form narrative responses are needed and formatting may matter, such as a description field in a report template or a comments section in a review form.

Plain Text Content Control

Restricts input to unformatted text. The most common choice for simple text fields: names, reference numbers, addresses, and single-line text entries where formatting is not needed or appropriate.

Picture Content Control

Displays a placeholder that the user can click to insert an image. Useful in templates requiring a photo, signature, logo, or supporting image as part of the form submission — staff profiles, incident reports, or product submissions.

Building Block Gallery Content Control

Allows the user to select from a list of predefined Building Blocks — reusable content blocks stored in the document or template. Useful in complex templates with standard text passages that vary based on context.

Checkbox Content Control

A tickbox that toggles between checked and unchecked states when clicked. Use for Yes/No questions, agreement confirmations, or multi-choice selections. In Office 2024, the checkbox supports custom symbols for checked and unchecked states via properties.

Combo Box Content Control

Provides a dropdown list of predefined options but also allows the user to type a custom value not in the list. Use when a dropdown is the primary choice but exceptions must be accommodated.

Drop-Down List Content Control

Provides a dropdown list of predefined options and restricts input strictly to those options — no custom entry is allowed. Ideal for classification fields (department, status, type) where only predefined values are valid.

Date Picker Content Control

Displays a calendar picker when clicked, allowing the user to select a date. The date is formatted consistently according to the properties you set. Use for all date fields in forms to prevent the format inconsistency (01/03/26 vs 1 March 2026 vs 2026-03-01) that plagues free-text date entry.

Inserting and Configuring Content Controls

Inserting a Control

1. Place the cursor where you want the control to appear in the document.
2. Go to the Developer tab.
3. Click the content control type in the Controls group. The control appears at the cursor position.

Design Mode

Click Design Mode in the Controls group to toggle a visual display of content controls in the document. With Design Mode active, you can see the boundaries of each control, edit their placeholder text, and move or resize them without accidentally activating them.

Control Properties

Select a content control and click Properties in the Controls group to configure:

• Title — A label shown in the control’s tab (visible in Design Mode). Use descriptive names: “First Name”, “Invoice Date”, “Department”.
• Tag — An internal identifier used for programmatic access and data extraction. Use a consistent naming convention: first_name, invoice_date, department.
• Show as — How the control displays: Bounding Box (shows a box around the control), Start/End Tag (shows tag markers), or None (no visual indicator when not in Design Mode).
• Cannot be deleted — Prevents the user from removing the control from the document.
• Contents cannot be edited — Makes the control read-only. Useful for display-only fields that should not be modified.
• Dropdown/Combo Box items — For list controls, the items list is configured here. Click Add to enter each option.
• Date format — For Date Picker controls, set the display format (e.g., dd MMMM yyyy for “01 March 2026”).

Designing a Practical Form

Employee Expense Claim Form

A typical expense form needs:

• Employee name — Plain Text control
• Department — Drop-Down List control with department names
• Claim period — Date Picker control (start) and Date Picker (end)
• Expense description — Rich Text control (allows multi-line, may need formatting)
• Category — Combo Box (predefined categories plus custom entry for unusual items)
• Amount — Plain Text control (note: Word form controls do not have a numeric-only option — for calculated fields or strict numeric validation, consider Excel instead)
• Receipt attached? — Checkbox control
• Manager approval — Drop-Down: Approved / Rejected / Pending

Layout the form using a table for alignment — a two-column table with field labels in the left column and content controls in the right. Set the table borders to No Border for a clean form appearance, or use Light Shading for structure. The table keeps labels and fields aligned regardless of the text length in any cell.

Placeholder Text

Each content control displays placeholder text when empty — the light grey instructional text visible before the user types anything. In Design Mode, click inside the control and edit the placeholder text directly. Write helpful, specific prompts:

• Instead of “Click here to enter text” — use “Enter your full name as it appears on your contract”
• Instead of “Choose an item” — use “Select your department from the list”
• Instead of “Click or tap to enter a date” — use “Select the first date of the claim period”

Protecting the Form

Form protection prevents users from accidentally (or intentionally) deleting content controls, adding or removing rows from your carefully structured table, or modifying the non-input parts of the form. It restricts editing to only the content controls themselves.

1. Go to Developer > Restrict Editing.
2. Under “Editing restrictions”, tick “Allow only this type of editing” and select Filling in forms from the dropdown.
3. Click Yes, Start Enforcing Protection.
4. Optionally set a password.

With protection enabled, clicking anywhere in the document moves the cursor to the next content control — creating a natural tabbing flow through the form fields. Users cannot alter the layout, styles, or static text content.

Section-Based Selective Protection

If you want some parts of the document to remain editable (e.g., a signature block where the manager types additional notes) while the form structure is protected, use section-based protection:

1. Insert section breaks to separate form areas from free-edit areas.
2. In the Restrict Editing pane, click Select Sections and choose which sections to protect with “Filling in forms” restriction. Leave other sections unrestricted.

Saving as a Template

Once the form is designed and protected, save it as a Word template (.dotx) rather than a regular document (.docx):

1. Go to File > Save As.
2. Select Word Template (*.dotx) from the file type dropdown.
3. Choose a meaningful name and a shared location accessible to the intended users.

When users open a .dotx template, Word creates a new document based on the template rather than opening the template file itself — preserving the blank form for future use.

Extracting Form Data

For collecting responses from multiple completed forms into a single dataset, manual data entry from each form is inefficient. Two approaches help:

Manual Approach: Table of Values

Open each completed form, copy the values from each content control, and paste them into a corresponding row in an Excel table. This works for small volumes but does not scale well.

VBA-Based Extraction

For larger volumes, a VBA macro can loop through all the .docx files in a folder, extract the values from each content control (identified by their Tag properties — another reason to set meaningful tags when building the form), and write them to an Excel workbook. This is a standard and achievable automation task for anyone with basic VBA knowledge, and it is one of the highest-value automations possible for teams processing high volumes of standardised form responses.

Word Forms vs Google Forms vs PDF Forms

Each approach has its place. Google Forms excels at high-volume anonymous data collection with automatic response aggregation. PDF forms are the standard in regulated industries and legal contexts where the visual fidelity and signing workflows of Adobe Acrobat are required. Word forms are best when the output document needs to look like a professional, formatted Word document — a completed and formatted contract, a staff appraisal with extended comment fields, or an internal report with a mix of structured data fields and narrative sections. The finished form looks like a polished document, not a data entry form, because it essentially is one.

Word Forms for Common Business Scenarios

New Employee Onboarding Form

An onboarding form collects standard information from new starters: personal details, emergency contacts, bank details for payroll, tax code information, and equipment preferences. Built as a Word form with clearly labelled content controls and instructional placeholder text, it provides a professional, branded first impression while ensuring consistent data collection. Protect it with the “Filling in forms” restriction so new employees can complete it without accidentally altering the structure, then return it for processing.

Client Brief Template

Professional services firms often use standardised client briefs to capture project requirements consistently. A Word form with sections for client information, project objectives, scope definition (with checkboxes for included/excluded activities), budget range (a Combo Box with typical ranges plus free entry), timeline requirements (Date Pickers for key milestones), and approval sign-off provides a structured framework that junior staff can complete confidently and senior staff can review efficiently.

Incident Report Form

Health and safety incident reporting requires consistent, complete data capture. A Word form with mandatory fields (enforced by careful use of protection and validation), dropdown lists for incident category and severity, a date and time picker for when the incident occurred, a Picture content control for attaching a supporting photograph, and a Rich Text field for detailed description creates a professional, legally defensible record that meets typical workplace reporting requirements.

Limitations to Be Aware Of

Word forms have genuine limitations compared to dedicated form tools. There is no built-in submission mechanism — completed forms must be returned by email or saved to a shared location manually. There is no server-side validation or business logic (such as showing different fields based on earlier answers, which is straightforward in tools like Microsoft Forms or Google Forms). For very high-volume data collection or complex conditional logic, a web-based form tool is more appropriate. Word forms are at their best for professional, document-centric use cases where the output needs to look like a polished, formatted document rather than a data submission.