A screen-block “transformation” is a controlled chain of decisions, not a jump from inspiration image to site. The brief, repeat module, physical prototype, representative assembly, production release and every later substitution need connected records.
This 16 March 2024 archive does not document a before/after project or a product-development sequence. Its two images show unidentified openwork screens at a stair and building exterior. They are preserved as visual references while the article now explains how to move a separate concept through stage gates without losing its identity or approval basis.
- Archive date
- 16 March 2024
- Source identity
- Unattributed external visual reference
- Body media
- Two originals retained in published order
- Guide role
- Stage gates and change records
Place this guide between the brief and procurement
Several existing pages already answer adjacent questions. Keeping their roles explicit prevents the change-control record from becoming another broad screen-block guide.
Inputs
The Screen Block Design Brief owns module, opening and concept intent. The Application Screening Guide owns use/location and early go/no-go conditions.
Controlled development
This page owns revisions between brief, reference unit, prototype, representative mock-up, released baseline and later change. It records what was reviewed, what changed, who accepted it and what evidence remains valid.
Outputs
The Breeze Block Procurement Guide owns exact product identity, purchase, receiving and handover. The Jali product page owns current range enquiry.
Use the Openwork Light & Shadow Guide for view/daylight studies and the Openwork Space & Safety Guide when a screen meets occupied circulation or an edge. This page does not replace either analysis.
Use six stage gates from concept to release
Each gate should close a defined question and issue a controlled output. “Approved” without a revision, sample ID, reviewer and scope is not a usable record.
| Stage | Controlled output | Gate question | Record to retain |
|---|---|---|---|
| 1. Brief | Marked screen zones, intended visual/spatial outcomes, critical views, exposure/use conditions, interfaces, responsibilities and required evidence. | Is the problem defined without assuming a lookalike product or unsupported performance? | Approved brief revision, decision owners, constraints, unresolved items and acceptance plan. |
| 2. Module baseline | Exact candidate unit/reference, repeat module, orientation, joint assumption, edges/corners/openings and preliminary support concept. | Can the concept be drawn consistently across plans, sections, elevations and schedules? | Basis-of-design sheet with source, product status, drawing IDs, assumptions and superseded alternatives. |
| 3. Prototype | Physical first-off/reference unit or development piece identified by product, body/process route, geometry, finish, date and revision. | Does the manufactured object match the intended geometry and appearance, and what remains untested? | Labelled prototype, inspection record, photographs with scale, deviations, disposition and next revision. |
| 4. Representative mock-up | Defined assembly showing sufficient modules, joints, support/interface, range, corners/openings/terminations and relevant adjacent construction. | Does the assembly demonstrate the visual/detail/performance questions written into its scope? | Mock-up drawings, bill of materials, build record, review conditions, results, comments and signed acceptance/rejection. |
| 5. Production release | Frozen product/profile, drawings, sample/range, assembly basis, evidence, quantity, packaging/spares and project responsibilities. | Are all order and inspection documents aligned to the accepted baseline with open risks assigned? | Release note, approved submittal register, control sample IDs, inspection/test plan and authorised signatories. |
| 6. Change and handover | Evaluated substitutions/revisions plus as-built product, batch, inspection, nonconformance, spare and maintenance records. | Has every deviation been assessed against the released baseline before use or acceptance? | Change log, impact review, approvals, superseded records, receiving/installation traceability and final handover index. |
Name what each sample or mock-up can prove
Teams often use “sample,” “prototype” and “mock-up” as if they were interchangeable. Give every object an ID and declared purpose so its approval is not stretched beyond what was reviewed.
Concept model
Tests pattern, scale, rhythm or orientation quickly. It may be digital, printed or made from another material; it is not product, manufacturing or performance evidence.
Colour/range sample
Sets a viewing reference and acceptable appearance range for an exact proposed body/finish. One ideal piece does not define batch distribution or system behaviour.
Production prototype
Checks whether the proposed manufacturing route can produce the geometry and appearance. Record tooling/process status and deviations; do not call it a current standard SKU without a controlled item record.
Detail mock-up
Studies joints, module accumulation, edges, corners, openings, support interfaces and adjacent work. Its construction must match the question it is meant to answer.
Performance mock-up
Uses a defined specimen/build-up, method, actions, instrumentation and acceptance criteria. A result applies only within its documented scope and cannot be inferred from appearance review.
Control sample or bay
Preserves the accepted production baseline for comparison during manufacture, receiving and installation. Protect it, label it and define who may authorise departures.
Evaluate every substitution against the released baseline
A replacement that looks similar can alter module, joint, support, tolerance accumulation, exposure response, maintenance, programme and the relevance of existing evidence. Do not approve by colour photograph, nominal dimension or unit price alone.
Describe the change
Record requester, date, reason and exact old/new product, body, plant/process, geometry, finish, drawing, assembly, quantity, packing or programme field. Attach marked comparisons.
Map affected records
Identify drawings, calculations, specifications, samples, mock-ups, tests, certificates, environmental files, approvals, orders, spares and maintenance information that may no longer match.
Review interfaces and risk
Ask the responsible parties to assess visual intent, dimensions/tolerances, supports/joints, safety, fire/water/exposure, access/replacement, supply, installation and statutory consequences as applicable.
Record the disposition
Approve, approve with conditions, reject or return for more evidence. Name reviewers, date the decision, update the baseline, mark superseded records and stop unapproved material from entering the works.
- approved brief, screen-zone schedule and current responsibility matrix;
- exact manufacturer/product/profile, production site/route, controlled drawings and item status;
- unit/repeat geometry, joints, orientation, edge/corner/opening/termination and assembly interface records;
- labelled appearance/range/control samples and representative mock-up scope, build and acceptance record;
- applicable calculations, tests, declarations and certificates matched to the proposed product and assembly;
- quantity, batches/lots, tolerances, inspection plan, packing, delivery, receiving, storage and spare strategy;
- open issues/hold points, nonconformance route, authorised change process and superseded-document index; and
- as-built identity, installation/inspection traceability, replacements, maintenance and final handover records.
This guide supplies no universal block dimensions, material formulation, open-area value, wall height, joint, mortar/adhesive, reinforcement, frame, anchor, test threshold, cleaning product or service result. Those fields belong to the exact unit, assembly, application and project evidence.
Issue a controlled development request
Send the approved brief, marked screen zones, candidate product/reference, module study, edge/opening conditions, support concept, sample/mock-up questions, evidence needs, quantity and programme. Ask for a dated development and release plan with named revisions, hold points and change authority.