Student RECO Guide
What the Student RECO Guide Is and When It Applies
Why a Clear Student RECO Guide Matters
A consistent Student RECO Guide ensures that recommendations are complete, auditable, and reproducible across reviewers and units, reducing disputes and administrative rework while preserving an official record of support or eligibility.
Who Completes and Relies on the Student RECO Guide
The Guide is used by multiple campus roles for different purposes — from admissions committees to internship coordinators and scholarship administrators.
- Admissions officers and graduate program staff who aggregate recommendations for selection panels and need consistent evaluative data across applicants.
- Faculty recommenders and department chairs who must document academic assessments, course performance, and suitability for a program or placement.
- Registrar and records staff who store the completed Guide as part of the student file and apply retention and privacy controls.
Different users will apply varying access controls and redaction rules depending on FERPA, institutional policy, and the intended use of the recommendation.
Stepwise Process to Complete the Student RECO Guide
-
01Prepare: Gather student ID, program name, and supporting documents before starting.
-
02Complete Fields: Enter all required fields using specified formats and avoid shorthand.
-
03Verify: Confirm identity and content, checking for FERPA-sensitive data.
-
04Sign & Submit: Apply signature, date the form, and route to the designated office or system.
How to Configure an Online Completion Workflow
| Field | Configuration |
|---|---|
| Template Fields | Map name, ID, program, date, and text to required form controls |
| Authentication | Use email link or SMS OTP; stronger KBA for high-sensitivity records |
| Routing Rules | Auto-route to admissions, registrar, or program reviewer per selection |
| Storage Location | Save final PDF to secure records storage with access controls |
Technical Requirements and Supported Formats
Ensure chosen platforms support secure PDF/Word forms, audit trails, and integrations with institutional systems before deployment.
- Document Formats: PDF and Word DOCX are standard; keep a final signed PDF for archives
- Integrations: Connectors for Google Workspace, Microsoft 365, Salesforce, and NetSuite ease routing
- Authentication Options: Email OTP, SMS, or enterprise SSO options improve signer attribution
Confirm the platform supports the institution's retention and access control policies, and that BAAs or other agreements are in place when required.
Where to Send and How Submissions Are Processed
-
Admissions Office: Receives finalized Guides for applicant files and committee review
-
Registrar: Archives signed Guides in the student permanent record system
-
Program Coordinator: Uses Guide to confirm placement eligibility or interview invitation
-
Third-Party Reviewer: Shared only with consent and redaction where FERPA applies
Typical Timelines and Expected Processing Timeframes
Submission Window:
Provide Guide at least 2–4 weeks before committee meetings for full review
Administrative Review:
Initial verification commonly completes in 3–7 business days
Committee Decisions:
Allow 2–6 weeks for committee deliberation in peak seasons
Final Archival:
Signed Guides are archived within 7–14 business days of approval
Expedited Requests:
Processing may be shorter by agreement with the receiving office
Key Milestones from Request to Record
Request Received
Student or staff initiates the Guide request and provides identifying data
Recommender Response
Faculty completes recommendation and signs, typically within two weeks
Administrative Check
Office verifies identity, redacts sensitive data, and confirms completeness
Archive & Notify
Completed Guide stored and notification sent to stakeholders
Common Preparation Mistakes to Avoid
- Incomplete identifiers leading to unmatched records and delays in processing
- Using informal program names that prevent automatic routing in workflows
- Omitting signature dates which can create ambiguity about effective timing
- Sharing sensitive student data without required FERPA consent or redaction
Principal Risks and Administrative Consequences
eSignature Vendor Pricing and Feature Snapshot
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Frequently Asked Questions About the Student RECO Guide
-
Can the Guide be signed electronically?
Yes. Electronic signatures are legally binding under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and record retention are met.
-
Do recommenders need to sign in person?
Not usually. In-person signatures are only required if the institution or a receiving party mandates notarization or witnesses for that particular use.
-
When is notarization required?
Notarization is rarely required for internal recommendations but may be required when a recommendation supports licensure, legal proceedings, or official certification.
-
How should FERPA be handled?
Obtain student consent before sharing education records externally; maintain redaction and access logs to demonstrate compliance with FERPA rules.
-
What authentication strength is recommended?
At minimum use authenticated email links; use enterprise SSO, SMS OTP, or knowledge-based methods for higher-assurance needs.
-
How long must the Guide be retained?
Follow institutional retention policy; federal baselines include IRS three-year rules and HIPAA six-year retention for health-related records.