From your policiesto a running program.

i‑Grow.co turns your own approved documents into lessons, practice and assessments, then runs them for the people you choose. You set the goal and the rules. Nothing is published to your team until both approvals are on the current version.

  1. 01

    Add your documents

    Upload the playbooks, SOPs and policies your people need to learn from. Each one has an owner who approves it.

  2. 02

    Approve the plan

    A person at your company signs off the plan before any materials are drafted.

  3. 03

    Approve the materials

    Lessons and practice stay labelled as AI-generated until a person approves them.

  4. 04

    Publish

    Publishing stays blocked until both approvals are on the current version.

  5. 05

    People learn and practice

    Short lessons, then private rehearsal by text or voice. Practice stays private to each learner.

  6. 06

    See evidence, not a leaderboard

    Leaders see who is enrolled and the formal results. There is no overall score.

Evidence in four levels,never blended.

Completion is one number among four. Each level has its denominator and says what it can’t prove. The figures below come from a fictional cohort.

1
Participation and completion

Completion

9 of 10 completed

Shows who took part and finished. One person left the company mid-program; access was removed that day.

Doesn’t show whether anyone can do the work.

2
Demonstrated capability

Demonstrated skill

7 of 9 passed

The final assessment is an unfamiliar corrective case scored on five criteria. Both who missed decided before asking for the employee’s side.

A passed assessment shows skill on that task, not consistent behavior at work.

3
Workplace applicationComing soon

Applied at work

5 of 9 approved

A real corrective conversation, documented and checked by the supervisor’s own manager. Self-reports don’t count.

Shows the behavior happened. It doesn’t prove the training caused it.

4
Business measure, from your own recordsComing soon

Business outcome

14 → 9 a month

Repeat late arrivals per team each month: median of 10 teams before, 9 after.

Small sample, no comparison group. A signal, not proof of return.

The workyou hand over.

The same jobs an L&D team would do, split cleanly. Your side of the line stays small and specific. Everything to the right of it, i‑Grow.co runs.

Diagnosis

You provide: The goal, who takes part, and what “ready” means

i‑Grow.co runs: Baselines on unfamiliar tasks, then a ranked list of gaps per personComing soon

Per program

Program building

You provide: Approved playbooks, SOPs and policies, each with an owner

i‑Grow.co runs: Lessons, guides, practice and assessments that cite their sources

Per program

Enrollment & delivery

You provide: Who takes part, and your working hours

i‑Grow.co runs: Invitations by email, reminders capped and sent inside working hours

Daily

Practice

You provide: Nothing

i‑Grow.co runs: Private rehearsal with realistic pushback, never shown to the employer

On demand

Assessment

You provide: A person to handle re-check requests

i‑Grow.co runs: Unfamiliar cases scored on clear criteria, re-check requests routed to that person

Per milestone

Maintenance

You provide: An approval when a source changes

i‑Grow.co runs: Affected lessons updated, only affected people retrained, history keptComing soon

When sources change

One operator betweenyour knowledge and your people

You approve the inputs on the left. Everything on the right is produced, delivered, checked and kept current from them. When something falls outside your rules, it comes back to the owner you named.

Goals and deadlines
Approved knowledge
People and roles
Operating rules
i‑Grow.coChecks sources and authority before every action
Lessons and job aids
Private practice
Assessments
Evidence reports

Six reasons it’s safeto hand over.

Each one is a rule the product follows on its own, shown here as it happens.

Attendance Policyv3.2 · approved
Corrective Action Guidev1.4 · approved
Supervisor Handbookv2 · approved
LessonWhat the policy requirescites Policy §2
PracticeAttendance write-upcites Policy §4
AssessmentUnfamiliar casecites Guide §3
Grounded

Your documents in, programs out

Every item cites the document it came from.

“Does a doctor’s note stop a written warning?”
Attendance Policy v3.2 §5Approved1
Corrective Action Guide v1.4 §2Approved2
Shift notes, unreviewedDraft · not used
A note excuses that absence 1; earlier late arrivals still count, so talk to HR before writing it up 2.
Sourced

Answers only from approved sources

If nothing approved fits, it goes to the owner.

Reminders to Benweekly limit: 2
MonSent
WedSent
FriHeld
Bounded

Inside the limits you set

Reminders are capped and sent only in working hours.

Reminder for KofiTue 9:00
EmailFailed: mailbox full
EmailRetried once, delivered
Resilient

A failed send is retried, never doubled

One key per reminder, so a retry can’t send twice.

Program for new supervisorssample
What the attendance policy requiresLesson
Facts, not labelsLesson
An attendance write-upPractice
One-page write-up checklistReference
An unfamiliar corrective caseAssessment
Role-based

A program for each role

Each role gets its own lessons, practice and assessment.

Sessions completed
Assessments scored
Weekly report · sample
Completed9 of 10
Demonstrated7 of 9
Accountable

Evidence adds up to a report

Results collect into one report with denominators.

Ready when a companycan do this alone.

Our release test for calling anything autonomous. Every program is measured against it, with failures and exceptions counted.

  1. 01

    Set a goal, add people and knowledge

  2. 02

    Review the scope and set the rules

  3. 03

    Launch a program

  4. 04

    An employee completes the experience

  5. 05

    Follow-ups, assessments and a useful report

  6. 06

    Resolve a genuine exception

  7. 07

    Repeat for another cohort

0manual moves by an i‑Grow.co founder between those seven steps. That's the target every program is measured against. The guided demo walks the same path.