Starting a drawing by copying the last project can feel efficient. Its layers, dimensions and sheet border are already there. Unfortunately, its project name, unusual settings and forgotten geometry may also be there, ready to become someone else’s problem.
A carefully prepared drawing template gives a new file a deliberate starting point. The useful question is which decisions should already be made when drawing begins, which information must remain blank, and how to establish that the resulting file behaves as intended. That makes template preparation a small design task in its own right.
Understand what a drawing template supplies
A drawing template is a reusable starting file containing drawing settings, named definitions and, where appropriate, drawing objects. In AutoCAD it normally uses the DWT extension. A new drawing created from it becomes a separate working file, usually saved with the DWG extension.
The template can establish layers, text styles, dimension styles, linetypes, layouts and page setups. It can also contain a sheet border, title block and deliberately included symbols. Its value lies in the combination: the new file begins with settings that have been considered together rather than assembled independently during the first hour of work.
The relationship is a starting relationship. Editing the new DWG does not revise its source DWT. Similarly, revising an ordinary DWT does not automatically retrofit every drawing previously created from it. Treat any change to existing project files as separate work with its own checks.
This distinction affects accountability. If an old drawing has a poor dimension style, publishing a better template helps future drawings. It does not establish that the old drawing has been corrected. A template release record and a project correction record answer different questions.
Define the drawing family before choosing defaults
A drawing family is a practical grouping of files that share enough conventions to start from the same template. A small product business might need one family for component drawings and another for preliminary layouts. The boundary should follow real differences in units, annotation or output, rather than the names of individual customers.
Write a short purpose statement before opening the template editor. State what the drawing represents, which unit convention it uses, which sheet arrangements it supports and which information the author must supply. A template called Component drawings in millimetres is more informative than one called New master final.
Avoid producing a separate template for every minor variation. Each variant creates another file to inspect when a shared convention changes. Conversely, forcing genuinely different unit systems or output requirements into one template can make the first steps confusing. The right number is the smallest set that makes a correct start reasonably obvious.
Review several representative drawings when deciding the boundary. If a setting appears repeatedly for a clear reason, it may belong in the template. If it exists because of one unusual project, leave it out or make the exception explicit in project guidance.
Separate reusable content from project information
An existing drawing can be useful raw material, but it needs a deliberate clean-up. Inspect model space, every retained layout and the definitions that remain available even when nothing appears on screen. An apparently blank drawing can still carry irrelevant styles or project-specific resources.
Model space is the drawing environment normally used for the geometry at its intended model size. A layout arranges paper space content and views for output. Looking at only the active layout can miss old geometry elsewhere, and looking at only model space can miss a populated title block on another sheet.
Use a simple classification while reviewing candidate content:
| Content | Appropriate template treatment |
|---|---|
| Agreed layer names and properties | Retain and review as reusable defaults |
| Approved text and dimension styles | Retain with clear purposes |
| Sheet border and title block structure | Retain if appropriate to the drawing family |
| Previous project number, revision or approval | Remove and replace with blank fields |
| Geometry from the previous job | Remove unless it is an intentional reusable starting object |
| External references and project images | Remove unless a documented dependency is genuinely required |
Do not use realistic sample project details as placeholders. A convincing date or approval name is easy to overlook because it looks finished. Blank fields make incomplete information visible, while a short instruction can explain who supplies it.
Also examine hidden and non-plotting content. Construction geometry may be intentional, but a copied internal note or obsolete option should not spread through every new drawing. The criterion is whether the content belongs to the drawing family, not whether it happens to be printable.
Make the unit convention explicit
The template should make the intended meaning of a drawing unit clear. A number displayed as 100 does not by itself establish whether the geometry represents millimetres, metres or another unit. Display format, insertion behaviour and the way geometry was originally drawn need to agree.
Choose a representative known length and check it in a fresh drawing made from the template. Then insert a known test block using the intended workflow and confirm its size. This reveals more than looking at a settings dialogue because it exercises the combination the author will actually use.
Do not assume a metric setting fixes geometry that was created under another convention. Autodesk documents the MEASUREMENT setting as controlling the choice of metric or imperial hatch and linetype resources; it is not a general rescaling operation. See Autodesk’s MEASUREMENT reference.
Keep any correction of inherited geometry separate from template preparation. Setting up CAD drawings with consistent units explains the wider relationship between drawing units, insertion and output. For a template, the essential test is that a new user can create and exchange a known object at the expected size.
Coordinate layers, styles and starting conditions
A style is a named collection of settings used by a type of drawing content, such as text or dimensions. Templates are useful places to establish these collections because an author can choose a suitable named style instead of reconstructing its properties each time.
Give each retained style a clear role. A general note style and a title style can be understandable distinctions. A collection of almost identical styles copied from several projects leaves the author guessing. Review both their names and their actual properties before deciding which ones belong.
Check how layers and styles work together. If a layer is intended for annotation, its appearance should support the text and dimensions placed on it. A suitable text height can still produce poor output when the chosen lineweight or colour treatment obscures it.
Starting conditions also matter. The current layer, current styles, grid display and drawing aids influence the first actions in the new file. Set these deliberately, but avoid treating every personal preference as an office rule. Authors may need different interaction preferences while still producing consistent drawing content.
Keep the template understandable enough that a user can recognise an inappropriate default. An undocumented collection of hundreds of definitions may contain everything someone could need, yet make the correct choice harder than a compact set of purposeful options.
Treat layouts and page setups as testable arrangements
A page setup is a saved collection of output settings associated with a layout, including choices such as paper and plotting configuration. It can save repeated work, but its usefulness depends on the resources available when the drawing is used.
Build only the layouts that suit the family. If a particular sheet arrangement is regularly needed, include the border, title block and relevant viewport arrangement. Leave the drawing-specific content and view framing for the project author rather than embedding a misleading completed sheet.
A viewport displays a view of model space within a layout. Its scale and framing must be checked with representative geometry. A tidy empty border does not establish that dimensions, labels and line patterns will remain readable once actual content is shown through that viewport.
Run an output test using the intended PDF or printer workflow. Review the resulting sheet at its intended reading size. Check border position, text legibility, line hierarchy and whether deliberately non-plotting content stays out of the output. Record any resource required to reproduce that result.
This is also where machine-specific assumptions become visible. A page setup can refer to an unavailable plotting configuration, and a text style can depend on a font missing elsewhere. The template provides references and settings; it does not guarantee that every supporting resource exists on another computer.
Save the template and test the new-drawing route
Prepare a working copy, then save the reviewed result as a DWT with a meaningful name and description. Choose a location that the intended users can access and distinguish from superseded copies. Avoid leaving several identically named candidates in personal folders.
Next, create a new drawing through the normal template selection process. Do not merely reopen the DWT and decide that it looks correct. The acceptance question concerns the file an author receives after starting new work, including which template the normal workflow actually selects.
Autodesk’s Working with Templates guidance describes the relationship between template selection and the default used for new drawings. Check that configuration in the installed version; a correctly prepared file is unhelpful if the usual new-drawing action still selects something else.
Use the fresh DWG for a small acceptance exercise. Draw a known shape, add a note and dimension, insert a known block, arrange a layout and produce output. Save and reopen that drawing. The purpose is to test a short chain of ordinary work, not every command in the application.
A worked example: a component drawing starter
This is an illustration. A small Australian product team prepares concept drawings for sheet components. It wants a consistent millimetre-based starting file, one standard sheet arrangement and an empty title block that clearly requires project details.
The team begins with a completed drawing because its border and annotation styles are useful. It removes the component geometry, old revision entries and project-specific notes. It then inspects the other layouts and finds an obsolete alternative view that would otherwise have remained in the template.
The retained content is modest: geometry, centreline and annotation layers; a note style; a dimension style; a border; and a page setup. The title block contains fields for the drawing number, title and revision, but no invented approval. An accompanying description states that one model unit represents one millimetre.
For the acceptance exercise, the reviewer starts a new DWG from the candidate template and draws a rectangle measuring 120 by 80 model units. Its expected perimeter is 400 units because twice the sum of 120 and 80 is 400. A direct measurement checks the geometry independently of the dimension appearance.
The reviewer adds a dimension and note, then places the view on the intended sheet. The test concerns whether the selected conventions produce a clear drawing; it does not establish that the component is suitable for manufacture. The PDF is checked for readable text, consistent line treatment and empty project fields that remain obvious.
Finally, another computer creates the same sample using the shared DWT. If a font substitution or missing output configuration changes the result, the team resolves the dependency before accepting the template. The second test gives a concrete answer to whether the starter works beyond its author’s machine.
Release changes without rewriting project history
A template revision is an identified version of the reusable starting file. It is useful to record what changed, why it changed and which new work should use it. A date and a short change note can be enough for a small team.
Keep a reviewed previous version available while introducing a replacement. If a change makes annotation unsuitable for an established output process, the team needs a known starting point while it investigates. This is easier when each released file has a clear identity and the working draft is kept separate.
Do not open every active project and apply the new defaults simply to make the files look current. A change in dimensions, layer appearance or plotting can affect an issued drawing’s meaning. Decide separately whether existing files need migration and how the revised outputs will be checked.
Templates and standards checks serve complementary purposes. A template supplies a starting condition; a drawing standards file can help inspect supported named properties later. Checking CAD drawings against office standards explains that later checking process and its limits.
Keep ownership proportionate to the business
One person should be responsible for the released template, even when several people suggest improvements. The role is to maintain a clear accepted version and organise a suitable test, rather than to approve every drawing decision made by the team.
Collect recurring setup problems as evidence for changes. If users repeatedly create the same missing style, that may justify adding it. If a definition is never used and has no clear purpose, review whether retaining it helps anyone. The template should evolve through actual drawing needs.
Include a short orientation for new users: which template to choose, what it assumes, which project details to complete and where to report a problem. Avoid burying these instructions inside a sample drawing that must be deleted before work can begin.
For a founder working alone, the same discipline can remain lightweight. A single accepted DWT, a small sample drawing and a brief revision note may be sufficient. The benefit is being able to reproduce a dependable start after time away from the project, without relying on memory.
Questions to ask
- Which drawing family and unit convention does this template support?
- Have old project details and unintended content been removed from every space?
- Do layers, styles and page setups work together in a fresh test drawing?
- Are fonts and output resources available to the intended users?
- Does the normal new-drawing action select the accepted template?
- Who reviews changes, and which existing drawings need separate attention?
Bringing it together
A useful CAD template makes recurring decisions explicit and leaves project decisions visibly unfinished. Build it around a defined drawing family, test it by creating and outputting a fresh drawing, and keep its revision history clear. Consistency then begins with a reviewed starting file instead of an accidental copy of yesterday’s project.
Source: Autodesk, Inc., Learning AutoCAD 2010, Volume 2 (2009), with supplementary Autodesk documentation linked above. The example and figures are illustrations. This article is general workflow information; check software behaviour and drawing requirements for your version and project.
