George Ferguson

George Ferguson

Location: lynchburg, virginia

About me

Who I Am
I'm the College Director at the CVCC Amherst Early College Center, a small satellite campus where I get to do the work I care about most — helping students take their first real steps into higher education. I oversee dual enrollment programming, manage faculty and day-to-day operations, and build the kind of community partnerships that open doors for the people we serve. I'm also a PhD candidate at Liberty University's School of Divinity, where my doctoral research explores forgiveness in the New Testament — specifically, the theological question of why some acts are described as forgivable, and others are not. It's deep, demanding work, and it shapes the way I think about grace, growth, and second chances in every part of my life. I believe everyone deserves someone in their corner — someone who will listen, show up, and help them figure out the next step forward.

What Drives Me
Leading a small campus means wearing every hat there is — advisor, administrator, coach, and sometimes the person fixing the printer. I love that. Small settings let you see the whole person, not just the transcript. I get to know my students by name, understand what they're working through, and meet them where they are. I'm committed to growing as a leader, not because I think I've arrived, but because the students and colleagues I serve deserve someone who's still learning right alongside them. Whether it's helping a first-generation student build a resume, walking a faculty member through a tough conversation, or staying up late pushing through another dissertation chapter — I want to be the kind of person who shows up fully.

What I Bring
My work sits at the intersection of higher education leadership and theological scholarship. On the campus side, I manage student services, faculty coordination, documentation, and community engagement. On the academic side, I'm trained in biblical exegesis, systematic theology, and doctoral-level research writing. I also have experience in career coaching, resume development, and helping students navigate the transition from community college to four-year institutions. I'm always looking for ways to connect — with other educators, with community organizations, and with anyone who shares a passion for making education more accessible and more human.

Interests

theology of forgiveness, servant leadership, ai in education, ai in education, first-generation student advocacy, biblical languages & exegesis, community partnerships, writing & scholarly research

Skills

higher education leadership, career coaching ai tools in education, scholarly research & writing, student advocacy, community partnerships

Activity

Your reflection captures a practical reality that has significantly reshaped institutional operations. The E-Sign Act's permission to substitute electronic signatures and records for traditional paper requirements represents a major shift in how institutions handle documentation, particularly in financial aid and enrollment contexts.

Your point also raises an important nuance the module addressed — that even with electronic records permitted, institutions must adopt reasonable safeguards against fraud and abuse. The shift from paper to electronic does not weaken privacy obligations; in some ways, it strengthens them, requiring password protection, regular password changes, access revocation protocols, user identification tracking, and random audits.… >>>

The FERPA Challenges to Consider module expanded my understanding of privacy law from FERPA alone to the broader regulatory landscape that institutions must navigate. FERPA does not stand in isolation — it interacts with HIPAA, the Solomon Amendment, the USA Patriot Act, the Gramm-Leach-Bliley Act, and SEVIS in ways that shape institutional practice.

The Solomon Amendment was particularly clarifying. Military recruiters have legal access to specific student recruiting information that may differ from what an institution designates as Directory Information. The reminder that the Solomon Amendment supersedes most FERPA elements means institutions must recognize multiple regulatory frameworks simultaneously rather than… >>>

Comment on Veronica Ortiz's post

Your reflection captures two practical insights from the module that often surprise people who work in higher education. The principle that FERPA rights end at death — defaulting to institutional policy and state law — is not widely understood, and it has real implications for how institutions handle posthumous record requests from family members, researchers, or media.

Your point about living former students still requiring written consent stood out as well. Many people assume that FERPA protections weaken after graduation, but the module made clear that former students retain inspection rights, amendment rights, and… >>>

Comment on Kathleen Theis's post

Your reflection raises an interesting tension the module surfaced: that FERPA protections are not uniformly applied across individuals and circumstances. Your observation that alumni records are not protected while requests for a former president's records typically still require consent shows how multiple layers of consideration shape disclosure decisions in practice.

Your phrase about leaning toward caution when it comes to privacy rights captures sound institutional wisdom. Even when FERPA technically permits a release — or no longer applies because a student has separated from the institution — additional considerations, such as state laws, institutional… >>>

The FERPA in Action module shifted my thinking from compliance as policy to compliance as a practiced discipline embedded in institutional culture. Knowing FERPA rules is necessary but not sufficient — institutions must operationalize privacy through security protocols, hiring practices, training, and oversight that work together to consistently protect student records.

The institutional security protocols framework was particularly clarifying. Limiting access to records based on legitimate role-based need, establishing strong password protocols, using automatic screen locks during inactivity, and protecting mobile devices through encryption all create the technical foundation for privacy protection. Without these systemic safeguards, even well-intentioned staff members… >>>

The FERPA in Action module shifted my thinking from compliance as policy to compliance as practiced discipline embedded in institutional culture. Knowing FERPA rules is necessary but not sufficient — institutions must operationalize privacy through security protocols, hiring practices, training, and oversight that work together to protect student records consistently.

The institutional security protocols framework was particularly clarifying. Limiting access to records based on legitimate role-based need, establishing strong password protocols, using automatic screen locks during inactivity, and protecting mobile devices through encryption all create the technical foundation for privacy protection. Without these systemic safeguards, even well-intentioned staff members can… >>>

Comment on Marsha Hunt's post

Got it, brother. Short peer reply. 💛

 
📝 YOUR REPLY (Ready to Copy and Paste):
 
Your reflection raises something many institutions overlook — that audit-related record reviews require the same documentation discipline as any other record disclosure. The module's reminder that each record selected during a regulatory audit must be individually noted (with agency name, date, information shared, and reason) is detailed work that is easy to skip when audit preparation feels overwhelming.

Your recollection from a past institution is honest and instructive. Many institutions assume that audit documentation is handled at… >>>

Comment on Terrence Mentzos's post

Your reflection captures the dual nature of FERPA compliance well — both a legal requirement and a relational discipline. The module's framework genuinely covers annual notifications, individual requests, and ongoing institutional practice as integrated elements rather than as separate concerns.

Your point about the overlap between PII and Directory Information stood out to me. The module's emphasis on the idea that institutions DEFINE what counts as Directory Information — within FERPA's limits — creates real institutional discretion. Some institutions are more permissive, others more conservative, and the same data element might be Directory Info… >>>

The FERPA Compliance module shifted my thinking from understanding FERPA principles to operationalizing them through institutional practice. Compliance is not just about knowing the rules — it requires disciplined documentation, intentional communication, and consistent application across every staff member who touches student records.

The annual notification requirement was particularly clarifying. Institutions must inform students of their rights to inspect records within 45 days, request amendments, request hearings, opt out of Directory Information, and file complaints. The notification can be delivered through catalogs, handbooks, websites, or registration materials, but it must happen annually. This is a non-negotiable institutional obligation.

The Directory… >>>

Comment on Danielle Bunner's post

Your reflection captures something the module taught indirectly but powerfully — that privacy compliance and pastoral integrity actually align. When educators document student interactions in ways that would be appropriate to share with the student directly, FERPA compliance becomes natural rather than challenging.

Your phrase about "secret notes" not needing to exist stood out to me. This is wisdom worth carrying. Notes written with the awareness that students may eventually read them tend to be more accurate, more constructive, and more focused on growth rather than judgment. The discipline of writing as if the… >>>

End of Content

End of Content