01
Onboard the person and business before access
Collect only the information required for contracting, payment, tax, procurement, security, and communication, using an appropriate secure channel.
General practice
- Verify the freelancer's legal or business name, contracting identity, primary contact, billing contact, and authorized signer.
- Identify the internal project owner, approver, accounts-payable route, access sponsor, and escalation contacts.
- Confirm the accepted agreement, scope, price basis, currency, invoice requirements, payment method, and purchase-order or reference needs.
- Request tax and bank information only when needed and through a secure process designed for that information—not casual project messages.
- Complete classification, conflicts, confidentiality, security, insurance, and procurement reviews before treating the freelancer as approved.
Start project selection with a usable brief, then add the administrative record.
- Client pathway →Define the need, evaluate evidence, agree scope, manage work, and close the project.
- Client project brief →Give candidates the same outcomes, deliverables, constraints, inputs, and approval process.
02
Treat worker classification as a legal and tax analysis
Calling someone a freelancer, issuing a contractor agreement, paying an invoice, or receiving a tax form does not by itself determine worker status.
State and local follow-up
| Layer | Current federal orientation | Required follow-up |
|---|---|---|
| Federal tax | The IRS examines relationship facts, including behavioral control, financial control, and the parties' relationship. | Use current IRS guidance and tax advice for the actual arrangement. |
| Federal wage and hour | The Department of Labor uses an economic-reality analysis under the Fair Labor Standards Act and currently flags rulemaking and enforcement developments. | Open the current Labor Department page rather than relying on a copied factor list. |
| Other federal statutes | Different statutes and agencies can use different definitions and purposes. | Identify every federal law relevant to the work and organization. |
| State and local | State wage, unemployment, workers' compensation, tax, leave, and other laws may use different tests. | Check the current law and agencies for every relevant work location. |
03
Determine whether tax documents and information reporting apply
The IRS provides current guidance on Form W-9 and Form 1099-NEC for independent contractors. Applicability depends on classification, payer, payee, payment type, amount, tax year, and other facts.
U.S. federal orientation
- Complete classification analysis before treating contractor reporting as a substitute for employment obligations.
- Use the current official Form W-9 and instructions to determine what information to request and how to protect it.
- Use current IRS reporting instructions to evaluate Form 1099-NEC or another form; do not rely on an old payment threshold or blog summary.
- Consider payment-processor reporting, backup withholding, entity type, exemptions, corrections, electronic filing, recipient delivery, and state reporting with qualified help.
- Restrict tax-identification data to authorized people and systems, and retain or dispose of it under current legal and business requirements.
04
Set invoice routing and exceptions before work
The freelancer should know exactly where to send an invoice, what reference it needs, who approves it, and what happens when the record is incomplete or disputed.
General practice
| Decision | Record before work | Exception to plan |
|---|---|---|
| Invoice route | Approved portal or address, billing entity, contact, and required fields. | Rejected, duplicate, suspicious, or misdirected invoice. |
| Reference | Purchase order, project code, milestone, service period, or other authorized reference. | Reference missing, changed, closed, or insufficient. |
| Approval | Named project and payment approvers and evidence needed for approval. | Approver absent, authority unclear, or work disputed. |
| Payment | Currency, method, timing basis, fees, remittance information, and verification channel. | Bank-detail change, failed payment, refund, overpayment, or fraud concern. |
| Reconciliation | How scope, change, delivery, invoice, payment, and accounting records connect. | Partial payment, credit, withholding, correction, or close-out difference. |
Use project and invoice records that both sides can reconcile.
- Invoice example →Review a fictional invoice with parties, work, prior payments, amount, currency, and payment details.
- Pricing and budgeting →Compare hourly, fixed, milestone, expenses, platform fees, and scope changes.
05
Maintain a complete vendor and project record
The record should show why the freelancer was selected, what both sides accepted, how the work changed, what was delivered, and how money and access were closed.
General practice
- Classification analysis and any professional advice or internal approval.
- Vendor identity, tax-document status, payment setup, insurance or procurement evidence, and authorized contacts.
- Signed agreement, scope, proposal, milestones, changes, confidentiality, ownership, and security requirements.
- Invoices, approvals, payment and refund records, expenses, tax-reporting records, and corrections.
- Deliveries, acceptance, licenses, repositories, account ownership, access history, retention, deletion, and offboarding.
06
Grant the least access needed for the shortest useful period
A contractor may need meaningful access, but broad shared credentials create avoidable privacy, security, operational, and offboarding risk.
U.S. federal orientation
- Use individual accounts, role-based access, multi-factor authentication where available, and a secure invitation or secret-sharing process.
- Give access only after confidentiality, security, data-use, subcontractor, incident, and return or deletion expectations are understood.
- Provide the minimum real data necessary; use sanitized test data and separate environments where practical.
- Maintain an access inventory and review it when work, people, systems, or risk changes.
- Require prompt reporting of lost devices, suspicious login, mistaken disclosure, malware, unauthorized access, or vendor incidents.
Use the dedicated information lifecycle guide for implementation details.
- Protecting client information →Plan minimization, secure sharing, access, AI use, retention, deletion, incidents, and handoff.
07
Manage the result without assuming classification
Project management choices are facts in a classification analysis. Do not use this guide to convert a desired label into a predetermined result.
State and local follow-up
- State outcomes, deliverables, quality, deadlines, interfaces, security constraints, and acceptance criteria clearly.
- Document who decides methods, schedule, location, tools, staffing, sequence, and work for other clients as those facts actually operate.
- Do not assume that remote work, part-time work, invoicing, an entity, multiple clients, a contract clause, or a tax form decides status.
- Reassess when the relationship becomes longer, more exclusive, more controlled, more integrated, or materially different from the approved arrangement.
- Use employment, tax, and state-law counsel when facts point in different directions or the consequences are material.
08
Offboard the project, vendor, access, and records
Final delivery is only one close-out event. Client teams should reconcile work, money, ownership, access, data, tax records, and continuing duties.
General practice
- Verify accepted deliverables, source files, documentation, licenses, repositories, domains, accounts, and organization ownership.
- Reconcile approved changes, invoices, prior payments, expenses, credits, final balance, and tax-reporting records.
- Remove individual accounts, tokens, keys, integrations, devices, forwarding, and physical access; rotate shared secrets that could not be avoided.
- Confirm confidential information and client property were returned, retained for an identified reason, or securely deleted under the agreement and applicable rules.
- Record final acceptance, unresolved issues, continuing support, warranties, confidentiality, ownership, retention, and incident contacts.
Source register
Official starting points for this guide
Reviewed September 22, 2026. These are federal starting points, not a substitute for state, local, profession-specific, contract, or current-year review.
- IRS: Forms and associated taxes for independent contractors ↗U.S. federal. Supports Form W-9 investigation, Form 1099-NEC investigation, current reporting instructions.
- IRS: Employee under common-law rules ↗U.S. federal. Supports federal tax classification, behavioral and financial control, relationship facts.
- U.S. Department of Labor: Independent-contractor rulemaking ↗U.S. federal. Supports FLSA classification orientation, current rulemaking and enforcement-change warning, economic-reality analysis resources.
- IRS: Recordkeeping ↗U.S. federal. Supports income and expense records, supporting documents, fact-dependent retention.
- FTC: Cybersecurity for small business ↗U.S. federal. Supports data protection, multi-factor authentication, vendor access, incident response and backups.
- FTC: Start with Security ↗U.S. federal. Supports data minimization, need-to-know access, secure lifecycle, retention and disposal.
Keep going
Connect administration to the actual project
Client pathway
Prepare and manage a freelance hire
Connect vendor administration with a usable brief, fair selection, project management, acceptance, and handoff.
Onboarding checklist
Put the approved engagement into operation
Coordinate vendor setup, classification review, project records, payment, communication, information, and access.
Offboarding checklist
Close the vendor relationship deliberately
Reconcile work, payment, records, rights, access, client information, support, and continuing duties.
Information security
Protect client information
Apply data minimization, secure sharing, least privilege, MFA, AI boundaries, retention, and incident planning.