A retention policy technically implements a retention rule that has been defined beforehand. So first agree with the responsible owners which period applies to which data. A single period for all SharePoint sites can be too short or too long for particular data.
Start with a data plan
Record document categories, purpose, responsible owner, applicable law, the event that starts the period and what happens at the end. For personal data such as rejected job applications, set the period with HR and legal advisers based on the purpose. The FDPIC explains limits on storing personal data.
Then choose the right Purview feature
A policy can cover SharePoint sites as locations; labels allow more targeted assignment to content. Both must follow the data plan. Microsoft describes how retention works in SharePoint and OneDrive, including the Preservation Hold Library. A file is not always permanently deleted when a user removes it from the library. Existing labels, other policies or an eDiscovery hold can continue to block deletion.
Test with sample documents
Choose one test document per category. Check which rule applies, when the period starts, who may apply a label and what happens when the period ends. Have the responsible business owner confirm the test. Document exceptions and review the rules when legal or business requirements change.
A concrete next step is a table of five common document types and the open legal questions. Only then is a production default policy worthwhile.

