Team onboarding & time tracking

A new contractor needed more than an account invitation. They needed to understand which assignment they owned, where the brief and working document lived, which checks preceded handoff, and how their time should be recorded. Noah created and delivered operational walkthroughs connecting these practical steps to 1SecondCopy’s production process. The evidence includes task training, knowledge-base explanations and a detailed Harvest setup procedure.

This was shared company work. Noah appears as a co-founder explaining the systems, clarifying confusion and coordinating setup. Writers, editors and operations staff performed the work and reviewed the output. A separate agency discussion specifically credits the cofounder with AI-tool documentation, so the full training curriculum should not be attributed solely to Noah. Company peak headcount is not a training-cohort count or Noah’s direct-report count.

The Harvest procedure starts with the hiring pipeline, not with a blank invitation. The operator locates the new hire and checks closed or completed statuses if search appears to miss them. Email provides a more dependable match when the person’s Slack display name differs from the application. The walkthrough also corrects an initial naming choice toward the legal name supplied in the hiring form because those records feed contractor invoices.

The operator retrieves agreed rate and weekly capacity, normalizes the rate to the agency’s internal USD convention and confirms it with the contractor. If a different capacity has been agreed after application, the newer agreement takes precedence. These are human setup and confirmation steps. They should not be presented as an unattended identity, currency or contract-management system.

The operator adds the contractor in Harvest with the relevant writing/editing role, capacity and cost information. The guide explains that an available subscription seat may be required before an invitation can be sent. It also notes an easily missed offboarding detail: archiving a user does not automatically reduce the paid seat allocation. These are operational checks documented for the person administering access.

Project access is then configured for current and future work, with irrelevant administrative projects removed. The invitation itself is only an intermediate state. Noah describes invitations going unaccepted and instructs the operator to contact the person, confirm receipt and make sure signup is completed. The procedure closes the gap between creating a user record and having a contractor who can actually record time.

The ClickUp walkthrough uses a test account and a sample assignment. It explains the parent task, the writing assignment, final-draft subtask and submission step. A personal assignment view includes work assigned on either a parent or a subtask. The parent retains article-specific instructions alongside reusable client requirements, so an editor must read the parent brief even when assigned only to the final-draft step.

The project-folder link contains the working Google Doc and any additional briefs, specifications or images. Writers are instructed to work in that document throughout production. The training explains due-date prioritization, moving the task to writing when work begins, completing checks before changing stages, and handing over to editing or readiness for submission. Comments, mentions and Slack provide a way to resolve uncertainty rather than silently advancing incomplete work.

The quality checklist covers read-throughs, source validation, formatting, client requirements, plagiarism checks and time recording. The Harvest guide adds a specific error case: people sometimes log writing time under a client-content-submission task instead of the writing or editing activity. Providing the time-tracking instructions and checking that classification were part of onboarding because the data also supports project-cost visibility.

During the move from ClickUp time tracking to Harvest, Noah recommends starting Harvest on a clean new day. Earlier ClickUp time can then be migrated for the period before that cutover. The operator is told to contact Noah to arrange the migration. The source describes an automated migration process, but the reviewed evidence does not independently test its reconciliation or show that every contractor completed it successfully.

An earlier Notion guide taught linked client records, project folders, rough-draft and final-edit handoffs, revision priorities and time breakdowns. It also pointed people to training resources on AI prompts and tool limitations. Later narration says production moved to ClickUp while Notion remained a documentation home. These sources show continuity of operating knowledge across a platform change, rather than proving that all tools were simultaneously the active production system.

The evidence also separates a proposed sequential course with view validation from deployed training. The proposal belongs to an operational planning update. Existing narrated tutorials and later retrospective descriptions of a structured learning sequence establish training activity, but do not prove a finished course platform, verified lesson completion, a specific cohort size or measured improvement in writer output.

A complementary offboarding guide asks staff to retrieve ClickUp time evidence before removing a user, because the historical reports become harder to access afterward. It calls for a screenshot containing the total and date range, and warns that Harvest-only time will not appear in a ClickUp report. That was an interim manual control, not a proven durable archival system.

Together, these procedures demonstrate Noah’s contribution to making a distributed workflow teachable and administrable: record lookup, access setup, invitation follow-through, task ownership, quality gates and a clear time-tracking boundary. No quantified onboarding saving, autonomous training result or current production-state claim is established by these historical recordings.