Distributing Proposal Building Blocks and Protecting Only the Front Matter
Halcyon Partners' proposal team of eight writers reuses the same four-page front matter: cover page, client-name dropdown, practice-area list, confidentiality statement, and signature block. One writer saved each piece as a Quick Part in her own Normal.dotm, so the other seven cannot see them; a second writer saved them in a document stored on a personal OneDrive. The team also wants writers to fill in only the client name, date, and engagement partner, while protecting the rest of the front matter from edits. When the protection is turned on, the client-name dropdown stops accepting input and the date picker shows 'Error! Bookmark not defined.' The signature block must remain editable by the engagement partner after protection, and the whole package must be available to new writers the day they receive a laptop, without each person rebuilding the parts. The firm uses a shared network Templates folder that is already mapped for all staff.
1. Where should the reusable front matter live so all eight writers see it, and what settings make that happen? Why is distributing Normal.dotm the wrong fix?
Read the worked answer
Normal.dotm is each user's personal global template. It lives in the user profile, can be recreated by Word, and cannot be reliably shared while Word is running. Copying it also overwrites personal customizations and is not a deployment mechanism.
Instead:
- Create a custom template, for example ProposalParts.dotx (or .dotm if code is needed), and store it in the shared network Templates folder.
- On each workstation, set File > Options > Advanced > File Locations > Workgroup Templates to that folder. Templates there appear in File > New and are available to all users.
- When saving each Quick Part, choose Insert > Quick Parts > Save Selection to Quick Part Gallery, and in Save in select ProposalParts.dotx, not Normal.dotm. Give each part a unique name and an appropriate gallery such as Cover Pages or Quick Parts.
- Re-save any existing parts into the shared template from the source document; the Save in list is the reliable way to put a part in a template.
- For new hires, the mapped folder plus the Workgroup Templates path delivers the parts on day one; a logon script or policy can set the path.
2. Protection is on, yet the client-name dropdown will not accept input and the date control shows 'Error! Bookmark not defined.' What is causing each symptom, and how do you protect the page while leaving the signature block editable?
Read the worked answer
Treat the two symptoms separately.
- The dropdown refusing input is a lock issue. Open Developer > Properties for that control. If Contents cannot be edited is checked, the user cannot change the selection even when the document is unprotected or form-protected. Clear it; keep Content control cannot be deleted if you want to prevent removal. Also check that protection is Filling in forms, which leaves content controls editable; Read only blocks them.
- A genuine Date Picker content control does not produce 'Error! Bookmark not defined.' Press Alt+F9 to show field codes. The message usually comes from a REF field or legacy form field whose bookmark was deleted when content was copied. Replace it with a Date Picker content control, or restore the bookmark, then hide field codes.
- For the signature block, make it a rich-text content control with Contents cannot be edited cleared, or put it in a separate section and exclude that section in Restrict Editing > Select sections. Do not use Read only for the whole document and expect an exception to make the block editable.
Enforce with a password and test as a standard user, not as the author.
3. Design the controls so writers fill only client name, date, and engagement partner, and the document still spell-checks their entries. Which control types and properties do you use, and what common mistake makes spell-check stop?
Read the worked answer
Use content controls because they survive protection and carry prompts:
- Client name: a Dropdown List control if clients come from a fixed list; a Combo Box if writers may type a new client. Set Title and Tag (for example ClientName) and add a meaningful placeholder.
- Date: a Date Picker control set to the firm's display format and locale; it stores a date value rather than free text.
- Engagement partner: a Combo Box populated from the partner list, or a plain-text control if the list changes often.
- Signature block: a rich-text control with editing allowed.
- Confidentiality statement: a plain-text or rich-text control with Contents cannot be edited checked so it cannot be altered.
A common mistake is using legacy form fields instead of content controls in a protected form; legacy fields depend on form protection and can behave inconsistently for proofing and editing. Keep the controls in the main document body, leave proofing enabled, and test with a misspelled client name while protection is enforced. If a style applied through Use a style to format contents has Do not check spelling or grammar enabled, that can also suppress proofing.