Project Support

Representative scope: Meeting arrangements, local schedules, contact management, site and supplier interfaces, action follow-up and issue tracking.

Information for review: Assignment objective, locations, authorised contacts, responsibility matrix, schedule, access rules, reporting format and escalation route.

Deliverables to agree: Contact plan, meeting and action records, status updates, issue log and agreed follow-up or escalation notes.

Supporting records: Contact lists, meeting minutes, action registers and supporting correspondence.

Scope boundary: Coordination does not authorise MASCO to bind the client, represent a public body or make commitments outside the agreed responsibility matrix.

Representative scope: Order acknowledgement, clarification follow-up, production or readiness updates, document status, inspection interfaces, packing and dispatch readiness.

Information for review: Purchase or enquiry reference, supplier contacts, milestone dates, document list, inspection requirements, delivery terms and escalation rules.

Deliverables to agree: Status tracker, overdue-action list, milestone updates, document status, readiness summary and issue escalation.

Supporting records: Supplier correspondence, submittal register, inspection notices, packing information and dispatch records provided by the supplier.

Scope boundary: Follow-up does not replace the supplier’s contractual obligations or guarantee production, approval or delivery dates.

Representative scope: Readiness dates, packing information, dispatch sequence, receiving arrangements, unloading interfaces, delivery evidence and exception follow-up.

Information for review: Material list, dimensions and weights, origin, destination, delivery terms, required sequence, access conditions and receiving contacts.

Deliverables to agree: Delivery plan, milestone schedule, dispatch status, receiving coordination, document checklist and exception log.

Supporting records: Packing lists, dispatch information, provider transport documents, delivery notes and receiving records.

Scope boundary: Transport, customs, freight forwarding, lifting and insurance remain separately assigned services; planning does not establish those capabilities.

Representative scope: Service requests, consumable planning, space-readiness checks, vendor attendance, inspection schedules and issue follow-up.

Information for review: Facility list, service requirements, contacts, operating hours, access rules, expected service standards, reporting frequency and priorities.

Deliverables to agree: Service-request register, attendance schedule, consumable plan, status reports, escalations and available completion evidence.

Supporting records: Service logs, checklists, provider reports, action registers and authorised photographs.

Scope boundary: This is coordination support. Physical repairs, specialist maintenance, utilities operation and ownership of the facility are not implied.

Representative scope: Maintenance calendars, work-order follow-up, access and permit coordination, contractor attendance, parts status, inspection follow-up and completion tracking.

Information for review: Asset or work-order list, priorities, service intervals, provider contacts, access constraints, required records and escalation rules.

Deliverables to agree: Maintenance schedule, work-order status, overdue-action report, attendance record, parts status and completion tracker.

Supporting records: Work orders, provider reports, inspection checklists, parts records and completion confirmations.

Scope boundary: Coordination is separate from physical maintenance or repair, which belongs to an agreed work package or the identified service provider.

Representative scope: Provider enquiries, collection and delivery schedules, packing and handling interfaces, document follow-up, dispatch updates and exceptions.

Information for review: Cargo, dimensions and weights, origin and destination, delivery terms, dates, handling needs, site access and required documents.

Deliverables to agree: Provider comparison where permitted, coordination plan, milestone updates, document checklist, delivery status and exception log.

Supporting records: Provider quotations, packing lists, dispatch and transport documents, delivery evidence and issue records.

Scope boundary: The external provider and its scope must be identified. Licensing, customs, insurance, dangerous goods and specialist handling require separate verification of the responsible party.

Representative scope: Readiness checklists, document-status tracking, travel and arrival coordination, access prerequisites, induction scheduling and equipment-readiness follow-up.

Information for review: Role or resource list, mobilisation dates, location, client prerequisites, medical or competence requirements and responsible contacts.

Deliverables to agree: Readiness tracker, missing-item report, schedule, interface records, mobilisation status and available arrival confirmation.

Supporting records: Checklists, document-status registers, travel or access information and induction records supplied by the responsible party.

Scope boundary: Visa, immigration, security, medical, travel and client-access decisions remain with the competent authorities and authorised providers.

Representative scope: Role-brief coordination, candidate sourcing support, application registers, screening against stated criteria, interview scheduling and qualification-document follow-up.

Information for review: Role descriptions, position numbers, mandatory qualifications, experience criteria, location, employment basis, schedule and authorised decision-makers.

Deliverables to agree: Candidate register, screening summary, interview schedule, document-status report and recruitment-action tracker.

Supporting records: Role briefs, screening criteria, application registers, client-supplied interview records and document checklists through an approved personal-data process.

Scope boundary: Selection, employment, visas, medical fitness, client acceptance and mobilisation are separate decisions. An approved personal-data process is required before handling candidate records.

Representative scope: Personnel lists, attendance inputs, document-expiry tracking, mobilisation status, training and access records, timesheet coordination and action follow-up.

Information for review: Approved personnel list, responsibility matrix, working pattern, records, reporting cycle, client formats, access rules and escalation process.

Deliverables to agree: Current personnel register, document-status report, assigned attendance or timesheet pack, training and access tracker and open-action report.

Supporting records: Personnel and status registers, attendance information, approved timesheets and training or access evidence handled through the approved data process.

Scope boundary: Employment authority, payroll, disciplinary decisions, immigration, medical matters and client acceptance remain with the parties identified in the contract.

Representative scope: Contact coordination, meeting arrangements, information exchange, access follow-up, provider interfaces and issue escalation.

Information for review: Interface map, authorised contacts, communication protocol, schedule, information requirements, approval boundaries and escalation route.

Deliverables to agree: Interface register, meeting records, action list, status updates, escalation notes and agreed correspondence support.

Supporting records: Contact and interface registers, minutes, actions, issue logs and supporting correspondence.

Scope boundary: The service does not imply government representation, regulatory approval or authority to commit another party. Any delegated authority must be documented separately.

Representative scope: Submittal and action registers, transmittal status, comment-response follow-up, due dates, meeting actions and completion lists.

Information for review: Document or action list, numbering rules, owners, due dates, status definitions, review workflow and reporting frequency.

Deliverables to agree: Current register, overdue-action list, status report, comment-response tracker and completion summary.

Supporting records: Registers, transmittal references, minutes, comment logs and status reports; source files remain within the agreed document-control system.

Scope boundary: Formal approval authority, revision control and retention responsibilities remain with the assigned document-control owner and system.