WReier-Aviles on DSKGBLS3C1PROD with RULES266878 Federal Register / Vol. 75, No. 209 / Friday, October 29, 2010 / Rules and Regulationsemployees could be rewarded throughpr<strong>of</strong>it-sharing or other payments forsuccess in meeting retention,graduation, and placement goals as longas they are not rewarded for the number<strong>of</strong> students recruited and admitted.These commenters requested that wedefine an acceptable percentage <strong>of</strong> anemployee’s compensation adjustmentthat can be based on the number <strong>of</strong>students recruited, admitted, enrolled,or awarded financial aid.One commenter asked that we clarifywhether payments tied to overallinstitutional revenues, including pr<strong>of</strong>itsharing,pension, and retirement plansare allowed. A number <strong>of</strong> commentersasked more broadly whether such planswould be permissible. A fewcommenters requested changes toincorporate the distribution <strong>of</strong> pr<strong>of</strong>itsharingor bonus payments undercertain circumstances, such as when apayment is made to a broad group <strong>of</strong>employees.Discussion: While there is nostatutory proscription upon <strong>of</strong>feringemployees either pr<strong>of</strong>it-sharing or abonus, if either is based in any part,directly or indirectly, upon success insecuring enrollments or the award <strong>of</strong>financial aid, it is not permitted undersection 487(a)(20) <strong>of</strong> the HEA or§ 668.14(b)(22).The <strong>Department</strong> agrees withcommenters that there arecircumstances when pr<strong>of</strong>it-sharingpayments should be permitted. Underproposed § 668.14(b)(22), an institutionmay distribute pr<strong>of</strong>it-sharing paymentsif those payments are not provided toany person who is engaged in studentrecruitment or admission activity or inmaking decisions regarding the award <strong>of</strong>title IV, HEA program funds. The<strong>Department</strong> believes that such paymentsare consistent with the HEA as they arenot being made to a particular groupwho is active in admissions or financialaid.For this reason, we are making achange to § 668.14(b)(22)(ii) to providethat institutions may make payments,including pr<strong>of</strong>it-sharing payments, solong as they are not provided to anyperson who is engaged in studentrecruitment or admission activity or inmaking decisions regarding the award <strong>of</strong>title IV, HEA program funds.Changes: We have revised§ 668.14(b)(22)(ii) to clarify that,notwithstanding the ban in§ 668.14(b)(22)(i), eligible institutions,organizations that are contractors toeligible institutions, and other entitiesmay make pr<strong>of</strong>it-sharing payments, solong as such payments are not providedto any person who is engaged in studentrecruitment or admission activity or inmaking decisions regarding the award <strong>of</strong>title IV, HEA program funds.Comment: Several commenters askedus to clarify what kinds <strong>of</strong> activitieswould not be considered under thedefinition <strong>of</strong> securing enrollments or theaward <strong>of</strong> financial aid. They asked thatwe revise the regulations to provideexplicitly that payments based on anyadditional activities are not allowed ifthey are directly or indirectly based onenrollment or the awarding <strong>of</strong> aid.Other commenters raised questionsabout the use <strong>of</strong> ‘‘aggregators,’’ that is,entities that assist an institution withthe institution’s outreach efforts. Theseefforts include but are not limited to,identifying students, <strong>of</strong>fering counselingand information on multipleinstitutions, and encouraging potentialstudents to fill out an applicationdirectly with the individual institutions.Aggregators are paid based on thestudent remaining at the institution fora certain time period rather than basedon the fact that the student enrolls.Commenters asked us to clarify whetherthese practices are permitted undersection 487(a)(20) <strong>of</strong> the HEA and§ 668.14(b)(22).Some commenters focused onarrangements under which institutionspay third parties for student contactinformation and asked whether suchinformation may be sorted or qualified.Further, they questioned whetherinstitutions would be permitted to payonly for information that yields actualcontact with a student. They asked thatwe confirm that institutions may paystudents for contact information on aper person basis as long as payments arenot based on the number <strong>of</strong> studentswho apply or enroll. In addition, theysuggested that we allow qualitativefactors to be included in theconsideration <strong>of</strong> the price to provideincentives to third parties toappropriately identify students thatmore closely fit an institution’s pr<strong>of</strong>ile.Some commenters believed that theproposed definition <strong>of</strong> securingenrollments or the award <strong>of</strong> financialaid does not make it clear that theactivities are prohibited through thecompletion <strong>of</strong> a student’s educationalprogram.Discussion: The <strong>Department</strong> agreesthat it would be helpful to clarify thetype <strong>of</strong> activities that are and are notconsidered securing enrollments or theaward <strong>of</strong> financial aid. For this reason,we have revised the definition <strong>of</strong>securing enrollments or the award <strong>of</strong>financial aid to specifically include (asexamples) contact through preadmissionor advising activities, scheduling anappointment for the prospective studentto visit the enrollment <strong>of</strong>fice or anyVerDate Mar2010 14:10 Oct 28, 2010 Jkt 223001 PO 00000 Frm 00048 Fmt 4701 Sfmt 4700 E:\FR\FM\29OCR2.SGM 29OCR2other <strong>of</strong>fice <strong>of</strong> the institution,attendance at such an appointment, orinvolvement in a prospective student’ssigning <strong>of</strong> an enrollment agreement orfinancial aid application (see§ 668.14(b)(22)(iii)(B)(1) <strong>of</strong> these finalregulations).We also revised the definition toclarify that it does not include makinga payment to a third party for theprovision <strong>of</strong> student contact informationprovided that such payment is not basedon any additional conduct by the thirdparty, such as participation inpreadmission or advertising activities,scheduling an appointment to visit theenrollment <strong>of</strong>fice or any other <strong>of</strong>fice <strong>of</strong>the institution or attendance at such anappointment, or the signing, or beinginvolved in the signing <strong>of</strong> a prospectivestudent’s enrollment agreement orfinancial aid application (see§ 668.14(b)(22)(iii)(B)(2) <strong>of</strong> these finalregulations).With respect to the commentsrequesting guidance on ‘‘aggregators,’’we do not believe it is necessary orappropriate for the <strong>Department</strong> toindicate whether these types <strong>of</strong>activities would, across the board, bepermitted. Each arrangement must beevaluated on its specific terms. As notedearlier in this preamble, we believe anyinstitution can determine whether apayment it intends to make isprohibited by § 668.14(b)(22) byapplying the two-part test we havedescribed. Specifically, the first step foran institution in determining if paymentfor an activity or action is consideredincentive compensation is to evaluatewhether the entity is receivingsomething <strong>of</strong> value, then to determinewhether the payment is made based inany part, directly or indirectly, onsuccess in securing enrollments or theaward <strong>of</strong> financial aid.Finally, we agree with commentersthat the definition <strong>of</strong> the term securingenrollments or the award <strong>of</strong> financialaid should be revised to specify thatthese activities include activities thatrun throughout completion <strong>of</strong> thestudent’s educational program.Changes: We have revised thedefinition <strong>of</strong> securing enrollments or theaward <strong>of</strong> financial aid in§ 668.14(b)(22)(iii)(B) to provide moredetail about actions that are consideredto be covered by the definition. We alsohave revised the definition to clarifythat it includes activities through thecompletion <strong>of</strong> an educational program.Comment: Numerous commentersrequested that the <strong>Department</strong> <strong>of</strong>ferguidance on the practicalimplementation <strong>of</strong> the proposeddefinitions. Many expressed concernabout our stated intention to address
Federal Register / Vol. 75, No. 209 / Friday, October 29, 2010 / Rules and Regulations66879WReier-Aviles on DSKGBLS3C1PROD with RULES2only broadly applicable principlesrather than responding to questions onindividual compensation issues. Thesecommenters asserted that institutionsneed guidance before they should be thesubject <strong>of</strong> an investigation or legalaction. They raised concerns about theconfusion that could result withoutadditional clarification and theattendant costs to partners in thestudent aid process in ‘‘today’s legalenvironment.’’ They believed that the<strong>Department</strong> already knows thatguidance will be needed based on ourpre-2002 experiences and noted thatissuing guidance is a fundamentalpurpose <strong>of</strong> the <strong>Department</strong> and shouldbe continued.Discussion: The <strong>Department</strong> believesthe proposed language is clear andreflective <strong>of</strong> section 487(a)(20) <strong>of</strong> theHEA. As modified, it is designed toappropriately guide institutions as theyevaluate compensation practices. To theextent that ongoing questions arise on aparticular aspect <strong>of</strong> the regulations, the<strong>Department</strong> will respond appropriatelyin a broadly applicable format and willdistribute the information widely to allparticipating institutions. This responsemay include a clarification in a<strong>Department</strong> publication, such as theFederal Student Aid Handbook or aDear Colleague Letter. The <strong>Department</strong>does not intend to provide privateguidance regarding particularcompensation structures in the futureand will enforce the regulations aswritten.Changes: None.Satisfactory Academic Progress(§§ 668.16(e), 668.32(f), and 668.34)GeneralComment: Many commenterssupported the proposed changes to theSatisfactory Academic Progress (SAP)regulations. Several commenters notedthat the consolidation <strong>of</strong> the SAPrequirements into § 668.34 would easecompliance and suggested that it wouldbe helpful to revise the Federal StudentAid (FSA) Handbook to mirror the neworganization <strong>of</strong> the requirements in theregulations.Several commenters noted that theyappreciated that the proposed SAPregulations retain the flexibilityprovided under the current regulationsfor institutions to establish policies thatbest meet the needs <strong>of</strong> their students.Many commenters expressed supportfor the proposed changes to the SAPregulations because they viewed themas a means for helping hold studentsaccountable for their academic goalsearlier in their careers, which theybelieved would lead to lower studentdebt levels. Several commenters notedthat their current policy and practiceseither met or exceeded the requirementsin the proposed regulations.Many commenters supported, inparticular, the definition <strong>of</strong> the termsfinancial aid warning and financial aidprobation as well as the standardizeddefinitions <strong>of</strong> other terms related toSAP. These commenters stated that thisstandardization would lead to a moreconsistent application <strong>of</strong> the SAPregulations among institutions, which,in turn, will make them moreunderstandable to students.Many commenters also supported theSAP regulations because they give thoseinstitutions that choose to evaluate SAPmore frequently than annually theability to use a financial aid warningstatus, which they viewed as beingbeneficial to students. They stated thatsuch a warning would lead to earlyintervention for students who faceacademic difficulties. Commenters alsonoted that the financial aid warningstatus will allow financial aid <strong>of</strong>fices tostrengthen their SAP policies toencourage students to use designatedsupport services on campus and lead t<strong>of</strong>urther student success.Discussion: The <strong>Department</strong>appreciates the support <strong>of</strong> its efforts toimprove program integrity through itsSAP regulations. With regard to thecomment recommending that we revisethe FSA Handbook to align it with thechanges we have made in the SAPregulations, we will take thisrecommendation into account duringthe next revision <strong>of</strong> the FSA Handbook.Changes: None.GeneralComment: Several commenters didnot support the proposed changes to theSAP regulations. Two commentersstated that the <strong>Department</strong> should delayimplementation <strong>of</strong> the SAP regulations,including proposed § 668.34, so that wecan resubmit these proposals fornegotiation and evaluation in a futurenegotiated rulemaking proceeding.These commenters argued that the<strong>Department</strong> had not made a sufficientargument for what would be gained bythe changes, and how these benefitswould justify the additional burdenimposed upon institutions by theseregulations.Two commenters stated thatinstitutions were in the best position todesign and implement a satisfactoryacademic progress policy that fit theirinstitutional needs, and that the currentregulations were sufficient for achievingthis purpose. These commentersasserted that the proposed changes wereintrusive and would lead to increasedVerDate Mar2010 14:10 Oct 28, 2010 Jkt 223001 PO 00000 Frm 00049 Fmt 4701 Sfmt 4700 E:\FR\FM\29OCR2.SGM 29OCR2audit exceptions. These commentersalso noted that the <strong>Department</strong> shouldconsider incentives to encourageinstitutions to research student successin light <strong>of</strong> their own SAP policies. Onecommenter stated that the proposedregulations were too prescriptive, andthat institutions would requiresignificant guidance in the FSAHandbook in order to be able to complywith the new regulations.Two commenters stated that whilethey generally agreed with the<strong>Department</strong>’s desire to clarify the SAPregulations and with the proposedapproach reflected in the NPRM, theregulations had a number <strong>of</strong> unintendedconsequences. These commentersindicated that the <strong>Department</strong>’sproposal would force institutions tochoose whether to take on additionalworkload by evaluating students eachterm, or to take on the additionalworkload caused by the dramaticincrease in appeals. One <strong>of</strong> thecommenters noted as an example aninstitution that has a number <strong>of</strong> AlaskanNative students to whom it providessignificant support, particularly early intheir careers; in this case, thecommenter stated that these studentswould be significantly harmed by theseSAP regulations as the students <strong>of</strong>tencannot remedy their academic problemsin a short period <strong>of</strong> time. Both <strong>of</strong> thesecommenters noted that while the<strong>Department</strong> believes that it has toaddress abuses with the currentregulations, that it should weigh thisagainst the unintended consequences <strong>of</strong>the proposed regulations, which includeincreased workload for institutions andunfair impact on certain groups <strong>of</strong>students.Discussion: The <strong>Department</strong> disagreeswith the commenters who suggestedthat these regulations should beresubmitted for the negotiatedrulemaking process. The proposedchanges to the SAP regulations in§§ 668.16(e), 668.32(f), and 668.34 havealready been through the negotiatedrulemaking process. In fact, thenegotiators reached tentative agreementon these proposed changes. Duringnegotiations, most negotiators statedthat it was appropriate for the<strong>Department</strong> to provide certainflexibilities for those institutions thatchose to check on the satisfactoryacademic progress <strong>of</strong> students more<strong>of</strong>ten than was required by the statutoryminimum <strong>of</strong> annually. Many <strong>of</strong> thenegotiators said that they supported theproposed changes to the SAPregulations because they continued toprovide significant flexibilities forinstitutions to craft SAP policies thatmet the needs <strong>of</strong> their student bodies
- Page 1 and 2: Friday,October 29, 2010Part IIDepar
- Page 3 and 4: Federal Register / Vol. 75, No. 209
- Page 6 and 7: 66836 Federal Register / Vol. 75, N
- Page 8 and 9: 66838 Federal Register / Vol. 75, N
- Page 10 and 11: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 12 and 13: 66842 Federal Register / Vol. 75, N
- Page 14 and 15: 66844 Federal Register / Vol. 75, N
- Page 16 and 17: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 18 and 19: 66848 Federal Register / Vol. 75, N
- Page 20 and 21: 66850 Federal Register / Vol. 75, N
- Page 22 and 23: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 24 and 25: 66854 Federal Register / Vol. 75, N
- Page 26 and 27: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 28 and 29: 66858 Federal Register / Vol. 75, N
- Page 30 and 31: 66860 Federal Register / Vol. 75, N
- Page 32 and 33: 66862 Federal Register / Vol. 75, N
- Page 34 and 35: 66864 Federal Register / Vol. 75, N
- Page 36 and 37: 66866 Federal Register / Vol. 75, N
- Page 38 and 39: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 40 and 41: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 42 and 43: 66872 Federal Register / Vol. 75, N
- Page 44 and 45: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 46 and 47: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 50 and 51: 66880 Federal Register / Vol. 75, N
- Page 52 and 53: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 54 and 55: 66884 Federal Register / Vol. 75, N
- Page 56 and 57: 66886 Federal Register / Vol. 75, N
- Page 58 and 59: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 60 and 61: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 62 and 63: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 64 and 65: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 66 and 67: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 68 and 69: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 70 and 71: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 72 and 73: 66902 Federal Register / Vol. 75, N
- Page 74 and 75: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 76 and 77: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 78 and 79: 66908 Federal Register / Vol. 75, N
- Page 80 and 81: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 82 and 83: 66912 Federal Register / Vol. 75, N
- Page 84 and 85: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 86 and 87: 66916 Federal Register / Vol. 75, N
- Page 88 and 89: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 90 and 91: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 92 and 93: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 94 and 95: 66924 Federal Register / Vol. 75, N
- Page 96 and 97: WReier-Aviles on DSKGBLS3C1PROD wit
- Page 98 and 99:
66928 Federal Register / Vol. 75, N
- Page 100 and 101:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 102 and 103:
66932 Federal Register / Vol. 75, N
- Page 104 and 105:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 106 and 107:
66936 Federal Register / Vol. 75, N
- Page 108 and 109:
66938 Federal Register / Vol. 75, N
- Page 110 and 111:
66940 Federal Register / Vol. 75, N
- Page 112 and 113:
66942 Federal Register / Vol. 75, N
- Page 114 and 115:
66944 Federal Register / Vol. 75, N
- Page 116 and 117:
66946 Federal Register / Vol. 75, N
- Page 118 and 119:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 120 and 121:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 122 and 123:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 124 and 125:
66954 Federal Register / Vol. 75, N
- Page 126 and 127:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 128 and 129:
66958 Federal Register / Vol. 75, N
- Page 130 and 131:
66960 Federal Register / Vol. 75, N
- Page 132 and 133:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 134 and 135:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 136 and 137:
WReier-Aviles on DSKGBLS3C1PROD wit
- Page 138 and 139:
66968 Federal Register / Vol. 75, N
- Page 140 and 141:
66970 Federal Register / Vol. 75, N
- Page 142 and 143:
66972 Federal Register / Vol. 75, N
- Page 144 and 145:
66974 Federal Register / Vol. 75, N