Planning a software-skills PD day for your office or department

Somebody has given you a professional development day and a budget, and the staff survey came back saying people want help with Excel. That is where most of these plans start, and it is also where most of them go wrong, because "help with Excel" describes six different problems held by people at four different skill levels who cannot all be taught the same thing on the same morning.

This is the structure I would use. It is not complicated, and once you have decided three things, the rest of the planning is logistics.

Decide the length first: half day or full day

A half day is roughly three hours. It fits one tool at one level, taught as a working introduction. Staff are back at their desks after lunch, and for a lot of offices that is the only version anyone will approve. It is a real training session, but be honest with the room about what it is: an introduction, not a complete program.

A full day is six hours. It fits one tool taught properly, or two tools split by level, and it is the format most teams take. The extra three hours are not more content. They are the practice time where people actually do the thing themselves rather than watch it done, which is the part that determines whether any of it survives the week.

Two half-days across a week is the underrated option. It works well for teams who cannot empty the office at once, and it has a real learning advantage: people go back to their desks between sessions, try what they learned, and arrive at the second half with actual questions instead of polite silence.

Decide what the day is actually for

Write one sentence: after this day, our staff will be able to ___.

If you cannot finish the sentence with something specific, the day will not be specific either. "Be better at Excel" produces a tour of features. "Produce the monthly departmental report without rebuilding it by hand" produces a day where we open the monthly report.

This is the single thing that separates PD days people remember from PD days people sit through, and it takes ten minutes to decide.

Decide how to handle a mixed-level room

Your room is mixed. Every room is mixed. There is the person who has been building PivotTables for years, the person who has never once used the Tab key and returns to the mouse for every single cell, and four people somewhere in between who would never say which group they are in.

Teaching all of them together means the confident ones are bored by ten and the nervous ones are lost by eleven. So split the day instead. A PD day is easier to structure than people expect, because you can run it like a small conference with two tracks rather than one long session.

The shape that works most often:

Morning, the foundation everyone needs. Word and Outlook fundamentals for the group whose day is documents and email. Structure in Word using Styles and sections, a table of contents that updates itself, and an inbox triage routine with a calendar that protects focus. This is the session where the widest range of skill levels can sit together, because almost nobody was ever formally taught either tool.

Afternoon, the intermediate group. Excel at the level that actually matches the work: real formulas, lookups, Tables, PivotTables, a sheet that prints cleanly. The staff who do not need it go back to their desks after lunch rather than sitting through it.

Reverse it if your nervous group is the Excel group. Beginner Excel in the morning when people are fresh, intermediate work in the afternoon. Either way, the principle is the same: two rooms' worth of content delivered in one day, with people attending the part that fits them.

Think of it the way a caterer thinks about a lunch. You do not serve one dish and hope. You ask what the room needs and plan around the actual mix, and it costs no more to plan it properly than to plan it badly.

Sorting the room without embarrassing anyone

Do not ask staff to self-report their skill level. People underestimate or overestimate, and in front of a manager, both are reputational.

Ask what they do instead. Three questions in an email, a week ahead:

What do you use this tool for in a normal week? What takes longer than you think it should? What do you currently ask someone else to do for you?

The third question is the useful one. The answers sort the room accurately, they are not embarrassing to write down, and they give me the real examples to build the session around. If four people say they ask the same colleague to fix the same thing, that is the day's agenda, already written.

How the money works

Pricing is published on every course page, and it is a session price rather than a per-seat fee. The Office foundation days, Word, Outlook, and PowerPoint, are listed at $750 to $1,495 CAD. The Excel levels are listed at $1,495 to $2,990 CAD. Where a quote lands inside the range depends on group size and scope, and you get the number in writing before anything is booked. There are no setup fees, no materials fees, and no venue cost, because the venue is your office. A half day is quoted at the lower end of the range; two half-days across a week are quoted and delivered as one session, not two.

The practical consequence for a PD day: because the price is per session rather than per person, the cost per head falls as the room fills. Six people in the room and twelve people in the room are close to the same invoice. If two departments each have four staff who need the same session, running it once for eight is substantially better value than running it twice, and the invoice can be split across both cost centres.

There is a ceiling on that, and it is pedagogical rather than financial. Hands-on software training stops working well past about a dozen people, because at that point I can no longer get to everybody who is stuck. If your group is larger than that, two sessions is the honest answer rather than one crowded one.

The logistics that actually matter

Very short list, because most of the usual PD-day worries do not apply to a session at your own office.

Everyone needs a computer with the software installed and working. Check this the week before, not the morning of. A staff member discovering at nine that their licence lapsed costs the room fifteen minutes.

A room where everybody can see a screen. A boardroom with a TV is fine. A projector is fine.

Real files. Send me two or three documents or workbooks your team actually uses, ahead of the date. The session is built on those rather than on sample data.

Protect the day. The single most common way a PD day underdelivers is people being pulled out for meetings. If the morning is booked, book it.

Where to start

• Browse the training topics to see what is covered at each level, with the price on every page.
• Microsoft Word training 101 - Styles, sections, and long documents that hold their structure.
• Microsoft Outlook training 101 - a triage routine and a calendar that protects focus.

Send me the date you are holding, roughly how many staff, and your one sentence about what they should be able to do afterward. You will get back a proposed shape for the day and a written quote.