Credential · Everyone, every department · 8 clock hours

AI ProductivitySet it up once. Check it every time.

Find the jobs that eat your week, set up the AI you already pay for to do them, and check it every time. We build each piece together on the big screen first. Then you build a tested template for every task you repeat and three workflows of your own, each with a check before anything goes out, and use them on a week of real work.

Hands-on training on your company's own AI: Microsoft Copilot, ChatGPT, Gemini or Claude

Plan training How it's earned

The credential at a glance

Credential: AI Productivity Certificate
Type: Certificate
Clock hours: 8
Format: Four 2-hour build sessions, in person
Schedule: One 2-hour session a week, or two 4-hour half-days a week apart
Price: $1,000 a seat, invoiced after the last session
Class size: 8 to 15 people
How it's checked: Six checks on the work itself, a live demo and a 20-question quiz
Department versions: 8 department versions. Every version earns the same AI Productivity Certificate, checked on the same six things. Only the practice work and examples change.
TechCred: Listing in progress. Reimbursement isn't guaranteed until the state lists it.
Issued by: Paglow Automations (Ohio AI Solutions LLC), Lima, Ohio
Before the first session: Comfortable with email, documents and spreadsheets. No technical background needed.
A business seat on the company's AI (Microsoft 365 Copilot, ChatGPT Business or Enterprise, Gemini in Google Workspace, or Claude Team or Enterprise), working before session 1.
Five tasks you do every week, picked with your manager in a 15-minute kickoff.
Real examples of those tasks with the red data taken out: old emails, documents, notes or exports.

For TechCred

What a holder can do

This is the list the state reads. TechCred pays for hands-on skills in developing, building, configuring or operating technology, so every skill below ends in something you built, set up or ran, and I check the evidence myself.

Build

Make the thing that does the work.

Build a prompt template for each recurring task, with the context, an example and the output format it needs.
Evidence: Prompt library
Build three multi-step workflows that take a real input through the AI to a draft output, such as inbox to reply drafts, notes to tasks, or a document from a template.
Evidence: Three workflows run end to end

Configure

Set the rules it runs under.

Class the data those tasks touch as green, yellow or red, and check the company account's privacy, sharing and data settings before any work goes in.
Evidence: Data rules signed by the manager, and a settings check
Configure an AI assistant for their job (a project, agent or skill, as the company's platform calls it) with written instructions, reference files and a fixed output format.
Evidence: The configured assistant and its instructions

Operate

Run it, test it, keep it running.

Test each template on three real, sanitized cases against a written checklist, and revise it until all three pass.
Evidence: Template test log
Check AI output before it is used (facts against sources, numbers against the original, tone against the company's voice) with a person approving anything that leaves the business.
Evidence: Verification checklists and an approval log
Run the workflows on a week of live work and keep a log of time spent, fixes made and anything that went wrong.
Evidence: One-week run log

Analyze

Measure the work before and after.

Measure five recurring tasks in their own job: how often they come up, how long they take, and what a good result looks like.
Evidence: Task baseline sheet
Measure before-and-after time on the five tasks, write a one-page playbook a coworker could follow, and demonstrate it in five minutes.
Evidence: Before-and-after numbers, playbook and live demo

The four sessions

Two hours each. Something built every time.

In person, on the schedule that suits your team. Every session starts with me building one on the big screen while you call out the next step. Then everyone builds their own. You leave each session with something you keep, and I check it.

Session 1 · 2 hours

Set it up right

You know how long your five tasks take today, and your AI is set up for your job.

Together on the big screen: we set up one assistant for a made-up job, and you call out the next step
Your company's AI rules, and your data sorted into green, yellow and red
Privacy, sharing and data settings checked on your company's own account
Five tasks you do every week, timed: how often, how long, what good looks like
Your assistant set up for your job (a project, agent or skill, depending on the platform) with instructions and reference files

What I check: Your task times, your data rules and your assistant, set up

Session 2 · 2 hours

Build the library

A tested template for every task you repeat.

Together: we write and test one template on a made-up task
A template for each task: the background, an example, and the format you want back
Three real test cases per template, red data taken out, and what a good answer looks like
Each template tested, scored and fixed until it passes
The library saved where you and your coworkers can reuse it

What I check: Your template library and your test log

Session 3 · 2 hours

Build three workflows

Three jobs from your week running from a real input to a draft, with a check before anything goes out.

Together: we build one inbox-to-replies workflow for a made-up business
Three workflows from your own job, each from a real input to a draft
Built with what your AI already has: projects, files and connectors. Scheduled or agent steps too, if your company allows them
A checklist for each: facts, numbers, names, tone
A person signs off before anything reaches a customer

What I check: Your three workflows working, with their checklists

Session 4 · 2 hours

Run it, prove it

A week of real work done the new way, timed and written down.

Together: we work out a made-up week's numbers and write its playbook
We go over your week of real work from your run log
Before-and-after times on your five tasks
A one-page playbook a coworker could follow
A five-minute demo and the quiz

What I check: Your run log, your numbers, your playbook, the demo and the quiz

Two ways to schedule it

Weekly, or two half-days.

Same four sessions, same 8 clock hours, same credential either way. I don't run it as one long day: the week between visits is when people put what they built to work on real tasks.

Weekly

4 visits

One 2-hour session a week for four weeks.

Between sessions, people use what they just built on real work, and the next session picks it up.

Two half-days

2 visits

Two 4-hour half-days a week apart: sessions 1 and 2 on the first, 3 and 4 on the second, with a short break in each.

Between the half-days

Each person uses their assistant and templates on real work, logs the time, and saves the week's real inputs. On day two those inputs run through the three new workflows.

What I check

How it's earned

You earn it with the work, not just by showing up. I check what you built against the same six things for everyone.

Pass all six things I check (the six rubric criteria) at Proficient or better, score 80% or more on the 20-question quiz (16 of 20), and be there for all 8 hours.

Check 1