TryPros Working with Freelancers: Contracts, Communication
Working with Freelancers: Contracts, Communication, and Payment
A freelance engagement needs an operating plan as well as a signed agreement. Someone must supply inputs, review submissions, approve changes, pay invoices, and keep control of the business accounts. Decide who does those jobs before the provider starts waiting for access or your team starts waiting for a deliverable nobody defined.
Follow the engagement from kickoff through handover using the checklist below. Use the separate contract worksheet for ownership and agreement questions, and the cost estimator to build the budget.
Turn the agreement into a working checklist
Translate the signed scope into a short list of outputs with owners and review dates. Each item should identify what will be delivered, what evidence shows it is complete, and who can accept it. Keep exclusions visible: “website implementation” may not include writing copy, buying images, or maintaining the site after launch.
For a hypothetical five-page website, the checklist could distinguish design approval, working pages, form delivery, launch checks, and handover. The provider owns the agreed production work; the client owns timely supply of approved copy and a named person for decisions. If another stakeholder must approve branding or legal language, include that dependency before scheduling the final review.
Make the relationship itself appropriate to the work. The IRS explains that a contractor label in a contract does not determine worker status. The actual working arrangement matters. If a project evolves into an indefinite staff-like role, revisit classification rather than assuming the original document settles it forever.
Prepare access without handing over the business
Create a list of systems the provider needs and the minimum role for each task. Prefer named accounts and scoped access over sharing the owner’s login. Keep domain registration, billing, recovery contacts, and essential business assets under the business’s control.
Check permissions in the actual product. For example, Google Drive distinguishes Viewer, Commenter, and Editor access. A reviewer may only need commenting, while someone producing files may need editing. Folder permissions are inherited: giving someone editing access to a parent folder cannot be undone by treating one ordinary child file as view-only. Use an appropriately restricted location for material that needs different access.
Keep tax forms, bank details, and unrelated customer records out of a broadly shared project folder. For any necessary sensitive data, agree where it may be stored, who may access it, and the return or deletion process. Confidentiality wording does not replace these operational decisions.
| Access record | Example entry | Closing action |
|---|---|---|
| Production system | Named collaborator, limited role | Remove after agreed support period |
| Project files | Dedicated folder with selected editors | Confirm business access and revoke extra sharing |
| Analytics | Read access for reporting | Remove if no further reporting is contracted |
| Billing or banking | No access unless specifically required | Review permissions and approval controls |
| Source repository | Named contributor | Confirm code transfer and remove access as agreed |
Record who can restore access if an account is locked. Discovering that the only administrator has left the project can turn a small handover into a prolonged interruption.
Hold a kickoff that resolves decisions
Use kickoff time to settle the open questions in the brief, not simply repeat everyone’s job title. Walk through the first deliverable and confirm what the provider needs before starting. Identify the approver, payment contact, backup contact, and channel for a genuine blocker.
A practical agenda is: scope and exclusions; available inputs; access; schedule and dependencies; review procedure; change approval; and handover. Send a short decision record afterward so absent stakeholders can see what was agreed.
Agree on availability, time zones, nonworking days, and response windows. For urgent support, define the covered incidents, contact method, staffed hours, and price. Put that coverage beside ordinary project delivery in the agreement.
Keep communication useful and searchable
Choose one place for task status and one durable record for approvals. Messages can support discussion, but major decisions should be easy to locate without reconstructing a long chat. Link the relevant file version whenever you request a change or accept work.
For a four-week design engagement, a useful starting cadence is a Friday written update and two scheduled design reviews. The update should cover completed work, the next deliverable, decisions needed, and the forecast completion date. Increase check-ins during a launch with several dependent teams.
When communication becomes difficult, name the problem before changing the meeting schedule. Missing source material needs an owner and delivery date. Conflicting feedback needs an approver. A complex explanation may benefit from a call or annotated example, but video is not the only effective or accessible way to communicate.
Use the remote communication guide for more detail on channels and time zones. Do not add tools merely because they appear on a standard software list.
Review against acceptance criteria
Separate three kinds of feedback: a failure to meet the agreed scope, a preference within an agreed revision round, and new work. That distinction helps both sides discuss responsibility and price without treating every comment as either free work or an extra charge.
For a website, “the contact form does not send to the agreed mailbox” describes a checkable defect. “Change the headline color within the selected design” may be an included revision. “Add appointment booking and payment collection” may be new scope. Resolve the classification against the actual agreement, not a generic assumption about how many revisions are standard.
Consolidate stakeholder feedback before sending it. Identify the version, describe the problem, explain its connection to the brief, and mark required corrections separately from suggestions. If stakeholders disagree, settle the business decision before asking the freelancer to implement conflicting instructions.
Maintain an acceptance record with the output, reviewer, date, and open conditions. Review design and implementation as separate milestones, and check that the handoff includes the rights and licenses specified in the agreement.
Put changes through a small approval process
A change request should state what changes, why it is needed, its price, its effect on the schedule, and who can authorize it. An email or task entry can capture the discussion, but use any formal amendment process the contract requires.
For example, suppose an agreed content package contains five articles and the client requests two additional articles. Ask for the additional fee, research requirements, and delivery date before production begins. If the original delivery date must stay fixed, discuss reducing another output or releasing the extra articles later.
Track approved changes against the budget reserve. A verbal suggestion during a meeting should not silently become permission to spend the full remaining budget. Similarly, a provider should not be expected to absorb new deliverables because a stakeholder describes them as “small.”
Make payment responsibilities explicit
Record the invoice recipient, currency, payment method, due date, tax documentation process, and any platform charges. Check these details with the person who actually processes payments. A project manager’s approval is not useful if the invoice cannot enter the accounting system.
Allocate payments to reviewable outputs such as discovery, design, implementation, and handover. For each amount, record when funds must be available and what triggers release. For hourly work, record the weekly authorization and invoice review window.
On Upwork fixed-price contracts, formal submission starts a 14-day review window. If the client does not act, funds are automatically released. Requesting changes through the workroom pauses release pending resubmission, which starts a new review window. These are Upwork’s published rules, so calendar the review rather than assuming an unanswered message will stop payment.
For direct engagements, follow the agreed payment and late-fee terms. For U.S. reporting and withholding, use the hiring FAQ’s tax section and have your accountant apply the rules to the payee and payment method.
Handle blockers and disagreements early
Record the specific missed obligation or failed acceptance check, its effect, and the proposed remedy. Give the other party a clear opportunity to explain and respond through the agreed process. Preserve relevant versions, messages, and submissions.
If a deadline moves, identify whether production, missing client input, or an approved scope change caused the delay. Request an updated schedule showing dependencies, then compare the recovery plan with the business deadline and available alternatives.
If the engagement must end, follow the notice and dispute process. Reconcile payments and rights to completed or partial work. Secure business accounts while preserving evidence and the access needed for the agreed handover.
Close with a usable handover
List the materials required to operate the result: final exports, editable source files where agreed, repository access, account ownership, license information, configuration notes, and outstanding issues. Check that the receiving person can open and use the materials without depending on the departing provider’s personal account.
For software or websites, ask for deployment and recovery instructions and the boundary of any warranty or support period. For design work, identify supplied formats and third-party asset licenses. For bookkeeping, reconcile the agreed period and explain unresolved items to the business owner.
Confirm portfolio permission separately, including whether the provider may disclose the company name, screenshots, or performance results. Remove access at the appropriate time, reconcile final invoices, and retain the contract and acceptance record. A successful handover leaves the business able to continue the work and both parties clear about any remaining obligations.