Scope before price
Sites, systems, interfaces, assumptions, exclusions and client decisions are identified before a fixed delivery price is treated as reliable.
Procurement & delivery assurance
Make the delivery evidence part of the scope.
For corporate workplace projects, UPNX defines who owns each interface, what must be tested and what evidence is required before handover. Applicable company, insurance, licence and specialist evidence is confirmed against the actual scope—not implied through a generic badge.
The project control chain
- Defined responsibility
- Controlled change
- Testable acceptance
- Documented handover
Delivery controls
What procurement and project teams can expect
The exact contract documents depend on the project and appointment. These six controls are the minimum commercial structure UPNX aims to establish before work proceeds.
Named responsibility
A responsibility matrix separates UPNX delivery, client duties, designer or consultant scope, specialist appointments and third-party dependencies.
Commercial control
Payment milestones, programme dependencies, provisional allowances and written variation rules are stated in the proposal or contract.
Safe mobilisation
Site access, method statements, risk controls, permits and competent-party requirements are agreed where they apply to the confirmed work.
Acceptance evidence
Testing and commissioning use an agreed plan, acceptance criteria, issue record and accountable close-out owner.
Operational handover
The project closes with the agreed drawings, schedules, test records, asset information, training, warranty boundary and secure credential-transfer route.
Evidence by stage
Ask for evidence at the decision point—not after the risk appears.
This is a procurement framework, not a claim that every document or appointment applies to every project.
01 · Before proposal
Fit and authority
- Confirmed contracting entity and commercial contact
- Actual project trigger, site and decision date
- Applicable registration, licence or specialist appointment check
- Reference wording and permission check where a client name is used
02 · Before mobilisation
Ready to execute
- Agreed scope, exclusions and responsibility matrix
- Programme, access, procurement and client dependencies
- Insurance, safety and subcontractor evidence required by the appointment
- Method, testing and change-control plan
03 · Before acceptance
Ready to operate
- Inspection, testing and commissioning records
- Defects, exceptions and outstanding-action register
- Approved handover deliverables and secure access transfer
- Warranty, support and final responsibility boundary
Claims
Evidence, licence and reference boundary
UPNX does not publish unverified licence scope, statutory-professional capability, savings outcomes, global rollout or client endorsements. Regulated work and specialist appointments must be matched to the confirmed project scope and supported by current evidence before proposal release. Client references describe approved scope only unless separate outcome evidence and permission exist.
Systems
Connected-system and data boundary
For IoT, metering, network, AV, security or BuildOS interfaces, the project should identify data ownership, network zones, vendor access, retention, support, credential transfer and incident responsibilities. Jary AI or BuildOS is optional and uses a separate technology scope when appointed.
FAQ
Procurement questions
Can UPNX provide licence, insurance and company documents during procurement?
Applicable documents should be requested against the named contracting entity and actual work scope. Availability, validity and the responsible-party model must be confirmed before contract or proposal release; this page does not replace that evidence.
How are subcontractors and specialist parties handled?
The proposal should identify their scope, commercial route, coordination owner and evidence requirements. UPNX does not imply that a specialist or regulated appointment is included unless it is explicitly confirmed.
What does handover include?
The agreed handover can include drawings, asset and data-point schedules, configuration records, inspection and commissioning evidence, issue close-out, training, warranty information and a secure route for credentials. The exact list belongs in the contract.
Does energy monitoring guarantee savings or statutory compliance?
No. Monitoring creates visibility. Any savings or compliance conclusion needs an agreed baseline, method and appropriately qualified appointment where required.