For technicians
General guidance that holds across the industry. Specifics vary by company, client and state, so confirm the detail with whoever you are working for.
Contract IT field work reaches you through four main channels. Dispatch companies, often called field service providers, hold national contracts with retailers, banks, restaurant groups and healthcare chains, then farm individual tickets out to local techs. IT staffing firms place contractors into longer engagements and are more likely to put you on their own payroll. Work-order marketplaces let you self-select tickets from an open pool, usually in exchange for a share of the rate. Direct clients — local businesses, managed service providers, AV and cabling contractors — pay you with nobody in between.
Most techs who stay busy use a blend. Marketplaces fill the gaps, dispatch companies supply volume, direct clients usually pay best. Knowing which channel you are dealing with changes what you should ask about, because each one judges you differently: a dispatch company cares about coverage and reliability, a staffing firm cares about your résumé, a marketplace cares about your rating, and a direct client cares about trust.
Read the full guide: How to connect with clients and dispatch companies
Onboarding follows a similar shape almost everywhere. You submit an application, build a profile with your skills and coverage area, upload documents, consent to a background check and sometimes a drug screen, sign the agreements — an independent contractor agreement, an NDA and a rate sheet — then complete any portal or app training and an acknowledgement quiz. Once your file is complete the company activates you and you become eligible for dispatch.
Elapsed time commonly runs a couple of weeks but varies widely, and the background check is usually the bottleneck. Most companies will not dispatch anything until every document is on file, so an incomplete profile quietly parks you with no rejection and no explanation. Keep one folder with current copies of everything so you can answer a request the same day. Before you finish, ask what actually triggers your first dispatch: some companies activate automatically, others need a coordinator to add you to a region.
Read the full guide: How to connect with clients and dispatch companies
General liability insurance and a COI. Most dispatch companies require a policy and a certificate of insurance naming them as certificate holder; limits around $1M per occurrence and $2M aggregate are a common ask . Buy from a small-business insurer and have your agent issue the COI. W-9. Download the current form from the IRS site and complete it with your legal or entity name and TIN. Background check. A consent form plus your details; results usually return within days. Drug screen. Required by some clients, particularly in healthcare, government and finance; you attend an authorised collection site. Tools. Expect a basic kit — hand tools, drivers, cable tester, toner, crimper, labeller, multimeter, and a ladder if you pull cable. Smartphone. Needed for check-in and check-out apps and photos. Reliable vehicle. Able to carry a ladder and reach sites inside the window. Business entity and EIN. An LLC with an EIN is common, separates your finances and is preferred by some companies.
None of this is instant, so start before you apply rather than after.
Read the full guide: Requirements checklist: what companies ask for before your first job
CompTIA A+ is the baseline many dispatch companies look for on hardware and break/fix work. Network+ signals that you can handle switches, routing basics and troubleshooting beyond the desktop. For cabling, low-voltage credentials carry real weight: BICSI installer levels and manufacturer certifications for structured cabling and fibre, plus any state or municipal low-voltage licence where one is required — licensing rules differ by state, so check yours. OSHA 10, and OSHA 30 for larger sites, is frequently requested for construction, warehouse and data-centre environments, and some clients will not badge you without it.
Beyond those, vendor-specific credentials follow the work you want: point of sale, ATM, network hardware or data-centre equipment. A certification rarely wins a job on its own, but it clears automated filters, supports a higher rate and keeps you eligible when a client tightens its requirements mid-contract.
Read the full guide: Certifications that actually get you more work
There are two common structures. Hourly pays for time on site, usually with a minimum — two to four hours is a typical ask — and may or may not include travel. Flat rate pays a fixed amount per ticket however long it takes, which is good when the job is predictable and painful when it is not. Travel is handled three ways: included in the rate, paid per mile beyond a radius, or not paid at all. Net terms describe when you are paid after invoicing; net 30 is common and net 45 or net 60 also appear . Some companies pay on a fixed cycle rather than per invoice, which can add weeks.
Before you accept anything, pin down the scope, what happens if the site is not ready or nobody lets you in, whether a trip charge applies, and who pays for parts and parking. The answers to those four questions decide whether a rate is actually good.
Read the full guide: Setting your rates: hourly, flat rate, travel and minimums
Late payment is usually a paperwork problem rather than an unwillingness to pay. Invoice against the work-order number exactly as that company formats it, and submit through the channel they specify — a portal upload often bypasses a queue that email sits in for weeks. Attach every required deliverable: the signed sign-off sheet or customer signature, before and after photos, serial numbers, closing notes, and tracking for any parts you shipped back. A missing signature is the single most common reason a ticket is held.
Invoice promptly. Many companies do not start the clock until the invoice arrives, and some enforce a submission deadline after which the ticket can be disputed outright. Keep a list of every open invoice with its due date, then follow up in writing a few days after terms lapse, quoting the work-order number. Escalate to the dispatch coordinator first, then to accounts payable.
Read the full guide: How to get paid on time, and what to do when you aren't
Dispatch coordinators reuse the people who make their day easier. Answer quickly: accepting or declining fast is worth more to a coordinator than accepting everything slowly. Arrive inside the window, and call ahead the moment traffic changes that. Check in and check out through the app every single time, because that is how the coordinator proves service levels to the end client — if you skip it, your good work is invisible to the people who report on it.
Photograph before, during and after, even when nobody asked. Write closing notes a stranger could act on: what you found, what you changed, serials, and what is still outstanding. Never leave a site without a signature or a documented reason. If you cannot complete the job, call from the site rather than reporting it afterwards, when it is too late to re-dispatch. Decline work you are not equipped for instead of failing it on site. Consistency over months, not heroics on one ticket, is what moves you to the top of a region's call list.
Read the full guide: On-site professionalism: what gets you called back
No single company will keep you busy. Techs who work consistently are typically onboarded with somewhere in the region of ten to twenty companies , so that a quiet month at one is covered by another. Onboarding is front-loaded effort: a few hours per company, once, that then pays out for years. Treat it as an investment you make during slow weeks rather than a chore you do when work dries up.
Widen your coverage radius deliberately rather than universally. Add the corridors you would drive anyway, and price travel into what you are willing to accept. Make sure every company holds your correct coverage area, because dispatch is filtered by radius before a human ever sees your name — a stale radius makes you invisible. Expect seasonality: retail freezes change windows late in the year, budget cycles slow the first quarter, and summer tends to bring refresh and cabling projects.
Read the full guide: How to get steady IT field work as a contractor
This is general information, not tax advice. Talk to a qualified tax professional about your own situation.
As an independent contractor you receive 1099 forms rather than a W-2, and no tax is withheld for you, so income tax and self-employment tax are yours to handle. Most contractors set aside a portion of every payment as it arrives and make quarterly estimated payments, which avoids both a large bill and a penalty at filing time. Keep business and personal money in separate accounts; every downstream task, from bookkeeping to proving a deduction, gets easier.
Track mileage as you go rather than reconstructing it later, because vehicle use is often the largest deductible expense a field tech has. Keep receipts for tools, insurance, phone, certifications and supplies, and save every invoice and payment record. When the 1099s arrive, reconcile them against your own records before filing — the totals do not always agree, and it is easier to query a figure than to amend a return.
Read the full guide: Taxes and paperwork for 1099 technicians
Be careful when a company will not put the rate in writing before you accept. Be careful with vague scope — “troubleshoot the network” with no site contact, no equipment list and no expected duration is a ticket that will overrun and then be disputed. Watch for a refusal to state net terms, or terms that keep sliding once the work is done. Treat any upfront fee to join a dispatch list, to buy mandatory proprietary tools, or to pay for your own background check as a reason to ask hard questions before you commit anything.
Be wary if nobody will give you a named coordinator and a number you can call from the site when something goes wrong. Jobs that require you to buy parts and claim them back later put your money at risk for someone else's project. And if the paperwork and the conversation disagree, trust the paperwork — the signed agreement is what gets enforced, not what you were told on the phone.
Read the full guide: How to get paid on time, and what to do when you aren't
For technicians
A realistic order of operations if you are starting from nothing. Timings are a guide, not a guarantee — background checks in particular set their own pace.
Week 1
Insurance quote and COI template, W-9, EIN if you are setting up an entity, background-check consent, tool list, résumé or skills summary, and a defined coverage radius.
Week 2
Work the directory in batches rather than one at a time. Same documents, same answers, different portals. Log who you applied to and when.
Week 3
Chase anything incomplete, sign agreements, finish portal training, and confirm with each coordinator that you are active and in the right region.
Week 4
Accept fast, document everything, invoice the same day. Then ask each coordinator what would make them send you more work.
For technicians
Tick what you already have. Nothing is stored or sent anywhere — this runs entirely in your browser.
For technicians
Free
Join the free Techwhere technician network. Tell us your skills and your area, and we'll keep your details on file. We never publish your address.
It takes about two minutes: your name, email, city, state and ZIP, and the work you do. We email you a link to confirm, and you can ask to be removed at any time.
Join freeAlready joined and changed your mind? Ask to be removed.
Full guides
Each one is a full article covering the topic in depth, with a checklist at the end.
Why contract IT field work dries up, how many companies to onboard with, and how coverage radius, response speed and a clean reliability record keep tickets coming.
Net terms explained, how to invoice right the first time, which deliverables stop a ticket being held, and what to do about late payments, disputes and short-pays.
What dispatch companies ask for before they will send you a ticket: insurance, W-9, background check, drug screen, tools, smartphone, vehicle, business entity and EIN.
What general liability insurance covers, the limits dispatch companies ask for, what a certificate of insurance and additional insured status mean, and how to keep cover current.
Which certifications dispatch companies actually filter on: CompTIA A+ and Network+, cabling and low-voltage credentials, OSHA cards, vendor certs, and which matter least.
Where contract IT field work comes from, how onboarding works step by step, how to build a profile that gets picked, and the intro email that gets a reply.
How IT field technicians price work: hourly versus flat rate, minimums, travel and mileage, after-hours premiums, and what to confirm before accepting a ticket.
What changes when you are paid on a 1099: estimated taxes, separating finances, mileage and expense records, and reconciling the forms you receive.
How IT field technicians earn repeat dispatch: response speed, arrival windows, check-in and check-out, photos, closing notes and knowing when to call from site.
A practical IT field service tool list by job type: core kit for every visit, plus cabling, networking, point of sale and break/fix, and smart hands additions.
Plain-English definitions of the IT field service terms technicians meet on work orders and in onboarding: smart hands, break/fix, NTE, SOW, COI, net 30 and more.
Pay once and keep it. No commission, no platform fees, no subscription.
