STANDARDS

Clear standards. Predictable outputs.

This page explains how Spanix delivers across engineering, architecture, design, and visualization: naming, versions, QA checkpoints, and delivery package structure. It is designed to reduce friction, improve review speed, and make every submission easier to trust.

View samples ↓ How we work

Core standards

What we enforce

Simple rules that prevent project chaos. If you already have your own standards, we follow yours and align our outputs to your client-facing system.

Naming & versioning

Consistent naming makes approvals faster and avoids submission mistakes across drawings, models, BOQs, reports, and design presentations.

Package code + discipline + content + revision
Revision history documented in delivery note
Single source of truth per package

Example pattern:

PRJ-AREA-DISC-CONTENT-REV
QPAC-B2-CIV-StormNetwork-R02
VILLA-A-ARCH-InteriorPackage-R01

Units, levels & references

We validate critical references so outputs can be trusted whether the package is technical, architectural, interior, landscape, or visual.

Units & coordinate reference checked
Key levels verified (invert/top/finished)
Drawings/models aligned with inputs

Units check Datum / levels IFC consistency Visual review

Delivery package

Folder structure we deliver

You receive a submission-ready package — not random exports.

01_ADMIN/
  Delivery_Note.pdf
  Revision_Log.xlsx
02_DRAWINGS/
  PDF/
  DWG/
03_MODELS/
  IFC/
  RVT_or_C3D/
  NWC_NWD/
04_REPORTS/
  QA_Checklist.pdf
  Issue_Log.xlsx
05_DESIGN/
  Boards/
  Materials/
  Landscape_Layouts/
06_VISUALS/
  Renders/
  Presentation_Images/
07_REFERENCES/
  Client_Inputs_(ReadOnly)/

If you use a different structure (Aconex / Asite / Procore / internal), we adapt to your submission system and naming logic.

Multidisciplinary coverage

Standards across all services

The same disciplined approach is applied across every Spanix service line.

Engineering & QS BOQ, takeoff logs, revision notes, and traceable quantity workflows.

BIM & Coordination Federated models, clash reports, issue logs, and structured file control.

Civil & Infrastructure Drawings, IFC/NWC outputs, levels checks, and constructibility notes.

Architecture & Design Drawing sets, review packages, design development outputs, and approval-ready boards.

Interior / Exterior / Landscape Layout packages, finishes coordination, landscape sheets, and presentation sets.

Visualization 3ds Max / rendering outputs, image naming, review comments, and presentation-ready visuals.

Quality

QA checklist (client-facing)

A short checklist that prevents rework and “why is this wrong?” cycles.

File naming + revision code consistent across all outputs.

Units, levels, coordinates, and references validated.

Drawings readability: lineweights, tags, legends, dimensions.

Constructibility flags logged (access, clashes, unrealistic routing).

BOQ/takeoff traceability documented (method + references).

Design packages checked for consistency, sheet logic, and presentation order.

Visualization outputs reviewed for naming, view consistency, and client presentation quality.

If you want, we can include your own QA checklist template and enforce it package by package.

Samples

Deliverables samples (links)

Replace the links below with your real sample files. You can keep them public, watermark them, or share them only under NDA.

BOQ + Takeoff Log Excel + reference notes Open sample →

Civil Package DWG/PDF + issue log Open sample →

Rebar BBS Schedules + summaries Open sample →

Architecture Package Plans, elevations, and review set Open sample →

Interior / Landscape Set Boards, layouts, and material coordination Open sample →

Visualization Output Renders + client presentation images Open sample →

Need a custom standard?

Send your company template and we’ll align our engineering, design, and visualization packages to your submission and naming rules.

Start a project → Email standards ✉️