SNAGSORT | ENTERPRISE PROCUREMENT
Enterprise Procurement Pack
NEC4 · JCT 2024 · Contract-neutral Schedule X
Supplier: GMBF Ventures Ltd, trading as SnagSort · Company No. 17286832 · 124 City Road, London, EC1V 2NX, United Kingdom.
Purpose
This pack gives procurement and legal teams a ready-to-adapt basis for requiring SnagSort as the project defect / snagging / rectification / evidence / close-out workflow while keeping contractual authority and formal notice mechanisms clear.
The Contractor shall use SnagSort as the mandatory project defect and close-out system for all Items within the scope of this Schedule.
Procurement decision summary
- Client normally procures/provides the SnagSort licence.
- Contractor prices administration, devices, connectivity, training and subcontractor coordination.
- Contractor acknowledges allocation, records proposed action and expected completion date, keeps status current and uploads sufficient evidence before requesting closure.
- Contractor remains responsible for relevant subcontractors.
- External “complete” means ready for review only.
- Only authorised client-side users close or withdraw unless project permissions explicitly provide otherwise.
- Email alerts are a convenience; the SnagSort System Record is the project defect-management record.
- A downtime/fallback route should be defined, with backfill to SnagSort after restoration.
Annex 1 — NEC4 drafting basis
Use the Scope to identify SnagSort as the required Defect-management communication/workflow system for the defined defect process. Keep NEC terminology precise: Defect, notify, correct, Supervisor and Project Manager.
Tender confirmation: “Tenderers shall confirm, without qualification, that they will use SnagSort as the mandatory digital Defect-management system in accordance with the Scope, including allocation, planned dates, correction evidence, Subcontractor coordination and close-out records. Any proposed exception shall be identified expressly in the tender return.”
Annex 2 — JCT 2024 drafting basis
Insert the requirement through the Employer’s Requirements, Preliminaries and/or Supplemental Conditions as appropriate. Preserve formal contract notices, instructions, certificates, Practical Completion and making-good procedures unless legal advisers deliberately amend them.
Tender confirmation: “Tenderers shall confirm that the Contract Sum includes full compliance with the SnagSort digital defect-management requirements and that the Contractor will require its relevant Subcontractors to participate in the workflow. Any proposed exception or alternative system shall be stated expressly in the tender return.”
Annex 3 — Contract-neutral Schedule X
- Mobilisation: Contractor establishes required users and workflow within 5 Working Days or the project-specific period.
- Acknowledgement: Contractor acknowledges allocation within 2 Working Days unless a shorter underlying contractual period applies.
- Action and date: proposed action and expected completion date entered within 2 Working Days.
- Maintenance: owner, target date and status kept current.
- Supply chain: Contractor coordinates and remains responsible for relevant subcontractors/tier-two parties.
- Evidence: sufficient completion evidence uploaded before closure is requested.
- Rejection: rejected close-out is addressed within 2 Working Days unless the contract/project requires sooner.
- Authority: external completion status is not client acceptance or certification.
- Confidentiality: project photographs/records remain within SnagSort unless Client expressly authorises an approved external route or law requires disclosure.
- Downtime: parties use the nominated fallback route and backfill the System Record promptly after restoration.
- Handover: project records are exported/retained in the agreed format at completion/exit.
Data governance
SnagSort is operated by GMBF Ventures Ltd. Customer project content remains owned by the customer/uploader/rights-holder under the underlying arrangements; GMBF Ventures Ltd receives only the rights needed to provide and secure the service. External users must accept the current External User Terms before project content is released. See Privacy, Security & data and Data Processing Addendum.