IT Procedure Documentation Template

New employee laptop provisioning — standard build (Windows 11)


Procedure Category
User Provisioning
Target System
Windows 11 — Standard Build
Approval Required
Line Manager
Procedure Owner
TLThomas Laurent

🎯 Purpose

This procedure documents how to provision a standard Windows 11 laptop for a new employee joining any office in the EU region. It covers hardware preparation, domain enrolment, software deployment, and handover. Follow this procedure for all standard-build requests; custom builds (development, design) follow separate procedures.

📋 Prerequisites

  • Approved onboarding ticket in ServiceNow (RITM number required)
  • New hire details from HR: full name, department, start date, office location
  • Laptop allocated from stock (Dell Latitude 5550 or equivalent)
  • Provisioning technician must have SCCM console access and local admin rights on the imaging server

📝 Step-by-step procedure

Step 1 — Image the device

Connect the laptop to the provisioning VLAN. Boot from PXE and select the EU-STD-WIN11-2026Q1 task sequence in SCCM. The imaging process takes approximately 45 minutes and installs Windows 11 23H2, domain joins the device, and applies the standard group policy baseline.

Step 2 — Enrol in Intune

After imaging completes, sign in with the provisioning service account. Open Settings → Accounts → Access work or school → Connect. Enrol the device in Microsoft Intune. Verify enrolment by checking that the compliance status shows "Compliant" within 15 minutes.

Step 3 — Deploy standard software

Intune pushes the standard software package automatically: Microsoft 365 Apps, GlobalProtect VPN, CrowdFalcon endpoint protection, and the Company Portal. Allow 30 minutes for deployment. Confirm all applications appear in Start Menu and the Company Portal shows no pending installations.

Step 4 — Configure user profile

Sign out of the provisioning account. Sign in as the new user (credentials provided by the Identity team via the onboarding ticket). Verify Outlook connects to the user's mailbox, OneDrive sync starts, and Teams loads with the correct tenant. Set the default printer for the user's office location.

Step 5 — Complete asset tagging

Affix the asset tag to the bottom of the laptop. Update the CMDB record in ServiceNow: link the device serial number to the user, set the location, and mark the CI status as "In Use". Close the RITM with a note confirming successful provisioning.

☑️ Verification checklist

CheckExpected resultPass
Device appears in Azure ADListed under user's devices
Intune compliance statusCompliant
VPN connects successfullyConnected to corp-gateway
Endpoint protection activeCrowdFalcon sensor running

↩️ Rollback instructions

If the imaging fails or the device does not pass the verification checklist, re-image from scratch using the same task sequence. If the device shows a hardware fault during imaging (drive errors, memory test failure), return it to the warehouse with a defect tag and allocate a replacement from stock. Update the RITM with a note explaining the delay.

📅 Revision history

VersionDateAuthorChanges
2.114/01/2026Thomas LaurentUpdated task sequence to 2026Q1 image; added Intune enrolment step
2.003/09/2025Marie ClaessensMigrated from Windows 10 to Windows 11 23H2; replaced WSUS with
Content continues in Elium...

Document how your IT team performs standard operational tasks. This template captures prerequisites, step-by-step instructions, verification checks, and rollback procedures — so any qualified team member can execute the process without relying on tribal knowledge or guesswork.

Try now in Elium

What is IT procedure documentation?

IT procedure documentation is a set of structured, step-by-step guides describing how to perform specific IT tasks — from prerequisites through execution to verification. Each document serves as the authoritative reference for how a process should be carried out, ensuring consistency regardless of who performs it.

Within ITIL-aligned service management, procedure documents underpin request fulfilment and standard changes. They turn implicit knowledge — steps a senior engineer runs from memory — into explicit, repeatable instructions any qualified team member can follow. Without documented procedures, execution quality varies between shifts, onboarding takes longer, and audit compliance becomes difficult to demonstrate.

Who should use this template?

This IT procedure documentation template is for teams responsible for IT service delivery and operations:

  • IT Service Desk Managers — standardise how routine tasks are performed so quality and compliance stay consistent across shifts and locations
  • CIOs and IT Directors — ensure operational procedures are documented, auditable, and resilient to staff turnover
  • Knowledge Managers — capture procedural expertise in a structured, searchable format that feeds human reference and AI retrieval
  • L1 and L2 Support Agents — follow verified step-by-step instructions instead of improvising or waiting for a senior colleague

What’s included in this template?

The template has two parts: structured metadata fields and narrative sections.

Metadata fields capture the context:

  • Procedure category (e.g. user provisioning, network configuration, backup)
  • Target system or service
  • Approval level required (e.g. line manager, change advisory board)
  • Procedure owner — the person accountable for keeping this document current
  • Last verified date

Narrative sections walk through the process:

  • Purpose — why this procedure exists and when to use it
  • Prerequisites — tools, access rights, and conditions required before starting
  • Step-by-step procedure — numbered instructions with expected outputs at each stage
  • Verification checklist — checks to confirm the process completed successfully
  • Rollback instructions — how to reverse the process if something goes wrong
  • Revision history — a log of changes with dates, authors, and reasons

How to create and customise this template in Elium

  1. Open the Template Builder — Go to your profile menu and select the Template Builder tab, or click “+ Create” and choose “Create a new template”.
  2. Set the scope — Choose an icon, enable the template, and decide whether it applies platform-wide or to specific spaces (e.g. your IT Operations space only).
  3. Add structured fields — Click “Field” to add metadata: a tag field for procedure category (pre-populate values like “User Provisioning” and “Backup & Recovery”), a text field for target system, a tag field for approval level, a user field for procedure owner, and a date field for last verified. Mark category and owner as mandatory.
  4. Build the body structure — Use the “+” button to add content blocks for each narrative section: purpose, prerequisites, step-by-step procedure (numbered list block), verification checklist, rollback instructions, and revision history (table block).
  5. Preview and save — Review the template layout, then save. Team members can now select it when creating new articles, and you can apply it to existing content in bulk.

How AI helps you create and use this template

Capture faster. When documenting a procedure you already run, describe the process to Elium’s AI in rough steps. It generates a structured first draft — purpose, numbered instructions, prerequisites, verification checks — that you refine rather than writing from scratch.

Retrieve smarter. Once procedures are published, your team asks Elium’s AI: “How do I provision a new laptop for a remote employee?” The AI returns the exact steps, prerequisites, and approval path from your documented procedure — not a generic guide from the internet.

Why teams use Elium for IT procedures

IT procedure documentation is only valuable when people can find and follow it. When agents cannot locate the right document, they improvise — and improvisation introduces errors, security risks, and inconsistency. Elium makes procedures actionable: structured templates keep the format consistent, AI-powered search surfaces the right procedure from a natural question, and expiration dates flag when a document needs review.

VINCI Energies — 97,000 employees across 61 countries — centralised IT procedures in Elium after years of documentation scattered across Word, SharePoint, and Teams. The result: 4,000+ articles maintained by 500+ daily users, with expiration-date governance ensuring procedures stay current as systems and policies change.

Frequently asked questions

IT procedure documentation is a set of step-by-step guides that describe how to perform specific IT tasks. Without documented procedures, execution depends on individual memory. Consistent documentation ensures repeatable quality, reduces onboarding time for new staff, supports audit compliance, and prevents knowledge loss when experienced team members leave.
A complete procedure template includes metadata (category, target system, approval level, owner, last verified date) and narrative sections: purpose, prerequisites, numbered step-by-step instructions with expected outputs, a verification checklist, and rollback instructions. Include a revision history so teams know when and why the procedure was last updated.
Documented procedures reduce errors by replacing improvised steps with verified instructions. They shorten onboarding time because new staff follow written guides instead of shadowing colleagues. They support audit compliance by providing evidence of standardised operations. Over time, a library of procedures also feeds AI-powered search, letting teams find the right process in seconds.
Start with a clear purpose statement — why this procedure exists and when to use it. List all prerequisites before the first step. Number each instruction and include the expected output so the reader knows they are on track. End with verification checks and rollback steps. Keep language direct: “Run this command” rather than “consider running”.
A procedure describes how to perform a specific task — step-by-step instructions for execution. A policy defines what must or must not be done — the rules and standards governing behaviour. Procedures implement policies. For example, a password policy requires 12-character minimum passwords; the password reset procedure documents the exact steps to reset one within those rules.

Related reading: Read more on our blog