Session Agenda

Trainer Dashboard

Enter the trainer passcode to view submitted results. Set your own passcode by editing TRAINER_PASSCODE in this file.

Trainer Dashboard

Live results submitted by trainees β€” refresh to pull the latest.

Loading…
Training Session

One File. One Standard.
Every Department.

A short, hands-on walkthrough of the DCC Document Tracker β€” how the Document Controller Center, every department, and IT use the same workbook to move documents from tagged files into the company knowledge base.

Please enter your name so your trainer can see your results.

Use β†’ / ← or the arrows below to move between sections. Press F for fullscreen.

Why We Need One Shared Tracker

The company is 70% digitalized. Phase 1 β€” labelling and tagging, led by the Document Controller Center and every department β€” is complete. But tagged files sitting in different folders and habits aren't yet a knowledge base.

1

The Gap

Tagging tells us WHAT a document is. It doesn't tell everyone WHERE it stands right now, or WHO needs to act next.

2

The Fix

One shared workbook β€” the DCC Document Tracker β€” so status, ownership, and hand-off are tracked the same way everywhere.

3

The Payoff

IT always knows what's ready to ingest. Leadership always has a live dashboard. No document gets lost between teams.

Four Tabs, One Workbook

Open the file once and you'll always find these four tabs in the same order.

i

Instructions

Purpose, how-to steps, the color legend, and standard dropdown values. Read this first.

2

Document Register

The main log. Every document gets one row here, from intake through ingestion.

3

Dashboard

Live counts by status and department, plus charts β€” updates automatically.

4

Lists

Editable dropdown sources for Department and Category β€” keeps everyone consistent.

Anatomy of a Row

Every column is color-coded so it's obvious who owns it. Nothing is guesswork.

Yellow β€” Document Controller Center / Department inputTitle, Department, Category, Owner, Tagging Status, Tags, Sensitivity, QA fields, Ready for Handoff
Blue β€” IT inputIT Ingestion Status, Storage Location / DB Reference
Gray β€” Automatic, formula-drivenDoc ID and Overall Status. Never type into these.
Doc IDTitleDeptTagging StatusSensitivityReady for HandoffIT IngestionOverall Status
DOC-001 Vendor Agreement Procurement Complete Confidential Y In Progress Ready for Handoff

The Workflow, Step by Step

"Overall Status" isn't typed β€” it reads the columns below and updates itself.

Dept / DCC

1. Log & Tag

Title logged, tagging status set to Complete.

β†’
Dept / DCC

2. QA Review

QA Reviewed = Y, reviewer and date recorded.

β†’
Dept / DCC

3. Mark Ready

Ready for IT Handoff = Y once truly ready.

β†’
IT

4. Ingest

IT sets Ingestion Status to Complete.

β†’

5. Overall Status

Automatically shows "In Knowledge Base."

Standard Dropdown Values

Everyone uses the same words β€” this is what makes counting and dashboards possible.

Tagging Status
Not StartedIn ProgressComplete
Sensitivity
PublicInternalConfidentialRestricted
QA Reviewed / Ready for Handoff
YN β€” never blank once a document reaches that stage.
IT Ingestion Status
PendingIn ProgressComplete
Department & Category
Pulled from the Lists tab. Need a new department or category? Add it there β€” it appears in the dropdown automatically.

Check Progress Without Opening the Register

The Dashboard tab counts everything for you β€” never edit it directly.

By Overall Status

How many documents are Not Started, In Progress, Tagged, QA Complete, Ready for Handoff, or already In Knowledge Base.

By Department

A live count of documents logged per department β€” useful for spotting who's behind.

Sensitive Documents

A running count of Confidential and Restricted records, so nothing sensitive is overlooked.

Two Auto-Charts

Bar charts for status and department β€” they redraw themselves as the Register fills in.

Do's and Don'ts

βœ“ Do

  • Fill in yellow columns as soon as tagging/QA happens
  • Use only the standard dropdown values
  • Mark "Ready for IT Handoff" only when it's actually ready
  • Add new departments/categories on the Lists tab
  • Check the Dashboard before status meetings

βœ— Don't

  • Type into Doc ID or Overall Status β€” they're automatic
  • Invent new status words not on the standard list
  • Leave Sensitivity blank on a real document
  • Edit the Dashboard tab directly
  • Skip QA Reviewer / QA Date to save time

Knowledge Check

Five quick questions. Click an answer to see instant feedback.
πŸ”’ Heads up β€” once you move forward from here, you can't go back to earlier slides.

Quiz score
0 / 5

Classify It: Who Owns This Column?

Click a chip, then click the bin it belongs in β€” DCC/Department, IT, or Automatic.

DCC / Department
IT
Automatic
Select a chip above to begin.
0 / 0

Scenario: Read the Row, Predict the Status

Scenario

A Confidential HR record has finished tagging (Tagging Status: Complete) and passed QA (QA Reviewed: Y). This morning the department confirms it's ready and clicks it over to IT.

Wrap-Up

You're Ready to Track Documents Consistently

Remember: yellow is DCC/Department, blue is IT, gray updates itself. Mark "Ready for IT Handoff" only when it's true β€” that's the signal that keeps the whole workflow moving.

Your total training score
0 / 16
Send your results to your trainer

Submitting as β€”