Project Delivery
One system for IT intake, delivery, change and reporting. It covers the parts of a project a general task tool leaves out — approvals, change windows, dependencies, and the record of what was decided.
Core capabilities
Each area is designed around how IT work is actually approved, scheduled and closed out.
Intake & demand
A single request form for new work, with required fields for sponsor, business justification, affected systems and target dates. Requests queue for triage instead of arriving as hallway conversations.
Approval workflow
Route requests and scope changes to the people who have to sign off, with the decision, the approver and the timestamp kept against the project.
Projects & phases
Break work into phases, milestones and tasks with owners, estimates and dependencies. Structure a cutover the way you would actually run it.
Schedule & dependencies
Each task records what it waits on, and a slip reschedules everything downstream on working days — skipping weekends, holidays and change freezes. A wait on procurement or another team is modeled the same way, with a lag in working days.
Change & release
Raise change requests against a project, record the implementation and rollback plan, book the maintenance window and capture the post-change outcome.
Resource & capacity
Allocate people across concurrent projects and see committed hours against realistic availability, with support and on-call load accounted for.
Risks, issues & decisions
A RAID log per project with owners, review dates and severity, so risks are worked rather than listed once at kick-off. An AI forecast surfaces delivery risk before it's logged — advisory, so a person accepts each one.
Reporting & portfolio
Portfolio health, project status, resource utilization and change activity — exportable, so the monthly update takes minutes instead of an afternoon.
Templates & runbooks
Turn a project you have run well into a reusable template — task list, checklists, approvals and roles — so the next site rollout starts from experience.
Roles & permissions
Role-based access so sponsors, engineers, contractors and clients each see the projects and fields relevant to them — and nothing else.
Time & effort
Record effort against tasks and projects to compare estimate with actual, and to support internal chargeback or client billing where you need it.
Make it your team's
Sign in the way your organization already does, and shape the workspace to fit how your team actually works.
Single sign-on
Sign in with your Microsoft Entra ID account (SAML). Claim your company email domains and your people land in the right workspace, with the right role, automatically.
Your brand, your words
Set your accent color, workspace name and logo, rename the main sections to match your team's language, and add your own custom fields to every project.
Personal task lists
A private to-do list for each staff member, with a goal date and a hard deadline — and built-in tracking of how long tasks take from when they're added to when they're done.
A closer look
Change is part of the project, not a separate tool
In most organizations the project plan lives in one system and change approvals live in another. The result is a maintenance window booked without the project manager knowing, or a change approved for a phase that has already slipped.
yourKEYtoIT raises change records from inside the project. The window, the approvers, the implementation steps and the rollback plan are attached to the milestone they belong to, and the schedule reflects them.
Capacity you can defend in a steering meeting
Committed hours are calculated from actual assignments across every project a person is on, then set against the availability you configure — including a reserve for support and on-call.
When someone asks whether a new request can start next month, the answer comes with the arithmetic behind it rather than a gut feel.
A record that survives staff turnover
Approvals, scope changes, status transitions and decisions are written to the project's history as they happen, with the person and time recorded.
When the engineer who ran the migration leaves, the reasoning does not leave with them. See how we handle your data for the detail.
Bring a project you are running now and we will walk it through the platform