Avoiding One to One Tables

I cannot ignore warnings given elsewhere in this forum against tables with
many fields and the temptation to break them apart into a series of
one-to-one tables. I'm sure you are all tired of dealing with this question,
as am I, but I still need to find an answer.

I have a table of Agreements, with a record for each agreement. Some of
these agreements are subject to a long list of Insurance Requirements. I
have been warned not to make a separate one-to-one table of requirements with
one field for each requirement, but instead, to normalize the data by having
requirements listed once in a Requirements table, and then make a
many-to-many join between Agreements and Requirements. The Value of the
requirement would be in a separate field in the join table. So the join
table would tell us which Agreement, which Requirement, and the Value for
that Requirement.

Here is the question: How do I format the Value field in the join table,
seeing that there are different kinds of requirements with different kinds of
values? I hate to get into tedious details, but here is a sampling of
Requirements, with their Values in parentheses:

Is GL Insurance Required? (yes/no).
Who is the Producer? (foreign key to Firms table).
Who is the Insurer? (foreign key to Firms table).
Policy Type? (CGL, Claims Made, Occur).
How is GL Aggregate Applied? (per Policy, per Project, per Location).
Policy Number? (text).
Date Effective? (date).
Date Expired? (date).
Limits Each Occur: (dollars).
Limits Rent Property Damage: (dollars).
Limits Medical: (dollars).
Limits Personal & Advertising: (dollars).
Limits General Aggregate: (dollars).
Limits Products/Completed Operations: (dollars).
Limits Explosion/Collapse/Underground: (dollars).
Additional Insured Endorsement? (yes/no)
Waiver of Subrogation? (yes/no).
Primary Coverage? (yes/no).
etc, etc.....

Thanks. (BTW, I'd rather not read offers of service for a fee, or
complaints about people who make such offers).
--Thanks, O.B.P.