Indicia stores dates in the sample. You can have nested samples, ie. sample, sub-sample then occurrence. I think this is more typically used to store records with a general location at the sample level and more accurate locations at the sub-sample. I see no reason why this could not be applied to dates as well. (The top level sample could contain a date range.) Note that species is recorded in the occurrence, not the sample. I'm not aware of a pre-built form to support this.
A better solution might to be to add nest sites to the location table. You could use location attributes to save habitat and nest details. Then, when repeat visits are made, you make a normal sample-occurrence record and, in the sample, store a reference to the location.
You might be able to achieve this with the 'Data Entry Form > Enter a Location' pre-built form to create the locations. The 'Data Entry Form > Enter a single record or list of records' form then has controls
[location autocomplete] - an autocomplete control for picking a stored location. A spatial reference is still required.
[location select] - a select control for picking a stored location. A spatial reference is still required.
[location map] - combines location select, map and spatial reference controls for recording only at stored locations.
I have used this principle once, some time ago, but I haven't tried it with the pre-built forms.