One track from the AI-Enabled GC program, shown as the actual pieces an instructional designer produces — not a description of them. Built for a blended model: video, quizzes, and in-person components, with assessments that make certification mean something.
What this track is, who it's for, and how "trained, used in the workflow, and assessed" gets applied to this specific tool.
A reviewer can independently evaluate a TrunkSubmittal-flagged discrepancy against the cited spec section, confirm or overturn the flag, and either resolve it or escalate it correctly.
When a submittal is received, TrunkSubmittal analyzes it against the project's specifications and relevant RFI responses, flags non-compliant line items, and generates a structured recommendation. Everything in this track teaches someone to work with that output.
Modules 1–3 complete — understands what the tool checks and can classify flag types correctly
Module 4 — reviewed real flags on their own project's live submittal log
Module 5 — correctly resolves or escalates flagged discrepancies independently
Mechanism description and module structure grounded in a real customer deployment (public case study); ROI and adoption metrics from that source are intentionally left out — this track teaches the task, not the business case for the tool.
"Walkthrough of one flagged submittal" — the actual pre-production document that would go to video production. No real TrunkSubmittal footage exists publicly, so each screen is a labeled placeholder for what would be a real product capture.
Two pieces of "assessments that make certification mean something": a knowledge-check question from Module 3, and the rubric an evaluator uses to certify Module 5.
Sample knowledge check — Module 03| Criterion | Pass |
|---|---|
| Correctly identifies whether each flag is compliant, partially compliant, or non-compliant | ✓ |
| Cites the specific spec section (not just "the spec") when confirming or overturning a flag | ✓ |
| Correctly overturns at least one deliberately-incorrect flag included in the assessment set, rather than approving it by default | ✓ |
| Drafts a response to the trade partner that names the specific discrepancy, not a generic rejection | ✓ |
| Completes all 5 flagged items within the session — no more than 1 requires evaluator prompting | ✓ |
The deliberately-incorrect flag (row 3) is the design decision that makes this assessment mean something — a reviewer who approves every flag without scrutiny fails, because the standard is judgment, not compliance with the tool's output.
How "trained, used in the workflow, and assessed" gets tracked in the LMS — sample learner records, not real data.
Sample data — illustrative only| Learner | Role | Trained | Used in workflow | Assessed |
|---|---|---|---|---|
| Learner 001 | APM | Complete | Complete | Certified |
| Learner 002 | PE | Complete | Complete | Scheduled |
| Learner 003 | APM | Complete | In progress | Not started |
| Learner 004 | PE | In progress | Not started | Not started |
A real tracker would also roll these records up by account, cohort, and business unit — shown here at the individual-learner level since that's the record the certification standard is actually applied to.
Built for the Instructional Designer & Learning Operations Lead role at Trunk Tools. Grounded in the company's actual product mechanism and a public customer deployment; placeholders are labeled everywhere real product footage or live data would be needed.