Describe the business before the tools
A useful Fairfax IT support brief starts with how your business works, where staff work, and what gets in the way. You do not need a technical inventory before asking for help. Start with the systems you recognize and label the things you need a provider to discover.
Use the actual service address when requesting onsite work. Fairfax City and locations within Fairfax County are not interchangeable addresses. Tell the provider about additional sites and home workers so the scope reflects the places support needs to reach.
Write a one-page support brief
- Business: the type of work you do, approximate staff count, and the person who can approve IT changes.
- Locations: office address, remote staff, and any building access or appointment requirements.
- Essential work: the applications and equipment needed for customer service, finance, and internal communication.
- Recurring problems: two or three examples, who is affected, and how often they happen.
- Current support: your provider or internal contact, contract timing if known, and where service records are held.
- Upcoming changes: new staff, an office move, a software change, or equipment that needs review.
Keep the first version short. Do not include administrator passwords, customer files, or employee identity documents. The provider can arrange an appropriate channel if a later technical review requires sensitive information.
Follow one problem across suppliers
An interrupted video meeting could involve the room equipment, office network, internet service, or meeting application. A payment terminal issue could involve the terminal, printer, network, or payment provider. Describe the symptom and list the suppliers you know about. Avoid deciding which one is at fault before diagnosis.
Ask who will coordinate those suppliers and who remains responsible for communicating with your office. Keep separate decisions visible. You may need managed IT support for daily operations, a meeting room project, or a Clover POS installation with its own scope.
Decide what needs attention first
Separate work that is currently blocked from planned improvements. Explain the business consequence, such as staff unable to access the day's schedule, rather than labeling every request urgent. Agree with the provider how requests are prioritized and how updates will reach you.
For planned work, identify the budget range you are comfortable discussing, the required completion date, and what depends on another decision. A move may depend on an internet installation and building permission before network work can be scheduled. Ask for those dependencies in the proposal.
Review the proposal against your brief
Check that each important need has an owner, an inclusion or exclusion, and a next step. Confirm support hours, response targets, onsite charges, licenses, and project assumptions. A free introductory conversation should lead to a recommendation about what is needed next, not an unsupported promise that the whole environment has been audited.
Use the managed IT quote comparison checklist if you receive several proposals. Its common-scope approach also works for a Fairfax office. Keep the brief and approved proposal together for future service reviews.
Start a Fairfax support conversation
UX Genius serves Fairfax and Falls Church businesses from its Reston office. Bring your brief, even if some details are still unknown.
Book a free 30-minute IT assessment. It is a conversation about your priorities, with no obligation. We will contact you to arrange a time. A site survey, technical audit, or implementation is scoped separately. You can also call (703) 755-0014.
IT support