Claude, your academic assistant (SOLD OUT)
You've already tried ChatGPT — and it made up a source or a number that didn't exist. You've tried NotebookLM — but you copy-pasted so much that you still need 4 hours a day to finish what you had to do. You gave it a whole project — but you had to explain so many details that it was easier to do it by hand.
You're not the problem. It's the way these tools were built. But now there's a different way to work: Claude works on your real files, not from memory, cites where each piece of information comes from, and learns your working rules once — you don't repeat them at every prompt.
Places sold out, let me know about the next edition →You work on your files — not on textbook examples. You tell him what you want, he works on your real files, you see every step — and where every piece of information comes from — and you decide.
How it works
You understand everything through applied exercises, on your laptop, on concrete cases.
| When | What we do |
|---|---|
| Tuesday, September 8 · 6:00 PM–9:00 PM | Session 1 · Fundamentals of using AI agents, collaboration on scientific literature and data analysis |
| Thursday, September 10 · 6:00 PM–9:00 PM | Session 2 · Academic routine work, project management, automation |
| Thursday, September 17 · 6:00 PM–7:30 PM | Q&A · come with any questions or obstacles you encounter |
Fundamentals of using AI agents, collaboration on scientific literature and data analysis
- What makes Claude Code different from a chat and how it works in your folder
- first task on real sources, directly on your laptop and your files
- How do you make him remember rules without repeating them?
- how to make verifiable, citable, non-hallucinated scientific literature syntheses
- how to use it for data analysis and publishable graphs
Session 2 · Academic routine work, project management, automation
- organizing a legacy project folder (minutes, emails, notes, photos, timesheets)
- administrative reports and documents: activity report, budget execution, time sheets, requirement reports, specifications
- how you create procedures for your routine work (e.g. learn to make your activity reports exactly according to your template)
- critical self-evaluation of one's own work with a panel of sub-agents
- Claude's connection to Semantic Scholar, PubMed, SciSpace, NotebookLM — no technical jargon
- routines: tasks that run automatically while you sleep
Q&A, September 17
You tell me what worked, what you couldn't apply, what you don't understand yet. You can come for 5 minutes with a specific question, you can stay the whole session. The important thing is that it's useful to you.
Each session is recorded, and the course is designed to be resumed individually after the workshop.
The problem we are solving
You rarely read just one paper: you have a stack, and you have to see where they contradict each other and what's missing. You have data that you have to gather correctly, not "from memory." You have your own paper, which you should look at critically before submitting.
And, in parallel, the project bureaucracy is not waiting: an inherited folder with meaningless file names, an activity report with a deadline to the funder, budget execution to explain, timesheets to fine-tune, reports of necessity and specifications to write. This is where the hours are spent — not on the actual research.
The workshop is for:
- researchers and university teachers
- doctoral and postdoctoral students
- project administrative staff (grant management, reporting)
- technology transfer specialists and project offices
- anyone who works with literature, data, reports, and funder deadlines
It's designed for academic research and project management — not general office work. (If you do PM, HR, or content without a research component, there's another workshop that's more appropriate, below under "Who it's not for".)
You don't need programming experience. You need real work with files — papers and datasets, but also project folders, reports, budgets, timesheets, purchases.
What will you be able to do in the end?
Each skill is practiced on a real case, on files — not on slides.
Literature synthesis on an entire corpus, directly from your folders.
From a stack of papers we extract comparative tables, cross-cutting themes, contradictions, limits and open questions, with each statement traceable to the source. Nothing invented.
Reproducible data analysis.
Claude runs code on your files (data tables), works with numbers, and you get accurate and reproducible results.
Organizing a chaotic project folder.
You transform a legacy folder into a clear structure: what each file is (including pictures read as images), what actions and deadlines it contains, what contradictions exist — flagged, not smoothed over.
Project reports and administrative documents.
Activity report in the financier's format, budget execution, time sheets, requirement reports, specifications — starting from your real files, with figures taken from the source.
A critical look at one's own work, with subagents.
A panel of sub-agents, each with a different lens, reviews your work before sending it for publication: weaknesses, questions for the author, score. Legitimately on your work, before you send it anywhere.
AI-learned work procedures, connected tools and routines.
You teach it your own work procedures once, it remembers them and applies them consistently. You connect it to the tools you already use for academic work and it works directly with them.
Claude on autopilot.
You set it to run overnight or at a fixed time. It's waiting for you in the morning with the day's agenda ready, reports already organized in folders, and drafts of responses to emails ready to be written — you just read them and press send.
At the end, you leave with a folder of examples, at least one of your own working procedures, and a way of collaborating with AI agents that you can immediately apply — both to research and to managing your projects. You can make up for the hours you wasted with copy-paste here.
Who teaches you?
I am Madalina Cocea. I have been working in research communication for over 20 years — currently at the Technology Transfer Center of the "Alexandru Ioan Cuza" University in Iași. I have trained over 2,000 researchers from over 10 universities: how to communicate what they do, how to structure their work, and how to manage communication on complex projects.
I know both research and project management inside out — the literature, the data, the reporting to the funder, the deadlines. I use Claude daily in my own work, with the discipline on sources that academia demands. This workshop is built from what works in practice, not from theory.
Your reservations — and why they shouldn't be
Any serious researcher has the same reservations. You're right. We'll put them on the table.
„"How do I know he's not hallucinating?"”
If you send a wrong number or a made-up quote to a funder or a journal, it's your responsibility, not the AI's — and you already know that. That's why I don't let it work from memory. At the workshop, Claude reads the source you give him and runs code on your data. Every statement is anchored to where it came from; what it doesn't find in the source is marked "to be verified," not invented.
„"How do I check what he wrote without taking on an extra job?"”
Verification is built into the flow, not pasted on at the end: every conclusion has its source next to it, every number comes from code you can run again. You don't redo the work — you follow the path.
„"Aren't you stealing my ideas?"”
The methodology, thinking, and decisions remain yours — Claude does the reading and drafting, you keep the thread. And you control what you expose: at the workshop we establish exactly what is okay to show when it comes to unpublished or sensitive data.
„"How do I understand what it does, if the mechanism is complicated?"”
You don't work in a black box. You write to him in Romanian what you want, he works step by step in front of you — you see what files he reads, what decisions he makes, what he writes — and you approve each step.
The entire workshop is based on the ethical use of AI, as it is now defined by funders and scientific journals (COPE, ICMJE, Nature, JAMA, the European framework): AI as a tool, not as an author; I teach you how to be transparent in your declaration; how to protect confidential data and how everything can be verified, without this process becoming a chore.
What's included
- 2 live sessions of 3 hours each, applied, on Zoom
- Written guide + setup video, sent before the workshop
- Recording of each session, available after the workshop
- An interactive course that you can resume as many times as you want
- Ready-made work procedures for research (literature synthesis, data profiling, review, activity report)
- At least one of your own work procedures, specific to you, built during the workshop
- Certificate of participation
- Follow-up Q&A in which we address any obstacles encountered or uncertainties
Places are limited to 25, so that I have time to respond to each one individually.
For whom it is not
If you want to fully automate article writing or bypass the integrity rules of journals and funders: this is not the workshop. Here we learn to use AI rigorously — with sources, verification, and human accountability.
And if you work in an office job (PM, HR, content, administrative) and want the same reflexes in your daily work, you have a dedicated course: Claude, your colleague at work.
What do I need?
- Own laptop (Windows or macOS), with rights to install a new application
- Account Claude with a paid plan that includes Claude Code — the most affordable, Claude Pro, starts at ~$20/month. (Claude Code, the tool we use, is only available on Anthropic's paid plans.)
- Stable internet connection and a Zoom account (free is enough)
Important: Claude's subscription is taken directly from claude.ai, not from other services that promise „access to Anthropic models.” It’s not the same thing and you won’t be able to work in the workshop with them.
Frequently Asked Questions
Do I need to know how to program?
No. You work through the Claude app — you write what you want to it, in Romanian, and it works on your files. The fact that it runs code on your data is an advantage (reproducible results), not something you have to write.
Do I have to give up my tools (Elicit, Consensus, SciSpace, NotebookLM)?
No. You keep using them for what they do well — search and discovery. Claude becomes the place where you gather what you find and transform it into a sourced, verifiable, and reproducible result: you connect it to your sources and literature indexes so that it starts from real works, not from memory.
What happens if I miss a session?
Each session is recorded, and you receive the recording after the workshop. Office hours are when we catch up on anything you missed in the meantime.
Can I pay with the teaching career card (Pluxee)?
No, unfortunately. In 2026, the Ministry of Education decided that the teaching career bonus can only be used for accredited postgraduate courses, on the official lists of the ministry — and this workshop is not an accredited course. Payment is made online, with any bank card. If your institution pays for the training, choose billing to "Company / institution" when registering and you will receive the invoice directly to the institution.
The September edition is full.
SOLD OUT
The September 8th edition is full. The 25 spots are occupied and I am no longer taking registrations, so that I can work closely with each participant.
And Claude, your colleague at work, the workshop that was due to start on September 1st, has closed registration. Leave me your details below and I'll email you as soon as I set a date for a new academic edition.
Do you want the next edition?
Leave me your details and I'll email you as soon as I set the date and open registrations. You don't pay anything now and you don't commit to anything.
English (UK) 
Română