Choose an IT provider that can explain how it will protect client information, support the systems your firm relies on, and restore work after an outage. Ask for written responsibilities, clear support targets, documented access controls, and evidence of tested backups. Compare providers against your actual workflows, then confirm who owns each task before signing.
In This Article
- What should an IT provider understand about a law firm's work?
- How can a firm evaluate security while keeping work moving?
- What should the firm ask about outages, backups, and recovery?
- How do Norcross office needs affect the provider choice?
- How should a firm compare proposals and references?
- Frequently Asked Questions
What should an IT provider understand about a law firm's work?

“John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed.”
A law firm's technology supports matter work every day. Email, document and practice management, billing, timekeeping, client portals, and remote access all affect how attorneys and staff serve clients.
Ask how the provider will learn which systems are essential, who depends on them, and what a disruption would prevent. A strong discovery process distinguishes a minor inconvenience from a missed filing deadline or an interrupted client document exchange.
Access needs vary by role and matter. Ask how the provider will review permissions with your firm rather than assume that one default setup works for every attorney, paralegal, and billing employee.
Discuss how access changes when someone joins, changes roles, or leaves. Mailboxes, cloud files, remote sessions, and line-of-business accounts may need separate actions. Confirm who requests, approves, and records each change.
Review five everyday control areas: identity, email, endpoints, matter access, and recovery.
Office projects can introduce additional dependencies. Internet service, cabling, Wi-Fi, access control, and cameras may involve property management, contractors, and carriers. Ask who coordinates the work and confirms the office is ready for staff.
The provider should understand your workflow before recommending tools or changes. That is the basis for useful support.
How can a firm evaluate security while keeping work moving?
Ask how the provider will protect accounts, devices, email, and client information in your firm's actual environment. The answer should address remote access and the systems staff use to handle documents and communicate with clients.
Ask how multifactor authentication will work for attorneys away from the office, employees using mobile devices, and approved outside professionals. A control needs a practical rollout plan so staff can follow it without resorting to workarounds.
Discuss how employees should verify changes to payment instructions. A message may appear to come from a client, colleague, or vendor. Confirm requests through a separate, trusted channel rather than relying on the display name or replying to the same message.
For confidential matters, ask how access is granted, reviewed, and removed. If permissions are matter-specific, find out how they stay current as teams change. Coordinate retention and litigation holds with your counsel or records owner; the provider should support the firm's process, not determine its legal duties.
Ask how the provider will help document security decisions and support the firm's incident response. Have qualified counsel determine whether Georgia breach-notification duties or client contract requirements apply, then confirm how the provider's procedures support the firm's response.
Look for specific explanations, not a promise that one product makes the firm secure or compliant. Good security protects confidentiality and lets routine work continue.
What should the firm ask about outages, backups, and recovery?
A backup matters only if the firm can restore the data and systems it needs. Ask what is included, how often copies are made, who can access them, and how restoration is tested. Request a recent test record or a clear explanation of the evidence the provider can share.
Discuss recovery in terms of the firm's work. If email or document management is unavailable, what can staff do? Which systems return first? Who approves temporary workarounds, and how will attorneys know when client information can be handled safely?
Ask the provider to document proposed recovery objectives and the assumptions behind them. Include dependencies on software vendors, internet service, and decisions the firm must make. Do not accept a recovery promise without a defined process and evidence that it has been tested.
A tabletop exercise can reveal gaps before an outage. Walk through a locked-account, unavailable-server, or failed-internet scenario. Include the people responsible for decisions, client communications, and coordination with outside counsel or vendors.
Cloud services still depend on working identities, internet access, devices, and permissions. For an office move or a project involving multiple suites, confirm who coordinates the carrier and how staff will work if a circuit or building connection is delayed.
GDS Technology lists data backup and recovery and disaster recovery planning among its services. Ask any prospective provider to define the proposed scope for your firm and explain how you can verify the recovery path.
Test recovery before a real outage makes the test urgent.
How do Norcross office needs affect the provider choice?
Law firms in Norcross may work in offices along the I-85 corridor or in buildings where projects require coordination with property management and other tenants. A new suite, renovation, or move can bring internet circuits, cabling routes, Wi-Fi coverage, access systems, and camera placement together.
Before work begins, ask whether the provider will identify building access rules, construction schedules, network demarcation points, and vendor responsibilities. Confirm who orders carrier service, meets contractors, and checks that network connections are labeled and documented.
Ask what local support means in the written agreement. Which issues are handled remotely, and when are onsite visits appropriate? What response targets apply, how are they measured, and what happens when a carrier or another vendor must act? A local search result does not establish a response time.
For staff working across Gwinnett County or nearby communities, secure remote support may resolve some issues without an onsite visit. Ask how the provider verifies a caller before making sensitive account changes and records the work performed.
GDS Technology is based in Norcross and provides managed IT, cybersecurity, cloud, and infrastructure services. Ask any provider to define the local work it will own and how it will coordinate with building and technology vendors.
Local knowledge matters when it produces a clear office plan and accountable handoffs.
How should a firm compare proposals and references?
Compare scope and accountability, not the number of products listed. Look for covered users and devices, included security work, backup responsibilities, project services, exclusions, and a process for handling work outside the agreement.
- Confirm which users, devices, systems, and security tasks are included.
- Identify backup, recovery, onboarding, migration, and project responsibilities.
- Clarify exclusions, escalation routes, and charges for out-of-scope work.
- Get response targets and their measurement rules in writing.
Ask how requests are submitted, prioritized, and escalated. Get response targets and definitions in writing, including when the clock starts and which events are excluded. If a proposal promises proactive monitoring, ask which alerts are reviewed and what actions follow.
Understand the full cost structure before signing. Request recurring charges, setup or migration costs, project work, licensing assumptions, and charges tied to user or device counts. Compare written proposals for the same scope rather than relying on a generic per-user estimate.
Before signing, request a sample service report, an onboarding outline, and an explanation of documentation and administrative access. Confirm who owns the firm's data and how it will be returned if the relationship ends. Have counsel review contract terms affecting confidentiality, retention, and incident notification.
Review IT services for law firms, managed IT services, cybersecurity services, and disaster recovery planning when defining the scope your firm needs.
Choose the provider whose commitments are clear, documented, and matched to your firm's work.
For the broader picture beyond Norcross, see our national guide on this topic.
Frequently Asked Questions
What should a Norcross law firm ask an IT provider before signing?
Ask which systems and users the agreement covers, how support is prioritized, and what response targets apply. Confirm how access changes are handled during onboarding and departures, what evidence is available for backup restoration tests, and who coordinates building or carrier work. Have counsel review contract terms that affect confidentiality and incident communications.
How can a law firm tell whether its IT backups are dependable?
Ask which data and systems are protected, who can access backup copies, and how often restoration is tested. Request a recent test record and discuss what would be restored first if email, document management, or another essential system failed. A sound plan identifies dependencies and responsibilities, not just where copies are stored.
Does using an IT provider make a law firm compliant?
No. A provider may help implement and document technical controls, but the firm must determine which legal, contractual, and ethical duties apply. Ask the provider to describe its work and coordinate compliance questions with qualified counsel. A product or service alone does not establish that the firm meets an obligation.
How should a firm compare managed IT costs?
Compare written proposals with the same scope and assumptions. Separate recurring service charges from licenses, onboarding, migration, project work, and out-of-scope requests. Confirm how user or device changes affect charges and what support is excluded. Without a verified local price range, do not treat a generic estimate as a Norcross market benchmark.