Skip to main contentSkip to footerOpens in a new tab.
Digital LED Sync Clocks & Systems Manufacturer in China

SYNC CLOCKS / Practical resources

Clock System Technical Submittal Package

Make a proposed clock system easier to review. Organize the selected equipment, drawings, responses and outstanding questions in one controlled package, with a clear reference from each project requirement to its supporting document.

Browse resources

Blank submittal register

Prepare package-control fields, a document register, a requirement-response matrix, an equipment schedule, a deviation register and review/change logs.

Download blank CSV template

Opens in Excel or compatible spreadsheets. Product capabilities and approval decisions are not prefilled.

How is a technical submittal different from an RFQ?

An RFQ tells suppliers what the buyer needs; a technical submittal explains the proposed response and provides evidence for review. Keep the two linked through requirement references, but do not replace the original requirement with a supplier's interpretation. If you are still defining quantities, locations and interfaces, start with the clock system specification and RFQ template.

Who prepares and reviews the package?

Identify the preparer, designated reviewer and purpose of the issue before collecting documents. The project may assign different responsibilities for equipment, mounting, network access and power. Record those boundaries explicitly so a product-data submission is not mistaken for approval of the complete installation. Use the review procedure agreed for your project.

Which documents belong in the package?

Build the register around the information needed to evaluate the proposed installation, rather than adding unrelated catalogues. For each requested item, record its document identifier, revision, issue date, applicable equipment and availability. Mark unavailable information as not supplied and identify who will provide it.

  • Product data identifies the proposed model, configuration and options.
  • A system diagram shows the proposed time-reference path and connection boundaries.
  • The equipment schedule links device tags, locations, quantities and display faces.
  • Mounting information identifies dimensions, access and installation constraints.
  • Power and network requirements distinguish supplier information from site responsibilities.
  • Instructions, requested evidence and proposed verification records support the review and subsequent handover.

A product catalogue is useful for browsing, but it may not contain the mounting drawing, configuration-specific evidence or instructions requested by a project. Check each requirement rather than treating a PDF download as a complete submission.

How should each requirement be linked to evidence?

Use one row per reviewable requirement. Include the original specification reference, the supplier's response, the exact model and configuration, and the supporting document and page. Separate a documented response from an unanswered question or a proposed deviation. Do not mark a requirement satisfied merely because it appears in a generic product description.

The blank matrix can track a requested mounting arrangement without entering a dimension until the applicable drawing is available. A reviewer can then locate the evidence and record the decision separately.

How do we handle missing information and deviations?

Keep an open-items register with the affected requirement, missing information or proposed difference, responsible party and target date. A deviation should describe what differs from the request and what decision is needed. Do not silently revise the requirement or describe an unresolved item as accepted. Ask the designated reviewer how it should be closed.

What changes need a revised issue?

Record changes that affect the proposed equipment, configuration, interfaces, mounting, supporting evidence or response to a requirement. Update the package revision, identify the changed documents and retain the earlier issue for traceability. Link reviewer comments to the revised response so the reason for each change remains clear.

What should be retained after review?

Retain the reviewed package, the review decisions and the record of changes that follow. Confirm that the equipment and documents supplied match the agreed configuration. Keep installation verification and handover records distinct from the design review: a reviewed submittal does not itself demonstrate installed-system performance.

Preparing a clock system submission?

Send your requirement list and requested document schedule to info@syncclocks.com. Identify the proposed equipment and outstanding questions so the applicable documentation and supply scope can be confirmed.

For project-specific integration, see custom clock systems.

Discuss your documentation needs