Security and IP Protection at a Glance
| Security Area | What Should Be Clarified |
| Confidentiality | What project and client information must remain private and which written terms apply. |
| File-sharing channel | Where drawings, references, markups and updated files will be exchanged. |
| Access requirements | Which assigned people require access to complete the agreed drafting work. |
| Client-managed permissions | How the client controls folder or link permissions when using its preferred sharing platform. |
| Document versions | How current drawings are separated from superseded or background information. |
| Markup handling | Where comments, revision notes and drawing updates are stored and returned. |
| Intellectual property | What ownership, licence and permitted-use terms apply under the engagement documents. |
| Communication | Which channels should be used for instructions, questions and sensitive information. |
| Project close-out | What should happen to access, shared links and files when a task or engagement ends. |
| Incident escalation | Who should be contacted if a file-access or confidentiality concern arises. |
| Final review | How the Australian client team retains review, approval and issue responsibility. |
Why Security Matters in Offshore Drafting
Residential architecture and building teams may need to share commercially or personally sensitive information with a drafting support provider.
This may include:
- client names and contact information
- residential property addresses
- project drawings
- design concepts
- construction details
- markups and revision histories
- company title blocks
- drawing templates
- Revit families
- ArchiCAD objects
- schedules
- internal drafting standards
- procedural documents
- file-naming conventions
- project-management information
- intellectual property connected to a design or practice
These materials should not be treated as ordinary public documents.
Security concerns are valid because poorly managed sharing can create:
- unnecessary file exposure
- access by people who do not require the information
- confusion about current and superseded files
- project information being sent through inconsistent channels
- unclear ownership or permitted-use expectations
- uncontrolled sharing links
- difficulty determining which instructions are authorised
- outdated access remaining active after work ends
- uncertainty about who must respond to a confidentiality concern
A responsible offshore drafting relationship should make these matters visible and discussable before sensitive project information is exchanged.
For the wider engagement sequence, visit Our Offshore Drafting Process.
Design.Aid’s File-Sharing Approach
Design.Aid recommends using the client’s preferred file-sharing platform or another channel agreed before work begins.
This allows the client to keep file exchange within a tool it already understands and manages.
Clients may provide:
- DWG files
- RVT files
- PLN files
- PDF files
- marked-up drawings
- image references
- cloud links
- company templates
- drafting checklists
- procedural documents
- schedules
- reference drawings
- previous examples of acceptable output
Files over 10MB should be shared by link.
Design.Aid prefers files not to be compressed or zipped because compressed packages can create unnecessary handling and may increase file-intake or compatibility concerns.
Before sending files, the client should confirm:
- which folder or link should be used
- which files are current
- which files are supplied only for background reference
- who has permission to access the shared location
- whether the sharing link has an expiry date
- whether download permissions should be limited
- where revised files should be returned
- who may authorise access changes
Where the client uses its own file-sharing system, the client generally retains control of the link and folder permissions it creates.
No Standalone Public File Upload at This Stage
Design.Aid should not promote a standalone “Upload Plans for Review” process unless a secure, monitored file-intake system has been implemented and approved.
The current recommended workflow is:
- The client contacts Design.Aid or requests a quote.
- The client describes the project, service requirement, software and timeframe.
- Design.Aid and the client confirm the appropriate file-sharing method.
- The client provides a link to relevant plans or files where available.
- Access and handling expectations are clarified before drafting begins.
A link field may be included inside an enquiry or quote form, but the website should not imply that visitors can upload arbitrary files directly into an unmonitored public intake system.
This approach reduces avoidable spam, malware and uncontrolled file-submission risks while allowing clients to use a file-sharing platform they already trust.
What Should Be Confirmed Before Files Are Shared
Before sensitive project information is supplied, Design.Aid and the client should clarify:
- the type of drafting support required
- the files needed to complete the work
- which information is confidential
- the client’s preferred file-sharing tool
- the main client contact
- which Design.Aid team member or drafting resource requires access
- who may provide instructions
- who may approve revisions
- what software environment is required
- how current and superseded files will be distinguished
- where markups and feedback will be stored
- whether an NDA or additional confidentiality wording is required
- what engagement terms govern intellectual property
- what should happen to access when the work ends
- how a security or confidentiality concern should be escalated
These details should be documented in the applicable engagement terms, onboarding records or agreed workflow instructions.
File Access and the Principle of Minimum Necessary Access
A practical security principle is that access should be limited to the people who need project information to complete the agreed work.
Before an engagement begins, the client should ask:
- which Design.Aid contact will coordinate the engagement
- which offshore drafting team member will work on the files
- whether any additional team members need access
- whether access is temporary or ongoing
- what folders or files each person needs
- how permission changes will be communicated
- how access should be reviewed when a person’s role changes
- what happens when the engagement ends
The exact access-control process must be confirmed during onboarding.
Design.Aid should not publish claims about formal role-based access controls, identity systems, device restrictions or access-monitoring tools unless those controls have been operationally verified.
Where access is provided through a client-managed folder or platform, the client should review the permissions it grants and remove access when it is no longer required.
Document Versions and Source-of-Truth Control
Version confusion can create both quality and security problems.
The client should identify:
- the current source drawings
- the current model or documentation file
- the latest approved markup
- files supplied only as references
- superseded drawings
- archived project information
- the required revision number
- the required file-naming convention
- where updated files should be returned
Current and superseded files should not be mixed together without clear labelling.
A simple project file structure may separate:
- current source files
- client markups
- references
- returned drafting work
- client-reviewed revisions
- superseded files
- final client-controlled outputs
Design.Aid’s drafting team should use the files and instructions identified by the client as current.
The client remains responsible for confirming which information represents the project’s authorised design direction.
Confidentiality Expectations
Confidentiality should not be assumed or left undefined.
Before an engagement begins, the parties should identify:
- what information the client considers confidential
- whether confidentiality obligations appear in the engagement documents
- whether a separate NDA is required
- which people are covered by the applicable terms
- how confidential information should be shared
- which channels should not be used
- whether particular documents require restricted access
- how confidentiality concerns should be reported
- what obligations continue after the engagement ends
The availability, wording and legal effect of an NDA or confidentiality clause must be confirmed in writing for the specific engagement.
Clients with specific legal, contractual or regulatory requirements should raise them before sharing project information.
Clients with specific legal, Non-Disclosure Agreements
Some clients may require a non-disclosure agreement before project drawings or internal documentation are shared.
Where an NDA is requested, the parties should clarify:
- whether an NDA is required in addition to the main engagement agreement
- which entities and individuals are covered
- what information is defined as confidential
- permitted uses of that information
- whether subcontractors or offshore team members are covered
- the duration of confidentiality obligations
- the process for reporting a concern
- what happens when the engagement ends
Any NDA arrangement should be confirmed through signed documentation.
Design.Aid should not publish a blanket statement that all projects are covered by the same NDA until the final contractual process has been approved.
Intellectual Property and Project Ownership
Client trust depends on clarity about ownership and permitted use.
The applicable engagement documents should address ownership of:
- project drawings
- client templates
- title blocks
- CAD standards
- Revit families
- ArchiCAD objects
- schedules
- project models
- markups
- design concepts
- design direction
- internal procedures
- returned drafting outputs
- revisions created during the engagement
As a general workflow principle, client-provided materials should remain under the client’s control and should only be used to complete the agreed drafting work unless the written terms state otherwise.
Design.Aid’s role is drafting production support. It should not present client drawings, templates, project information or designs as Design.Aid-owned portfolio assets without written permission.
Final ownership, licensing, permitted-use and reuse terms must be confirmed in the signed engagement documents.
This page provides general workflow information and does not constitute legal advice.
Client Materials and Design.Aid’s Support Role
| Client-Controlled Material or Decision | Design.Aid’s Support Role |
| Project drawings | Complete agreed drafting updates or revisions. |
| Design concepts | Follow the client’s confirmed design direction. |
| Templates and title blocks | Use them to support consistent drafting output. |
| CAD standards | Apply supplied standards where relevant to the task. |
| Revit families and project files | Use supplied elements for the agreed Revit documentation work. |
| ArchiCAD objects and project files | Use supplied elements for the agreed ArchiCAD drafting work. |
| Markups and revision notes | Process updates based on the client’s instructions. |
| Client or consultant information | Use it only for the agreed drafting workflow. |
| Internal procedural documents | Use them to understand the client’s drafting and review process. |
| Final drawings | Support production; the client checks and approves them before use. |
| Final design and project decisions | Remain with the Australian client team. |
Secure Communication Practices
Sensitive project information should be discussed through the agreed communication channels.
The client and Design.Aid should confirm:
- where formal instructions are sent
- how file links are provided
- where access questions are raised
- how revisions are requested
- where approvals are recorded
- which contact can authorise changes
- how unexpected file requests are verified
- how a suspected confidentiality issue is escalated
Clients should avoid sending sensitive information through informal or unapproved channels when an agreed project channel is available.
Design.Aid should not publish claims about encrypted messaging, certified systems, monitored networks or formal security standards unless those capabilities are verified and documented.
Markups, Revisions and Confidential Information
Markups may contain more than drafting instructions.
They can also include:
- client names
- addresses
- internal comments
- consultant information
- design discussions
- pricing or commercial notes
- planning concerns
- approval status
- unresolved project decisions
Clients should review markups before sharing them and avoid including unrelated sensitive information that is not required for the drafting task.
Markups should be:
- shared through the agreed channel
- attached to the relevant drawing
- clearly dated or versioned
- limited to the information needed for the task
- consolidated where practical
- reviewed by the nominated client contact
Design.Aid can process drawing updates from client-provided markups, but the client retains responsibility for the content of the instruction and the final decision it represents.
Project Close-Out and Access Review
Project close-out should include a review of file access and active sharing links.
The client and Design.Aid should clarify:
- whether the drafting task or engagement has ended
- whether further revisions are expected
- which shared links remain active
- whether access should be removed
- whether files need to remain available for an agreed period
- which final files have been returned
- who controls the project archive
- whether any contractual retention obligations apply
- how future work would be restarted
Design.Aid should not publish a fixed deletion, destruction, archive or retention period until that process has been operationally and legally confirmed.
Where files remain in a client-managed platform, the client should review and update its own sharing permissions at close-out.
Backups, Storage and Device Controls
Buyers may reasonably ask how project files are stored, backed up and accessed.
Before publishing specific answers, Design.Aid should operationally confirm:
- which platforms are used for storage
- whether project files are stored locally or in cloud systems
- what backup process applies
- what device controls apply
- whether personal devices may be used
- how accounts are authenticated
- whether access activity is logged
- how compromised access is handled
- how files are retained or removed
- which procedures apply to offshore drafting team members
Until those details are confirmed, this page should not claim:
- certified information-security standards
- formal encryption specifications
- guaranteed backup frequency
- managed-device enforcement
- multi-factor authentication across all systems
- continuous monitoring
- automatic deletion
- fixed file-retention periods
- independent security audits
Clients with specific technical-security requirements should raise them during the strategy and onboarding discussions.
Security and Quality Are Different Controls
Security and quality assurance address different risks.
Security and confidentiality focus on:
- who can access information
- how files are shared
- how confidentiality is defined
- how permissions are managed
- how project information is used
- how IP and ownership terms are recorded
Quality assurance focuses on:
- whether the correct files were used
- whether the brief and markups were followed
- whether discrepancies were identified
- whether drafting updates were completed
- how issues were communicated
- how the client reviews the returned work
A secure file-sharing process does not guarantee drafting accuracy, and a strong QA process does not replace confidentiality or access controls.
For the drafting-review framework, visit the Design.Aid Quality Assurance Framework.
Security and the Wider Drafting Process
Security considerations should be built into the wider engagement process.
| Process Stage | Security or Confidentiality Consideration |
| Initial enquiry | Avoid sending unnecessary sensitive files before the sharing method is agreed. |
| Discovery | Identify confidentiality, NDA, file-access and IP requirements. |
| Scope confirmation | Confirm which files and project details are required. |
| File handover | Use the client’s preferred sharing tool and identify current files. |
| Drafting production | Limit use of the information to the agreed drafting tasks. |
| QA and return | Return work and issue notes through the agreed channel. |
| Client review | Keep final checking, approval and issue control with the client. |
| Revisions | Share updated markups and source files through the agreed process. |
| Close-out | Review access, sharing links and any retention requirements. |
For the complete engagement workflow, visit Our Offshore Drafting Process.
What Design.Aid Supports and What the Client Controls
Security is a shared responsibility.
| Design.Aid Supports | Australian Client Team Controls or Retains |
| Following the agreed file-sharing workflow | Which files and project information are shared |
| Using client-supplied files for the agreed work | Client-managed folder and link permissions |
| Drafting production and revisions | Design direction and project priorities |
| Raising questions about unclear or conflicting information | Who may provide project instructions |
| Handling markups through the agreed process | Client and consultant decisions |
| Returning work for client review | Final review and internal quality sign-off |
| Flagging file or access concerns | Planning, compliance and permit decisions |
| Supporting project close-out discussions | Final approval, issue and use of drawings |
For business outsourcing engagements, the client retains design direction, drawing compliance, planning and permit responsibility, documentation readiness, approvals and final issue responsibility.
What a Stronger Security Workflow Looks Like
| Stronger Security Practice | Higher-Risk Practice |
| Files are shared through agreed channels. | Files are sent through several informal channels. |
| The client identifies current files. | Current and superseded files are mixed together. |
| Access is limited to people who need it. | Sharing links are distributed broadly. |
| The client controls permissions in its chosen system. | Permissions are granted without review. |
| Confidentiality expectations are documented. | Confidentiality is assumed but not discussed. |
| Markups are consolidated and versioned. | Feedback is scattered across unrelated messages. |
| One contact coordinates instructions. | Several people issue conflicting directions. |
| NDA requirements are raised before sharing. | Legal requirements are raised after files have been exchanged. |
| Close-out includes an access review. | Links remain active without a clear reason. |
| Security concerns have an escalation contact. | No one knows who should respond to a concern. |
A secure workflow depends on disciplined behaviour as much as it depends on technology.
What to Ask Before Starting Offshore Drafting Support
Before sharing files or beginning an engagement, clients should ask:
- What files are required?
- Which file-sharing platform will be used?
- Can we use our own preferred file-sharing tool?
- Who will need access?
- Who will coordinate the offshore drafting work?
- What confidentiality terms apply?
- Is a separate NDA required?
- What IP and ownership terms appear in the agreement?
- How should current and superseded files be identified?
- Where should markups and revisions be sent?
- Who can authorise project instructions?
- How are access concerns escalated?
- What happens to access when work ends?
- Are there any confirmed file-retention requirements?
- Who reviews and approves returned work?
- Which responsibilities remain with our Australian team?
These questions help turn security from a vague concern into a defined part of the drafting workflow.
Start With a Security-Conscious Drafting Conversation
The appropriate file-sharing and confidentiality workflow depends on the project information, client requirements and support model.
A useful first conversation should clarify:
- what drafting support is needed
- which files and project details must be shared
- which information the client considers sensitive
- which sharing platform the client prefers
- whether files over 10MB will be sent by link
- whether the files can be supplied without compression
- who should have access
- who can provide project instructions
- whether an NDA or additional confidentiality clause is required
- what intellectual-property terms are needed
- how markups and revisions will be handled
- who will review and approve returned work
- what should happen to file access after the engagement
- what technical or contractual security requirements the client must satisfy
Book a Drafting Strategy Call to discuss how Design.Aid can support your residential drafting workflow while addressing confidentiality, file-sharing and IP requirements.