Historically we have entered constituent records for couples with the husband on the Bio1 Tab and the Spouse in the Spouse Tab.

We recently purchased NetCommunity and therefore are being required to implement the events module.  It seems with the addition of these two modules, we will now need to create separate constituent records for EXISTING and new constituent records. 

I am overwhelmed with anticipation of how this change is going to affect all of our existing procedures and would appreciate communication with anyone who has met and conquered and conquering these challenges with the Events AND/OR NetCommunity respectively.  We are now using the event module and need immeidate help in respect to that.  NetCommunity is planned to go live before year-end.

 Thank you for your time.

Historically we have entered constituent records for couples with the husband on the Bio1 Tab and the Spouse in the Spouse Tab.

We recently purchased NetCommunity and therefore are being required to implement the events module.  It seems with the addition of these two modules, we will now most likely need to create separate constituent records for spouses (EXISTING and new). 

I am overwhelmed with the anticipation of how this change is going to affect our existing procedures and would appreciate feedback from any of you that hacve experience with same.

Thank you for your time.

I do not have net community but do have times when the spouse record is actually made a constituent record. I would advise using a separate Constituency code for the spouse (I use Second Account) and making sure your Head of Household is set up properly so that secondary spouse accounts can be easily excluded from mailings such as invitations and solicitations so that one per household is sent if that is how you do your business.

Thanks.  Do you have any advise on Head of Household procedurers as well?

If you set up the spouse as the secondary constituency code - make sure that the Head of Household checkmark is NOT on that account - it should be on the 'Primary' account. This way, when you are using the MAIL processes and EXPORT processes you can use Head of Household processing to get one mailing or record per household. You can run a constituent query to look at these fields and make edits if necessary

Some people might think the Second Account Constituency code is going too far - but I find it helpful as exclusion criteria when running queries.