That works. Big to small, here's the big issues I see:
1. Numerated field names. When you start adding numbers to field names to differentiate them, it's time for a new table. All that consent call data needs to go into a new table with this structure:
ConsentCalls
cc_ID, autonumber, primary key
ID_t2, number, foreign key to [T-2 year data].ID field
Call, same field type as [Reminder consent call 1] field, will hold its data
Notes, same field type as [Reminder consent call 1 notes], will hold its data
That's it, just 4 fields. That means when you have 8 consent calls you add 8 records in this new table.
2. Seperate date and time fields. A date/time field can hold both of those pieces of data, you shouldn't store them seperatly. That means [Recall 1 expected date] and [Recall 1 expected time] are not both necessary, just one of them which will hold both pieces of data. Doing this will allow you to easily use the Date/Time functions access has.
3. Lots of events in one table. T-2 year data looks like its essentially a project management table--lots of dates. Instead of a new field for each event, I think you should use a seperate table where you store the event not in a field name but in the field value. For example:
Events
event_ID, autonumber, primary key of table
ID_t2, number, foreign key to [T-2 year data].ID field
event_Type, text, will hold value currently in field names (e.g. Consent form sent, Consent form received, Recall 1 expected, etc.)
event_Date, Date/Time, date/time the event occured
Again, 4 fields and that's it. Instead of 18 fields for events in [T-2 year data] you would have 18 records in Events to accomodate that data.
I suggest searching this forum for an 'Events Database' or 'Project Management'. I'm sure someone has an example that you can steal for your own purpose.
4. Only use alpha-numeric characters in names. Coding and querying will be easier if you follow this rule. That means, remove all spaces and dashes from table/field names.