Site-approved access duties
Define entry support and handovers against the access permissions you approve.
- Visitor records and authorised-area instructions
- Supervisory contacts and escalation routines
Data Centres
Your protocols.
Clear duties.
Access support, approved-area cleaning, support staffing and facility coordination with permissions, work windows and task boundaries agreed with your site team.
Keep general support distinct from IT operations and critical infrastructure work. Confirm the exact scope and required competence before deployment.
Relevant services
Defined support
for controlled sites.
Choose individual services or a coordinated requirement. Agree the duties, resources and responsibilities your premises need.
Non-critical support-area cleaning
Specify approved support areas and methods with the responsible site team.
- Cleaning tasks, materials and permitted work windows
- Area-specific instructions and inspections
Defined support roles
Set personnel requirements for general support duties included in the brief.
- Role criteria, checks and site induction
- Attendance, reporting and access boundaries
Maintenance interfaces
Clarify general facility coordination alongside your specialist infrastructure teams.
- Approved building-support tasks and work permissions
- Request routing and specialist responsibilities
Use the site’s approval process as the starting point.
Identify authorised areas, work permissions, escalation contacts and retained specialist duties. Critical infrastructure and IT responsibilities require an explicitly reviewed scope.
How it works
Confirm permissions.
Define the work.
Make the scope clear before work starts, with practical arrangements for preparation, daily coordination and review.
Review the support brief
Identify approved areas, roles, work windows and site procedures. Confirm the team responsible for scope and access approval.
Agree duties & preparation
Specify competence, personnel checks, induction and permitted tasks. Separate general support from specialist infrastructure or IT responsibilities.
Coordinate & review
Set approved handovers, service records and escalation routes. Review access, inspections and issues with the designated site contacts.
Common questions
Know what to expect.
Clarify the work, operating arrangements and quote details before you agree a service scope.
Does the service include servers or critical infrastructure maintenance?
General support does not by itself define responsibility for IT or critical systems. Identify each specialist requirement separately and confirm the scope, competence, approvals and retained duties.
Which areas can cleaning personnel access?
The site team should specify approved support areas, access permissions, methods and materials. Confirm any additional area or specialist requirement before work is included.
How are work windows and permissions handled?
Share the site’s approval process, permitted times and supervising contacts. The agreed plan should identify what work is authorised and how changes are approved.
What checks and induction should be agreed?
Specify personnel requirements, identity/background checks, induction and access records needed for review. Confirm who approves personnel and their assigned responsibilities.
How are reporting and response expectations agreed?
Define the reporting routine, contact availability and escalation responsibilities for each agreed service. Any specific response expectation or specialist commitment should be reviewed and explicitly included in the engagement scope.
Your next step
Let’s define your
site-support scope.
Share the location, approved areas and support requirements. Start with clear responsibilities and a proposal discussion.