Seems an awful lot of work for a small return.

Approach 1: Without telling the client, re-word the document so the problem
simply doesn't arise. If the form is directed at the person, write it all in
the second person (you, yourself, etc); otherwise use 'they', 'them', 'the
recipient' etc throughout.

Approach 2: Use 'he/she', 'himself/herself' in the dropdowns etc; then use a
macro on completion to Find and Replace as needed.

Probably best to avoid the entirely non-gendered "s/h/it" approach.

Hi Susan,

This is perfectly possible, but does require a bit of work.

First of all, write the text in the template so that it is all male.

Next, you need to define all the gender/specific word pairs that you want to
handle, e.g. he/she, him/her, his/hers.

Then in the template go to File, Properties, click the Custom tab and insert
a property for each word pair, with both the name and value set to the male
version. So you would have a property called "he" whose value is also "he".

Then, find every example of the "he" in the document and replace it with a
DOCPROPERTY field referencing the "he" custom property. Do the same for each
of the other properties you have defined.

Then create a UserForm, where the user can choose the gender. If the user
chooses male, then you can leave all the properties with their male values.
If the user chooses female, then the code in the form sets the values of all
the custom document properties to their female values. So, for instance you
would set the value of the "he" property to "she".

Then the code updates all the fields in the document so that the display
matches the property values.