Selections, Change Orders & Project Milestone Control
Every decision the client owes, every change to scope, and every milestone that affects the schedule becomes a visible, dated, owned item, and change orders get written and approved before the work happens.
- Tier
- Growth
- Build order
- 4th of 7 for smart home and AV
- Shape of it
- 8 steps, 1 escalation rule
- At launch
- Runs supervised, with you approving what goes out
The problem this solves
Two failures, both invisible until the end of the job.
Decisions. The project is waiting on the client to choose a finish, confirm a rack location, approve a keypad engraving, or sign off a network plan. The client does not know they are blocking anything, because nobody told them in those terms. The integrator knows but is on another job. Days pass. Then the electrician's rough-in date moves, and the project slips a month.
Change orders. Someone asks for something on site. The lead tech says yes because they are helpful and it is a small thing. It is not documented, not priced, not approved in writing, and not attached to a payment milestone. Ten of those across a project is real money, and the owner finds out when the job margin comes in below plan with no single explanation.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
- It escalates to a person
Step 1Trigger
Every client decision the project depends on is registered as an item with a date, an owner and a stated consequence: what it blocks and what happens if it is late.
Step 2
The client sees decisions in those terms. "We need the keypad finish by Friday or the electrician's Tuesday rough-in moves" is a different message from "let us know about the keypads".
Step 3Escalation
Decisions approaching their date escalate: first a reminder to the client, then to the trade partner who owns the dependency, then to the project manager.
Step 4
A change request cannot become work without a written change order. The request is captured on site, priced, sent for approval, and only released when approved.
Step 5
Approved change orders attach automatically to the next payment milestone, so billing them is the default rather than a memory test.
Step 6
Milestones are triggered by real events: rough-in complete, trim complete, rack built, programming complete, commissioning complete.
Step 7
Trade dependencies are tracked, because an integrator's schedule is mostly somebody else's schedule. When the builder moves, the affected items move with a visible consequence.
Step 8
Anything overdue appears on the exception brief with its cost or schedule impact.
How it gets built
Built inside what you already run
- D-Tools
- iPoint
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Map
List the decisions a typical project actually waits on, with the design lead and the project manager in the same room. This list is shorter and more repeatable than anyone expects.
Nothing is designed until we have looked at what already exists, including the parts nobody officially owns.
- 2
Build
Attach a real consequence to each one. Without the consequence, a decision reminder is nagging.
Built inside the software you already run, against your stages and your language.
- 3
Build
Build the change order path, and agree who can approve one on site and up to what value.
- 4
Build
Connect approved change orders to payment milestones.
- 5
Agree
Define the milestone triggers with the install manager.
The thresholds, the wording and the names are yours. We write them down with you and get the consequential ones signed off.
- 6
Build
Build the trade-dependency view.
- 7
Prove
Run one full project supervised before going live.
It runs with a person approving what goes out until you are happy with the tone. Nothing sends unreviewed on day one.
What changes after it goes live
How it runs today
Two failures, both invisible until the end of the job.
After this one is live
Decisions stop being the silent cause of schedule slip, because the client can see what they are holding up. Change orders become recorded revenue instead of absorbed cost. And the project manager stops being the only person who knows what a project is waiting on.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Two numbers, and the company has both. Take last year's completed projects and count change orders that were performed but never billed, valued at their labour and materials. Then count schedule slips attributable to a client decision, and value them at the cost of a crew standing down or a return mobilisation. The first number is usually larger and almost never measured.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
This trade does not carry the healthcare regulation of the med spa and dental playbooks, but it carries a different and equally serious exposure.
Client privacy is the primary risk. These systems are installed in the homes of wealthy and often deliberately private people. Every system here touches data that must never leave the business:
- Never expose a client address, a floor plan, a rack elevation, a network diagram, credentials, camera locations or a security configuration in a demonstration, a case study, a proposal template or a marketing asset.
- Every demonstration uses synthetic data. No real project, no real address, no real client name, even with permission, because a permission granted once travels further than anyone intends.
- Credentials handed over at completion go through a secure mechanism, not an email body.
- Remote access and monitoring integrations are a security surface. Any automation touching them needs the same review an integrator would apply to a client's network.
United States messaging rules still apply. Automated SMS to clients and prospects sits inside the TCPA and inside carrier A2P 10DLC registration:
- Classify every system as service or marketing before it sends. An appointment confirmation and a seasonal upgrade offer are different things under different consent standards.
- Record consent per number with date, source, wording and scope.
- Quiet hours 8am to 9pm in the recipient's local time.
- Honour STOP and free-text opt-outs immediately, cancel queued messages, and propagate suppression across every sending system.
- Route replies to a monitored human queue. A reply saying the system is down is not a marketing response.
Trade partner relationships are commercially sensitive. Builders, architects and designers refer work on the strength of trust. Any automation that contacts a homeowner in a way that cuts across the partner's relationship with their own client will cost referrals. Every system that touches a trade-referred project needs the partner's role defined before it sends anything.
Nothing in this document is legal advice. State privacy and telemarketing law, carrier policy and contractual obligations to manufacturers and trade partners can each add requirements. Every template stating a commercial term requires review by the company's own counsel before it goes live.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forsmart home and AV.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
- 3Proposal Follow-Up & Decision RecoveryUsually the single largest recoverable pool in the business.
- 4Selections, Change Orders & Project Milestone Controlyou are hereStops the margin loss, and is the one the project manager will champion hardest.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5The Complete Project SystemThe flagship, once the pieces are proven individually.
- 6Service Agreements, Installed Base & Recurring RevenueCompounds everything above, and depends on the installed base data that System 5 starts producing properly.
- 7The Owner's Morning BriefOnly meaningful once there are systems to report on.
The tiers are the dependency order for smart home and AV, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Do not build all seven at once.
Each stage is proven against its agreed measure before the next begins.
One sequencing note specific to this trade. System 3's existing backlog of open proposals should be worked by hand in week one, before any of it is automated. At project values of ten to a hundred and twenty thousand dollars, one recovered proposal usually pays for the entire engagement, and working it manually is what tells you what the five branches should actually say.
Back to the smart home and AV overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.