Three things have to be true before the trainer walks in: every attendee can sign in to the same assistant from a company machine on the company network, every attendee has named one real task they want to finish in the session, and the documents for those tasks are in the facilitator’s hands a week early. Everything else on a pre-work list is optional.
Almost every vendor page reduces this to one bullet about tool access, aimed at participants. That framing is the problem. Most of the work that decides whether a session lands is not homework anybody in the room can do — it is license tiers, firewall rules, tenant settings, and a manager briefing. It belongs to the buyer, its lead times run in weeks, and it usually lands on a coordinator in the last 48 hours, well past the point where IT provisioning can still succeed.
So treat pre-work as a small procurement project with dates and owners. Here is the version that survives contact with a 200-person company.
The three items that change the session
Rank pre-work by what it protects. A hands-on session has a fixed number of working minutes, and each failed item eats them predictably.
- Verified sign-in, tested on a work device on the work network. Not “the company has licenses.” One person per function opens the assistant on their own laptop, in the office or on the VPN, and confirms they can start a conversation and upload a file. Access that fails at 9:05 costs the first half hour of a three-hour session, in front of the room’s skeptics.
- One named task per attendee. A sentence, not a project: “turn the weekly pipeline notes into the Monday summary I send to four partners.” A room that arrives with twelve named tasks is a different room from one expecting to be shown features.
- The documents behind those tasks, a week early. Redacted where policy requires. The facilitator needs them to build the exercises, and building exercises from real material takes days, not hours.
Everything else — pre-reads, videos, self-assessments, vocabulary primers — comes third. It does not change what happens in the room, and it competes for the same scarce attention.
Contact hours and coaching are what move people from a license to a habit, which is why those minutes are worth protecting. BCG’s AI at Work 2025 survey of more than 10,600 workers across 11 countries found that employees with five or more hours of training, particularly in person and coached, were significantly more likely to become regular users, while only 36% felt adequately trained. Five hours is not many, and losing forty minutes of them to sign-in problems is expensive in a way the invoice never shows.
A T-minus schedule with a name against every row
Pre-work fails because nobody owns it, not because nobody knows what it is. Put a date and a name on each row before the contract is signed, and give the whole list to one coordinator rather than to the group.
| When | Owner | Item | What breaks if it slips |
|---|---|---|---|
| T-3 weeks | Sponsor | Confirm the assistant the room will use and the license tier each attendee holds | The session gets designed around the lowest tier present |
| T-3 weeks | IT | Allow-list the assistant’s domains; confirm SSO provisioning and data-retention settings | Access cannot be fixed inside a week, so the format degrades to a demo |
| T-2 weeks | Coordinator | Send the intake: one named task per person, current tools, one frustration | Exercises come out generic because nothing specific arrived |
| T-2 weeks | Function leads | Brief managers on what the session is for and what they expect to see after | Attendance becomes optional and the quiet half declines |
| T-10 days | Coordinator | Collect three to five real documents, redacted if needed, from named people | Exercises run on invented material and teach nothing transferable |
| T-1 week | Facilitator | Build exercises and a starter prompt set from those documents | Live time goes to setup instead of practice |
| T-3 days | Coordinator | Confirm sign-in results per function; chase whoever did not reply | Failures surface in the room rather than in a thread |
| T-1 day | Coordinator | Restate the data-handling rule in one line in the calendar invite | People paste what they should not, or freeze and paste nothing |
The habit worth copying from the better vendor pages is the lead time. One provider publishes a four-item preparation list due at least ten business days before delivery — licenses verified, a survey on workflow frustrations, manager briefings, and a check that network rules allow the required services from the venue. The deadline is the useful part. A list with no date gets done the night before.
If the hours themselves are hard to protect, settle the calendar before the pre-work clock starts; those constraints are covered in our look at scheduling a session around a team that bills by the hour.
Access is a procurement job, not a participant chore
Four access decisions sit above the pay grade of everyone who will be in the room.
License tier. Free tiers gate the features a working session needs — file upload, longer context, saved projects, newer models. A room split across tiers either gets taught to the lowest one or watches half the exercises fail. Decide the tier for everyone attending, three weeks out.
Network reachability. Many corporate networks block consumer assistant domains outright, and a license does nothing about that. The test is not “does it work at home” but a work laptop, on the work network, uploading a file.
Tenant settings. Whether conversations are retained, whether they can train models, and whether an audit log exists are administrator-level switches. Participants cannot check them and should not have to guess. Get the answer in writing: it determines the one sentence in the invite about what may be pasted.
Identity. SSO provisioning for 30 or 80 people is a ticket in a queue, not a form. Three weeks is comfortable; three days usually loses.
Enablement is the part you build; provisioning is the part you buy. Confusing the two is how a company ends up with full seat counts and no capability, which is the argument in our case for treating this as capability rather than licenses.
One real task per person, and the document that goes with it
The intake question that produces usable answers is narrow: name one task you do at least weekly that takes longer than it should, and attach one example of what it produces.
Ask it that way and you get “the monthly board summary,” “client onboarding emails,” “turning survey comments into themes.” Ask “what are your AI goals” and you get sentences nobody can build an exercise from.
Two rules keep this workable. Cap the ask at about 30 minutes per person, because a non-technical room will not do more and the attempt damages the session’s reputation before it starts. And make redaction the coordinator’s job on a handful of documents: one person applying one standard beats 30 people improvising.
What arrives also decides whether the curriculum can be shaped at all. A vendor who receives nothing will teach the deck they already own, which is the distinction we draw in custom curriculum against an off-the-shelf course.
Pick one assistant for the room and say so in the invite
Standardize the room on one assistant and name it in the calendar invite. Two findings point the same way. Microsoft’s 2024 Work Trend Index, fielded across 31,000 knowledge workers in 31 markets between February and March 2024, found 78% of AI users bringing their own tools to work, rising to 80% at small and mid-sized companies. The default room is mixed, whatever the license report says. And Nielsen Norman Group’s guidance on preparing AI-enhanced workshops, published in May 2025, recommends that participants all use the same assistant so the room can troubleshoot together instead of losing time to differences between tools.
That piece adds two items worth copying: upload context files prepared in advance rather than setting context live, and test every one of those files beforehand. If the facilitator plans to use a custom assistant loaded with your context, that build belongs on the T-1-week row.
Standardizing for the day does not settle which tools the company keeps. A team already running three assistants has a separate problem, handled in training a team that already runs three assistants.
What the intake request tells you about the vendor
Read the pre-work request as a procurement signal. You get it free, before you sign.
- Asks for nothing. The session is a fixed deck. Price it as a talk, not as training.
- Asks for tool access only. The floor. It says they intend hands-on exercises, and nothing about customization.
- Asks for documents, tasks, and a short survey, with a deadline. They are building something specific, and they have been burned before by material arriving late.
- Asks for 90 minutes of pre-reading or a completion certificate. Either they are filling a gap the session cannot fill, or the format is a lecture with a quiz.
Buyers misread the last signal most often: a heavy reading list looks rigorous and usually means the opposite. The questions worth putting to a facilitator are set out in the workshop design playbook, which treats the intake as part of the design rather than paperwork.
Three pre-work items that are theater
Long pre-reads. A 20-page primer on how models work does not help somebody rewrite a client email faster; 15 minutes of guided practice on their own task does. Pre-reading has one honest use: a paragraph telling the room what the session will and will not cover.
Course completion as an entry ticket. Requiring a self-paced certificate before a live session sounds like rigor and works as a filter against attendance. Academic programs can enforce completion gates because their cohorts compete for a place. A company asking 40 people to finish several hours of catalog material before a Tuesday morning is buying resentment, not readiness.
Maturity self-assessments. A 40-question questionnaire scoring the team’s AI maturity produces a number nobody acts on. Three questions produce exercises: the weekly task, the tools already in use, and what most often goes wrong.
What published courses ask of you before the session
Checked against current public pages this month, here is what the catalog requires before you show up.
| Provider | Published unit | Published price | Pre-work published |
|---|---|---|---|
| Project Management Academy | One-day live virtual, 8 hours | $795 per person | A real checklist: approved assistant, basic familiarity, a recurring workflow, and a real or anonymized document. Says attendees without an approved tool cannot complete several modules |
| Certstaffix | Half-day overview plus four one-day live online titles | $350 per person per title | None stated |
| Google AI Essentials on Coursera | Five self-paced courses, under 10 hours | $49 per month after a 7-day trial | None; the page states no experience is required |
The spread is the point. One provider treats preparation as a gate and says what happens if you ignore it. The others ask for nothing, because a per-seat catalog course has nothing to customize. Neither is dishonest — they are different products, and only one can run on your documents. Private delivery at market rates, roughly $2,000 to $15,000 a session, is where pre-work becomes real, because that is where what you send in advance changes what gets taught.
When the pre-work does not happen
Assume partial completion. Some of it always slips.
- Access fails for a few people. Pair them. Two people on one screen is a legitimate format, and the pair that debugs together often learns more than the user who sails through.
- Access fails for most of the room. Move the session. A hands-on format with no hands is a webinar, and running it anyway spends budget and goodwill at once.
- No documents arrive. Make document selection the first 15-minute exercise. Slower, and recoverable — which is why the facilitator should hold a fallback set built from public examples.
- Nobody named a task. Spend the first 20 minutes extracting one per person out loud. The session gets shorter and still works, because the task is what everything else hangs on.
- The data rule is unclear. Default to the strictest reading: no client names, no personal data, no unreleased financials. Say it once at the top, show one redaction, move on.
An optional 15-minute sign-in clinic two days before removes most of this. It is the cheapest insurance in the program.
Frequently asked questions
How much pre-work is reasonable for a corporate AI workshop?
About 30 minutes per attendee, and no more. That buys a verified sign-in, one named task, and one document. Anything beyond that competes with the day job and gets skipped, which leaves the facilitator teaching two rooms at once.
Who inside the company should own the pre-work?
One named coordinator, with IT owning access and function leads owning the manager briefings. The coordinator chases individuals rather than mailing the group. Pre-work addressed to “all attendees” is how you arrive with half a room ready.
How far in advance should pre-work go out?
Three weeks for access and licensing, two weeks for the intake survey, ten days for documents, and a sign-in confirmation three days out. Access is the long pole because SSO provisioning and firewall changes sit in someone else’s queue.
What if IT blocks the assistant we planned to use?
Find out at T-3 weeks, not T-2 days. If allow-listing is refused, teach the tool the company already sanctions, often the assistant bundled with its productivity suite. Skills transfer between assistants; a session cannot survive a tool nobody can open.
Should attendees complete a pre-reading or an online course first?
Rarely. A short paragraph on what the session covers beats a reading list, and requiring a certificate mostly reduces attendance. Spend the reading budget on one page about the data-handling rule, which people do need before touching real material.
What document should each person bring?
The output of a task they repeat weekly: a status report, an email thread, meeting notes, a proposal section, survey comments. One example each, redacted by the coordinator against one standard rather than by 30 people improvising.
What happens if nobody does the pre-work?
The session degrades from practice to demonstration, and demonstrations do not change Monday. If the intake is empty two days out, move the date or rebuild the agenda to extract tasks live. Do not run a hands-on format and hope.
Does pre-work change what the workshop costs?
Not the fee. It changes the return on it. The expensive line item is the room’s time, and pre-work is what converts those hours from a presentation into practice on work people are already behind on.
Key takeaways
- Three pre-work items matter: a sign-in verified on a work device and work network, one named weekly task per attendee, and the documents behind those tasks a week early.
- Most pre-work is buyer logistics, not participant homework. License tier, firewall rules, tenant data settings, and SSO provisioning are decisions nobody in the room can make on the day.
- Put a date and an owner on every row, starting three weeks out. Access is the long pole: it sits in another team’s queue.
- Cap the per-person ask at about 30 minutes. Long pre-reads, completion certificates, and maturity self-assessments look rigorous and change nothing.
- Standardize the room on one assistant and name it in the invite. With most AI users bringing their own tools, the default room is mixed.
- Read the intake request as a procurement signal. A provider who asks for nothing has nothing to customize, which is why catalog courses publish no prerequisites.
Pull the license report, send one person to test sign-in on a work laptop from the office network, and ask three colleagues to name the weekly task they would most like to hand off. Twenty minutes of work tells you whether a session next month would land. A free AI-readiness call will tell you which function should go first and what its pre-work should ask for.
Arthur Wandzel
