Decide whether the next step is a repair or a review
A planning review is useful when you cannot explain recurring problems, compare proposed solutions, or identify who owns important work. It is not a prerequisite for every support request. Restore urgent business operations through your established support route first; investigate longer-term decisions separately.
Before buying more support, write down what is missing. You may need a specific repair, clearer responsibilities, a technical investigation, or an approved change. This guide helps prepare that question without assuming that a consulting project is always the answer.
Describe the uncertainty you want resolved
Give a prospective adviser one decision to help you make. For example: why does the same application keep failing, which overlapping subscription is actually needed, or what must change before a second office opens? Avoid a brief that only asks someone to make all IT better.
Separate observations from suspected causes. Record the affected task, dates, users, existing tickets, and any workaround. A recurring fault is evidence to investigate, not proof that the entire network needs replacement.
Gather the records you already have
- A list of essential applications, equipment, cloud accounts, and locations.
- Current support responsibilities and contacts for other suppliers.
- Recent requests that illustrate the problem, with sensitive details removed.
- Upcoming renewals, notice dates, office moves, or staffing changes.
- Known access restrictions and the person authorized to approve investigation.
NIST's small business cybersecurity guide recommends maintaining an inventory of the hardware, software, systems, and services a business relies on. Use existing records as a starting point and label what has not been verified. Do not email passwords or recovery codes with a planning brief.
Check the agreement before buying duplicate work
Ask your current provider whether investigation, service reviews, lifecycle planning, or vendor coordination already falls within the agreement. A recurring problem may reflect an excluded task, an unresolved technical cause, or an unclear approval. Check the facts before assuming another contract will solve it.
If a service is included but not being delivered, use the agreed escalation route. If it is outside scope, request a defined proposal. Our consulting and managed services comparison explains how advice, implementation, and ongoing care can be assigned.
Choose a proportionate starting point
The examples below are planning prompts, not diagnoses or customer results.
| Situation | Useful next question |
|---|---|
| One fault | Can the existing support owner investigate a defined issue? |
| Repeat fault | What evidence is needed to distinguish a workaround from a lasting correction? |
| Tool overlap | Which users, features, integrations, and renewal terms must be compared? |
| Office change | Which systems, suppliers, permissions, and dates depend on each other? |
| Unclear scope | Who is responsible today, and which task lacks an owner? |
Define the review before authorizing access
Agree on the question, systems covered, records required, permitted activities, deliverable, and price. Identify who can approve access and changes. Reading documentation, inspecting configurations, running tests, and changing systems are different activities and should not be treated as interchangeable.
Ask how the adviser will report unknowns and explain recommendations. A useful result can be a finding that no purchase is needed, that more evidence is required, or that an existing supplier should complete a covered task. Confirm whether implementation and follow-up are included.
Turn findings into decisions you can check
For each finding, request the evidence, business impact, options, estimated costs, dependencies, and proposed owner. Separate confirmed issues from assumptions. Choose acceptance checks before implementation so staff know what improvement they should test.
Use the IT roadmap worksheet when several approved changes need sequencing. A review does not guarantee savings, prevent every incident, or certify compliance. Measure results against your own starting position and the agreed work.
Prepare for a local planning conversation
For a Reston, McLean, Fairfax, or Falls Church office, include the full site address, suite, building contact, and any access or work-window restrictions. An office move may involve internet service, cabling, phones, meeting rooms, and other suppliers with separate scopes. Name the dependencies before setting an implementation date.
UX Genius is based in Reston and serves McLean, Fairfax, and Falls Church. Review the managed IT scope, then discuss what your IT review should answer in a free 30-minute assessment. It is a conversation with no obligation. We will contact you to arrange a time. Technical investigation and implementation are scoped separately. Call (703) 755-0014 if you prefer to talk.
Questions before commissioning a review
Should we delay support until a review is complete?
No. Report active problems through the established support process. Agree separately on the longer-term investigation and any changes.
Must a small business buy a full audit?
No. Start with the question you need answered. Confirm whether a focused investigation is sufficient or broader discovery is needed.
What if the review recommends a new contract?
Ask which findings justify it, what work it covers, which alternatives were considered, and how the proposed result will be checked. A recommendation is not spending approval.
Source documents and current details
Use the original guidance when a policy, product, or contract detail matters to your decision.
IT planning