Reading tracks

It organizes the wiki pages (as well as external videos, courses, and training) in the order they should be read, by position or by role, and records the acceptance of each item with date, time, and page version. It gives newcomers a starting point — the first week already scripted — and gives the company proof that the standard was communicated, with a verifiable code certificate when the track is completed.

On each item, the plus icon builds a quiz question (one option per line; the correct one is the line number, starting at 0). Learners answer through the question-mark icon and the score is stored on the enrollment. A finished path gets a certificate with a code. Anyone hired in the last 30 days is enrolled automatically in mandatory paths when this screen opens.

A track is a thought-out sequence, not a list of links. The "why read this" field is what separates "read this" from "read this because, without it, you'll get the first service call wrong" — and it's what makes the person open the page.

Accepting the whole track with one click is what happens with terms of use, and that's why nobody reads terms of use. Each page has its own "I read and understood", and the record keeps the date, time, origin, and the VERSION of the page that was read.

With the record, "nobody told me" becomes an objective conversation. Without it, sometimes the phrase is simply true — and the company has no way of knowing.

Besides the wiki page, an item can be an external link, a video, a document, or IN-PERSON training (which has no link at all — completion is self-declared). The reason is practical: restricting the track to the wiki forces the company to keep a second list outside the system, and it's always in that second list where progress dies. Each item can declare an estimated duration in minutes, and it's the sum of those that answers the only question the person really asks before starting: does this fit in my week?

Enrollment is the record that says who is taking the track, since when, and until when. Before it, there was always someone at 0% with no way to know whether they were behind schedule or whether the track wasn't even theirs. The "Enroll the target audience" button creates enrollment for whoever holds the track's role or position; it is idempotent — running it again does not duplicate anyone or reset those who already progressed. Whoever opens their own track is also enrolled on the spot. The deadline is counted from the start, with the number of days defined in the track; without a deadline there is no delay, only the absence of an agreement.

It comes from the acceptances: mandatory items completed over mandatory items in the track. OPTIONAL items are not counted — if they were, nobody would reach 100% and the number would stop meaning anything. Nobody can edit the percentage anywhere in the system, and that is what keeps it as proof instead of a recorded opinion.

This is intentional, and it's the rule that surprises people the most. When the procedure changes and you add a mandatory page, whoever was already at 100% becomes pending on that item again. The alternative would be worse: the proof of communication would silently go stale, and the company would keep believing everyone knows the new version of a rule that nobody read.

When someone is registered, has their hiring completed or changes role, Tenka enrols them right away in the mandatory tracks that apply to them: the company-wide ones, those for their role and those for the duties they hold. Anyone already enrolled keeps what they completed. People who have left the company are not enrolled.

It's usually a track that's too long, too generic, or pointing to outdated pages. Start with the first week of ONE role, with few pages, and expand later.

The person can report how many minutes they spent on the item they're completing; if left blank, the estimated duration applies. The system does NOT measure anyone's screen time — besides being surveillance, the number would be false (an open tab is not a read tab). What is stored serves the training hours that the company reports in audits, and it is honest precisely because it is self-declared.