Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Opportunity object to display an error message if the Stage field is Closed lost and the Loss Reason field is blank. Reference: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm&type=5

Flow Builder and Process Builder are two automation tools that should be used to accomplish this request. Flow Builder can be used to create a flow that defines the logic and actions for creating a renewal opportunity, such as setting the stage, close date, and amount. Process Builder can be used to create a process that triggers the flow when an opportunity is closed won. Reference: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.process_overview.htm&type=5

Grant access using Hierarchies is a setting that can be used to configure the custom object to meet this requirement. Grant access using Hierarchies determines whether access to records of the custom object is granted through the role hierarchy. If this setting is unchecked, managers are unable to see the feedback records from their staff, unless they are given access by other means, such as sharing rules or manual sharing. Reference: https://help.salesforce.com/s/articleView?id=sf.security_sharing_owd_custom_objects.htm&type=5

As long as the fiscal year begins on the 1st of any month and follows the standard months, then custom fiscal years are not required.