Worklenz
Sign in
EN

Software & IT template

IT Project Template

Plan an IT project such as a system rollout, upgrade or migration: assess needs, plan and procure, implement, roll out to users and hand over to support.

Worklenz has a built-in Information Technology template you can pick during setup, then shape it to match this plan.

  • Free plan available
  • Open source (AGPL-3.0)
  • Cloud or self-hosted
IT team working in a server room

What's included in the IT Project template

phases
6
tasks
18
labels
5
statuses
3
1. Assess · 3 tasks
  • Define the business needWhat problem the project solves, who it affects and how success will be measured.
  • Audit the current setupDocument current systems, versions, integrations and known issues.
  • Assess risks and securityList technical, security and business risks and how to reduce them.
2. Plan · 3 tasks
  • Write the project planScope, milestones, owners, budget and the change window.
  • Agree the change and rollback planHow the change will be made, tested and reversed if needed.
  • Plan communication with usersWho needs to know what, and when, before and after the change.
3. Procure · 2 tasks
  • Compare vendors or optionsCompare options on cost, fit, security and support.
  • Order hardware and licencesPlace orders and track delivery dates.
4. Implement · 3 tasks
  • Configure and buildInstall, configure and integrate the new system in a test environment.
  • TestTest functions, integrations, performance and security.
  • Migrate dataMove data from old systems and check it is complete and accurate.
5. Roll out · 3 tasks
  • Train usersShort training sessions and simple guides for each user group.
  • Go liveSwitch over in the agreed change window and run checks.
  • Provide early supportExtra support for the first days to fix issues quickly.
6. Handover · 4 tasks
  • Document the systemConfiguration, credentials storage, procedures and contacts.
  • Hand over to supportBrief the support team and agree service levels.
  • Decommission old systemsRetire old systems safely, including data retention and licence cancellation.
  • Review the projectCompare results with the original need and record lessons.

Labels

  • Security
  • Change window
  • Vendor
  • Blocked
  • User impact

Who this template is for

  • Managed service providers and IT consultancies running client projects
  • Internal IT teams rolling out new systems or upgrades
  • Operations leads coordinating technology changes across departments

When to use an IT project template

IT projects affect people who never see the plan. A new system, an upgrade or a migration can disrupt the whole business if users are not told, data is incomplete or the change cannot be reversed. An IT project template makes sure the technical work and the people side are both planned.

Use it for system rollouts, infrastructure upgrades, office moves, security improvements and software migrations. It suits managed service providers and IT consultancies running client projects, and internal IT teams.

How the template is structured

  1. Assess. Define the business need, audit the current setup and assess risks and security.
  2. Plan. Write the plan, agree the change and rollback approach, and plan communication with users.
  3. Procure. Compare vendors or options and order hardware and licences early, since delivery times are often the critical path.
  4. Implement. Configure and build in a test environment, test thoroughly and migrate data.
  5. Roll out. Train users, go live in the agreed window and provide extra support in the first days.
  6. Handover. Document the system, hand over to support, decommission old systems and review the project.

The User impact label marks tasks that affect staff directly, so communication is not forgotten.

How to use it in Worklenz

  1. Start from the built-in Information Technology template during setup, or create a project with these phases.
  2. Link the client if you are an MSP or consultancy.
  3. Set due dates around the change window and label related tasks Change window.
  4. Attach documentation and vendor quotes to their tasks.
  5. Track time on the Pro plan and above to compare effort with the quote.

Making IT project work visible and billable

MSPs and IT consultancies often quote projects separately from ongoing support, and project hours can leak into support contracts or the other way round. Time tracking keeps them apart. On the Business plan, project finance compares the project budget with the cost of logged time, and client invoices can be created from the work.

Example: moving a firm to a new email platform

An IT consultancy is moving a 50-person firm to a new email and file platform. The assessment finds two old shared mailboxes and a legacy file server with permissions nobody remembers. The plan sets a weekend change window and a rollback approach. Licences are ordered in the first week.

The team configures the new platform, migrates a pilot group and fixes a permissions issue before the full migration. Staff get a one-page guide and two short training sessions. After go-live, the consultancy provides extra support for three days, documents the setup and decommissions the old file server after the agreed retention period.

Planning the change window

The change window is the agreed time when the live system is changed, often an evening or weekend when fewer people are working. Choose it with the business, not just the IT team, and avoid busy periods such as month-end or a product launch. Write down the exact start time, the point at which you decide to continue or roll back, and who makes that call. Tell users in advance what will be unavailable and for how long. A clear window and a clear decision point turn a stressful night into a routine one.

Who should be involved

A project lead owns the plan and communication. Engineers own configuration, testing and migration. A security lead reviews risks. On the client or business side, a sponsor approves the change window and department contacts help with communication and testing.

Common IT project mistakes

The first mistake is planning the technical change without telling users. The second is skipping the rollback plan. The third is leaving old systems running indefinitely after go-live. Each has a task in this template.

Tips for smoother IT projects

  • Order early. Hardware and licence delays move go-live dates.
  • Pilot first. A small group finds problems before everyone else does.
  • Tell users what changes for them. Not how the system works, but what they need to do.
  • Decommission on purpose. Old systems left running cost money and create security risks.

Related: the data migration template and the security assessment template.

Start your it project project in Worklenz

Sign up free, then set up the phases and tasks above for your team.

IT Project template FAQs

What are the phases of an IT project?

Assess, plan, procure, implement, roll out and hand over. This template turns each phase into tasks with descriptions.

Why do IT projects need a rollback plan?

Changes to live systems can fail in ways that testing did not catch. A rollback plan lets you restore service quickly instead of fixing problems under pressure.

Is this IT project template free?

Yes. The full template is on this page, and Worklenz's free plan includes task lists, kanban boards and built-in project templates.

Does Worklenz have a built-in IT template?

Yes. Worklenz includes a built-in Information Technology template you can pick during account setup and adapt to this plan.

Software & IT

Software Development template

Plan and deliver a software project in sprints: requirements, technical design, iterative development, testing, release and early support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Bug Tracking template

A simple bug tracking workflow: capture clear reports, triage and prioritise, fix with review, verify and close, then learn from patterns.

5 phases · 15 tasks. By Worklenz.

Software & IT

E-commerce Development template

Build or rebuild an online store: discovery, platform and design, product catalogue, checkout, payments and shipping, testing and a launch that protects sales.

6 phases · 19 tasks. By Worklenz.

Software & IT

Data Migration template

Move data between systems safely: assess and map the data, clean it, run test migrations, cut over with a rollback plan and validate the results.

6 phases · 17 tasks. By Worklenz.

Software & IT

QA Testing template

Plan and run software QA: define scope and approach, write test cases, prepare environments, execute tests, track defects and sign off the release.

5 phases · 15 tasks. By Worklenz.

Software & IT

Security Assessment template

Run a security assessment from scope to remediation: inventory assets, review risks and controls, test for vulnerabilities, report findings and track fixes to closure.

6 phases · 17 tasks. By Worklenz.

Explore more templates

Run your next project from a template

Worklenz is an open-source platform for agencies and service teams: projects, time tracking and client work in one place.