At a glance
Illuminated-sign work benefits from one record that makes the approved visual outcome and still-open technical dependencies equally clear. A proof is important; it is not an electrical, structural or installation plan.
01 / Trigger and problem
Start when the visual request and technical unknowns can be separated.
The trigger is a request for an illuminated sign with a location and intended visual result. The problem is that a convincing render can hide unresolved dimensions, construction, power, mounting, access and approval dependencies.
A concept proof is not an electrical design, structural decision or complete production specification. Keep the visible outcome and technical dependencies equally clear.
02 / Inputs, owners and output
Hand each decision to the person competent to own it.
Commercial and artwork owners define the sold visual scope. Survey and project owners record site facts and open dependencies. Production owns the make instruction. Appropriately competent specialists own electrical, structural and installation decisions. The output is a controlled job packet plus a clearly separated dependency register.
| Input | Responsible owner | Concrete output |
|---|---|---|
| Type, dimensions, finish and day/night intent | Commercial / artwork owner | Scoped proof and specification basis |
| Mounting, power and access observations | Survey / project owner | Source-labelled dependency record |
| Components and make information | Production owner | Controlled production instruction |
| Technical and site controls | Competent specialist / installation owner | Approved project-specific evidence |
03 / Fictional process artefact
The handover should show what the proof does not approve.
This is a fictional illuminated fascia example. Proof V04 shows logo, return colour and intended night appearance. The job packet states that the power point, isolator, load assessment, mounting detail and final connection method remain subject to site verification and competent decisions.
04 / Current state
The operational thread is demonstrated; technical capability is not claimed.
The website provides browser-local survey and handover tools and a fictional connected workflow. Spectra does not claim electrical design, LED specification, component inventory, energy calculations, structural design, compliance certification, live supplier connections or permit management.
| State | Inspectable now | Boundary |
|---|---|---|
| Implemented on this website | Survey and handover documents | No technical design or project persistence |
| Demonstrated | Fictional proof-to-install context | No real site, component or approval |
| Not claimed / application dependent | Technical, supplier and compliance functions | Need competent and representative evidence |
05 / Prerequisites and limitations
A workflow records specialist decisions; it does not make them.
Agree the proof scope, source labels, component and production records, site verification, approval authority and handover acceptance. Obtain appropriate electrical, structural, access, planning, landlord and safety input for the actual site and work. This content is operational guidance, not certification or technical advice.
06 / Fit and next action
Use it when visual approval and technical readiness are being confused.
This may fit a sign team that needs clearer separation between artwork approval, production release and site readiness. It is not a design calculator, component selector, supplier system, compliance service or assurance of technical suitability.
Build a synthetic survey brief, review the proof-approval route and prepare a handover pack. Carry every unresolved technical item forward rather than treating the fictional example as a complete sign specification.