Using P21 for CAD Electronic Submissions: Basic Procedures and 5 Checkpoints

Table of Contents

• First, organize when to use P21 for CAD electronic submissions

• Understand P21’s role so your decisions don’t waver

• Checkpoint 1: Align submission requirements and the purpose of the drawings first

• Checkpoint 2: Clean up drawing data before conversion

• Checkpoint 3: Grasp the mindset when exporting to P21

• Checkpoint 4: Verify appearance and information loss after export

• Checkpoint 5: Review related files and operational conditions just before submission

• Things to keep in mind to maintain drawing handover quality

• Common confusions when handling P21 in CAD electronic submissions

• Summary

First, organize when to use P21 for CAD electronic submissions

To use P21 in CAD electronic submissions, it’s important to first understand why P21 exists within the practical workflow. On site, there are cases where you can hand over drawings in the native CAD format used to create them, but for public works or formal electronic submissions there is a requirement to deliver in a format that preserves reproducibility even if the recipient’s environment differs. This is where standardized formats for CAD data exchange come into play. Among these, P21 functions as an intermediary format for transferring drawings, and understanding it that way helps grasp the overall picture.

Beginners tend to think they can finish the source drawing and then convert it at the end. In practice, however, focusing only on the final conversion step often leads to failures. That’s because the export results to P21 are strongly influenced by how the original drawing was created: layer structure, text handling, linetypes and colors, and how external references are managed. In other words, using P21 is not simply a change of file format; it’s part of the process of preparing the drawing quality that will be conveyed to the recipient.

Therefore, the order of decisions should be: first confirm the submission conditions, then organize the drawing structure, then convert to P21, check the appearance and content after conversion, and finally ensure the overall consistency of the submission. Proceeding in this order reduces the likelihood of rework. Conversely, if you try conversion first, you may later find garbled text, distorted linetypes, broken symbols, or unexpected layer behavior that will force you to return and correct the drawings themselves.

What those who use P21 in CAD electronic submissions should know is that, although P21 is touched at the final stages of submission work, the preparation for it begins in the early stages of drawing creation. Simply keeping this mindset can significantly reduce last-minute panic and unnecessary corrections before submission.

Understand P21’s role so your decisions don’t waver

When understanding P21’s role, an important point is that the source CAD data and the exchange data for submission have different purposes. Source CAD data are working data intended to make drawing and revision efficient. P21, on the other hand, is exchange data meant to facilitate transfer and reuse. Not all of the information contained in the working data will necessarily be represented identically in the exchange data. Therefore, when converting to P21, you need to be conscious of what must be preserved and what can be simplified.

In practice, the term “P21” can become a buzzword, and some may assume that as long as the file extension is correct, that’s sufficient. What truly matters is whether the drawing, when opened by the recipient, contains the necessary information without omissions or misinterpretations and is valid as a drawing. For example, if the hierarchy of line weights collapses so that primary structures and auxiliary lines can no longer be distinguished, the file may be formally deliverable but practically degraded in quality. If text shifts and annotations become hard to read, the drawing’s meaning is not conveyed. If scale, coordinates, or the relationship with the drawing border become ambiguous, downstream processes will be affected.

In short, P21 is not merely a file format; it is a container for bridging drawing information to a different environment. To fit information into this container without forcing it, you should standardize the original drawings, prioritize readability over decoration, and reduce special expressions. Understanding this clarifies what to prioritize when organizing files before conversion.

Also, how P21 is handled will be influenced by project-specific operation. The electronic submission guidelines and the client’s procedures may vary in how they check and what drawing structure they expect. Therefore, while understanding the basics of P21 in general is important, ultimately you must tailor the deliverable to the project’s submission requirements. Knowing the basics and then adjusting to individual conditions leads to consistent decisions.

Checkpoint 1: Align submission requirements and the purpose of the drawings first

The first checkpoint is to align the submission requirements and the purpose of the drawings before starting work. If you skip this and begin working, you may find that even if the conversion result is correct, it does not meet the submission requirements. Practitioners should first confirm whether P21 is required for the project, whether required formats differ by drawing type, whether both source and exchange data are needed, and whether folder structures or naming conventions are specified.

A common confusion among beginners is proceeding with drawing production and creating submission deliverables with the same mindset. Even if a drawing is easy to read, it is insufficient for electronic submission if the submission units are not organized correctly. Since plans, profiles, cross-sections, structural drawings, location plans, etc. each have different roles, you need to decide up front which information goes into which drawing. Conversion to P21 becomes stable only after this organization is done.

At this stage, it’s important not only to confirm drawing completeness but also to verify what the drawing is meant to convey to the recipient at submission. For example, a reference drawing used during construction and a finalized deliverable submitted formally require different levels of rigor. Abbreviations or temporary notes acceptable for internal use must be cleaned up for official submission. If layer names and classifications remain optimized only for your own workflow, the recipient may find the structure hard to understand.

When confirming submission requirements, it is effective to consider the drawing readers. The audience might include the client, inspection staff, maintenance teams, and future reusers. To produce P21-converted drawings that still make sense, arrange them so they are difficult for anyone to misinterpret. Thus, the first checkpoint is not only a matter of format but an exercise in organizing the communicative purpose of the drawings.

When this organization is complete, you have a decision-making standard for later doubts. If you hesitate about retaining a special expression, decide based on whether the recipient can read it correctly. If you hesitate about decorative expression, decide based on whether it will be reproduced stably after conversion. Aligning submission requirements and drawing purpose at the outset provides the foundation for all subsequent work.

Checkpoint 2: Clean up drawing data before conversion

The second checkpoint is to clean up drawing data before conversion. Many of the issues that occur when exporting to P21 originate from insufficient cleanup at this stage. Even if problems look like conversion software or export function bugs, they often stem from overly complex or highly customized source drawing structures.

First, make the elements composing the drawing as straightforward as possible. Even if lines, text, dimensions, hatching, symbols, borders, and title blocks coexist, organizing the role of each element reduces conversion-induced distortion. Layer separation is a representative example. Drawings where everything is placed on the same layer may be visible during work, but they become very difficult to check and correct after export. Simply organizing major geometry, auxiliary lines, centerlines, text, dimensions, and borders makes it easier to locate causes of post-conversion issues.

Next, it’s important to remove unnecessary data. Sketch lines, leftover annotations, duplicate entities, temporary data outside the visible area, and unused blocks or definitions are not only unnecessary for deliverables but can affect the appearance and stability of the file after conversion. Duplicate lines are especially troublesome: they can be hard to notice visually but may appear thicker after export or behave oddly when selected, so pay attention.

Text also needs cleanup. Text styles, text size, rotation, vertical writing, and handling of special symbols are parts that are easily affected by environmental differences. Do not assume that because text looks fine in the source drawing it will be fine elsewhere; review whether the expressions make sense to the recipient. Avoid excessively unusual fonts or proprietary notation rules and prefer common expressions for safety. For dimensions and annotations, check that they do not overlap shapes excessively, are readable relative to the scale, and have clear references—this makes post-conversion checks easier.

Also review the handling of external references, images, and embedded objects. Features convenient during drafting may not transfer stably in an exchange format. Separate information that must be included in the deliverable from auxiliary information used only during work. Ensure necessary information is reflected in the main drawing, and keep supplementary materials organized to reduce confusion at submission.

The essence of pre-conversion cleanup is not merely tidying the drawing’s appearance but making its structure robust for transfer. Beyond visual arrangement, move the drawing toward a state where its meaning is preserved in other environments. If you complete this level of organization before conversion, exporting to P21 becomes a final conversion step rather than a risky peak stage.

Checkpoint 3: Grasp the mindset when exporting to P21

The third checkpoint is to grasp the mindset when exporting to P21. In this step, people tend to focus only on the operation procedure, but in practice it’s important to prioritize what you want to preserve in the export. Whether you prioritize visual fidelity, element editability, or readability will change how you prepare and what you check.

First, as a basic premise, exporting to P21 is not a perfect copy of the source data but a translation into an exchange format. Therefore, fine settings available in the original CAD environment may not be communicated in the same form. If you export without this premise, you will be confused by differences in appearance after conversion. Conversely, understanding that some differences may occur allows you to calmly judge which differences are acceptable and which require correction.

Practitioners should confirm that the information needed by the reader is prioritized. For example, decorative linetypes or complex expressions may look good in the source drawing but if they break down after conversion and reduce the visibility of key information, that defeats the purpose. For deliverables, readability and avoidance of misinterpretation are more important than visual aesthetics. Therefore, before export, recheck that major structures, boundaries, dimensions, and annotations are presented clearly for reading.

Also adopt a mindset of not trying to finalize export in one go. Especially for new projects or unfamiliar drawing types, perform a trial export to check results and then iterate adjustments to the source drawing if necessary. This back-and-forth should not be seen as failure. In electronic submissions, assuming such iteration is safer. Rather than converting everything at once at the end, try representative drawings first to understand tendencies; doing so improves the accuracy of subsequent work.

Additionally, consider file naming and how drawings are split at this stage. If the unit of exported files is ambiguous, it becomes hard to correlate drawings and files after submission. Combining too many drawings into one file is confusing; splitting too finely is hard to manage. Balance readability and operational convenience. Electronic submission should be organized so that recipients can handle it without confusion, not according to the convenience of the creator.

When exporting to P21, the key perspective is how to maintain the meaning of the drawing, not merely the act of using the conversion function. With this perspective, you can proceed without losing sight of the essentials even if there are small operational differences.

Checkpoint 4: Verify appearance and information loss after export

The fourth checkpoint is to verify the appearance and information loss after export. This is an often-overlooked step by beginners, but it is critically important in practice. Feeling relieved just because a P21 file was created is a common reason for post-delivery problems. Completion of conversion and a drawing being valid are separate matters.

When checking after export, first compare the result with the original drawing to see whether there are major differences. Check whether major lines have disappeared, annotations are missing, text positions are shifted, directions of dimensions or arrows are broken, or linetypes have become unnatural. At this point, it’s important to view the drawing from a step back, not only looking at details. Confirm whether the overall visual hierarchy is preserved, whether important elements are not obscured, and whether the drawing’s reading order is intact—this often reveals issues that mere surface matching would not.

Next, zoom in and check details. Small text and dimensions, auxiliary symbols, and areas around hatchings are parts where differences often appear after conversion. Something that looks fine at full view may reveal overlapping annotations or irregular letter spacing when enlarged. Pay special attention to sections such as profiles, structural drawings, and annotation elements related to quantities, where judgment errors can directly affect operations.

Also check not only the appearance but whether information has been lost. For example, ensure elements are not hidden due to layer states, attribute data has not been lost, and the intended drawing order is preserved—confirmation from non-display aspects is necessary. In electronic submissions, recipients may be expected to not only open the drawings but inspect them properly and reuse them later. Thus, do not be satisfied with correct visual appearance alone; also ensure continuity of information.

The important point in this step is not to aim for zero differences. Minor differences from the original drawing can be acceptable if the drawing’s meaning remains unchanged and it poses no practical problems. Conversely, small visual differences that make dimensions hard to read or cause misunderstanding in annotations must be corrected. In other words, the axis of verification should be the drawing’s validity and communicative quality, not perfect visual equality.

Careful post-export checks help prevent last-minute rework. Over time, you’ll also accumulate knowledge about which expressions are prone to break and which drawing types need special attention. Gaining experience in this verification process is the fastest route to becoming a person who can handle P21 stably.

Checkpoint 5: Review related files and operational conditions just before submission

The fifth checkpoint is to review related files and operational conditions just before submission. Even if the drawings themselves are correct, the overall evaluation suffers if the submission package is incomplete. In electronic submissions, not only the drawing files but folder structure, naming, related documents, management information, and transfer procedures are parts of quality. Therefore, the final review should be regarded as a consistency check of the entire submission, not a mere formal check.

First, check that file names correspond to drawing contents. Can you infer the contents from the file name? Do names follow the naming rules? Are there inconsistencies with drawing numbers or types? Though simple, this kind of error is very common in practice. If you replaced a drawing but left the old file name, or naming varied across multiple workers, post-submission confusion will arise.

Next, verify consistency with related drawings and documents. Ensure that annotations on plan drawings do not contradict expressions in structural drawings, that drawings related to quantities do not conflict with explanatory documents, and that the drawing border doesn’t contain outdated notes. Checking inconsistencies that are not visible in individual drawings is important. The evaluation considers not only the quality of the P21 file itself but also whether the entire deliverable is coherent.

Also, review with the recipient’s viewing and checking in mind. Even if the files open fine in your environment, reproducibility in the recipient’s environment is another matter. Confirm that your drawings do not depend on special settings and that their appearance will not break under standard conditions. For some projects, rechecking representative drawings as if during acceptance can provide reassurance.

Just before submission time is often short, and it’s tempting to rush the formalities. However, pausing at this stage and viewing the submission as a whole rather than focusing on single drawings is indispensable for stabilizing quality. Using P21 is not an end in itself—the goal is to deliver drawings that convey information correctly in the correct form. Performing the final checks from that perspective reduces oversights and strengthens your position against post-submission inquiries.

Things to keep in mind to maintain drawing handover quality

When using P21 for CAD electronic submissions, there are attitudes practitioners should maintain. Quality of drawings is not merely about neat appearance but about ensuring that the same meaning can be read by the recipient. A drawing that looks tidy on the drafter’s screen is not sufficient if it leads to misreading in another environment.

To maintain quality, first standardize expressions. Special drawing techniques or proprietary rules may work internally but are risky for handover. Adopt layer structures anyone can understand, common ways of writing annotations, and not overly complex line representations to increase stability after conversion. This is not about restricting drawing freedom but about prioritizing deliverable quality.

Next, create drawings that are easy to revise. If a problem is found just before submission, a well-structured source drawing can be fixed quickly. Conversely, drawings built up from ad-hoc fixes become hard to understand what to change and how it will affect other parts, making them prone to collapse in the final stage. Drawings that are strong for electronic submission are not perfect from the start but have a structure that withstands revision and review.

Furthermore, avoid completing drawings based solely on one person’s sense. Where possible, structure drawings so another reviewer can still follow their meaning. You may think you understand a shorthand or arrangement, but others often do not. People familiar with the source drawing tend to mentally correct differences when checking P21 conversions, so the idea of making drawings readable to a third party is effective.

Handover quality is not produced solely by conversion technique. It is the cumulative result of how you structure, organize, and verify drawings in daily work. P21 is the final stage that reveals this quality, not a magic format that creates quality afterward. With that understanding, it becomes easier to act from drawing creation with the submission in mind.

Common confusions when handling P21 in CAD electronic submissions

A common question in practice is why it’s necessary to recheck with P21 when the source CAD data looks clean. The easy way to understand this is that working data and exchange data have different purposes. Working data are for efficient drafting in the same environment. P21 prioritizes readability in different environments. Rather than expecting them to look identical, focus on whether the meaning is preserved.

Another confusion is how much difference is permissible. Trying to force perfect equality can make the submission process unstable. What matters is whether the drawing’s meaning is unchanged, whether it avoids misinterpretation, and whether it does not interfere with practical decisions. Examine strictly the parts that affect decision-making—primary structure representation, dimensions, annotations, boundaries, and quantity-related information. Conversely, if small visual differences do not change the drawing’s intent, make a pragmatic judgment according to project operations.

Some think it is efficient to convert everything in bulk just before submission, but beginners are better served by intermediate checks. If you convert representative drawings early and confirm tendencies, you can identify vulnerable expressions sooner. This often reduces total workload compared with checking everything at once at the end. Electronic submission is more accident-prone the more you rush it, so small staged checks are more suitable.

It is also dangerous to assume that correct file format automatically guarantees quality. The format is only the foundation for transfer; it does not automatically ensure readability or consistency. That is why the order of confirming submission requirements, organizing before conversion, exporting, checking, and reviewing the whole submission is important. Observing that order reduces uncertainty for beginners and helps experienced staff minimize quality variation.

Summary

When using P21 for CAD electronic submissions, do not think of it as merely changing the format at the end; treat it as part of a flow that creates transfer quality. First understand P21’s role, align submission requirements and drawing purpose, organize drawings before conversion, check appearance and information loss after export, and finally review the overall submission for consistency. Following these five checkpoints in order makes the process easier to follow for beginners and stabilizes decision-making for practitioners.

Especially important is recognizing that the purpose of using P21 is to deliver drawings that are correctly understood by the recipient. A drawing’s value is not determined the moment it is created but when it is transferred, read, and used for subsequent work. Therefore, consider not only drafting convenience but also post-exchange reproducibility, readability, and consistency.

In practical electronic submissions, occasions to improve efficiency increasingly include not only drawing handover but handling location information, field verification, and linking with as-built data or point clouds. For those who want smoother integration between drawings and field information, it is worthwhile to look into methods that make acquiring location information and using point clouds easier on site. For example, systems like LRTK that can be attached to an iPhone for high-precision positioning are an accessible option for those interested in improving on-site position checks, recording, and civil engineering workflow efficiency. By broadening your view to not only delivering drawings correctly but also connecting site and data, you can more easily raise the daily quality of your work.