Day-to-day operating brief
What IT Project Manager work looks like in practice
An IT Project Manager coordinates people, vendors and technical work to deliver an agreed change within scope, time and budget. The role governs plans, risks, dependencies, change requests and acceptance but does not replace technical, security or business owners. Terms should define portfolio, travel, budget and contract authority, reporting, procurement, confidential programme information, working hours and responsibility for transition into support. Transition planning should name service owners, support hours, monitoring, documentation and unresolved defects before launch. Delivering functionality without operational acceptance can move project risk into a team that lacks access, budget or trained staff. Dependency dates should distinguish a supplier estimate, team forecast and formally committed milestone. Treating all three alike produces plans that look precise but cannot support accountable escalation when upstream work moves. Closure should reconcile purchase orders, licences and temporary access, preventing unused subscriptions or supplier accounts from continuing after the delivery team disbands. Lessons should identify a future owner and practical change, not become an unassigned archive of observations that never influence estimates, procurement or governance.
Individually written and reviewed against the maintained role record.