Need-to-Know Access
Limit project-file access to personnel whose responsibilities require it, with access changes reviewed when team assignments change.
Engineering drawings, CAD models, project specifications and commercial documents often contain sensitive information. This page outlines the security considerations and handling principles that guide discussions about protecting client-supplied information during engineering drafting and detailing engagements.
At 7Solutions India, a project may involve architectural plans, structural drawings, connection details, material schedules, revision registers and related correspondence. Such materials can reveal design intent, site constraints, proprietary methods or commercial arrangements. They should therefore be handled with appropriate care from initial inquiry through project closure.
Good information security depends on more than a locked office or a single software control. It includes limiting who needs access, using agreed communication channels, tracking versions, reviewing external sharing, and defining what happens to files when a scope of work ends. Specific safeguards, retention periods and contractual obligations should be agreed according to the project and the information involved.
Limit project-file access to personnel whose responsibilities require it, with access changes reviewed when team assignments change.
Agree on appropriate channels for sharing drawings, reference files, transmittals and deliverables rather than relying on informal forwarding.
Identify current drawings and superseded revisions so teams do not accidentally base work on an outdated project package.
Use client documents for the agreed project scope and address any proposed reuse or external disclosure through appropriate authorization.
Provide a clear contact route if a missing file, unintended recipient, unusual access request or other concern is discovered.
Define whether project data should be retained, archived, returned or deleted, with any legal or contractual requirements considered.
Different drawing packages present different risks. A structural engineering scope can include load assumptions and technical calculations, while fabrication shop drawings may contain assembly marks, dimensions and project-specific manufacturing details. Rebar detailing and precast shop drawings can include connection information, embedded components and coordinated installation references.
Project owners and consultants should identify any particularly sensitive material at the outset, such as tender information, restricted facility plans, unpublished design concepts, customer details or documents subject to nondisclosure terms. Information should not be treated as public merely because it appears in a drawing set.
Client-provided credentials, payment card information, unnecessary personal records and unrelated confidential documents should not be included in ordinary engineering drawing submissions. Where restricted access is necessary, the method of access should be agreed separately.
The following five-stage process is a practical framework for discussing project handling requirements. It does not assert that every technical or physical safeguard is currently implemented for every engagement; confirmed controls should be reflected in the project agreement.
Identify the document types, authorized parties, confidentiality requirements and applicable client instructions.
Use the agreed transfer channel, acknowledge necessary files and flag missing or unexpected information.
Work from identified drawing revisions and route technical questions through the designated project contacts.
Check deliverable references, recipients and issue status before sending the agreed drawing package.
Follow the agreed approach to archive, return or dispose of project records when the engagement concludes.
Information security responsibilities should be documented in the commercial and operational scope rather than assumed. Depending on the engagement, a client may require a nondisclosure agreement, named project users, specified file-transfer tools, region-specific storage conditions or a documented reporting route for incidents. These requirements must be assessed for feasibility before acceptance.
Confidentiality and cybersecurity are related but not identical. A confidentiality undertaking addresses permissible access and disclosure; operational security concerns how information is handled and protected in practice. Neither should be treated as a substitute for clear technical instructions, revision management or authorized engineering review.
For the broader treatment of confidential information, see our Confidentiality Policies. Clients requesting structural or CAD support can review the Engineering Services overview, then provide their documentation requirements through our Contact page.
Yes. Clients can raise nondisclosure requirements before sharing confidential files. The scope and terms must be reviewed and agreed by the relevant parties.
No. It is better to confirm authorized recipients and an agreed method of transfer, especially for sensitive plans, proprietary designs or large CAD packages.
Drawing registers, filenames, issue dates and revision identifiers can help. The specific version-control procedure should follow the client's project requirements.
No universal retention or deletion period is stated here. Any archival, return or deletion obligations should be confirmed in the engagement terms.
No. It is a description of security considerations and handling principles, not evidence of third-party certification or an independent security audit.
If your engineering drawing package has confidentiality, access, transfer or retention requirements, share those conditions with our team before project files are exchanged.