Americorp Timesheets

AmeriCorps Member File Requirements

Senior Writer · · 11 min read
Cover illustration for “AmeriCorps Member File Requirements”
AmeriCorps Compliance · August 1, 2026 · 11 min read · 2,439 words

A member file is not a formality. It's the evidentiary record that stands between your program and a cost disallowance. Program staff who understand this distinction run fundamentally different operations than those who treat file-keeping as administrative housekeeping. The governing logic flows from a clear order of precedence: federal statutes first, then federal regulations, then the Notice of Grant Award, then program-specific and general terms and conditions. Member file requirements exist at every layer of that hierarchy. When an Office of Inspector General auditor or state commission reviewer opens a file, they're not looking for effort or good intentions. They're looking for documentation. Programs rarely fail audits because they ran a poor program. They fail because their records don't reflect what actually happened. What follows is a document-by-document account of what belongs in each member file and the compliance logic behind every component.

The Eligibility Documents That Establish a Member's Right to Serve

Every member file begins with the same foundational question: is this person legally authorized to serve? AmeriCorps membership is restricted to U.S. citizens, U.S. nationals, and lawful permanent residents. The file must prove it. This is not a procedural nuance; it's a condition of enrollment.

Programs using the MyAmeriCorps Portal to verify citizenship and Social Security status can rely on that verification in lieu of paper documents, per 45 CFR § 2522.200(c), but only if the program can demonstrate the verification occurred. That demonstration matters. A portal confirmation that disappears into a system with no audit trail proves nothing during a review.

Roughly 10 percent of members are flagged by the Social Security Administration during portal verification and require additional documentation. For those individuals, the Social Security card and supporting citizenship documents go directly into the physical or digital file. For all members, the standard documents to capture include proof of citizenship (a birth certificate, passport, or green card), a government-issued photo ID, a Social Security card or acceptable substitute, and proof of education where the position requires it.

The most common finding in this category is not missing documents. It's late documents. Collect eligibility materials before enrollment, not after. Retroactive collection is a recurring compliance gap precisely because it's so easy to defer when a program is onboarding multiple members at once.

The Member Service Agreement and Position Description as the Contract of Record

The signed member service agreement is the binding contract between the member and the program. It must be executed and in the file before service begins. Not on the first day of service. Before. This sequencing is a compliance requirement, not a preference. If the member is under 18, a parent or guardian co-signature is also required on the agreement.

The position description is not a separate optional document. It's a required component of the service agreement itself. Per AmeriCorps guidance, each member enrolled in the Member Portal must have a position description on file before service begins, and that description must accurately, completely, and specifically describe the activities the member will perform.

This specificity requirement is where many programs develop chronic vulnerabilities. Generic position descriptions that apply to every member regardless of placement are a compliance liability. When an auditor compares a position description to a member's timesheets and finds that the described activities don't match the recorded ones, the program has a problem that extends beyond that single file. Treat position descriptions as audit documents. Write them to reflect the actual role, and update them if the role substantively changes during the service term.

Criminal History Check Documentation and What the File Must Show

National Service Criminal History Check requirements are congressionally mandated under the Serve America Act and the National and Community Service Act. They're not discretionary program policy, and they're not waivable at the program level.

Three checks are required for covered individuals. First, a name-based check through the National Sex Offender Public Website. Second, a state criminal history repository check covering both the state of service and the state of residence. Third, a fingerprint-based FBI criminal history check. All three must be completed, reviewed, and an eligibility determination made no later than the day before the member begins service. Post-hoc checks don't satisfy the requirement. A check completed on the member's first day of service is a compliance failure.

As of late 2024, Truescreen is the single approved vendor for NSCHC, with Fieldprint handling Livescan fingerprinting as a Truescreen subcontractor. Programs that haven't verified their current vendor relationships against this requirement should do so immediately.

Two categories represent absolute disqualifiers: being registered or required to register as a sex offender, and a conviction for murder. These aren't subject to case-by-case adjudication. Members under 18 are exempt from NSCHC on first enrollment, but if they re-enroll at age 18 or older, the full check must be completed before that subsequent enrollment.

NSCHC records carry a seven-year retention requirement, which is longer than the general three-year program record rule. Programs need a retention schedule that tracks these separately, because a single purge date applied to all member records will result in the premature destruction of legally protected documents.

Orientation Documentation and the 20% Training Cap It Helps Substantiate

Every member must receive orientation, and the file must document that it happened. Acceptable documentation forms include timesheets, sign-in sheets, or an organizational form, but the minimum standard is something dated and signed. An undocumented orientation is, for compliance purposes, an orientation that didn't occur.

Orientation documentation serves a specific protective function beyond administrative completeness. It must cover prohibited activities during AmeriCorps service hours. If a member later engages in a prohibited activity, a program that can't demonstrate it covered those prohibitions at orientation has a materially weaker position than one that can.

The training cap established under 45 CFR § 2520.50 limits education and training to no more than 20 percent of the aggregate of all member service hours. This is a ceiling on the program, not just on individual members, and it requires ongoing tracking to substantiate. Orientation timesheets and subsequent training records work together to build that calculation.

One significant rule change took effect October 1, 2024. AmeriCorps can now waive the 20 percent cap, up to 50 percent, for specific program types: apprenticeship programs, job training and readiness programs, GED and credentialing programs, and programs primarily enrolling economically disadvantaged members. If a program holds such a waiver, that waiver documentation belongs in program records and should be readily accessible alongside the training-hour calculations it authorizes.

Timesheets as the Running Proof That Service Hours Were Real and Allowable

Timesheets aren't bookkeeping. They're the continuous evidentiary thread that connects a member's enrollment to their education award eligibility, and they're among the first documents an auditor will examine. Complete, accurate, supervisor-signed timesheets are required to document each member's service.

The most important technical requirement is that timesheets reflect after-the-fact actual activity, not budgeted or estimated hours. This distinction carries significant weight in audits. A timesheet that documents what a member was scheduled to do is not the same as one that documents what the member did. When an auditor identifies this pattern, the legitimacy of the entire hours record becomes questionable.

Both paper and electronic timesheets are acceptable. Programs using electronic systems must maintain an audit trail of any revisions. A timesheet that can be edited without a record of what was changed and by whom doesn't satisfy this standard. Programs must also have a written timekeeping policy in place by the second program year, covering how members track time, who approves timesheets, the approval timeframe, and how revisions are handled.

One of the most consequential and underappreciated compliance vulnerabilities involves staff allocated across multiple grants. A program director managing both a National Direct award and a State Commission award must have timesheets that document actual time per grant. If that allocation can't be substantiated, auditors may question and disallow total salary costs, not just the disputed portion.

The most effective internal control in this area is straightforward: a staff member other than the member's direct supervisor should review timesheets at least twice per year. This review should occur once mid-year while corrections are still easily made, and again immediately before a member exits service to confirm that the total hours on record are accurate before the exit form is filed.

Mid-Term and End-of-Term Evaluations as Supervisory Records With Compliance Weight

Both mid-term and end-of-term evaluations are required and must be in the member file. Their purposes differ. The mid-term evaluation is developmental: it identifies what is working, where the member needs support, and how goals should be adjusted for the remaining service period. The end-of-term evaluation closes the performance record and provides the program with a documented basis for planning subsequent service years.

All supervisory meetings, correspondence, and disciplinary actions must also be documented and stored securely. Because the program operates under a federal grant, these records are subject to review and should be maintained with the same rigor as financial documentation.

A missing evaluation is not a minor file gap. It's a gap in the file's narrative. An auditor reviewing a member file expects to see a coherent arc from enrollment through exit: eligibility established, service agreement signed, orientation documented, hours tracked, performance assessed, and service concluded. A missing mid-term evaluation breaks that arc and raises questions about the quality of program oversight, which is a question no program wants to be answering during a compliance review.

The Exit Form and Close-of-Service Documents That Complete the File

The exit form documents the completion of a member's term of service. It's part of AmeriCorps' formal information collection requirements and is not optional. The exit form connects directly to the enrollment record: members enrolled in the National Service Trust to earn education awards need a properly filed exit to trigger that award eligibility. An improperly filed or missing exit form creates downstream problems for the member and the program simultaneously.

As of December 2024, AmeriCorps proposed adding language to the exit form allowing outgoing members to opt in to sharing contact information with federal partners for continued service engagement. This is a modest but real change, and programs should confirm that their current exit documentation reflects the most current approved form.

The close-of-service file should include, at minimum, the following: the exit form, final timesheet reconciliation, the end-of-term evaluation, and any program-specific close-out documents. All of these should be confirmed complete before the member is fully exited from the system. A member exited with an incomplete file creates retroactive problems that are substantially more difficult to resolve once the member has departed. Hours disputes, benefit eligibility questions, and audit exposure all become harder to address when the individual is no longer present and engaged.

Electronic Storage and Signature Rules for Programs Managing Files Digitally

AmeriCorps State and National Terms and Conditions permit programs to store member files electronically and use electronic signatures. Two conditions govern this permission. The validity and integrity of the record and signature must be maintained, and the system must provide for safekeeping, security, and storage in a usable, readable format.

These conditions have practical teeth. A shared drive where any staff member can open and edit a signed document doesn't meet the integrity standard. A system with version control, role-based access permissions, and a documented audit trail does. The distinction is not semantic. If a document can be altered after signing without any record of that alteration, its value as an evidentiary record is compromised.

Programs should document their electronic storage procedures in writing. Using a system is not sufficient. Having a written policy that describes how the system works, who has access, how records are protected, and how the retention schedule is enforced is itself a procedural safeguard that may be reviewed. Cloud storage systems that allow an account administrator to delete records without a retention lock represent a genuine compliance risk, particularly given the seven-year NSCHC retention requirement and the three-year general rule operating simultaneously.

How Long to Keep Member Files and What Can Extend the Retention Clock

The general rule under 2 CFR § 200.334 of the Uniform Guidance is that all member, programmatic, and financial records must be retained for three years. That three-year clock starts from the date of submission of the final financial report, not from the end of the grant period. In practice, this typically means records must be maintained for 15 to 18 months after the end of the third program year, once all members are exited and final reports are submitted.

Five categories of exception can extend the retention clock significantly: unresolved audits, active litigation, property records, indirect cost records, and program income records. Any of these conditions resets or suspends the retention period. A program that believes it has satisfied its retention obligation but has an unresolved audit open against that grant year hasn't satisfied it.

NSCHC records, as noted, operate on a separate seven-year schedule. Programs need a retention schedule that explicitly tracks both timelines. A single purge date applied uniformly across all member records is an operational shortcut that creates legal exposure. The most important practical implication: a program that closes a grant year and immediately archives or deletes member files may be destroying records it's still legally required to keep.

Building a File System That Makes Audit Readiness a Byproduct of Normal Program Operations

The difference between programs that scramble before compliance reviews and those that don't is not a difference in program quality. It's a difference in systems. Programs that consistently produce clean files treat file completion as part of their enrollment and exit workflows, not as a separate compliance task that activates when a review is announced.

A member checklist attached to each file, tracking every required document from eligibility through exit, gives supervisors and program directors a real-time view of what is missing before it becomes a finding. This is not a sophisticated intervention. It's a discipline. Internal timesheet audits conducted twice per year surface errors while corrections are still possible and the member is still in service. Electronic systems with required fields, access controls, and retention locks reduce the probability that staff turnover or human error creates file gaps that compound over time.

The goal is not a perfect file produced under pressure at audit time. It's a system in which a complete, compliant file is the natural output of how the program is managed every day. When file completion is embedded in workflow rather than treated as a retrospective exercise, audit readiness stops being a periodic crisis and becomes a structural characteristic of the program itself. That's the practical standard every AmeriCorps program can and should achieve.

Sources

  1. americorps.gov
  2. serve.illinois.gov
  3. content.govdelivery.com
  4. federalregister.gov
  5. americorps.gov
  6. voicesforservice.org
  7. americorps.gov

More in AmeriCorps Compliance