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
- Assess. Define the business need, audit the current setup and assess risks and security.
- Plan. Write the plan, agree the change and rollback approach, and plan communication with users.
- Procure. Compare vendors or options and order hardware and licences early, since delivery times are often the critical path.
- Implement. Configure and build in a test environment, test thoroughly and migrate data.
- Roll out. Train users, go live in the agreed window and provide extra support in the first days.
- 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
- Start from the built-in Information Technology template during setup, or create a project with these phases.
- Link the client if you are an MSP or consultancy.
- Set due dates around the change window and label related tasks Change window.
- Attach documentation and vendor quotes to their tasks.
- 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.





