Training for higher education · Effectv.ai for Education

Built on your faculty's own work, not on a generic curriculum.

A hands-on AI program for teaching, assessment, research and academic writing. Nothing is designed until we have spoken to you. Most of the room's time is spent working on material your faculty brought with them, and what they do with it afterwards is followed up and reported back to you.

Faculty and educator programs are currently running.

Faculty are five roles at once

Teacher, course designer, subject expert, administrator, researcher. Each has its own AI use.

Most faculty are already picking these tools up on their own, without a shared framework and without knowing what their institution or their publishers require of them. The question is not whether faculty use AI. It is whether that use is confident and correct.

Two rooms. Faculty choose their own.

Room A

Teaching and assessment

Course and session design. Turning a subject into a case or a simulation. An honest look at what students can already produce, and redesigning an assessment so it still tests what it is meant to test. A teaching assistant built on the faculty member's own course material.

Room B

Research and academic writing

Literature work without fabricated citations. Drafting support that keeps a paper's own voice. What publishers currently require in disclosure. Multi-step research work.

Both rooms cover the same core: what the tools do, how to check the output, and building one working assistant. They differ in what the worked examples are made of. The rooms normally run on separate days and are never merged into one. What the institution and publishers require comes first, before any hands-on work — that block sets out the requirements, it does not tell faculty what position to take on them. The day ends with them having drafted that themselves.

Fundamentals, then hands-on, then application

Three stages, and the third one runs after everyone goes home.

The three stages
01FundamentalsPlain language, no technical background assumed. Why different tools give different answers to the same question, how to check output, what can and cannot go into which tool — plus a working section on agents. Consistent across every room, so the faculty ends with one shared baseline.
02Hands-on, on their own materialFaculty work in small groups on something real: a case, an assessment, a reading list, a paper draft. Everyone builds one working assistant on their own course material, during the session. Everyone drafts one written position: a course or programme AI policy and a disclosure position, in their own words.
03Application, tracked over ninety daysOn the day, each faculty member names the one task they will hand to AI first. At day 30, a short written check-in. At day 90, a short note to you on what faculty actually did — papers submitted, assessments redesigned, course policies adopted.

And one thing that runs on all year: a monthly newsletter for faculty, on what is new and what faculty elsewhere are doing with it. Everyone in the room is enrolled at the end of the day, for a year — it is the reason the work does not stop when the day does.

What each faculty member leaves with

  • One working AI assistant, built during the session, on their own course material.
  • A clear picture of what their students can already produce, and what to do about it.
  • A one-page position, in their own words — what I use, what I disclose, what my journal requires, what my institution requires, what I will not do. Written and signed on the day.
  • A place on the monthly faculty newsletter, for a year.

What the institution leaves with: ten to twelve pages compiled from what the rooms produce — each department's drafted course or programme AI policy, and the disclosure position worked out for research. Written by your own faculty, which is the only reason it is worth anything. Dated, and ready to go through whatever approval it needs. Plus the note at ninety days on what faculty actually did.

What this program does not deliver

A first draft, not a finished policy.

This program builds capability and a working starting point. It does not deliver a finished institutional AI policy, a redesigned curriculum, or ongoing one-to-one research support. Those are real pieces of work, and faculty who want them can be scoped separately, after the program, once it is clear which ones are actually wanted.

The document handed over on the day is a first draft written by your own faculty. It is not an approved policy. This is stated before the program rather than after it, because a proposal that oversells the outcome underdelivers the trust the program runs on.

Who delivers it

Rajeev Soni, Founder & CEO, Effectv.ai. Eighteen years in product. Global Director, Search and Recommendations at Gartner. Founded SeeQR, later acquired. MBA, Ross School of Business, University of Michigan. Faculty and educator programs are currently running — Rajeev takes these regularly.

We sell no software and hold no vendor partnerships that pay us. What we recommend in the room is what we think is right for your faculty.

A short call with the dean or department heads.

To confirm faculty numbers, departments, and any existing AI policy we should build around. That sets how the rooms are arranged, and the dates follow.