Skip to main content

Building and Managing an IT Plan

How to create recommendations, set priorities, and track plan items through completion in the IT Plan.

Updated today

The IT Plan is where client meetings shift from evaluating where things stand to planning where they're going. While the Assessment captures what needs attention, the IT Plan captures the specific projects, upgrades, and initiatives you're recommending and tracking over time.

If you're on a new account, Dunder Mifflin already has a filled sample IT Plan attached. Start there to get a feel for how it works. If your account doesn't have it set up yet, go to the Marketplace, download the IT Plan template and the IT Plan - Filled Sample, and attach the Filled Sample to Dunder Mifflin. You can customize it to suit your process, though we recommend keeping the core structure intact.


What's in an IT Plan

Each Plan contains Items: individual projects, initiatives, or recommendations you're tracking. Items are organized by Year and Quarter, with a Backlog section for items you've identified but haven't scheduled yet.

For each Item you can fill out:

  • Item: a clear, client-facing project name (e.g., "Server Migration," "Laptop Refresh," "Email Security Overhaul")

  • Status: where the item stands. Options include Open, In Progress, Decision Needed, Future, and Completed.

  • Explanation / Risk: why this item is being recommended and what's at risk if it's not addressed. This is client-facing.

  • Next Steps: what needs to happen before the next meeting

  • Estimated Budget$: a ballpark figure for client conversations. Use this to start the financial discussion, share a budgetary quote, or get early buy-in before your team invests time in a full scope of work. This field does not flow to the Roadmap or Budget.

  • Confirmed Budget$, Year, Month: once a project is committed to, fill these out. These are the fields that land items on the Roadmap and Budget Parts of your Report.

Adding a Plan to a Report

Plans are not tied to your Report template the way the Assessment is. Each Plan is attached individually per client. There are two ways to do it:

Option 1: Create in the Plan Module first, then attach

  1. Open the Plan Module and find the company

  2. Click the page icon next to the company name

  3. Choose from a template or start from scratch

  4. Name it IT Plan and click Create

  5. Open the Report, go to Report Settings, click Add Part, set the type to Plan, and select your IT Plan

Option 2: Create directly from a Report

  1. Open the Report and go to Report Settings

  2. Click Add Part and set the type to Plan

  3. Choose to create a new Plan on the spot and name it IT Plan. It will be created and attached in one step.

Tips for effective IT Plans

  • Start with 5-10 items for a new client. Add more as you learn their environment and priorities.

  • Write for the client. "Server Migration" is better than "Azure migration project phase 1." Your client will see this in their Report.

  • Use Estimated Budget$ early to get buy-in before investing time in a full scope.

  • Fill in Confirmed Budget$, Year, and Month once a project is committed. That's what builds your Roadmap.

  • Keep a Backlog. Use the Future status for items you've identified but aren't ready to schedule. It keeps the Plan complete without cluttering the active timeline.

  • Review and update before each meeting. Items get completed, priorities shift, new projects emerge.


Did this answer your question?