Northeast Remote Surveillance and Alarm, LLC maintains an Actionable Feedback Policy to provide commercial and industrial clients, project stakeholders, and authorized partners with a clear process for raising service, installation, documentation, technical, and project-related concerns.
The purpose of this policy is straightforward: receive relevant feedback, evaluate it appropriately, determine whether corrective action is required, document the outcome, and use recurring issues to improve future performance.
Purpose of the Actionable Feedback Policy
Commercial and industrial security projects can affect building operations, system reliability, documentation, access procedures, security response, and long-term serviceability.
NERSA uses actionable feedback to identify conditions that may require:
- Technical correction
- Process improvement
- Documentation correction
- Service refinement
- Operational improvement
- Risk reduction
- Clarification of project requirements
Feedback is treated as information that may help identify a specific issue or improve the way future work is performed.
Scope of This Policy
This policy may apply to feedback received from:
- Commercial clients
- Industrial clients
- Property managers
- Authorized facility representatives
- Security or operations personnel
- Contractors involved in a NERSA project
- Other authorized project stakeholders
Feedback may relate to areas such as:
- System performance
- Installation quality
- Project documentation
- Service responsiveness
- Project communication
- Configuration
- Technical integration
- Project coordination
The policy is intended to provide a consistent method for reviewing concerns associated with NERSA work and service relationships.
What Is Actionable Feedback?
Actionable feedback is information specific enough to be evaluated and, where appropriate, acted upon.
Examples may include:
- A system function not operating as expected
- Configuration concerns
- Credential or access-control issues
- Documentation discrepancies
- Video retention concerns
- Communication issues during a project
- Service-response concerns
- Installation-quality concerns
- Questions about an agreed project requirement
- Recurring technical problems
Useful feedback generally identifies:
- What happened
- Where it occurred
- When it occurred
- Which system or project is involved
- Who observed the condition
- What outcome was expected
The more specific the information, the easier it is to evaluate the issue accurately.
How to Submit Feedback
Clients and authorized project stakeholders may provide feedback through normal NERSA service and project communication channels.
These may include:
- Direct communication with the assigned project contact
- Service department communication
- Written correspondence
- Post-project discussions
- Scheduled system-review meetings
- Formal written concerns
For assistance, call 1-888-344-3846.
Feedback involving an active service problem should include enough information to identify the property, affected system, and observed condition.
NERSA Feedback Review Process
NERSA uses a structured process to review actionable feedback.
1. Acknowledgment
Formal actionable feedback is acknowledged within one business day.
Acknowledgment confirms receipt of the concern. It does not necessarily mean that the cause or resolution has already been determined.
2. Classification
The issue is reviewed and categorized according to its nature.
Examples may include:
- Technical
- Operational
- Communication-related
- Documentation-related
- Warranty or service-related
- Escalation-level concern
Classification helps determine who should review the issue and what information may be required.
3. Investigation
Appropriate personnel review the information relevant to the concern.
Depending on the issue, the review may include:
- Installation documentation
- Configuration information
- Service history
- Manufacturer guidance
- Project scope
- Available system records
- Site-specific information
- Communications related to the issue
The objective is to determine what occurred and whether corrective action is appropriate.
4. Resolution Plan
When corrective action is required, the response may identify:
- The issue
- Relevant findings
- Required corrective action
- Responsible party
- Applicable next steps
- Method of confirming resolution
The scope of the corrective action depends on the specific issue and applicable project or service conditions.
5. Verification and Closure
Where appropriate, the resolution is verified after corrective action has been completed.
Relevant information may then be documented for future reference and service history.
Priority Escalation
Certain concerns may require a higher level of internal review.
Examples can include feedback indicating a potential issue involving:
- Life-safety-related system operation
- Significant operational disruption
- Critical system availability
- Important security functionality
- Significant documentation discrepancies
- Other conditions requiring management attention
Issues requiring priority review may be escalated to appropriate NERSA personnel.
Escalation does not predetermine the outcome of the investigation. Its purpose is to make sure potentially significant concerns receive the appropriate level of attention.
Documentation of Actionable Feedback
NERSA may document actionable feedback and related findings to support:
- Service history
- Quality control
- Recurring issue identification
- Project review
- Corrective-action tracking
- Training
- Future process improvement
Documentation should be appropriate to the nature of the issue and the work involved.
Records are maintained according to applicable NERSA operational documentation practices.
Continuous Improvement
Recurring feedback can provide useful information about how systems are installed, configured, documented, serviced, and supported.
Feedback trends may be reviewed to identify opportunities to:
- Improve installation procedures
- Improve documentation
- Refine internal processes
- Strengthen training
- Improve project communication
- Reduce recurring service issues
- Improve equipment-selection practices
- Improve future project execution
The purpose of this review is not simply to close individual concerns.
It is also to identify patterns that may improve future work.
Constructive and Critical Feedback
NERSA welcomes specific, professional feedback concerning its work and service.
Providing a legitimate concern does not prevent a client or authorized stakeholder from requesting continued service or communicating additional project requirements.
Critical feedback should be evaluated according to the facts and circumstances of the issue rather than treated as a reason to discourage future communication.
Confidentiality of Feedback
Feedback may contain information about:
- Facility operations
- Security equipment
- System configuration
- Access procedures
- Project conditions
- Internal business concerns
NERSA treats feedback information as operationally sensitive when appropriate and limits internal sharing to personnel who need the information to evaluate, investigate, resolve, document, or manage the issue.
Information may also be handled according to applicable contractual, legal, manufacturer-support, or service requirements.
For broader information about the handling of personal information, review the NERSA Privacy Policy.
Feedback Does Not Replace Emergency Reporting
The Actionable Feedback Policy is intended for service, project, quality, communication, and operational concerns.
It should not be used as a substitute for emergency services, emergency building procedures, law-enforcement reporting, fire reporting, or other immediate response procedures when an urgent condition exists.
Clients should follow their established emergency procedures when immediate action is required.
Feedback Related to an Active Service Issue
When feedback concerns equipment that is currently malfunctioning, the information should clearly identify the affected system or device.
Useful details may include:
- Property location
- System type
- Affected device or door
- Observed symptoms
- Approximate time of occurrence
- Whether the issue is constant or intermittent
- Whether any recent changes were made
This helps separate a general quality concern from an active technical service requirement.
Feedback Related to Completed Projects
Clients may also provide feedback after installation or project completion.
Post-project feedback may involve:
- Installation workmanship
- Documentation
- System usability
- Training
- Communication
- Project coordination
- Final configuration
- Outstanding concerns
When an issue can be verified and corrected, the appropriate next step can be determined through the review process.
Feedback Related to Project Scope
Some concerns involve the difference between:
- Work included in the approved project
- Additional requested work
- Existing-site conditions
- Customer-provided infrastructure
- Third-party responsibilities
- New requirements identified after installation
When scope is relevant to the feedback, NERSA may review applicable proposals, change documentation, project correspondence, site conditions, and other available information before determining the appropriate response.
Client Participation
Clients can help make the feedback process more effective by providing accurate information and access to relevant system conditions.
Where applicable, this may include:
- Identifying the affected equipment
- Providing authorized site access
- Identifying the appropriate customer representative
- Explaining the observed condition
- Providing relevant dates or event times
- Identifying recent system or building changes
- Providing available screenshots, photographs, or system information
Accurate information can reduce unnecessary troubleshooting and help focus the review on the actual condition.
Policy Limitations
Submitting feedback does not automatically establish:
- The cause of a technical problem
- Responsibility for a particular condition
- Warranty coverage
- Contractual responsibility
- A specific corrective action
- A specific resolution time
Those matters depend on the facts, applicable agreements, system conditions, available records, equipment support, and the results of the review.
The purpose of this policy is to establish a consistent process for evaluating feedback—not to predetermine the outcome.
Contact NERSA About Actionable Feedback
To provide actionable feedback concerning a Northeast Remote Surveillance and Alarm project, installation, service visit, system, or client experience, contact NERSA with enough information to identify the issue and affected property.
Northeast Remote Surveillance and Alarm, LLC
1-888-344-3846
Frequently Asked Questions
What is the purpose of the NERSA Actionable Feedback Policy?
The policy provides a structured process for receiving, reviewing, investigating, documenting, and responding to actionable feedback related to NERSA projects and services.
What types of feedback should be submitted?
Feedback may involve system performance, installation quality, documentation, project communication, service responsiveness, configuration, technical integration, or another specific concern related to NERSA work.
How quickly is formal feedback acknowledged?
NERSA’s policy is to acknowledge formal actionable feedback within one business day.
Does acknowledgment mean the issue has already been resolved?
No. Acknowledgment confirms receipt. Investigation may still be required before the cause and appropriate response can be determined.
What happens after feedback is received?
The concern may be classified, investigated, reviewed for corrective action, and documented according to the nature of the issue.
Can technical problems be submitted through this process?
Yes. Technical concerns can be submitted, although an active equipment failure may also require a normal service response.
What information should I provide?
Provide the property, affected system or equipment, observed condition, approximate time, and any other information that can help identify the issue.
Is critical feedback accepted?
Yes. Specific professional feedback about NERSA work or service can be submitted for review.
Is feedback kept confidential?
NERSA treats feedback information as operationally sensitive when appropriate and limits internal access according to the needs of investigation, resolution, documentation, and applicable requirements.
Does submitting feedback automatically mean NERSA is responsible for the issue?
No. The facts, project scope, system conditions, available records, applicable agreements, and investigation must be reviewed before responsibility or corrective action can be determined.
Can feedback lead to changes in NERSA procedures?
Yes. Recurring or significant findings may be used to improve procedures, documentation, training, equipment-selection practices, and future project execution.
Who should I contact about actionable feedback?
Call 1-888-344-3846 or use the NERSA contact page to provide information about the concern.