IT consultation form template

An environment questionnaire that turns the first site visit into verification: user counts, core stack, six-tap security posture, and the compliance layer that applies.

Discovery Before the Site Visit

IT consultants burn billable hours on discovery their clients could have self-served: user counts, core stack, backup reality, and the compliance regime somebody’s industry quietly imposes. An environment questionnaire completed before the first visit flips the visit into verification — walking the server room to confirm answers rather than to collect them.

Inventory the Fundamentals

Number fields for users, sites, and servers; a dropdown for primary stack and hosting posture — on-prem, cloud, or the hybrid truth nobody admits to; a website field for the public footprint. Ten factual answers that scope everything else, answered in the time it takes to explain why you’re asking.

Security Posture in Six Taps

A yes/no battery cuts through vendor-speak faster than any walkthrough:

  1. MFA enforced everywhere — or just where it was easiest?
  2. Backups tested by restore, or tested by faith?
  3. End-of-life systems still in production?
  4. A written incident plan someone has actually read?
  5. Cyber insurance — and does the insurer’s checklist match reality?
  6. Offboarding that revokes access the same day?

Six honest no’s map the risk register faster than a day of interviews, and the pattern of them tells you which conversation to have first.

The Compliance Layer

Industry dictates the framework: healthcare brings its privacy regime, finance brings card rules, government contractors bring theirs. A dropdown of regimes with conditional follow-ups keeps the questionnaire relevant — a dental office should not be asked about payment segmentation, and a card processor should not escape it. Asking only what applies is why clients finish this form.

Pain, in Their Words

One long text: describe the last outage, the workaround everyone tolerates, the week the ticket queue won. Anecdotes are requirements in disguise, and clients write to a form what they would never put in a requirements document.

Frequently Asked Questions

The client doesn't know their own user counts. Now what?

Estimates are welcome — a wide range flags the documentation gap, which is itself one of the most valuable findings the form produces.

Can the form collect network diagrams?

Yes — file upload handles diagrams and license lists. Passwords travel through your password manager, never the form.

How do we keep multiple client submissions straight?

A hidden field in each client’s link attributes every submission automatically — nobody has to remember an account number.

How do we route toward managed services versus a one-off project?

Their answers route it: security gaps and complexity point managed; a defined migration points project. Sibling formats live in the IT collection and the technology category.

Access 2000+ templates

It's as simple as one-two-three, and guess what? You don't even need to pay to try it out!