Most contractor relationships end in one of two ways: the contractor leaves because they feel undervalued or unclear about what’s expected, or the business owner ends it because the contractor isn’t performing at the standard they imagined but never articulated. Both outcomes are expensive. Both are largely preventable.
The prevention isn’t a better contract. Contracts cover legal obligations; they don’t cover working style, communication expectations, or what “good” looks like in your specific business. The prevention is a pre-hire document, a direct, honest description of what it’s actually like to work with you, sent before anyone signs anything.
A contractor who reads this document and still wants to work with you is a contractor who’s already aligned. A contractor who reads it and decides it’s not the right fit just saved you 90 days of discovering the same thing through expensive friction.
Why Most Onboarding Fails Before It Starts
Onboarding typically begins after the contract is signed. That’s already too late. By the time a contractor starts, they have expectations built from the interview process, their history of other work engagements, and whatever assumptions filled the gaps in your communication. If those expectations don’t match your reality, the first two weeks are spent on corrections that feel personal rather than structural.
A pre-hire document eliminates most of that gap. It answers, before the first day:
- What does working with you actually look like?
- What tools do you use?
- How quickly do you respond to messages?
- What does “good work” mean to you specifically?
- What will the first 90 days involve?
Contractors who know the answers to these questions before starting have a dramatically different first month than those who discover them through trial and error.
Section 1: How We Work (Values and Communication Style)
Start with what’s non-negotiable about your working style. Not a list of generic values, specific, honest descriptions that would cause a contractor who doesn’t fit to self-select out.
What to include:
Your communication rhythm: “I work asynchronously by default. I check Slack twice daily, morning and afternoon. I don’t respond within the hour to most messages, and I don’t expect you to either. If something is urgent, call me.”
Your quality standard: “I’m more precise than most clients about [specific thing, word choice, pixel alignment, data accuracy]. I’ll give specific feedback, not vague ‘make it better.’ I expect that feedback to result in specific changes, not a general revision.”
Your decision style: “I’d rather you make a reasonable judgment call and tell me than wait for my sign-off on every small decision. Take ownership of your scope. When you’re unsure about something significant, flag it early, don’t solve it alone and surprise me at delivery.”
Your response to mistakes: “Mistakes happen. What I need is for you to tell me when something goes wrong before the deadline, not on it. Early problems are fixable. Last-minute ones create client issues.”
Keep this section to 200-300 words. Specific over comprehensive.
Section 2: Rituals and Tools
List everything a new contractor needs to access and the communication channels they’ll use. This section is operational, not cultural, it answers “how do I actually do things here?”
Template:
Project management: We use [Notion/Asana/ClickUp] for all project tracking. Every task has a due date and a brief. Check it at the start of each day. If a task doesn’t have what you need to complete it, comment on the task, don’t wait until the deadline.
Communication: Slack for day-to-day messages. Email for formal deliverable submissions and external communication. Video calls for complex discussions that would take more than 10 Slack messages to resolve.
File storage: [Google Drive/Dropbox/Notion] organized by client and project. New files go in [specific folder structure], see the naming conventions doc linked here.
Weekly standup: Record a 2-4 minute Loom by Monday at 10am. Three questions: what did you complete last week, what are you working on this week, anything blocked.
Monthly team call: First Thursday of each month, 12pm [timezone]. Informal, no agenda, no project updates. Budget 45 minutes.
This section should be a functional checklist, not a narrative. Contractors should be able to reference it on Day 1 and find every answer they need about daily operations.
The tools section is where most onboarding documents stop. That’s why most onboarding fails, logistics without culture is a map without a destination. The tools section tells people how to work. Sections 1, 4, and 5 tell them why the way you work matters and whether they’ll succeed. Both halves are necessary.
Section 3: Expectations (Availability, Turnaround, Quality)
Be explicit about what you expect without being unreasonable. The goal is no surprises, not a performance management document.
Availability: “I don’t expect any specific hours, work when you work best. What I do expect: if you’re unavailable for more than 24 hours on a weekday, let me know in advance. If something will cause a delay in a deliverable, I need to know 48 hours before the deadline, not on it.”
Turnaround times: “For tasks under 3 hours, I expect completion within 2 business days of assignment. For projects, we’ll agree on a deadline when the project is briefed. Once agreed, deadlines are real. If the deadline needs to change, raise it when you see it coming, not when it arrives.”
Quality standard: “I review everything before it goes to a client. I’ll give specific feedback, not as a criticism, as a calibration. After 4-6 projects together, I should be giving substantially less feedback because you know my standard. If we’re at Month 3 and I’m still giving the same volume of feedback, we’ll need to discuss whether the role is the right fit.”
Revision expectations: “My projects include two rounds of revisions in scope. If I ask for a third round because something missed the brief substantially, we’ll treat it as within scope. If you deliver work that meets the brief and I change my mind, that’s a separate scope conversation.”
Section 4: Compensation and Review Cadence
State the rate, payment terms, and review schedule explicitly. This prevents the awkward compensation conversation at Month 4 when the contractor assumes a raise is coming and you haven’t budgeted for one.
Template:
Rate: $[X/hour or $Y/month for retainer]. Invoices submitted by the last business day of the month, paid within 5 business days.
Overtime: If a project requires more hours than scoped, flag it before the overage happens. Unilateral overages won’t be paid. For pre-approved overages, I’ll pay at your standard rate.
Review cadence: We’ll have a 30-minute performance and compensation check-in at Month 3 and Month 12. Month 3 is about fit and adjustment, are expectations clear, is the work going well, what needs to change. Month 12 is about compensation review, if you’ve performed well, I’ll discuss a rate adjustment at that point.
Rate increases: I’m open to rate increases after the first year of strong performance. My standard is 15-20% annually for performers who are meeting the success criteria in this document. Please don’t raise the rate discussion before Month 12 unless something significant has changed in scope.
Section 5: What Success Looks Like in 90 Days
This is the most important section. Define success concretely, specifically, and with enough detail that both parties can evaluate it honestly at Day 90.
Template structure:
By Day 30: You’ve completed [specific number] of projects using the process documented in our SOPs. Feedback has been incorporated accurately on the first revision. You’re using the project management tool consistently and your tasks are never more than 24 hours overdue.
By Day 60: You’re completing your task type with [X% fewer revision rounds / Y% faster than the first month]. You’re asking fewer clarifying questions because you know my standards. At least one client has provided positive feedback on work you produced.
By Day 90: You’re operating independently on your core scope with minimal oversight. The quality of your work on standard tasks meets my standards without revision in most cases. We’ve had the Month 3 check-in and both parties are satisfied with the engagement.
Be specific. “Meets my quality standards” is not measurable. “Produces copy that requires fewer than 2 rounds of significant revision on 80% of assignments by Day 90” is measurable.
The pre-hire document is not a performance management tool, it’s a mutual alignment document. The business owner is also committing to things in it: responsive feedback, clear briefs, fair compensation review, honest communication. It works because both parties can hold each other to it.
Sending It and Following Up
Send the document 2-3 days before signing the contract. Not as an afterthought after the contract, as part of the pre-commitment conversation. “Before we finalize the agreement, I want to share how we work. Read through this and let me know if you have any questions or if anything gives you pause.”
The phrase “gives you pause” is intentional. It gives the contractor explicit permission to raise concerns or opt out without it feeling like backing out of a commitment. You want contractors who self-select in knowingly, not ones who sign and then discover surprises.
Contractors who reply with specific questions are engaged and paying attention. Contractors who reply with “looks good, excited to start” without any questions may not be reading carefully. Both are fine, the document does its job regardless.
After the engagement begins, reference the document explicitly at the Month 3 check-in: “Do you feel like the way we’ve been working matches what the pre-hire doc described? What was accurate, what was different?” That conversation reinforces that the document was real, not performative, and gives you honest feedback about your own working style that you can use to improve the document for future hires.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
