Scope and responsibilities
Agree the outcome, deliverables and exclusions. Identify the decisions, access and prerequisites needed from each party.
IT services
Turn an agreed technical change into work your organisation can follow. Connect scope, specialists, dependencies and communication from the first plan to handover.
DELIVERY WITH SUBNET
Agree the outcome, deliverables and exclusions. Identify the decisions, access and prerequisites needed from each party.
Connect the technical tasks with people, suppliers and operating constraints. Understand what must happen first and what changes the plan. Agree equipment and licensing needs, purchasing authority and ownership before rollout. Separate supplier terms and ongoing subscription costs from project work.
Keep project status, upcoming activities, decisions and open actions visible. Weekly updates and the agreed project portal support that conversation.
Discuss the effect of scope or schedule changes before proceeding. Plan implementation, validation and the transition to ongoing ownership. At handover, agree who is responsible for ongoing licensing and renewals.
WHY A PROJECT MANAGER
A technology project often crosses several teams, systems and providers. A project manager connects the technical work with business priorities, makes dependencies visible and keeps decisions moving.
Subnet’s Project Management Office coordinates work across its engineers, your internal team and relevant third parties. That gives the project a clear point of contact without removing the responsibilities owned by each party.
Agree how status is reported, who approves changes, how risks are escalated and what information is needed before a significant change. The aim is a controlled, understandable delivery process, not a promise that every project finishes without change.
Clarify the brief, responsibilities, assumptions and the work needed to start.
Review progress, dependencies, risks and decisions. Discuss changes with the people authorised to approve them.
Bring together the agreed validation, documentation, outstanding actions and ownership of the next step.
PROJECT VISIBILITY
Subnet’s project portal provides a shared view of project status and the delivery plan. Together with weekly updates, it helps people follow progress, upcoming activity and the information needed from them.
Agree the audience, reporting cadence and responsibilities for keeping the plan useful. A portal complements the project conversation; it does not replace an agreed decision, change approval or escalation.
A USEFUL PROJECT UPDATE
Illustrative reporting topics, not a live portal screenshot or a standard reporting entitlement. No customer project data is displayed.
THE PEOPLE BEHIND DELIVERY
Project coordination connects specialist engineering work with scope, dependencies, decisions and communication. The agreed plan and handover help your organisation follow the work and prepare for ongoing ownership.
Jelena’s project delivery background includes cloud migrations, Microsoft 365 deployments, and network and server refreshes across complex multi-site environments. Her experience spans design through to client handover.
Tracey’s background brings together IT strategy, project management and team leadership. Her professional development includes completed PMI courses in AI in Agile Delivery and Generative AI for Project Managers.
START WITH YOUR CHANGE
YOUR QUESTIONS
Agree the outcome you want, the deliverables, what is deliberately out of scope and the assumptions the plan relies on. Also record the access, decisions and prerequisites needed from each party, and who is responsible for each. Clear exclusions and assumptions make it easier to see later whether a request is part of the agreed work or a change to it. Where early assessment or design work is needed, the proposal should say so and how it will be scoped.
No. A useful starting point is the outcome you need, what you know about the current environment and the questions you need answered. Subnet's engineers and project managers can help turn that into a scope, including the dependencies and handover expectations that are easy to miss in an early brief. Bring whatever you have, such as current equipment lists, contracts or known constraints, and the conversation can build from there.
Responsibilities stay with the party that owns them. Subnet's project coordination connects the engineering work, your internal team and relevant third parties, but it does not remove your team's or a supplier's own responsibilities. Agree early who sponsors the project, who can approve decisions and changes, who supplies access and information, and how risks are escalated. Naming those people in the plan keeps decisions moving.
Technical delivery and coordination are different jobs. A project manager keeps the dependencies between tasks, people and suppliers visible, tracks decisions and open actions, and gives you one point of contact for status and questions. That helps most when work crosses several teams, systems or providers. It is a way to run delivery in a controlled and understandable way, not a promise that a project will finish without change.
Agree the reporting arrangements in the scope: who receives updates, how often, and what they cover. A useful update shows work completed and what is next, dependencies and decisions with owners, risks and their possible impact, and any change to agreed dates. Subnet's weekly updates and project portal can support that conversation where they form part of the agreed arrangements. A portal or report complements, but does not replace, an agreed decision, change approval or escalation.
Changes are discussed, and their effect on the plan understood, before the work proceeds. Agree at the start who can approve a change, how it is recorded and how it is assessed for effort, cost, timing and risk, so that a request does not quietly alter the project. Some changes come from discoveries in the environment or from your own priorities moving; both are normal and are easier to manage when the approval path is already agreed.
Agree equipment and licensing needs, who has authority to purchase, and who will own each item before rollout begins. Keep supplier terms and ongoing subscription costs separate from the project work itself so you can see what is a one-off project cost and what continues afterwards. Where a project depends on product availability, confirm with the supplier early because lead times can affect the schedule.
Agree the completion conditions during scoping. Handover normally brings together the validation that shows the change works for real business activities, the documentation and administrator details your team needs, any outstanding actions with owners, and who takes responsibility for the next step. Formal acceptance by the people who sponsored the work, followed by a record of lessons learned, is a sound way to close a project cleanly.
Decide this at handover rather than leaving it to chance. Name who is responsible for ongoing licensing, subscriptions and renewal dates, who holds the vendor accounts, and how the team will be reminded before terms lapse. Subnet can support procurement and renewal management as a separate arrangement if you want it, but ownership should be recorded either way so that nothing lapses without someone noticing.
It can, and the planning matters more as areas are added. Work in one area often depends on another: for example, a change may rely on connectivity, sign-in arrangements or backup arrangements being ready first. A combined plan sets the order of work, the decision points and who coordinates the specialists involved. You can also stage separate projects over time; the scope should say how they connect.
BEFORE WE TALK
You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.
LET’S TALK
Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.