For architectural, engineering, and construction practices across the United Kingdom, delivering accurate, well-organised project documentation is non-negotiable. As projects grow in complexity, often spanning hundreds of drawings, models, and revisions, relying on manual drawing management is no longer viable. Enter the BricsCAD Sheet Set Manager (SSM), a robust, centralised hub designed to streamline your draughting workflows, enforce studio standards, and drastically reduce administrative overhead.
If your team is transitioning to BricsCAD or simply looking to optimise existing workflows, mastering this tool is essential. This comprehensive BricsCAD Sheet Set Manager guide for UK CAD teams will walk you through everything you need to know: from setting up your first project and automating title blocks to aligning with UK CAD drawing numbering standards and collaborating seamlessly across multidisciplinary teams.
Let us dive deep into how you can harness the power of sheet sets to transform your daily CAD operations.
At its core, the BricsCAD Sheet Set Manager is an interface that allows you to manage CAD drawing sheets from a single, unified panel. Rather than opening individual DWG files to update title block information, print a set of plans, or check drawing numbers, the SSM binds everything together into a logical, hierarchical structure.
When you use sheet sets in BricsCAD, you are essentially creating a sophisticated digital index of your project. This index allows you to reorganise layouts, automate textual data across multiple files, and publish entire drawing packages with a few clicks.
The backbone of this system is the Sheet Set Data, or DST, file. The DST stores the information and associations used to define a sheet set, including its sheets, subsets, views and properties. Moving or renaming referenced drawings can affect those associations, so drawing locations and sheet links must be checked whenever project files are relocated.
For many UK engineering and architectural firms, the move to BricsCAD is driven by licensing flexibility and performance. A common concern during this transition is how the drawing management tools compare.
The good news? When evaluating the BricsCAD Sheet Set Manager vs AutoCAD SSM, you will find a remarkably familiar environment. BricsCAD has engineered its SSM to closely mirror the functionality and interface of AutoCAD’s offering, ensuring a minimal learning curve for experienced draughtsperson.
BricsCAD supports DST sheet set files and includes them among the resources that can be migrated from AutoCAD. The migration should still be tested before production use. Associated drawing templates, blocks, fonts, PC3 and PMP files, plotters and plot styles must also be made available and validated in BricsCAD.
BricsCAD supports both foreground and background publishing. Background publishing allows users to continue working while publishing is in progress, but Octave states that it takes longer than foreground publishing. Foreground publishing is faster but prevents further work until the publishing operation is complete.
Establishing a strong foundation is the secret to a smooth project lifecycle. Whether you are starting a new residential development in London or a commercial infrastructure project in Manchester, knowing exactly how to create BricsCAD sheet sets properly will save countless hours down the line.
If you are initiating a completely new project, the wizard will guide you through the setup process:
If you already have a folder full of DWG files with finished layouts, you do not need to recreate them.
BricsCAD will instantly link these layouts to your DST file, allowing you to begin organising them into subsets (e.g., General Arrangement, Elevations, Sections, Details).
For UK projects, teams should refer to the current BS EN ISO 19650 series and to the requirements stated in the project appointment, information requirements and project information standard. The former 1192 standards have been withdrawn and are no longer supported or revised. Requirements applying to a particular public sector project must be confirmed from its procurement and contractual documents.
For UK implementation, the revised National Annex to BS EN ISO 19650 2 recommends an information container identification structure using Project, Originator, Functional Breakdown, Spatial Breakdown, Form, Discipline and Unique Number. The project information standard should define the permitted values, field lengths and separators.
Sheet Set Manager can support this level of information management by storing custom sheet set and sheet properties and displaying their values through fields. The property structure must still be configured and checked against the project information standard. By utilising Efficient CAD project organization techniques, you can set up subsets within your SSM that reflect the required volume or discipline. Furthermore, you can assign custom sheet properties to hold the specific ISO 19650 metadata fields.
Instead of manually typing PRJ-ARC-ZZ-XX-DR-A-0001 into a text box on every single drawing, you can break these components down into custom Sheet Set properties. This structured approach can reduce repeated data entry and improve consistency across the drawing package. It does not by itself guarantee compliance or eliminate human error, so identifiers, fields and CDE metadata must still be checked before issue.
A successful sheet set relies heavily on robust metadata management. Managing project metadata in BricsCAD involves distinguishing between two types of properties within the SSM:
Defining these properties centrally reduces repeated data entry, but the DST should not be described as the project’s sole source of truth where the project CDE controls formal metadata, review and issue status. After changing a sheet set property, update the affected fields and save or resave the sheet drawings before publishing.
One of the most powerful reasons to adopt this workflow is the ability to eradicate repetitive typing. Automating drawing title blocks with fields transforms your BricsCAD title blocks from static linework into intelligent, data-driven assets.
To achieve this, you need to link standard attributes within your title block block to the properties managed by the DST file.
When a sheet containing correctly configured Sheet Set fields is associated with a sheet set, those fields can display the relevant sheet set and sheet property values. Run UPDATEFIELD and save the drawing before checking or publishing the sheet.
In UK engineering and architectural workflows, revision control is paramount. You can add custom sheet properties such as Rev_Letter, Rev_Date, and Rev_Description. Custom sheet properties can hold current revision values and title block fields can display them. After changing a revision property, run UPDATEFIELD and save or resave the affected sheet drawings before publishing. The Sheet Sets panel includes a Resave All Sheets command that can assist with this process.
A complex UK construction package requires meticulous cross-referencing. Sections, details, and elevations must be clearly linked back to the general arrangement plans. BricsCAD provides intelligent tools to manage this through the SSM.
To make navigation intuitive, you can configure custom callout blocks and view labels that are inextricably linked to your sheet set. When you place a section mark on a floor plan, you want it to automatically display the correct detail number and the sheet number where that detail is located.
If a Sheet View is moved to another sheet, update the relevant fields and verify every affected callout before issue. Sheet Set fields can reduce manual cross-referencing, but they do not remove the need to check references for accuracy.
Many drawing submissions include a drawing register or sheet index, depending on the project information requirements. BricsCAD can insert a Sheet List Table from the Sheet Sets panel. However, Octave states that the current Sheet List Table is not associative and is not updated automatically when sheets are added, removed or renamed. Recreate or manually verify the table against the active sheet set before every issue.
When Friday afternoon arrives and the client requires a full drawing package, manual plotting is a bottleneck you cannot afford. The Sheet Sets panel can send selected sheets to the Publish dialog, where publishing can be performed in either the foreground or the background.
For major UK infrastructure or commercial projects, drawing counts can easily stretch into the hundreds. Batch plotting to PDF for large projects is handled natively within the BricsCAD SSM.
You can select the entire sheet set, or hold Ctrl to select specific subsets or individual sheets. Right-click and choose Publish to PDF. Because the SSM respects the page setups (paper size, plot style tables, orientation) saved within each individual layout, you can seamlessly publish a single PDF document that contains A1 landscape general arrangements alongside A3 portrait detail sheets.
Beyond PDF output, BricsCAD Publish can send sheets to the plotter named in each page setup. BricsCAD does not provide a native Publish to DWF option. DWF or DWFx output requires a separate export, printer driver or conversion workflow. eTransmit is a packaging command rather than a publishing format.
The eTransmit feature within the SSM is particularly valuable for UK CAD teams. Selecting eTransmit from the Sheet Sets panel opens the eTransmit procedure for the selected sheet set, subset or sheets. The package can include selected drawings and dependencies such as xrefs, images, font files, plot configuration files, plot style tables and font map files. The output can be a ZIP file or a folder. Review the included files and transmission report, then test the package before issue because eTransmit does not guarantee that every recipient will avoid missing reference or compatibility problems.
Modern engineering is rarely a solitary pursuit. Multi-disciplinary teams, architects, structural engineers, civil engineers, and MEP specialists, must often work concurrently on the same project package.
Sheet Set Manager centralises sheet organisation, properties and publishing information. It should not be treated as a complete common data environment. Use the project CDE for controlled information states, metadata, review, authorisation, formal distribution and archive. BricsCAD supports multi-user access to a DST stored in an accessible shared location. Sheet set data changes are saved to the DST, but the DST remains a file-based project resource and should not be described as a network database.
When working on a shared local server or a cloud-synced environment (such as Bricsys 24/7, SharePoint, or a local NAS), syncing sheet properties across multi-user environments is handled through file locking and polling.
BricsCAD includes improved support for multi-user sheet set scenarios and saves sheet set data changes directly to the DST. Teams should still control who may change sheet set structure and global properties, use read-only opening where appropriate and refresh the Sheet Sets panel when current status information is required. Do not assume that BricsCAD locks an individual sheet property node unless that behaviour has been verified in the organisation’s deployed version and storage environment.
To optimise this collaborative environment, UK teams should adhere to a few best practices:
Even with the most meticulous setup, issues can occasionally arise, particularly when moving legacy projects or restructuring server folders. Troubleshooting BricsCAD sheet set link errors is a vital skill for any CAD Manager.
Here are the most common issues and how to resolve them:
Missing Values in Fields: If a Sheet Set field displays hyphens, BricsCAD has no available value for that field. Check that the relevant sheet set or sheet property contains a value, confirm that the layout belongs to the intended sheet set, then run UPDATEFIELD. Other error displays should be diagnosed from the field definition and drawing context rather than assumed to mean that the link is broken.
Adopting the SSM is just one part of the puzzle; the way you structure your data determines your ultimate success. Implementing efficient CAD project organization techniques will elevate your team’s output quality.
Transitioning to advanced drawing management doesn’t have to be a daunting task. For practices looking to elevate their output, the BricsCAD Sheet Set Manager provides a powerful, intuitive, and highly compatible environment.
By managing sheets centrally, using fields in title blocks and aligning the workflow with the project information standard, teams can reduce repeated data entry and administrative draughting time. These tools do not eliminate human error, so fields, sheet lists, references and published outputs must still be checked.
Whether you are migrating AutoCAD sheet sets to BricsCAD or building a new collaborative CAD workflow for UK engineering firms from the ground up, the Sheet Set Manager is your key to delivering accurate, professional, and on-time project packages.
Invest the time to set up your DST files BricsCAD correctly, train your team on field-driven sheet list tables, and embrace the power of batch publishing. The return on investment in productivity and consistency will transform the way your UK CAD team operates.
Question: What is a DST file in BricsCAD, and where should our team store it? Short answer: A DST is a Sheet Set Data file that stores the information and associations defining a sheet set. For a multi-user project, keep one authoritative DST in controlled shared storage with a consistent access path. A local DST is valid for single-user or test work. Test any project relocation and verify the sheet links afterwards because relative paths do not guarantee that every dependency will remain valid.
Question: Can we open our existing AutoCAD sheet sets in BricsCAD without rebuilding them? Short answer: BricsCAD supports the migration of DST sheet set files from AutoCAD. The result should still be validated before production use. Migrate and check the associated drawing templates, blocks, fonts, PC3 and PMP files, plotters and plot styles, then test opening, editing and publishing the project. Background publishing allows continued work but is slower than foreground publishing.
Question: How do we implement ISO 19650-compliant drawing numbering and metadata in the SSM? Short answer: Implement the information container identification structure defined by the project information standard. For UK implementation, the revised National Annex to BS EN ISO 19650 2 uses Project, Originator, Functional Breakdown, Spatial Breakdown, Form, Discipline and Unique Number identifiers. Sheet set and sheet custom properties can store and display these values through fields, but subsets and fields alone do not establish compliance. Validate each final identifier and keep it consistent with the CDE metadata.
Question: How do we automate title blocks, and manage revisions, using Fields? Short answer: In your title block DWG, define attributes (ATTDEF) and insert a Field for each one. Choose the SheetSet field category and map attributes (e.g., DRAWING_TITLE → CurrentSheetTitle, PROJECT_NUMBER → CurrentSheetSetProjectNumber). Save this file as your template. For revisions, add sheet properties such as Rev_Letter, Rev_Date, and Rev_Description and link them to title block fields. After editing sheet set or sheet properties, run UPDATEFIELD and save or resave the affected sheet drawings before publishing. If a field displays hyphens, confirm that the relevant property contains a value and that the layout is associated with the intended sheet set. FIELDEVAL can control specified update events, but it does not replace the documented UPDATEFIELD procedure or automatically save every affected drawing.
Question: What’s the quickest way to issue a large mixed-size set and share it with external consultants? Short answer: Use the SSM to batch publish. Select the whole set (or chosen subsets/sheets) and Publish to PDF; BricsCAD honours each layout’s page setup, so A1 landscape and A3 portrait sheets publish into one correctly ordered PDF. For external DWG delivery, use eTransmit to package the selected sheets and selected dependencies, which can include xrefs, images, fonts, plot configuration files and plot style tables. The output can be a folder or a ZIP file. Review the available file list and transmission report, confirm that included fonts may be distributed and test the package before issue. eTransmit reduces but does not eliminate missing reference and compatibility risks.
