When you delegate work and it comes back wrong, the instinct is to blame the contractor. Usually the problem started earlier: the handoff was a sentence in a chat window, and everything else lived in your head. The contractor guessed. You corrected. You guessed how long the correction would take. Two rounds later you have spent more time than doing it yourself.<\/p>\n
This is fixable without software. What follows is a handoff spec you can build in a blank spreadsheet in about forty minutes, plus a worked example and a rule for deciding what to hand off first.<\/p>\n
A vague brief does not reduce your workload. It converts it into a slower, less predictable form of the same work: reviewing, clarifying, re-explaining and redoing.<\/p>\n
Three failure patterns cause most of it.<\/p>\n
None of these are personality problems. They are missing fields in a specification that nobody wrote down.<\/p>\n
Open a spreadsheet. One row per delegated responsibility, five columns. Fill every cell before anyone starts.<\/p>\n
Write one sentence describing the state of the world when this is done right, in the reader’s language, not yours. Not manage the inbox<\/em> but no customer email older than one business day without a reply or an owner<\/em>. If you cannot write the outcome as an observable state, you are not ready to hand it off.<\/p>\n Three to six checkable items. Each one must be answerable yes or no by someone who is not you. Looks professional<\/em> is not a criterion. Uses the brand template, no placeholder text, all links resolve, filename follows YYYY-MM-client format<\/em> are four criteria.<\/p>\n This is the single highest-value column. It converts taste into a checklist, which is the only form of taste another person can execute.<\/p>\n List every tool, file, credential, calendar and inbox required, who grants it, and the permission level. Grant the minimum that lets the work happen. Use per-user accounts rather than shared passwords, and note an expiry or review date for each item so offboarding is a filter on a column rather than an archaeology project.<\/p>\n Decide in advance when you look at the work and what you are looking at. A useful default for anything new: a small sample at roughly 10 percent of the effort, a draft at 50 percent, and final delivery. The early checkpoint exists to catch a misread brief while it costs an hour instead of a week.<\/p>\n Write who initiates each checkpoint. If the answer is always you, you have built a system that depends on your memory.<\/p>\n Separate one-time projects from standing duties. For anything recurring, record the cadence, the trigger, the deadline and what happens if it is missed. Invoices go out on the third business day<\/em> is a responsibility. Send the invoices<\/em> is a favor you will end up chasing.<\/p>\n Suppose you run a four-person studio and you still do invoicing yourself on the first weekend of the month. You bring in a part-time bookkeeper.<\/p>\n Outcome:<\/strong> every active client is invoiced for the prior month’s approved hours and fixed fees, delivered by 5pm on the third business day, with a receivables list sent to you the same day.<\/p>\n Acceptance criteria:<\/strong><\/p>\n Access:<\/strong> invoicing tool at billing-user level, read-only access to the time tracker, the shared client folder, and a shared mailbox alias so invoices come from billing rather than a personal address. No access to the bank account. Reviewed every six months.<\/p>\n Checkpoints:<\/strong> month one, the bookkeeper prepares all invoices as drafts and you approve before sending. Month two, they send the three smallest accounts and draft the rest. Month three onward they send everything and you review the receivables list only. Escalate to you within two hours if a timesheet is missing or an amount changed by more than 10 percent versus last month.<\/p>\n Recurring:<\/strong> monthly, trigger is the timesheet lock on the last calendar day, deadline is the third business day, missed deadline means a message to you that same morning with a revised time.<\/p>\n That is one spreadsheet row. It removes roughly every question this handoff would otherwise generate, and the 10 percent variance rule catches the expensive mistakes without requiring you to read each invoice.<\/p>\n Do not start with the task you hate most. Start with the one that scores best on four questions.<\/p>\n Three yeses means hand it off this month. Two means write the spec now and hand it off after you have run it once yourself while taking notes. One means it is not a delegation problem yet.<\/p>\n It will, at least once. Respond to the spec, not the person.<\/p>\n The work came back wrong.<\/strong> Before you give feedback, check the output against your acceptance criteria. If it passes every criterion and you still dislike it, the criteria were incomplete. Add the missing one and say so plainly. If it fails a criterion, point at the criterion. That conversation takes two minutes instead of twenty.<\/p>\n The deadline slipped with no warning.<\/strong> The gap is in your checkpoint column. Add an earlier, smaller checkpoint rather than a stricter deadline.<\/p>\n You keep getting questions.<\/strong> Log every question against the row it belongs to. After two weeks, the rows with the most questions show you exactly which outcomes were written vaguely. Rewrite those three, and the question volume drops without a single process meeting.<\/p>\n Rework keeps happening on the same step.<\/strong> Ask the contractor to write the checklist for that step and send it to you for approval. People follow instructions they wrote.<\/p>\n Be honest about the limits. A spreadsheet handles this well up to roughly five contractors and a few dozen recurring responsibilities. Past that you start hitting real problems: no version history on who changed an acceptance criterion, no automatic reminder when a checkpoint is due, no audit trail of who had which access in March, and no safe way to let a contractor see their rows without seeing everyone else’s rates.<\/p>\n At that point you want either a proper task system with recurring templates, or shared documentation with permissions. The spreadsheet has still done its job, because the hard part was never the tool. It was deciding what finished looks like. Migrate the thinking, not the file.<\/p>\n You should also revisit the sheet on a schedule. A quarterly pass to close out finished projects, revoke stale access and delete responsibilities nobody actually needs keeps it from becoming a museum.<\/p>\n Pick the single responsibility you most want off your plate, write its five columns today, and run the next cycle against it. If you would rather work from prepared templates than a blank sheet, the Delegation & Contractor Handoff OS<\/a> packages the same spec as ready-to-fill worksheets and checkpoint trackers. You can browse the full range in the Cursiqa shop<\/a>, or keep reading practical operations guides on the blog<\/a> first.<\/p>",
"protected": false
},
"excerpt": {
"rendered": " Delegation fails when the brief is vague. Here is a five-part handoff spec – outcomes, acceptance criteria, access, checkpoints and recurring duties – plus a worked example.<\/p>",
"protected": false
},
"author": 1,
"featured_media": 0,
"comment_status": "open",
"ping_status": "open",
"sticky": false,
"template": "",
"format": "standard",
"meta": {
"_jetpack_memberships_contains_paid_content": false,
"footnotes": ""
},
"categories": [
33
],
"tags": [
135,
134
],
"class_list": [
"post-473",
"post",
"type-post",
"status-publish",
"format-standard",
"hentry",
"category-business-productivity",
"tag-contractor-management",
"tag-delegate-work"
],
"aioseo_notices": [],
"aioseo_head": "\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t2. Acceptance criteria<\/h3>\n
3. Access<\/h3>\n
4. Checkpoints<\/h3>\n
5. Recurring responsibilities<\/h3>\n
A Worked Example: Handing Off Monthly Client Invoicing<\/h2>\n
\n
A Decision Rule for What to Hand Off First<\/h2>\n
\n
What to Do When the Handoff Goes Wrong<\/h2>\n
Where a Spreadsheet Stops Being Enough<\/h2>\n
Start With One Row<\/h2>\n