Printed forms are *TERRIBLE* models for table design. The logical structure of
your tables should follow the logical structure of the data. It sounds like a
typical many-to-many relationship: each "particular" (you don't say what
real-life Entity this printed form represents) has zero, one or more
Requirements, and each Requirement applies to zero, one or more "particulars".
The normalized table structure for this would have three tables:

Particulars
 ParticularID <Primary Key>
 <fields describing the particular entity>

Requirements
 RequirementID <Primary Key>
 Description
 <other info about this requirement, if any>

PermitRequirements
 ParticularID
 RequirementID

That said... you can create a user interface which looks like the paper form,
with unbound checkbox controls and fields for the Particular data; you'll need
a little VBA code to loop through all the checkbox controls and add a record
to PermitRequirements for each one that is checked.

Then the mail merge will become very easy - you can simply base it on a query
joining all three tables, picking up the particulars of the Particular from
Particulars, and the description of the requirement from Requirements, using
PermitRequirements as the link between the two.

            John W. Vinson [MVP]