Many users, but not all,  do keep the Events in line with the sample. Recorder facilitates this approach with the option to bring the events data into line when the sample data is changed.  Help explains events as follows

'Survey events describe visits by surveyors to localities. A survey is composed of a set of such visits, and samples are made during these visits. The information recorded for a survey event details where surveyors went, who took part and the date (or date range). Information on conditions during the visit, and a comment to allow amplification (for example, to give extra details of exactly where surveyors went) can also be recorded.'

If for example you and some firends went Recording in a local Nature Reserve over  a weekend. This could be input as just one event with the date(vague date covering two days),  location (just a site centroid would do) and a list of the people attending. The samples would then have specific dates and accurate grid refs and indicate which of those involved in the event  were involved in recording the sample. In this example there would just be one event with mutiple samples.