Tender submissions
Separate pricing schedules from the technical drawings shared with each bidder.
File sharing for construction
The right drawing.
In the right hands.
Exchange drawings, tender documents and project packages with contractors and subcontractors.
Named recipients · Defined access · Recorded activity
MX / CONTROLLED EXCHANGE02
Assemble the approved package.
↗
Tender-Drawings-Rev-C.zipIllustrative file package
MXTHE EXCHANGE IN CONTEXT
Give the handoff some context.
A subcontractor starts from an old drawing while the revised package sits in a different inbox. The handoff needs a clear revision, a defined recipient and a record the project team can find.
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.
Site revisions
Issue the approved revision with a short note explaining what changed.
Project handover
Assemble the agreed operation manuals and completion documents for the receiving team.
A HANDOFF, IN PRACTICE
The right files.
The full context.
A project coordinator needs to release a revised package to a subcontractor before the next work stage. Separate the drawings approved for that trade from the wider project folder, and make the issue reference visible in the inventory. Keep superseded drawings out of the delivery.
Illustrative workflow · Adapt to your approved process
Issue a contractor drawing pack
↗Tender-Drawings-Rev-C.zip
A POSSIBLE PACKAGE
- ✓Approved drawing register
- ✓Current drawing PDFs
- ✓Revision and issue notes
INTENDED RECIPIENT
The subcontractor's appointed project contact
A USEFUL RESULT
The recipient can identify the issue, open every drawing and distinguish the current set from the previous release.
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 drawing register 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 recipient can identify the issue, open every drawing and distinguish the current set from the previous release. Record any remaining questions before making the exchange part of routine work.
FROM PREPARATION TO RECEIPT
Give each exchange
a clear sequence.
Use Tender-Drawings-Rev-C.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 the master drawing register in your project system. Identify the issue and revision before sending a package; a transfer record does not establish which drawing is approved.
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 construction and the exchange workflow.
What belongs in the covering note?+
State the project, drawing issue, scope of the package and the action expected. If the material is for review rather than construction, make that distinction explicit. Keep formal project approval in the agreed project process.
Can MX replace our common data environment?+
Use MX for the controlled exchange boundary. Keep design coordination, drawing approval and the authoritative revision register in the systems your project already uses.
How should we prepare the files?+
Separate pricing schedules from the technical drawings shared with each bidder. 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