Consultant coordination
Deliver the agreed drawings and reference material for the next coordination stage.
File sharing for architecture firms
Design intent.
Delivered with context.
Exchange drawings, design packages and client deliverables with project partners.
Named recipients · Defined access · Recorded activity
MX / CONTROLLED EXCHANGE01
Assemble the approved package.
↗
Planning-Submission-Set.zipIllustrative file package
MXTHE EXCHANGE IN CONTEXT
Give the handoff some context.
Design packages move between clients, consultants and project teams throughout a building project. The recipient needs to know the purpose and revision of the material they receive.
MX provides a route for sensitive business files between named recipients. Match access conditions to the purpose of the exchange and use the available activity record to support follow-up. Keep the underlying approval and information-handling decisions in your own process.
WHERE THE WORKFLOW HELPS
The moments that need a handoff.
Client reviews
Share the approved presentation set with named client representatives.
Submission packages
Assemble the required drawings and supporting documents for the appointed recipient.
A HANDOFF, IN PRACTICE
The right files.
The full context.
An architectural practice is asking a consultant to review a defined design issue. Assemble the drawings around that issue and include the register so the consultant can check completeness. Explain the requested response and keep unapproved options out of the package unless they are explicitly part of the review.
Illustrative workflow · Adapt to your approved process
Issue an architectural review package
↗Planning-Submission-Set.zip
A POSSIBLE PACKAGE
- ✓Approved plans and sections
- ✓Drawing register
- ✓Review scope and issue notes
INTENDED RECIPIENT
The named consultant responsible for the review
A USEFUL RESULT
The consultant can reconcile the register and comment on the correct issue without confusing it with earlier design options.
MAKE THE FIRST EXCHANGE COUNT
Test the details.
Then repeat with confidence.
Use the example package as a starting point for a small, representative trial. Agree the success criteria with the person who will actually receive the files.
Check completeness
Approved plans and sections should be easy to identify in the inventory. Open the delivery copy independently of your working folder to catch missing files or local dependencies.
Walk through access
Test with the intended recipient role and receiving environment. Confirm the access conditions, the instructions and the route for getting help.
Agree what success means
The consultant can reconcile the register and comment on the correct issue without confusing it with earlier design options. Record any remaining questions before making the exchange part of routine work.
FROM PREPARATION TO RECEIPT
Give each exchange
a clear sequence.
Use Planning-Submission-Set.zip as an example of a defined package. Replace it with the approved files and instructions for your actual task.
Explore the MX feature set ↗- 01
Confirm the purpose and recipient
Check who is entitled to receive the information. Record the business purpose through your normal approval process before assembling the package.
- 02
Prepare an approved package
Choose the required files, check their versions and remove unrelated information. Include concise instructions so the recipient knows what to do next.
- 03
Apply the access conditions
Confirm authentication, availability and any download conditions for your service. MX's existing features include named access, MFA and configurable expiry controls.
- 04
Review the exchange
Check the recorded activity and follow up through the agreed process. Keep the exchange reference with the project or client record it supports.
DEFINE THE BOUNDARY
Check the fit
before the first file.
Keep drawing approval, model coordination and the authoritative issue register in your design process. Mark superseded material clearly before assembling a package.
Assess the controls against a representative package and recipient. Confirm any mandatory capability, contract term or deployment requirement with the MX team before relying on it.
Discuss your exchange requirements ↗PRACTICAL QUESTIONS
What to know
before you begin.
Questions about file sharing for architecture firms and the exchange workflow.
Where should design approval remain?+
Keep approval, change control and the authoritative model in the practice's project systems. The exchange supports delivery of a defined issue; it does not establish that the design has been reviewed or approved.
Can recipients view every BIM format in MX?+
Do not assume built-in format support. Confirm viewing requirements in a trial and provide suitable exports or the required specialist software.
How should we prepare the files?+
Deliver the agreed drawings and reference material for the next coordination stage. Check the approved version, any required dependencies and the recipient's ability to use the package. Include only the material needed for the purpose.
What should we verify during a trial?+
Test a representative exchange from sender preparation to recipient access. Check authentication, permissions, expiry behaviour and the activity available afterwards. Include the actual file types and recipient environment you expect to use.
Does an access expiry remove downloaded copies?+
Do not assume expiry deletes a recipient's local copy. Agree post-download handling and retention responsibilities, and confirm the precise behaviour of the service configuration you plan to use.
Where can we check product details and commercial terms?+
Use the current MX product information and confirm the proposed service with the team. Review the plans and pricing alongside your actual users, workflow and deployment requirements.
YOUR NEXT EXCHANGE STARTS HERE
Valuable data.
Better protected.
Put better controls around your next sensitive file exchange. See how MX fits your organisation's workflow.
7 days freeUp to 5 usersNo credit card
- Full feature access
- Unlimited file size transfers
- Named recipients and MFA
- Custom branding and upload portals