how-to
Alspec System Technical Documentation & Support: A Guide
Table of Contents
- Where to Find Alspec System Technical Documentation
- Alspec Window System Details: Reading the Specifications
- Document Types and When to Use Each One
- How to Request Alspec Technical Support
- Alspec Shop Drawings: What to Check Before You Detail
- Your Window and Facade Shop Drawing Checklist
- Compliance, Standards and Document Currency
- Frequently Asked Questions
Last Updated: October 21, 2026
Where to Find Alspec System Technical Documentation
Alspec system technical documentation support starts with one destination: Alspec's online technical library, which holds product manuals, specification sheets, CAD files and installation guides for each window and door system.
The problem isn't a lack of information.
Below, we'll cover the document types, how to identify your system, what to check before you detail, and how to lodge a support request that gets a useful answer first time.
The Alspec technical manual: what it covers
The Alspec technical manual is the reference set for a given system: section profiles, glazing details, allowable spans, fixing points and performance data. Each system has its own manual, so the one you need depends on the system you're specifying.
The manual answers "how is this system built and what will it do," but it does not replace project-specific engineering.
Download the manual for the exact system revision you're using. Older revisions stay online, and detailing to a superseded revision is one of the most common causes of rework.
Alspec Window System Details: Reading the Specifications
Reading Alspec window system details properly means separating three things that get muddled together: what the system is rated to do (the specification), what the project requires (the brief), and what your drawing actually shows. Your shop drawing has to reconcile them.
Start with the performance table. Note the rated values for water penetration, air infiltration and structural performance, then check them against the project's nominated requirements.
Then look at the interface details: head, sill, jamb and any movement joints. These are where specifications and site conditions diverge most often.
- Check that the nominated glazing thickness matches the glazing pocket detail
- Confirm the sill detail suits the actual substrate, not a generic slab
- Verify any fire or acoustic rating is achieved by the tested assembly, not by the system alone
The difference between a smooth project and a difficult one usually comes down to how carefully someone read these details before fabrication started.
Document Types and When to Use Each One
Choosing the right document is a decision, not a search result. Here's how the main types map to the question you're actually asking.
| Document type | Answers this question | Use it when |
|---|---|---|
| Technical manual | How is this system assembled? | Early design and system selection |
| Specification sheet | What is this system rated to do? | Comparing systems against project requirements |
| Installation manual | How is it installed on site? | Briefing the installer and checking sequencing |
| CAD drawings | What does the geometry look like? | Setting out and drawing production |
| Certificates and test reports | Can I prove compliance? | Building approval and certification |
| Name plates and labelling | How is the installed product identified? | Site inspection and handover |
Most documentation problems trace back to using a specification sheet as an installation manual, or assuming a certificate covers a configuration it was never tested for. Certificates apply to specific tested assemblies: change the glazing, frame depth or fixing method and you may have stepped outside the scope of the evidence.
How to Request Alspec Technical Support
A support request gets resolved quickly when it contains enough for the technical team to answer without a phone call: the system, the project stage, the specific clause or detail in question, and what you've already checked.
Alspec publishes contact details and support channels on its website, and the right path depends on whether your question is about product selection, documentation or a live project issue.
The support request workflow
Here's the sequence we recommend, in the order a technical reviewer will actually work through it:
- Confirm the system name and code from the project schedule or fabricator's quote
- Download the current manual and specification for that exact system revision
- Note the page, clause or detail number your question relates to
- Describe the project conditions that make the standard detail insufficient (wind load, substrate, deflection limit, acoustic requirement)
- Attach your draft detail or drawing marked up with the question circled
- State your deadline and what decision the answer unblocks
- Ask for the answer in writing so it can be filed with the project documentation
Step 7 matters more than it looks. A verbal answer is not evidence of suitability and disappears when the person who took the call leaves the project. Ask for the response in writing, even if the initial conversation is verbal.
What to include in a support request
A complete request covers six things: project name and location, system code and revision, the document reference, the specific question, supporting drawings, and your required response date.
Write the question so it can be answered yes or no, or with a specific figure.
If you're coordinating multiple consultants, send the same marked-up detail to everyone in one thread. It stops the same question being answered three different ways and gives the technical team visibility of what others have already said.
Response expectations and escalation
Set expectations internally before you lodge the request. A design-stage documentation query and a live site issue are not the same priority, and the channel should reflect that. A common pattern:
- Design-stage documentation queries, lodge in writing with the marked-up detail and allow time for a considered response; these are rarely same-day.
- Live project issues, flag the project stage and the consequence of delay in the subject line, and follow up by phone if the written channel has not responded within your project's tolerance.
- Compliance and certification queries, direct these to the certifier as well as the supplier, because the certifier is the party who has to accept the evidence.
If a response doesn't resolve the question, escalate by replying in the same thread with the specific gap, a new thread loses the context the reviewer already built up. Where the issue is a missing or superseded document rather than a technical question, say so explicitly; document requests are handled differently from engineering queries.
Keep a support log for the project: date lodged, channel, question reference, response date and the answer in writing. When an RFI lands six months later, the log is the fastest way to show what was asked and what was advised.
Never treat a verbal answer as approval to depart from a tested configuration. If the advice changes a detail, get it in writing and update the drawing register before fabrication.
Alspec Shop Drawings: What to Check Before You Detail
Before you draw a single line, confirm the system revision, the performance requirements and the interface conditions. Alspec shop drawings translate standard details into a project-specific set, and every translation is a chance to introduce an error.
A common mistake is detailing from memory of a previous project. Systems get revised, profiles change, and a detail that worked two years ago may no longer reflect the current manual. Open the current document every time.
What most guides miss is the interface. The system detail is rarely the problem; the junction between the system and the structure, adjacent cladding or waterproofing membrane is where drawings fail on site.
Your Window and Facade Shop Drawing Checklist
Use this checklist before any shop drawing set leaves your office. It's the same sequence we apply at BluePrint Facade when producing documentation for Alspec, Capral and Darley systems.
- System name, code and revision stated on every sheet
- Performance requirements cross-referenced to the specification
- Head, sill and jamb details match the actual substrate conditions
- Glazing thickness and type consistent between detail, schedule and specification
- Movement joints shown and dimensioned
- Waterproofing and flashing interfaces detailed, not implied
- Fixing type, spacing and embedment specified
- Fire, acoustic and thermal ratings traced to a tested assembly
- Name plate and labelling requirements noted for handover
- Drawing revision and date consistent across the set
The checklist catches the errors that become RFIs. An RFI at documentation stage costs a phone call. The same gap discovered during construction costs a delay.
Compliance, Standards and Document Currency
Compliance documentation is only useful if it's current and applicable. Building work is governed by the National Construction Code and the relevant Australian Standards, and evidence of suitability must match the assembly actually being installed, not the system in general, and not a previous revision.
Two habits keep you out of trouble: check the revision date on every document before you rely on it and re-check at each milestone, and keep a document register recording which revision each drawing was based on.
Checking document currency
A document is current when three things line up: the file revision matches what the supplier currently publishes, the revision date post-dates any relevant standard amendment, and the system code matches your schedule. If any one fails, you're detailing to something that may not be supported.
A practical check at each milestone:
- Re-download the manual and specification rather than reusing the file from the last project
- Compare the revision code on the download against the revision recorded in your document register
- Check whether the referenced Australian Standards have been amended since the document was published
- Confirm the certificate or test report covers the specific assembly, glazing type, frame depth and fixing method, not just the system family
Superseded revisions often stay online for reference, useful for legacy installations, but a trap for new detailing. If you're working from a superseded revision, stop and confirm with the supplier whether the current revision changes the detail you're relying on.
Evidence of suitability in practice
The NCC sets out the categories of evidence that can show a building solution complies, and the certifier decides which evidence they'll accept.
Where a project requires certification, confirm with the certifier which evidence they'll accept before you finalise details. Doing this at documentation stage is cheap; after fabrication has started, it is not.
For the regulatory framework itself, the Australian Building Codes Board publishes the NCC and its evidence of suitability provisions, and Standards Australia maintains the referenced standards.
A certificate for a tested assembly does not cover a modified assembly. If your detail departs from the tested configuration, the certificate no longer applies, and the compliance problem typically surfaces during construction rather than at approval stage.
This is where a documentation partner earns their keep.
Frequently Asked Questions
Where can I find technical documentation for Alspec systems?
Alspec publishes product information, system specifications and installation manuals through its own technical resources and its network of licensed fabricators. Start with the system name or code, confirm you have the current revision, and check that the document matches your project's wind, water and thermal requirements. If a document is not publicly listed, a fabricator or a facade documentation consultant can usually obtain it. Keep a dated copy in your project file so your Alspec technical documentation record stays traceable through construction.
What information is included in Alspec window system details?
Alspec window system details typically cover profile geometry, section properties, glazing rebates, drainage and weathering paths, fixing and anchorage zones, and recommended assembly sequences. They also indicate compatible accessories such as mullions, transoms and gaskets. Use these details to confirm the system suits your span, height and exposure before you commit to Alspec shop drawings. Where a project needs performance beyond the published range, get written confirmation rather than assuming the standard detail applies.
What should I check before preparing Alspec shop drawings?
Confirm the correct system code and revision, the project's design pressures and serviceability limits, glass make-up and thickness, and all interface conditions with structure, cladding and waterproofing. Cross-check architectural and structural drawings for conflicting dimensions. Run through a window and facade shop drawing checklist covering tolerances, drainage, fire and energy requirements, and access for installation. Getting these settled first reduces RFIs and rework, and it keeps your drawings aligned with the manufacturer's published technical requirements.
How can I check that an Alspec system detail meets project performance requirements?
Compare the system's published ratings against the project's specified wind load, water penetration resistance and thermal targets, then verify the glass and framing combination used in the detail matches the tested configuration. Check that any amendments, such as deeper mullions or different glazing, have supporting documentation. Australian projects should reference the relevant NCC provisions and Australian Standards for glazing and facade performance. If the detail falls outside published limits, request engineering confirmation in writing before documentation proceeds.
