IT change management template
An IT change management app for planning service changes, recording risk-based review responsibilities and coordinating implementation. Check shared-service maintenance overlaps, invalidate stale approvals after plan changes, complete dependent steps and record a post-change outcome.
What is this change management template?
Prepare a change with impact, rollback and validation plans, affected services and an explicit UTC window. Review responsibilities depend on risk: Service owner and Operations for Low or Medium risk, plus Security for High risk. Decisions apply to the current plan revision. Material planning edits require fresh review, while an implementation runbook keeps its approved structure. Record execution evidence and finish through post-change validation, rollback review or follow-up. The app coordinates manual work in ToolJet Database; it does not deploy changes, verify reviewer identity or reserve maintenance windows transactionally.
- Screens
- 5 connected pages
- Data source
- ToolJet Database
- Language
- English
- Appearance
- Light + dark
Built for IT operations and service owners coordinating reviewed infrastructure changes.
From change readiness to a reviewed outcome.
Connect service impact, recorded authorization, execution evidence and the next decision.
- Home
Find the next change decision
Scan a five-day UTC service maintenance summary and pending decision context, then open an actual change from the register or continue in the review workspace.
- Changes
Create and prepare a request
Create a change for an active service, then define risk, impact, rollback and validation plans, affected service codes, and the UTC maintenance interval.
- Review
Review the current plan revision
Record the required responsibility decisions with impact, rollback and test-plan checks. High-risk work also needs a recorded Security review.
- Implementation
Execute and review the runbook
Complete steps with expected results and prerequisite checks, then record post-change validation, lessons and a Successful, Rolled back or Follow-up required outcome.
- Services
Maintain service context
Maintain service codes, names, owners and criticality. Retirement is blocked while linked primary-service changes remain open.
What does the template cover?
UTC windows and affected-service conflicts
Define start and end dates and times in UTC with multiple affected service codes. Overlapping nonterminal changes sharing a service block review and start against the currently loaded records; adjoining endpoints are allowed.
Review responsibilities tied to the current plan
Record Service owner and Operations decisions, plus Security for High risk. Only the latest decision for each required responsibility on the current plan revision counts. Editing a plan, window or runbook before implementation returns the change to Draft and increments its revision.
Dependent runbooks with acceptance criteria
Each runbook step has an owner, expected result and an optional prerequisite chosen from preceding steps. A step cannot finish before its prerequisite, and a completed prerequisite cannot reopen while its completed child depends on it. During implementation, structure stays locked while state and execution evidence can change.
Post-change validation and follow-up
All steps must be Done before Post-review. Record validation, lessons and a named review owner for the outcome. Rollback review cannot yield Successful. Follow-up required records the needed work, returns Draft, resets task completion and requires new review.
ToolJet Database with sample data
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Services | 3 sample services | Payments, workforce identity and analytics services with owners and criticality. |
| Changes | 11 sample changes | Three original change records and eight enterprise examples covering planning, review and operational decision contexts. Synthetic QA-created records are excluded from the template inventory. |
No infrastructure execution, deployment integration, automatic rollback, notifications, enforced reviewer identity, independent approval or role-based access policies. Review responsibilities are manually recorded. UTC is the only maintenance timezone input; there is no blackout calendar or resource-capacity scheduler. Overlap checks use the current loaded records, not an atomic reservation or cross-session conflict guarantee. Plan revisions retain decision history but do not provide an immutable audit log or complete historical plan snapshots. The pilot loads up to 1,000 rows per dataset. Public deploy/download remains unavailable until export and clean-install validation; v2 workflow and visual acceptance are separate pending checks.
Make it yours with AI.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
How to use this template.
Add it to your workspace
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Start with the included database
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Make it work your way
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
Template FAQs
What does the IT change management template include?
It includes a service directory, change planning, UTC windows, shared-service overlap checks, plan-revision review responsibilities, dependent runbooks and post-change outcomes.
How are maintenance conflicts detected?
The app compares overlapping UTC start/end intervals on shared affected services among loaded nonterminal changes. Touching endpoints do not overlap. This snapshot check blocks review and start, but it is not a transactional booking or concurrency guarantee.
Which reviews are required?
Low and Medium risk require recorded Service owner and Operations decisions. High risk also requires Security. Each responsibility must have a qualifying approval on the current plan revision. These are manual records, not enforced user roles.
What happens when an approved plan changes?
Material planning, window or runbook edits before implementation return the request to Draft and increment the plan revision. Earlier decisions remain historical and do not authorize the new revision.
How do runbook prerequisites work?
A step can depend on a preceding step and cannot finish until that prerequisite is Done. A completed prerequisite cannot reopen while a completed child depends on it. Approved structure stays locked during implementation.
Does finishing the runbook close the change?
No. Fully completed work proceeds to Post-review. A recorded review captures validation, lessons and an outcome. Follow-up required returns Draft and resets steps; rollback is reviewed separately and cannot be recorded as Successful.
Does it deploy changes or enforce independent approvals?
No. Infrastructure work, reviewer identity and independent authorization are outside this pilot. It records planning, manual decisions and execution evidence.
Can AI customize the app?
Yes. Prompt for branding, layout, fields, translations or workflow extensions. Added timezones, permissions and integrations need implementation and testing before being advertised.
Expense reimbursement
Receive individual expense claims, review receipt references against saved per-expense limits, and record approval or reimbursement.
Security exception management
Track time-limited security exceptions with a risk owner, compensating controls, recorded assessment and remediation evidence.
Employee probation reviews
Coordinate employee probation reviews using role-specific periods, manager feedback, competency scores and documented confirmation or extension decisions.