Written coverage schedule
Selected views, monitoring windows, site time zone and the specific activities included in the proposed service.
Monitoring plans & coverage
Agree the coverage before you compare the quote.
A camera count alone does not describe a monitoring service. The useful questions are which views need attention, when they need it, what an operator should look for and what happens next. CoreVision builds the discussion around those choices so the proposed coverage can be assessed clearly.
Coverage windows
Match the monitoring period to the reason you need it.
After-hours coverage may focus on agreed restricted zones and access to a closed business. Trading-hour coverage may need more context because customer, staff and delivery activity are expected. A store trading around the clock still needs a clear schedule and defined priorities for each period.
Discuss a combination where the site's needs change. The agreement should identify the actual coverage windows, including the site's time zone and how holiday or operating-hour changes will be communicated. Round-the-clock opening does not automatically mean every camera receives uninterrupted observation.
A monitoring plan should also explain whether the service includes live observation, specified checks, event review or a combination. These activities have different delivery requirements. They should be described explicitly instead of hidden behind a broad service name.
- After-hours: expected inactivity, access and restricted zones.
- Trading hours: relevant activity and specific observable exceptions.
- Multiple locations: site-level instructions plus agreed consolidated reporting.
Access & escalation
Agree what an operator can see and what they are authorized to do.
Access should be limited to what is needed for the agreed service and established through a secure onboarding process. Do not send camera passwords through public contact channels. The technical assessment needs to establish compatible viewing access and the permissions required for any agreed review or evidence handling.
The escalation brief should name contacts, preferred channels, the order of contact and the situations that trigger each step. It should also explain what happens when a contact does not answer. An operator's attempt to reach someone does not establish that the recipient received the message or took action.
Emergency contacts and local response arrangements must be appropriate to the site. Remote monitoring does not include physical intervention or guarantee emergency-service dispatch, arrival or a particular outcome.
The diagram, in plain language
Four parts of an authorized workflow.
-
01
Owner approval
The business owner reviews requirements and approves the agreed cameras and access.
-
02
Camera access
Only authorized, selected views are made available from the store or gas station.
-
03
Human monitoring
Operators review observable activity and document it under the agreed procedures.
-
04
Escalation & reports
Operators follow the approved contact sequence and record observations, actions and outstanding follow-up for owner review.
Scope & pricing
Know what changes the proposal.
Relevant inputs include the number and usefulness of selected views, monitoring hours, expected activity, complexity of observation instructions, escalation requirements and reporting detail. A busy counter with transaction-related review needs a different brief from a quiet rear entrance after closing.
Existing camera access and image quality may also affect feasibility. The review should identify gaps before a proposal implies coverage that the system cannot support. Additional work, such as a separately supported transaction-data workflow, needs its own confirmed scope.
Request a written proposal stating the service, inclusions, exclusions and commercial terms. No price on this page replaces NETEX's approved pricing or a site-specific quotation. If you later add cameras, locations, hours or reporting requirements, agree the revised scope before treating the additions as covered.
- Which cameras and hours are included?
- What triggers an alert, and who must act?
- What reporting and evidence handling are included?
- How are outages, schedule changes and additional work handled?
Define the deliverables
A useful scope ends with clear outputs.
An escalation brief
Agreed triggers, contacts, channels and follow-up responsibilities, with clear boundaries on remote action.
Reporting requirements
A defined format, frequency and recipient list for agreed reporting, plus handling instructions for supporting material where available.
Common questions
A few things worth knowing.
Is every camera included automatically?
No. The agreed scope identifies selected views and monitoring activities. Additional installed cameras, new locations or extended hours need to be assessed and included explicitly.
Do the illustrations show a client portal I will receive?
No. Interface imagery on this website is a labeled demonstration. It does not represent a functioning customer portal, an included software license or a confirmed integration. Reporting delivery is agreed separately.
Can I choose a plan without sharing camera passwords?
Yes. The initial enquiry needs only business and coverage information. Any necessary technical access belongs in a separately arranged secure onboarding process after scope and authorization are established.
Your next step
Request a Free Risk Review ↗
Turn your requirements into a clear monitoring brief.
Tell us which sites, hours and situations matter. We will use that context to discuss suitable coverage and what needs assessment.