The contractor kickoff checklist: scope, milestones, rhythm

Most contractor engagements that fail were lost in the first week — not to bad hiring but to a missing kickoff. The fix costs thirty minutes: a one-page scope, visible milestones, an update rhythm agreed on day one, and access scoped to the first task. Here's the checklist, in the order you run it.

Why do engagements fail in week one?

Because "you're hired" and "productive work is happening" are separated by a set of small decisions nobody owns: what exactly is in scope, how progress will be visible, where questions go, what to start on. Left unowned, each resolves itself late and expensively — scope by dispute, visibility by chasing, the first task by a week of drift while the brief "comes soon."

The kickoff checklist just makes those decisions on purpose, while everything is still cheap.

☐ 1. Scope: one page, with edges

Write the outcome in two sentences, then the part everyone skips — what's not included — then done-criteria you could check without the contractor in the room ("checkout works on Safari 16+, passes the payment test suite").

The not-included list is the highest-value paragraph you'll write this engagement. Ambiguity always resolves toward whoever it favors at the moment of dispute: on fixed-price it shrinks your deliverable, on hourly it grows your invoice (the two models fail differently — the one-pager protects you under both). Keep it to a page; detail belongs in tasks.

☐ 2. Milestones: visible checkpoints for anything over two weeks

Break the work into two-to-five checkpoints a non-expert can verify. Their job isn't project-management ceremony — it's making trajectory visible early. "Milestone one slipped three days" in week two is planning; the same fact discovered at the deadline is a crisis. Attach rough dates and treat the first slip as a conversation, not a crime; the milestone's job is to surface the slip while it's small.

☐ 3. Rhythm: the update expectation, set today

One line in the working agreement: "Short weekly update every Friday — what got done, what's next, anything blocked. Everyone here does it, employees and contractors."

Timing is everything. Stated at kickoff, it's house process and nobody blinks. Introduced mid-engagement — after silence has already annoyed you — the identical request lands as an accusation. Decide where updates land, too: one shared place, not your inbox. (This is the habit that makes a five-contractor bench readable — see managing multiple freelancers — and it's what feeds a proper Monday digest covering everyone.)

☐ 4. Access: minimum first, widen deliberately

Grant what the first task needs: their brief, their tasks, a channel for questions. Not your whole toolchain, not the company wiki, not standing invitations to internal meetings. This isn't distrust — it's asymmetry management: widening access later takes two minutes; retracting it is an awkward conversation that damages a working relationship.

On WorkedOn's business side this shape is the default: a contractor sees exactly their own engagement — brief, tasks, thread — and nothing else, while their work still flows into your one company picture. Adding them takes about a minute (paste their profile link and the details prefill — from the URL and text you provide, nothing scraped), and they're assignable before they've even set a password.

☐ 5. First task: startable today

The single best predictor of engagement momentum is whether real work begins in the first 48 hours. Pick something meaningful but bounded — "reproduce the Safari checkout bug and post what you find" beats "get familiar with the codebase" — and assign it at kickoff so it's waiting when they log in. Early output does double duty: you learn how they work and communicate while course-correcting is still free.

☐ 6. Mechanics: questions and money

Two housekeeping lines that prevent outsized annoyance later: where questions go (one named channel — questions scattered across email, DMs, and comments are questions lost), and how invoicing works (schedule, format, who approves, when money moves). Contractors who trust the payment mechanics take risks like flagging problems early; contractors chasing invoices go quiet in every other way too.

---

Run the seven boxes and the first week looks like this: scope agreed, milestone dates visible, the Friday rhythm known, access granted in minutes, the first task already done — and your total setup cost was half an hour. The engagements that go wrong from here go wrong for interesting reasons, which is a luxury.

FAQ

What should a contractor kickoff include?

Four things in writing: a one-page scope (outcome, boundaries, done-criteria), milestones for anything over two weeks, the update rhythm (day, format, where it lands), and scoped access plus a first task they can start today.

How detailed should the scope document be?

One page. Long specs go unread and drift anyway; what prevents disputes is the outcome, the explicit not-included list, and measurable done-criteria. Detail lives in tasks, not the scope doc.

When do I set the update expectation with a new contractor?

At kickoff, framed as house process: "We do a short Friday update — everyone here does." Stated on day one it's professionalism; introduced in week six after frustration, the identical request reads as distrust.

What access should a new contractor get?

The minimum for the first task: their brief, their tasks, a place to ask questions. Not your full toolchain. Widening access later is a two-minute decision; retracting it is an awkward conversation.