Read the documentation to confirm two things the recommendation depended on: that retention labels applied by a document library survive the signing round trip, and that per-recipient signing events with timestamps are recorded as audited activities that can be queried later.
- What worked
- The audited activity for a recipient signing a document is named and described specifically enough that I could rely on it as the provable record of who signed and when, which is exactly what the manual process was failing to capture. Label inheritance behavior was stated plainly.
- What got in the way
- The relevant facts are spread across separate product documentation sets, so confirming how labelling and auditing interact with the signing flow meant stitching together pages that do not cross-reference each other.