Quality Assurance
Check with Precision,
Deliver with Confidence.
Every deliverable is reviewed against the agreed scope, project information and client standards before release.
Our Approach
Quality Is Part of Production.
Production begins only after the scope and applicable standards are agreed. Work proceeds against confirmed project information, with questions raised where information conflicts and an internal check completed before release.
- 01
Defined Scope
Production begins against confirmed inputs, deliverables, exclusions and responsibilities.
- 02
Adopted Standards
Client templates, conventions and project requirements guide the work.
- 03
Independent Review
Every item is verified by someone other than the person who produced it.
- 04
Clear Exceptions
Items requiring client input are listed explicitly rather than resolved through undisclosed assumptions.
Evidence
A Documented Quality Gate.
No deliverable is released without completing a documented check, verified by someone other than the person who produced it.
View Our Process- 01Checked
Standards Compliance
Layers, line weights, text heights, dimension styles, title-block data, and sheet or view naming are verified against the adopted standard.
- 02Checked
Model or Drawing Integrity
Warnings, unplaced or orphaned elements, worksets, unused content, references and file health are reviewed as applicable.
- 03Checked
Coordination
Clash testing is performed and logged where applicable. Unresolved clashes are reported rather than carried forward silently.
- 04Checked
Delivery Verification
Specified formats and folder structure are checked, PDFs are plot-tested, and native files are verified to open cleanly.
QA Process
Checks at Every Stage.
- 01
Scope Review
Confirm the deliverable, applicable standards, software, programme and review process.
- 02
Standards Setup
Collect or agree templates, title blocks, naming, libraries and annotation styles.
- 03
Production Check
Review work as it proceeds rather than waiting until completion.
- 04
Technical Review
Verify the work against the adopted standard and relevant deliverable requirements.
- 05
Coordination Review
Perform and log applicable coordination checks and report unresolved items.
- 06
Final Handover
Audit the files, issue the QA report and record items requiring client input.
Your Standards
Your Standards Stay in Control.
We collect your template, title block, layer conventions, family and block libraries, sheet naming and annotation styles. Where no documented standard exists, one may be derived from completed projects and submitted for approval before production begins.
- Templates and title sheets
- Layer or workset conventions
- Families and block libraries
- Naming conventions
- Annotation and dimension styles
- File and exchange formats
- Revision procedures
- Project-specific requirements
Applicable standards are confirmed during scope review.
Final Review
What We Check Before Release.
The review is matched to the agreed deliverable. Open questions are recorded rather than concealed inside the work.
Document Control
- File naming
- Sheet or view naming
- Revision information
- Required formats
Content
- Completeness
- Dimensions and annotations
- References and schedules
- Project information
Coordination
- Drawing consistency
- Model warnings
- Relevant clashes
- Unresolved issues
Delivery
- Native files
- Specified exports
- File accessibility
- QA report
Traceability
Issues Recorded. Revisions Controlled.
- 01
Identify
Record omissions, conflicts and unresolved information.
- 02
Communicate
Raise a clear question or RFI before production proceeds on an unverified assumption.
- 03
Resolve and Record
Apply the confirmed decision and keep revision information current.
Questions
Frequently Asked Questions
Can you work with our templates and office standards?
Yes. We adopt your template, layer conventions, title block, naming, libraries and annotation styles before production begins.
How are deliverables reviewed?
No deliverable is released without a documented check verified by someone other than the person who produced the work.
How do you manage revisions?
In-scope revisions continue until the deliverable is accepted. A change to the agreed scope is issued as a written variation for approval before further work proceeds.
What happens when source information conflicts?
Conflicts and unresolved information are raised before they are built into the deliverable. Items requiring your input are listed explicitly.
Can you work within our project environment?
Yes. BIM 360 / Autodesk Construction Cloud, SharePoint, Egnyte and Dropbox Business are supported, or files can be delivered directly.
Which native and exchange formats can you deliver?
Formats are confirmed in the written scope. Deliverables may include native files and specified PDF, DWG, IFC or other required exports where applicable.
Next Step
Set the Standard Before Production Starts.
Share your scope, templates and project requirements so we can define the appropriate delivery and review process.