Quick answer: After award, use the actual contract’s submittal and release procedure. Build a traceable product/document package, resolve review comments, control samples and approved demos, and plan operator, administrator and IT training. Close out with what was actually installed: drawings, full SKUs and serials, configuration/firmware records, test results, agreed service terms and a secure account handover. Award, approval and release dates are different milestones.
On this page
What goes into a security system submittal package?
Use the bid documentation checklist with the actual submittal, procurement-release and closeout clauses. A contract may use Division 01 and a surveillance section, but generic section numbers or review stamps do not establish every release milestone. Record required approvals, permitted early releases, revisions, format, reviewer and response dates before making commitments.
| Submittal item | What it contains | Common rejection reason |
|---|---|---|
| Product data | One spec sheet per full SKU, specified rows highlighted, deviations listed | Generic brochure; SKU letter not matching the schedule |
| Shop drawings | Device location plans, riser, rack elevation, network diagram with VLAN and IP plan, mounting details per camera type | The consultant’s plan repeated without field dimensions or mounting heights in ft (m) |
| Compliance documentation | The procurement, safety, emissions or other records actually required for each offered full SKU/revision/configuration; separate each clause and its responsible reviewer | A brand-level letter where product-level evidence was asked |
| Warranty statement | Written product terms for the actual supplied SKU/revision/order, separately from agreed workmanship terms and their start milestones | “6-year on everything” or a PTZ term copied from the camera row |
| Qualifications | Installer licenses (state / provincial), low-voltage license where required | Expired documents; wrong jurisdiction |
| Test and commissioning plan | How each camera and recorder will be verified; the report form | No night-time or time-sync check |
| Closeout list | What the as-built package, training and spare parts will contain | Submitted at closeout, not up front |
Read the actual stamp, comments and contract procedure; status labels and their effects vary. Identify actions and approvals needed before procurement, installation or acceptance. Carry accepted revisions into the order and as-built record without assuming that a stamp waives other requirements.
How do you build product data per SKU without blanket claims?
Tie each numbered requirement to the full proposed model/revision and exact source record. The list below is an evidence checklist; a catalog comparison is not a completed project approval.
- One sheet per full SKU/revision, matching the schedule. For CS-I8XQ II-2.8mm, resolve the catalog p.18 I/II column-label issue with current manufacturer documentation before assigning features. Highlight the actual numbered requirement and verified source row; do not borrow the more favorable column or another model’s missing value.
- For the recorder, use the exact revision: catalog p.55 lists CS-N220 P16H-AI at 20 channels, 16 PoE ports, 160 Mbps incoming (120 Mbps with AI on), 80 Mbps outgoing, simultaneous HDMI/VGA and up to 10 TB per HDD. Verify actual channel/stream use, bandwidth and usable storage independently; include bitrate, recording mode, scene variation, reserve and the approved retention target.
- For network equipment, request actual listing/emissions evidence when required. Catalog p.63 lists FCC Part 15 Class B and CE/LVD EN 62368-1 for CS-POE33024PF without a UL/ULC row. Omission does not prove listed or unlisted status; obtain the required exact-item record rather than inventing a certification.
- Compliance: separate the exact procurement, safety, origin and other clauses. Request available records for the offered full model/revision and configuration; mark missing evidence and required decisions. Do not promise an official per-SKU certificate exists for every requested condition or copy a blanket brand claim.
- For a required ONVIF conformance claim, verify the full model and firmware in the official ONVIF database. Then test the required streams, recording, playback and events with the actual client/version. A profile list or brand name is not a complete integration statement.
- Describe CASE Connect only by the functions confirmed for the actual device and software version. Android is available; iOS is forthcoming. A web version exists, but do not publish an unverified access URL or assume feature parity. CASE Station desktop and CASE Cloud remote NVR configuration are separate products; neither name establishes cloud recording. List required analytics by exact model and firmware, including concurrent limits and a project test record.
Record each verified difference and its effect, and keep missing evidence pending. Use the or-equal equivalence guide to structure the comparison, then follow the actual authorized review procedure. Disclosure does not guarantee acceptance or silently change the contract.
When do you need samples or demo units, and how do you manage them?
Specifications sometimes call for samples (a camera or mount approved for appearance before release), and owners sometimes ask for a demo unit before accepting a product. The two need different paperwork.
| Item | Purpose | Paperwork | End of life on the project |
|---|---|---|---|
| Sample for approval | Owner or consultant approves finish, size, appearance | Sample transmittal citing the spec paragraph; tag “SAMPLE, not for installation” | Returned or incorporated as the spec allows, recorded |
| Approved demo product | Evaluation of the product on site or on the bench | Serial number, date out, condition, holder; for approved demo products we provide a 90-day test period under the approved demo return process. This is not a general return policy. | Disposition under the approved demo process; any purchase or project incorporation needs explicit agreement and correct order records |
| Mock-up | One complete camera position showing mounting, cable entry and labeling | Record the authorized mock-up review, conditions and agreed reference; use permitted photographs where required | Retain, remove or incorporate only as the actual project approval permits; record its final status |
Track samples, mock-ups and demos separately by serial number, holder, condition, purpose and due/disposition record. A demo does not become project equipment by default. Confirm any purchase or incorporation and its order/warranty records explicitly. A missing item is an unresolved closeout or commercial issue to handle under the agreed terms, not an automatic deduction from final payment.
What does the owner training plan contain?
Read the actual training and execution clauses for hours, attendance, supported tasks and required records; 01 79 00 is a possible project reference, not a universal training plan. Use the CASE Connect customer-handover guide for app-related preparation, then agree operator, administrator and IT sessions for the actual installed versions and roles. Use permitted test material rather than unnecessary identifiable footage.
| Session | Audience | Topics | Deliverable |
|---|---|---|---|
| Operator | Security staff, front desk, managers who view video | Demonstrate actual live/playback/search and export/replay workflows on the confirmed system. Teach the supported CASE Connect functions for the actual devices/app version separately; do not assume every task is available on every client | Sign-in sheet; one-page quick guide |
| Administrator | Facilities or security manager | Verified role, account and sharing controls for the actual NVR/app version; approved retention/preservation and service process; owner control and any separately authorized service role | Permissions matrix and a record of the agreed secure administrator handover; no passwords in the training report |
| IT and network | Owner’s IT staff or managed service provider | VLAN and IP plan, remote-access method as installed, firmware updates, time synchronization, log retention | Network diagram; firmware record |
Where desktop viewing is required, confirm the CASE Station version and supported workflow separately from the mobile app and CASE Cloud remote configuration. Use the NVR user-roles guide to document owner-authorized control and the agreed secure transfer. Keep a separate named service account only with written authorization, least privilege and a review/revocation process.
What goes into the as-built and closeout package?
Build the closeout record from the reviewed package, corrected to the actual installation and agreed acceptance status. Record full SKUs, serials, firmware, drawings, test results and open items with responsible contacts. Find the IP camera user manual for the installed model/version as part of O&M, rather than substituting a generic brochure or an unverified setup procedure.
- As-built drawings: actual device locations, mounting heights, cable IDs, switch/patch ports and head-end layout. Carry accepted revisions into the record, and identify any unresolved note with its owner and required next step rather than marking it resolved without action.
- Final camera schedule: each position with full SKU, serial number, MAC and IP address, firmware version and mount; labels match the schedule. Labeling and Documentation Standard for Camera Installs gives the naming pattern.
- Network documentation: approved VLAN/IP and remote-access plan, time source, named account roles and the secure credential-handover record. Keep actual passwords out of general as-builts and shared reports.
- Commissioning report: per camera, day and night image checked, field of view photographed, recording and time sync verified; per recorder, storage and retention.
- O&M manuals: spec sheets and manuals for every SKU installed, plus the firmware record.
- Warranty letter (next section) and spare parts as the spec requires, with serial numbers.
How do you write the warranty letter?
Write the warranty letter from the actual supplied-item and order records. Separate product terms from workmanship terms, including their start milestones, exclusions and responsibilities. Category guidance and catalog badges help identify questions; they do not establish every supplied item’s warranty.
| Letter section | What to write |
|---|---|
| Project and date | Project, owner, date of substantial completion (per phase if phased), your workmanship warranty period |
| Product warranty by category | General category policies are a starting point, not a warranty for every SKU. Confirm the term, exclusions and claim process for the exact model and revision in writing. Project Series items, intercoms, powered accessories and model-specific exceptions need their own confirmation; hard-drive claims follow the applicable drive-manufacturer terms. |
| Project Series items | For any CSP- item, only the term, certificate and support arrangement confirmed in writing by Anabon for this project |
| Service route | Warranty/service requests start with the named supplying company; it coordinates assessment and the authorized claim route. Repair, replacement, freight and timing follow the actual written terms. |
| Exclusions and contacts | Exclusions as your contract states; your service phone and email; the owner’s administrator of record |
For warranty and service, the customer starts with the installer or company that supplied the system. The warranty/RMA workflow guide describes the professional partner route; assessment, authorized claims, repair/replacement, freight and timing follow the actual written terms. Do not promise automatic approval or a universal no-cost replacement.
Post-award checklist
Copy this into your job folder:
- Submittal package per 01 33 00, with a deviation sheet in front of the product data.
- Submittal approved or approved as noted; notes carried into the order and the as-built; lead time per SKU re-confirmed in writing at release.
- Samples and demo units logged by serial number, tagged, with a return date; mock-up signed off.
- Training delivered to operators, administrators and IT; commissioning report completed per camera and recorder, day and night.
- As-builts, final equipment schedule, controlled network/O&M documentation and actual training/test records delivered as agreed. Record written warranty terms and the secure transfer of authorized account control; keep passwords out of shared reports.
What to tell your customer
A closeout cover note should list the documents, accepted revisions, installed equipment, tests and training actually delivered under the agreed scope. Identify unresolved items with an owner and next step. State the actual product/workmanship service terms and the recorded secure handover of account control, without exposing passwords or claiming unperformed tests.
FAQ
What is a submittal package for a security camera system?
It is the product, drawing, evidence and test package required by that project’s contract. It ties each proposed full SKU/revision to the relevant requirement and disclosed deviation. Read the actual approval and release clauses rather than assuming award, a reviewer’s stamp or a generic section number automatically starts procurement.
What does “Approved as Noted” mean on a submittal?
The stamp’s effect comes from the actual contract and notes. As a scoped US federal construction example, FAR 52.236-21 addresses shop-drawing review, disclosed variations and approval; it does not remove responsibility for drawing errors or waive every contract requirement. It does not define every Canadian/private “Approved as Noted” stamp. Resolve the actual required actions and retain accepted changes, revised supply assumptions and the authorized record.
Do compliance letters belong in the submittal or at closeout?
Supply required evidence at the milestone the actual contract sets, before any release or commitment that depends on that approval. Do not leave a required earlier record for closeout. Tie the procurement, safety, emissions or other requirement to the offered full SKU/revision/configuration and document what is available or pending. A distributor request, broad brand statement or catalog row is not an exact-item certificate or the buyer’s acceptance.
Who gets the administrator password at handover?
The owner’s authorized administrator receives access through the agreed secure handover method. Record who received control and when, not the password itself in the closeout report. Retain a separate named service account only with written authorization, least privilege and an agreed review/revocation process. Remove default credentials and verify the owner can manage access.
References
- Anabon current documents and manuals
- Discuss the project and required documents
- Anabon warranty and RMA workflow
