Roll Students Into a New Program Year

EOC programs do not use rollover. A new program year starts empty, and each participant joins it when your program serves them. To add a returning participant, open their profile, choose the ... menu next to Log Contact, then choose Add to the current program year. If they apply again, the new application is flagged as a possible duplicate, and merging the two records adds the year to the record you keep. See Review Possible Duplicates. The rest of this article is for Upward Bound, UBMS, Talent Search, SSS, McNair, and VUB programs.

Rollover carries your continuing participants from the current program year into the next one, so you do not re-enter them. It creates a next-year record for each participant whose status you choose to roll, carrying some information forward and starting the rest fresh, as your settings and the Field Actions you choose for the run say. It lives in Settings → Program Year.

Rollover is optional. No program has to run it. Use it when you want your continuing participants to have their next-year records ready in one step.

When to Run It

Rollover always moves the current program year into the next one, so there are no years to pick. If you use it, run it before the current program year ends. The Set Up the Rollover card names the day your current program year ends, from your reporting periods in Settings > Reporting, and the Program Year tab says it too. Once the next program year starts, it becomes the current year, and the year that just ended can no longer be rolled.

Rollover adds records to the next year and gives the students it rolls a Continuing tag. It never changes anyone's current-year record.

Nothing rolls until you choose. On each run, you tick the statuses that roll, from Pending, Active, Served, and Reportable. Students marked Rejected or Inactive never roll, except, for Upward Bound, UBMS, SSS, McNair, and VUB, a record that holds an APR cohort year (see below). For Upward Bound, UBMS, SSS, McNair, and VUB, every Reportable record also rolls, whatever you tick, because it is on the year's APR data file, unless your program's federal rule drops it or you choose one enrollment cohort under Who Rolls (see Upward Bound and UBMS and SSS, McNair, and VUB below). Students with a status you leave unticked stay in the current year. For example, a program that keeps some students Served because they are not part of the cohort it reports can leave Served unticked. Run a simulation first to see exactly who would roll.

Choose the Statuses That Roll

Simulate Rollover and Run Rollover both start with Statuses That Roll, one checkbox per status:

• Pending, Active, Served, and Reportable can be ticked. Only students whose status is ticked get a next-year record.
• Inactive and Rejected show unticked and cannot be ticked. For Upward Bound, UBMS, SSS, McNair, and VUB, the one exception is a record that holds an APR cohort year: it rolls with its status unchanged, and the review asks you to confirm it before you commit. Talent Search has no such exception, because no objective in its APR counts from a cohort year stored on the record.

If your program saved a choice under Rollover Behavior (see below), those boxes start ticked, and you can change them for the run. Otherwise no box is ticked, and you can't preview or simulate until you tick at least one.

Two Separate Tools

Rollover has two separate tools:

• Simulate Rollover: a rehearsal that saves nothing. It shows what would happen (who rolls forward, what carries over, what resets). Run it first, as many times as you like.
• Run Rollover: creates each participant's record for the next program year.

Practice With a Simulation

1. Go to Settings → Program Year and choose Start a Simulation.
2. Tick the Statuses That Roll. Then pick the New-Year Status rolled students should start the year with: Pending or Active. Or pick No Change: Keep Each Student's Current Status if your program does not reset statuses at rollover, and each student carries their own status into the new year. Either way, students marked Inactive or Rejected are the exception: they are not rolled into the new year. They stay in the year you marked them and do not come back each new year as Pending. The only exception, for Upward Bound, UBMS, SSS, McNair, and VUB, is a record that holds an APR cohort year: it rolls and keeps its status. To see them afterwards, set the Program Year picker on the Students list to that year, or to All Years.
3. Adjust Field Actions if you like. That card sits below the setup card, with one row per built-in per-year field: choose Carry Forward or Reset. Increment +1 appears only on the numeric fields, grade level and age at first service. For Talent Search, the age at first service row has no choice, because rollover always calculates the new year's age from the date of birth (see Control What Carries Over below), and the plan's per-field action list says From date of birth. Choices here apply to this run only.
4. Choose Run Simulation and review the plan: how many would roll and how many are skipped, Records by Status (see below), the reasons for each skip, anything flagged for review, a per-field action list, and a before and after sample of students.

The rehearsal covers every student with a ticked status. Nothing is saved, so simulate freely until the plan looks right.

Run the Real Rollover

1. From Settings → Program Year, choose Start a Rollover.
2. Tick the Statuses That Roll, pick the New-Year Status (including the No Change choice, which keeps each student's current status), and under Who Rolls choose all eligible students or one enrollment cohort (students who share a first year of enrollment).
3. Adjust Field Actions further down the page if needed, then choose Preview Rollover.
4. Review the full plan, just like a simulation.
5. If Served students will roll, or Reportable students will roll in a Talent Search program, or an Inactive or Rejected record rolls because it holds an APR cohort year, confirm each status. For Upward Bound, UBMS, SSS, McNair, and VUB, Reportable records carry without this step, and the Federal File card shows them. The review names the count and what the status can mean, for example: "53 Served students will get a PY 27-28 record. Served can mean a student your program keeps out of its reported cohort." Tick Roll these 53 Served students to go on. Pending and Active need no extra step.
6. For Upward Bound, UBMS, SSS, McNair, and VUB, the review also asks you to confirm the students who hold an APR cohort year and will not roll because you did not tick their status. Rollover carries the records on the year's APR data file, so these records are not on it, and the review says so. For Upward Bound and UBMS: "3 students who hold an APR cohort year will not get a PY 27-28 record, because their status is not chosen to roll. Rollover carries every record on your PY 26-27 APR data file (Reportable), and these records are not on it. They will be left out of your program's cohort objectives and APR data file for PY 27-28 and later years." For SSS, McNair, and VUB the second sentence reads: "Rollover carries the records on your PY 26-27 APR data file (Reportable) that your program's APR instructions keep, and these records are not on it." Tick Leave these 3 students out of the cohort objectives and the APR data file to go on, or go back and tick their status to keep them counted. Rollover never rolls them on its own.
7. For the same programs, if you chose one enrollment cohort under Who Rolls, the review also asks you to confirm the students outside that cohort who hold an APR cohort year: "2 students who hold an APR cohort year will not get a PY 27-28 record, because they are outside the cohort you chose under Who Rolls. They will be left out of your program's cohort objectives and APR data file for PY 27-28 and later years." Tick Leave these 2 students from other cohorts out of the cohort objectives and the APR data file to go on. To keep them counted, also run the rollover for their cohort, or for all eligible students.
8. Type the number of records that will roll, shown on the Confirm card, then choose Commit Rollover. You can't commit until what you type matches that number. A comma or space in the number is fine.

If who would roll changes after your preview, for example because a colleague adds a student or changes a student's status, the commit is refused and nothing is saved. Go back, preview again, and check the review.

The setup page also offers an optional APR Settings for the New Year section. Expand it to enter the new year's grant numbers (Number Funded to Serve and per-objective targets), pre-filled with the numbers the new year uses now: the latest numbers you entered, unless you already set the new year's own. If you skip it, the new year keeps those numbers, and you can set them any time on Settings → Reporting under Grant Numbers by Program Year. These boxes follow the same rules as Settings: a funded number is a whole number of at least 1, a target is a whole number from 0 to 100, and you can leave either blank. If a number does not fit, Preview Rollover stops and tells you what to change, so nothing you typed is dropped. If saving them fails after the rollover commits, the rollover itself is unaffected and the page tells you to enter them in Settings.

For Talent Search, the setup page also tells you when no Postsecondary Attainment choices are recorded for the new year. If the new year starts a new grant cycle, record the choices your APR form shows in Settings → Reporting. The notice does not block the rollover.

Rollover does not change a Talent Search enrollee list that is recorded as filed or imported, and it does not copy a year's Section II.L choice (Competitive Preference Priorities) to the new year: record the new year's choice on Settings → Reporting when you know it.

Everyone who rolls also gets a Continuing tag next to their name, except that for Upward Bound, UBMS, SSS, McNair, and VUB a record carried as a prior-year participant shows Prior-Year Participant instead.

You can run rollover again safely. Students who already have a record for the new year are skipped, so it does not create duplicates.

Upward Bound and UBMS

The federal instructions require your upload to include every record in the Department's match file, and TRIOPilot's APR data file holds the year's Reportable records. So for Upward Bound and UBMS, every Reportable record in the current year carries into the next year, whatever statuses you tick. The review shows a Federal File card with how many carry and how. If you choose one enrollment cohort under Who Rolls, a Reportable record outside that cohort does not carry in that run; run the rollover for its cohort too.

Rollover follows your own project year. A project whose year starts June 1 rolls PY 25-26 into PY 26-27 until May 31, 2026; from June 1 the current year is PY 26-27. If your start type in Settings > Reporting is a summer start, or moving from a summer start to a fall start, enter your reporting period on the Reporting Periods card first: without it TRIOPilot cannot tell whether your year ends in May or June, so rollover says so and changes nothing. Until you enter it, the Program Year tab and the rollover setup pages say your year's dates are not known, instead of showing September 1 to August 31.

Each record carries in one of two ways:

• As a prior-year participant, when its own federal fields say the person left before the new year began: Participant Status is Prior-year participant, field #26 (Deceased or Incapacitated) is a prior-year option, or the Date of Last Project Service is a date before the new year begins. It starts the new year as Reportable, with Participant Status Prior-year participant. A field #26 of "served during reporting period but is now deceased" or "now permanently incapacitated" changes to its prior-year option. Grade Level at the beginning of the year follows the rule below; when last year's next-year status is not recorded, the grade starts blank unless it is 13 (enrolled in or completed postsecondary education).
• As a current participant, for everyone else, because rollover cannot know who you will serve. It starts at the new-year status you chose, or Pending when you choose No Change, so it is not on the new year's file until you record Participant Status and mark it Reportable. A Date of Last Project Service in the new year means the person was served into it, so they carry this way too. For a summer-start project (Project Start Type in Settings → Reporting), the new year starts in the summer: a Date of Last Project Service from June 1 to August 31 is in the new year, because the instructions say summer bridge participants "will be included in the next year's data file as 'continuing participants'".

For every record, current or prior-year, the new year's Grade Level at the beginning of the year is last year's Grade Level / PSE Status at Beginning of Following Year when that is recorded. The instructions define it as the grade or postsecondary status at the beginning of the next academic year. Both fields use the same September 1 to August 31 academic year, and the instructions place a student in a grade only if they "met the requirements for progression to that grade". So a student who repeated a grade starts the new year in that grade, and a 12th grader whose next status is recorded starts there, with no flag. When it is blank or Unknown, a current participant's grade goes up one grade, from 8th through 11th grade. A 12th grader, or a student in a fifth year of high school, keeps that value and is flagged, because what comes next (postsecondary, a fifth year of high school, or neither) is for you to record. The other options (postsecondary, Other, Not applicable and Unknown) stay as they are. A grade level that is not one of the form's options is kept and flagged.

A record that holds a postsecondary enrollment cohort keeps it, and High School Graduation Status and Date, Date of First Postsecondary Enrollment, and Date of Last Project Service carry forward. Rigorous Secondary School Program of Study, Postsecondary Remediation, and FAFSA start blank, because the form asks about them for the reporting year only.

The Department drops some records from each year's download file. The 2024-25 instructions publish the record-drop criteria for the 2024-25 APR (for example, cohort 2018 or earlier), and for later years TRIOPilot applies the same rule one year later each year. Either way the result is a prediction, so rollover never skips a record for it: the record carries as a prior-year participant, and the review says "Predicted by the record-drop criteria to be dropped by the Department this year" with the criterion. The instructions say to "delay any deletions until you have verified which of your records (if any) the Department has removed from the download file". Check your download file, and remove the Reportable status of any flagged record that is not in it.

The review also flags a current participant who graduated high school and has no Date of Last Project Service (a summer bridge participant stays a current participant), and a record with field #26 of a current-year option and no Date of Last Project Service in the current year.

If a prior-year participant is served again, record Participant Status as Continuing if they were served last year, or Reentry if they were not, and change their Date of Last Project Service to Not applicable, participant is still in the program.

To carry one record you missed, open the APR report for the year: Records Missing From This Year's File lists every record on last year's file that is not Reportable this year, and Carry Into PY carries one with no record this year, as rollover does. Add to PY on a student's profile does the same for a record on last year's file. Each group on the card shows its first 10 records; choose Show All to see the rest.

SSS, McNair, and VUB

The APR instructions for each of these programs keep last year's records on the new year's APR data file, with its own rule for the records that leave it, and TRIOPilot's APR data file holds the year's Reportable records. So for SSS, McNair, and VUB, every Reportable record in the current year carries into the next year, whatever statuses you tick, except a record your program's rule drops. The review's Federal File card shows how many carry, how, and how many the rule drops, by rule. If you choose one enrollment cohort under Who Rolls, a Reportable record outside that cohort does not carry in that run; run the rollover for its cohort too.

Each record carries in one of two ways:

• As a prior-year participant, when its own federal fields say the person left before the new year began. It starts the new year as Reportable, with the program's prior-year Participant Status:
• SSS: Participant Status is 3 or 4; Persistence Status (field #34) says they are not enrolled at your institution at the start of the next year (2 to 6); Reason for Withdrawal (field #29) records why they withdrew or did not return, or that they are deceased; or the Date of Last Project Service falls in the current year. Rollover writes 4 (no longer enrolled) when Persistence Status says they are not enrolled at your institution or they are deceased, and 3 (enrolled but not receiving SSS services) when Persistence Status says they are still enrolled. When Persistence Status is blank, rollover keeps last year's 3 or 4, or writes 4 when a Reason for Withdrawal is recorded. When only a Date of Last Project Service says they left and Persistence Status is blank, rollover cannot tell 3 from 4, so it carries the record as a current participant and flags it. A Reason for Withdrawal beside a served Participant Status and a Date of Last Project Service that says they are still participating, or that is from an earlier year, is flagged, not read as leaving, because the instructions keep the reason only "unless the participant re-enrolls in the program".
• McNair: Participant Status is Prior-Year Participant or Prior-Year Participant, Deceased, which carries unchanged.
• VUB: Participant Status is Prior-year participant; field #25 is a prior-year option; the Date of Last Project Service falls in the current year; Completion Year (field #31) is the current year or earlier, or a code that says they left; or Date of First Postsecondary Enrollment (field #37) is a date before the new year begins, or 99/99/9999. Rollover writes Prior-year participant, and a field #25 of "served during reporting period but is now deceased" or "now permanently incapacitated" changes to its prior-year option. Service in the new year comes first: when the Date of Last Project Service or Completion Year falls in the new year, or Date of First Postsecondary Enrollment does and nothing says they left in the current year, the record carries as a current participant, flagged, unless Participant Status is Prior-year participant or field #25 is a prior-year option. Reason for Leaving (field #32) also says they left, unless it is Not applicable, still in the educational program offered by the project. A Reason for Leaving beside a served Participant Status and a Date of Last Project Service that says they are still in the program, or that is from an earlier year, is flagged, not read as leaving.
• As a current participant, for everyone else, because rollover cannot know who you will serve. It starts at the new-year status you chose, or Pending when you choose No Change, with Participant Status blank, so it is not on the new year's file until you record Participant Status and mark it Reportable.

A record carried as a prior-year participant starts blank in each field the form answers with a Not applicable code for prior-year participants, and the APR data file reports that code:

• SSS, only for Participant Status 4 (no longer enrolled): Enrollment Status (field #23), Academic Standing (#24), Cumulative GPA (#25), and the current College Grade Level (#27). Participant Status 3 keeps them, because the form asks these fields of prior-year participants still enrolled.
• McNair: Project Participation Extent (field #24), Funding Source (#25), STEM Major (#26), Research Activity (#32), Other Scholarly Activity (#33), and McNair Research Internship (#34).
• VUB: Served by Another Federal Program Similar to VUB (field #27), Academic Improvement on Standardized Test (#29), and the four services (#33 to #36).

If a prior-year participant is served again, record their values for this year in these fields.

Each program's rule decides which records leave the file. A record the rule drops, decided from recorded values, gets no new-year record, and the review counts it as Dropped from the new year's APR data file by your program's federal rule:

• SSS: "For 4-year institutions, a project must retain the participant records for six (6) years from the time of first service" (four years at a 2-year institution), and a prior-year participant with cohort 99 stays only if "at any point in the past five years served by the project" (three years at a 2-year institution). Rollover reads the year first served from Student Cohort Year (field #21), or from the first program year when it is blank, and the institution level from Settings → Reporting. When the level is not recorded, the 4-year period applies and the review flags the records only it keeps. A current participant is never dropped, because the rule drops only a participant not served this year.
• McNair: the APR form requires "all records in your final" APR data file of the year before, except a bachelor's cohort the Department no longer accepts (for 2024-25, cohorts before 2014-15). TRIOPilot moves that year forward one year each year, as the 2023-24 and 2024-25 forms do.
• VUB: the Department retires records by three criteria (for 2024-25, cohort 2018 is one), and the upload may include "only those in the download file". TRIOPilot applies the criteria one year later each year, as the 2023-24 and 2024-25 instructions do. The third criterion depends on dates the instructions publish only for 2024-25, so for a later year rollover carries such a record and flags it instead of dropping it.

A record the rule cannot check, because a value it reads is not recorded, carries and is flagged; check it against your download file. To keep a dropped record, use Carry Into PY on the APR report's Records Missing From This Year's File card, or Add to PY on the student's profile: either one carries it as a current participant, flagged, for you to record Participant Status. Keep one only when your program's federal text allows it on the file:

• SSS: when it is in your download file, or when you serve the student this year ("If, in 2024-25, a grantee serves a student from an out-of-range cohort, they must report this student").
• McNair: only when it is in your download file. For a bachelor's cohort before the first one the Department accepts, the form says "The Department will not be accepting reports for students from these cohorts on the Student Record File."
• VUB: only when it is in your download file. The instructions allow on the upload "only records in the download file, plus records that you add this year in which Participant Status (field #26) is 1 (new)".

Date of Last Project Service (SSS and VUB) and Reason for Withdrawal (SSS) carry forward into the new year. For VUB's Date of Last Project Service and SSS's Reason for Withdrawal, the instructions say they do not change in later years (VUB field #30: "must not change in subsequent years' APRs"; SSS field 29: "do not change it in subsequent reporting years"). SSS's Date of Last Project Service (field 28) carries forward because the SSS retention rule for cohort 99 reads it in later years ("at any point in the past five years served by the project"). When someone is served again, change their Date of Last Project Service to Not applicable, still participating in project (SSS) or Not applicable, still in the educational program offered by the project (VUB), or to the new date when they leave, and update Reason for Withdrawal if they re-enroll. A Date of Last Project Service from an earlier year beside a served Participant Status is flagged, not read as leaving.

Read Records by Status

The review opens with Records by Status: one row for each status in the current year, with the number of records, how many roll, the status they start the new year with, and how many are skipped and why. A student whose status you did not tick is skipped as Status not chosen to roll. If any of those records hold an APR cohort year, the review says how many. Where your program's cohort objectives count from that year, the review counts only the cohort years those objectives read. It also says that those students are left out of the objectives for the new year and later years, because the APR counts a student in a cohort only from their record in the year being reported, and you confirm leaving them out before you commit (step 6 above). In the same programs, a student skipped as Outside the selected cohort who holds such a cohort year is counted the same way, and you confirm that too (step 7 above). For Upward Bound, UBMS, SSS, McNair, and VUB, both notes also say these students are left out of the APR data file. For Upward Bound, UBMS, SSS, McNair, and VUB, an Inactive or Rejected record that rolls because it holds an APR cohort year shows in its own row, keeps its status, and needs your confirmation.

Set the Rollover Behavior

The Rollover Behavior section at the bottom of Settings → Program Year holds two optional defaults:

• Statuses That Roll: the statuses ticked here start ticked on Simulate Rollover and Run Rollover, and you can still change them for any single run. Leave them all unticked to choose every time. For Upward Bound, UBMS, SSS, McNair, and VUB, every record on the year's APR data file (Reportable) carries into the next year whatever you tick here, because the federal instructions require it, except a record your program's rule drops (SSS, McNair, and VUB) or one outside the enrollment cohort you choose under Who Rolls for a run; these choices apply to your other records.
• Default New-Year Status: the status a rolled student starts the new year with. It pre-fills both flows, and you can still change it for any single run. Choose No Change: Keep Each Student's Current Status if your program does not reset statuses at rollover. This setting never applies to students marked Inactive or Rejected: they do not roll, and a record that rolls because it holds an APR cohort year (Upward Bound, UBMS, SSS, McNair, and VUB only) keeps its own status.

For every program, rollover never starts a student in the new year as Served, because a Served record says the student was served in that year, and nobody has served them in it yet. Every program's APR counts a participant as served only for a year in which they received services. Served students can still roll; they start the new year as Pending or Active. If you tick Served and choose No Change, the rollover is refused, and the page says so: choose a new-year status, or untick Served. The same happens if you tick Served and set the Status field action to Carry Forward: set it back to Reset, or untick Served. If your program's saved Default New-Year Status is Served, Settings shows it with a note: choose Pending, Active, or No Change and save.

For Talent Search, rollover also never carries a student into the new year as Reportable, because a Reportable record counts in that year's APR and nobody has served the student in it yet. If you tick Reportable and choose No Change, the rollover is refused, and the page says so: choose a new-year status, or untick Reportable. The same happens if you tick Reportable and set the Status field action to Carry Forward: set it back to Reset, or untick Reportable.

For SSS, McNair, and VUB, rollover carries the APR data file itself, as for Upward Bound and UBMS: a Reportable record carries as a prior-year participant (Reportable, with the prior-year Participant Status written) or as a current participant (Pending under No Change), and each program's rule decides which records leave the file (see SSS, McNair, and VUB above).

Choose Save Settings to apply them. Until you save, no status is ticked to roll, and rolled students start as Pending. See Understand Student Statuses for what each status means.

Control What Carries Over

Each per-year field has a saved default that decides whether its value carries forward, starts blank, or increases by one each year. You set that per field in Settings → Participants, in the Profile Fields section: under Built-in Fields for TRIOPilot's own fields, and under How Often It Is Answered when you add or edit one of your own fields.

Open Built-in Fields there and each row offers A value each year, carried forward from last year or A value each year, starting blank. A number each year, going up by 1 is offered only on the fields TRIOPilot counts, which is why Age at First Service has it and the rest do not; for Talent Search and EOC, that row shows A value each year, calculated from the date of birth instead, with no choice. A few built-in fields, such as Low-Income and Assigned Advisor, can also hold One value, the same every year, so those rows offer that as well. Your own fields use the same picker, with all four choices, except that a Choose One or Choose Several field cannot go up by 1, because a choice from a list has no next value. Grade level increments on its own and is not listed in Profile Fields; it stops at 12, and the plan flags anyone who would have gone past it.

For McNair, every rolled record starts the new year with Graduate School Enrollment Status (next fall) (#38) and First-Year Graduate Persistence Status (#39) set to 5, Other, and Graduate Assistantship (first-year grad students) (#42) set to 99, Not applicable: the form gives those answers to anyone who did not receive a bachelor's degree, or was not a first-year graduate student, in the new reporting period. Change them only for the year's new graduates and first-year graduate students. Current Year of Graduate Study goes up one year at rollover, from the 1st through the 3rd year of graduate or professional study to Beyond 3rd year, which stays as it is. The other options (Other, Previously recorded as 1st-yr graduate incorrectly, Not enrolled in a graduate degree program this year, Unknown) stay as they are, and a value that is not one of the form's options is kept and flagged.

For Talent Search, rollover always calculates Age at First Service from the date of birth instead of adding 1 to last year's age, because the APR counts "the age of project participants at the time of first service in the reporting period". A rolled student has no contact in the new year yet, so the age is their age on the first day of the new program year. When the student's first contact in the new year is logged, TRIOPilot calculates the age again as of that contact, so you do not need to check rolled students' ages by hand. If the date of birth is missing, falls after that day, or gives an age under 5 or over 130, the age stays blank and the plan flags it. The flag names the reason, for example Age at First Service left blank (date of birth gives an age under 5 or over 130). For these two programs the field has no other action: Settings does not offer A value each year, carried forward from last year or A value each year, starting blank for it, and the run's Field Actions row reads From date of birth. For the other programs, whose APR does not count an age, rollover adds 1 to last year's age, or carries it forward or starts it blank if your program or the run chose that. See How Age at First Service Is Calculated.

A few built-in fields start blank each year on some programs, because that program's APR form asks about them for the reporting year only, so last year's answer would be wrong:

• Upward Bound and Upward Bound Math-Science: FAFSA Completed and the built-in FAFSA or Other Financial Aid Completed (the form's field 44 asks about participants who graduated "during the reporting year"), Rigorous Secondary School Program of Study Completed (field 36, graduates of that school year) and Postsecondary Remediation (field 64, one enrollment cohort). High School Graduation Status, HS Diploma / GED Received, Enrolled in Postsecondary and Postsecondary Education Enrollment Cohort keep carrying forward, because a diploma and a first postsecondary enrollment stay true in later years.
• Talent Search: Status at Time of First Service (Section III reports each participant's status "at the time of first service in the reporting year", so it can change from one year to the next). The built-in FAFSA or Other Financial Aid Completed also starts blank; Talent Search records the FAFSA in FAFSA Completion on the Program Outcomes panel, which Section II.K reads and which starts blank each year, because Section II.K counts the FAFSA completed "during the reporting year". The diploma, postsecondary and institution fields keep carrying forward.

Every other program carries these fields forward as before. Your program can still choose differently for any of them that it lists in Built-in Fields, or for one run in Field Actions.

Field Actions and the plan's Per-Field Actions card show a built-in outcome field only where your program's APR uses it: Institution Type on Talent Search programs, and none on the other program types, whose outcomes are their own APR fields. A stored value in an unlisted field still follows the behavior described above.

On Talent Search, Upward Bound and Upward Bound Math-Science programs, Target School carries forward by default, so each participant starts the new year at last year's school. Update it for anyone who changed schools, for example from middle school to high school; the Set Target School button on the Students page changes a whole group at once. If your program would rather start every year blank, choose A value each year, starting blank for Target School in Built-in Fields, or Reset in the run's Field Actions.

The Field Actions list in the rollover flow overrides those defaults for one run without changing your saved settings. It covers the built-in per-year fields; your custom per-year fields still roll, using their saved behavior. See Customize Student Profiles.

Tip

Always simulate first, so you catch a problem before any record is created.