Welcome to Integratd Living
Terry, this is the role we want to build with you.
A project-delivery role with technical depth: connecting people, details and decisions so great work moves cleanly from promise to handover.
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 give the team one reliable line of sight across them — then help close the gaps.
In one sentence
You are the connective layer that helps the right people do their best work at the right time.
02
Your team
A clear support network
You are not expected to carry every answer.
Your value is knowing what needs attention, bringing the right people together and keeping the outcome moving.
Direct managerArian
Priorities, commercial decisions, escalation, development and role direction.
Your positionTerryProject delivery
+ technical coordination
+ technical coordination
Project engineeringGeorge
Design intent, technical decisions, drawings, engineering review and delivery planning.
ProgrammingTim
Loxone Config, programming standards, testing, commissioning and technical mentoring.
The relationship is collaborative: coordinate confidently, respect technical ownership and make escalation easy.
03
The role
Six connected lanes
One role, with room to grow.
Project delivery is the anchor. Technical work, programming and service become a larger part of the role as capability and confidence grow.
Primary lane
01Project delivery
Build a reliable view of active and upcoming work. Track actions, dates, dependencies, decisions and risks from planning through handover. Follow up early enough that the team can solve a problem before it becomes a delay.
What this can look like
Project action register
Readiness and dependency checks
Early risk escalation
04
Ownership
A simple decision filter
Own the follow-through. Share the decisions.
Visibility + coordination
Actions, owners, dates, project rhythm, follow-up, documentation and making risks visible.
Cross-team delivery
Site readiness, materials, drawings, suppliers, programming, commissioning and handover dependencies.
Technical execution
Engineering, programming, commissioning and service tasks with the right review until ownership is agreed.
Decisions with consequence
Safety, commercial scope, cost, client commitments, design changes, major timing risks and unclear priorities.
05
How we work
The operating rhythm
Lightweight structure. High visibility.
Project pulse
What changed, what is blocked, what is next and where a decision is needed.
Close the loops
Update owners and dates, follow up commitments and keep the source of truth current.
Readiness check
Drawings, materials, access, dependencies, programming and responsible people confirmed.
Clean handover
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.
06
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 view of active work, next actions and blockers.
- 04
Understand our engineering, programming, commissioning and handover standards.
- 05
Agree the first supervised technical and programming tasks.
07
Success
What great looks like
Calm projects. Clear ownership. Fewer surprises.
Nothing important is invisible.
The team can see status, actions, dates, dependencies and decisions without reconstructing the story.
Risks arrive early.
People have time to make a good decision before timing, cost, quality or the client experience is affected.
Handoffs stay clean.
Office, engineering, programming, site and service receive the information they need at the right time.
Your technical ownership grows.
You become progressively more capable in Loxone, commissioning and support without compromising standards.
The system gets better.
Recurring friction becomes a checklist, decision rule, instruction or workflow the whole team can use.
08
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.
09
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.