Welcome to Integratd Living
Terry, this is the role we want to build with you.
A project-delivery role with technical depth: managing multiple projects, connecting every moving part and making sure the whole team stays across what happens next.
01
The mission
Why this role exists
Make sure nothing important lives only in someone's head.
Integratd projects have many moving parts: design, procurement, site readiness, programming, commissioning, clients and handover. Your core mission is to manage the project picture across all of them — protecting quality, timing and follow-through while keeping Arian, George, Tim and the wider team properly informed.
In one sentence
You are the connective layer that helps the right people do their best work at the right time.
02
The company
What you are joining
Technology, design and delivery — working as one.
Integratd grew from more than two decades of audiovisual integration and live-production experience. Integratd Living brings that same precision into intelligent building automation.
We design, build and support connected systems for homes, commercial spaces and multi-residential projects, bringing comfort, performance and energy efficiency together.
Build it properly and leave a result we are proud to stand behind.
Details, testing and documentation matter because the whole system depends on them.
Good delivery depends on people seeing the same truth at the right time.
Turn what we learn on one project into a better way of working on the next.
Interactive project journey
How a project moves through Integratd.
Tap any stage to see what it means and where your coordination keeps the delivery healthy.
Stage 01
Project request + alignment
Confirm the client outcome, project context, scope boundaries and the information the team still needs.
Terry's coordination focus
Make open questions, next actions and decision owners visible from the beginning.
03
Your team
Different roles. One delivery team.
No one sits above the work.
Each person brings a different area of ownership. Tap anyone to see when to involve them and how they can help you keep a project moving.
Visibility + follow-through
Terry
Project Delivery + Technical CoordinationKeeps the full project picture visible and moving: actions, owners, dates, dependencies, risks and handovers across multiple projects.
Go to Terry forProject statusActions + dependenciesCross-team coordinationDelivery follow-through
Every circle is equal in size because this is a collaborative project-support map, not a reporting ladder.
04
The role
Six connected lanes
One role, with room to grow.
Project delivery and management are the anchor: keep multiple projects healthy, accurate and moving. Technical work, programming and service become a larger part of the role as capability and confidence grow.
Primary lane
01Project delivery
Own the day-to-day coordination and health of multiple active and upcoming projects. Keep scope, milestones, actions, dates, dependencies, decisions, documentation and risks accurate from planning through handover. Juggle priorities deliberately and follow up early enough that the team can solve a problem before it becomes a delay.
What this can look like
Multi-project delivery view
Milestones + dependency checks
Quality, risk + action follow-through
05
Ownership
A simple decision filter
Own the follow-through. Share the decisions.
The multi-project view, actions, owners, dates, milestones, follow-up, documentation and making quality or delivery risks visible.
Site readiness, materials, drawings, suppliers, programming, commissioning and handover dependencies.
Engineering, programming, commissioning and service tasks with the right review until ownership is agreed.
Safety, commercial scope, cost, client commitments, design changes, major timing risks and unclear priorities.
06
How we work
The operating rhythm
Lightweight structure. High visibility.
What changed across every active project, what is blocked, what is next and where a decision is needed.
Update owners and dates, check project health, follow up commitments and keep the source of truth current.
Drawings, materials, access, dependencies, programming and responsible people confirmed.
Testing complete, decisions documented, customer prepared and follow-up scheduled.
Useful escalation format
What happened → what it affects → what we tried → decision needed → recommended next step.
07
First 90 days
A starting path, not a stopwatch
Learn. Own. Improve.
Progress will follow real projects and the support available. The purpose of these phases is shared direction, not a rigid deadline.
Days 1–30
Learn the system. Build the map.
The first month is about context, relationships and visibility — not pretending to know everything immediately.
- 01
Shadow Arian, George and Tim across active projects.
- 02
Learn the Integratd project lifecycle, Simpro rhythm and file structure.
- 03
Build a simple, trusted multi-project view of milestones, actions, next steps and blockers.
- 04
Understand our engineering, programming, commissioning and handover standards.
- 05
Agree the first supervised technical and programming tasks.
08
Success
What great looks like
Calm projects. Clear ownership. Fewer surprises.
The team can see status, actions, dates, dependencies and decisions without reconstructing the story.
People have time to make a good decision before timing, cost, quality or the client experience is affected.
Office, engineering, programming, site and service receive the information they need at the right time.
You become progressively more capable in Loxone, commissioning and support without compromising standards.
Recurring friction becomes a checklist, decision rule, instruction or workflow the whole team can use.
09
Why you
The overlap we see
Your experience already connects the worlds this role needs.
You have coordinated concurrent technical projects, solved practical problems under pressure, trained people and built clearer ways of working. You also want deeper automation, programming and end-to-end project ownership. That combination is exactly why this role should not be narrow.
Project coordinationTechnical problem-solvingTraining + documentationSystems thinkingCalm follow-throughCuriosity
We hired the whole person — not only a list of tasks.
10
Good to know
Questions we would expect
Clarity beats guessing.
No. It is a working charter: clear enough to make ownership real, flexible enough to evolve as we learn where your strengths have the greatest impact.
No. You bring strong technical foundations and project experience. Platform depth will be built deliberately with Tim through practice, review and progressively larger pieces of work.
Make it visible and ask early. Clarify the decision, the owner and the due date. If the ambiguity could affect safety, quality, cost or timing, raise it with Arian rather than letting it sit.
Brief and early: what happened, what it affects, what has already been tried, the decision needed and your recommended next step.
It is the anchor. The team needs you to maintain a reliable view across several projects, coordinate the moving parts, protect delivery quality and make sure Arian, George, Tim and everyone involved know what is happening next.