Freelance checklists

How to use these checklists (without creating more busywork)

A checklist is a tool for execution, not a tool for feeling organized. If it is not tied to a real moment (a call, a kickoff, a payment problem, a weekly review), it becomes another tab you mean to get to later.

The best way to get value from this library is to pick the checklist that matches your current bottleneck, run it end-to-end once, and then reuse it as your default process. The "one checklist, one outcome" rule keeps you from turning checklists into procrastination.

Step 1: Pick the checklist that matches the moment

Most freelance problems show up in the same places. Use that predictability.

• If the moment is a sales call, start with the Discovery Call Checklist.
• If the moment is "turn this into scope and terms," use the Quote to SOW Checklist and pair it with the Statement of Work (SOW) template.
• If the moment is kickoff and access/approvals, use the Client Onboarding Kickoff Checklist.
• If the moment is scope drift, use the Scope Change Checklist and the Change Request Addendum Pack.
• If the moment is overdue invoices, use the Late Payment Checklist and the invoice template + late payment sequence.
• If the moment is weekly drift, use the Weekly Review Checklist.

A simple end-to-end sequence (from lead to paid)

If you want a default route that covers most projects, this sequence is a good baseline:

1. Qualify and capture constraints with the Discovery Call Checklist.
2. Turn notes into scope using the Quote to SOW Checklist and write it down with the SOW template.
3. Start delivery cleanly with the Client Onboarding Kickoff Checklist.
4. When scope changes (and it will), switch to process using the Scope Change Checklist and the Change Request Addendum Pack.
5. If payment drifts, run the system with the Late Payment Checklist and the invoice follow-up sequence.
6. Keep everything from drifting with the Weekly Review Checklist.

You do not need to run this sequence perfectly. The value is that you stop improvising in the high-stakes moments.

Step 2: Run it in the browser (then copy it once)

These checklists are interactive. When you check items off, progress is stored locally in your browser. If you want to adapt a checklist to your own terminology, use "Copy as Markdown" and paste it into your own doc.

The key is to copy once, customize, then reuse. If you copy every week, you are rebuilding the tool instead of using it.

Customization pass (15 minutes)

A checklist becomes powerful when it matches your reality. The fastest customization pass looks like this:

1. Copy as Markdown and paste into your own doc.
2. Rename the headings to match your language (for example, your preferred terms for milestones, approvals, or roles).
3. Add the 3-5 steps you always forget (access requests, billing details, decision-maker confirmation, etc.).
4. Delete anything you will not do. A checklist you do not follow is not a checklist. It is a guilt generator.
5. Save it as your default and reuse it until you learn something new.

The rule is: shrink friction, not vocabulary. The more the checklist matches how you actually work, the more likely you are to use it when you are busy.

Step 3: Turn it into a default operating rhythm

Checklists work when they become part of your cadence. A simple cadence that fits most freelancers:

1. Use discovery and scoping checklists when leads show up (so your pipeline turns into signed work, not vague conversations).
2. Use onboarding checklists at kickoff (so delivery does not start with missing access and unclear approvals).
3. Use scope and payment checklists when things drift (so you do not negotiate in a panic).
4. Use the weekly review checklist on a fixed day (so admin does not expand to fill your whole week).

Illustrative weekly rhythm (use what fits)

If you want a concrete example, here is an illustrative weekly rhythm that many solo freelancers can adapt. This is not a rule. It is a starting point that makes it harder for admin and ambiguity to take over your week.

• Monday: run the Weekly Review Checklist and send pipeline follow-ups.
• Midweek: schedule discovery calls and run the Discovery Call Checklist so calls end with a next step.
• When a lead is real: translate notes into scope with the Quote to SOW Checklist.
• Kickoff week: run the Client Onboarding Kickoff Checklist so access, approvals, and cadence are set early.
• Any time scope changes: switch to process with the Scope Change Checklist and document decisions with the Change Request Addendum Pack.
• Invoice day: send invoices and schedule follow-ups so money does not drift by accident.

The point is not to fill every day with process. The point is to give your week a few predictable anchors so sales, delivery, and money do not become emergencies.

When a checklist is the wrong tool

If you need a bigger reset (your offer is unclear, your rates are guesswork, you are burned out, or your pipeline is empty), checklists alone will not fix the underlying system. In that case, use Start here to pick a path, and use the Codex for the maintained system.

Common pitfalls (fast fixes)

• Pitfall: running five checklists at once. Fix: pick one that matches the bottleneck and finish it.
• Pitfall: treating the checklist as a script. Fix: use it as structure and notes, not as a performance.
• Pitfall: skipping the "in writing" step. Fix: if a decision matters (scope, approvals, payment), document it.
• Pitfall: never customizing. Fix: copy once, add your own common client confusions, and reuse.

Want the maintained system behind the checklists?

Checklists are the operational layer. The Codex is the maintained explanation layer. Two strong starting points:

• Set freelance rates (discovery, scoping, and pricing as risk management).
• Onboarding, delivery, retention (cadence, approvals, scope control, and client experience).