CAD, BIM and Digital Workflows

Introduction

Foundation and flooring documentation has moved from isolated two-dimensional drawings to coordinated digital information models. Computer-aided design (CAD) remains essential for producing accurate plans, sections, details and schedules. Building information modelling (BIM) extends this capability by connecting geometry with information about materials, dimensions, quantities, specifications, construction status and maintenance requirements.

For a civil draftsman, digital competence is not simply the ability to draw lines quickly. It involves establishing a reliable information structure, modelling elements at an appropriate level of development, coordinating disciplines, checking information, managing revisions and communicating clearly with engineers, architects, surveyors and contractors. Errors in foundation or floor documentation can produce serious consequences, including incorrect excavation, misplaced reinforcement, inadequate clearances, drainage conflicts, material waste and costly rework.

This chapter explains a practical workflow for creating and coordinating foundation and flooring documentation using CAD and BIM. It also introduces templates, layers, parametric objects, common data environments, version control, digital surveying and basic clash detection.

Learning objectives

By the end of this chapter, students should be able to:

• distinguish between CAD drawings and BIM information models;
• establish useful layers, templates, naming conventions and units;
• create foundation and floor documentation using suitable views and details;
• apply parametric objects and understand their limitations;
• coordinate architectural, structural, civil and services information;
• use a common data environment and a controlled revision process;
• incorporate digital survey information into a project model;
• perform basic model checking and clash detection;
• identify ethical, security and quality risks in digital documentation.

1. CAD and BIM in foundation and flooring work

CAD

CAD software represents design information primarily through graphical entities such as lines, arcs, polylines, hatches, text, dimensions and blocks. A CAD foundation plan may show wall centre-lines, isolated footings, strip footings, slab edges, levels, set-out dimensions and notes. CAD is highly effective for precise drafting and remains common for small projects, fabrication details and consultant deliverables.

A CAD object usually has limited meaning beyond its layer, geometry and associated annotation. A rectangle may represent a footing, slab edge, room boundary or excavation outline. Its meaning depends on layers, symbols, notes and drawing conventions.

BIM

BIM represents building or infrastructure components as information-rich objects. A footing can possess a type, width, depth, material, reinforcement reference, fire or durability requirement, construction phase and identification code. A floor slab can be related to a level, room, finish, thickness, structural function and quantity schedule.

BIM does not mean merely producing a three-dimensional image. A useful BIM model contains coordinated information that supports decisions throughout the asset life cycle. The model may be used for design coordination, quantity extraction, construction planning, asset management and future alteration.

BIM does not eliminate the need for drawings. Plans, sections and details remain the principal communication method on many construction sites. Rather, BIM improves the reliability and traceability of the information from which those drawings are produced.

2. The digital information workflow

A disciplined workflow can be understood as a sequence:

1. Receive and inspect information. Collect survey files, architectural backgrounds, geotechnical information, structural criteria and project standards.
2. Establish the project environment. Confirm units, coordinate system, levels, origin, templates, file naming and layer or category rules.
3. Create or reference the model. Build foundation and floor elements from approved information rather than from unverified assumptions.
4. Generate documentation. Produce plans, sections, schedules, details and notes at suitable scales.
5. Coordinate. Compare structural, architectural, civil and services information.
6. Check. Review geometry, dimensions, levels, materials, annotations, constructability and compliance with project requirements.
7. Issue and record. Publish approved information through the common data environment and archive superseded versions.
8. Revise under control. Record the reason, author, date, status and effect of each change.

Figure: A controlled digital workflow for foundation and floor documentation.

The workflow is iterative rather than strictly linear. A clash may require a design change; a revised survey may require model adjustment; and a constructability review may require a new detail. The important principle is that every change is traceable and coordinated.

3. CAD standards for foundation and floor drawings

Units and precision

Project units must be set before drafting begins. Civil and structural drawings commonly use millimetres for building dimensions, while survey data may use metres. Confusing these units can create a scale error of 1,000 to 1. A drawing should state units where they are not obvious, and dimensions should not be silently converted without checking the source data.

Precision should reflect construction requirements. Excessive decimal places imply accuracy that may not exist, while insufficient precision can obscure a required tolerance. Survey control, design dimensions and construction tolerances should be distinguished.

Layers

Layers organise visibility, line appearance and editing. A useful layer system separates both discipline and function. For example:

Layer names should be documented in a project standard. Colours and lineweights should support hierarchy rather than aesthetic preference. For example, a cut foundation element may have a heavier line than an overhead service. Layer states can be saved for foundation plans, slab plans, setting-out plans and coordination views.

A layer is not a substitute for a correct object or category. Hiding a layer can conceal a design problem, so visibility controls must be used for communication and not to avoid checking.

Templates and reusable content

A template should contain approved page sizes, title blocks, units, text styles, dimension styles, line types, layers, plotting settings, view scales and standard notes. Reusable blocks or families may include footing tags, section markers, column symbols, pit symbols, slab edge details and benchmark symbols.

Templates improve consistency, reduce setup time and lower the likelihood of omissions. They must nevertheless be reviewed when standards, legislation, client requirements or software versions change. An outdated template can reproduce the same error across many projects.

External references

External references allow a drawing to display another file without permanently copying its content. Architectural, survey and services backgrounds can therefore be updated independently. Reference paths must be managed carefully, and the issued drawing must record the referenced file and revision. Before issuing, the draftsman should verify that references are present, correctly positioned, correctly scaled and not accidentally unloaded.

4. Foundation and flooring documentation in BIM

Levels, grids and coordinates

A BIM project should establish shared levels and grids before modelling major elements. Foundation depth, finished floor level, structural slab level and external ground levels must be clearly distinguished. A local project origin may support efficient modelling, while survey coordinates provide the relationship to the real site. Excessively large coordinate values can cause display or numerical problems in some software; the project team should therefore follow the agreed coordinate strategy.

Foundation objects

Common foundation objects include strip footings, pad footings, ground beams, pile caps, piles, retaining walls and foundation slabs. Each should have appropriate geometric and non-geometric properties. For example, a pad footing may include length, width, depth, material, reference mark, level and construction phase. The model must not imply design information that has not been provided by the responsible engineer.

A draftsman should distinguish between:

• design intent, such as the required footing location and dimensions;
• documentation geometry, such as symbolic representation in a plan; and
• construction information, such as reinforcement, joints, laps and tolerances.

These are related but are not interchangeable.

Floor objects

Floor documentation may include ground-bearing slabs, suspended slabs, screeds, membranes, insulation, finishes, falls, movement joints and penetrations. Layered construction should be represented consistently. A floor finish may be modelled as a separate layer or documented through a finish schedule, depending on the project’s information requirements.

Floor plans should identify changes in level, steps, ramps, drains, falls, thresholds and penetrations. Sections are essential where a plan cannot communicate vertical relationships, such as the connection between a slab, damp-proof membrane, footing and external paving.

Parametric objects

A parametric object changes its geometry or properties when parameters are edited. A footing family might use width, length and depth parameters; a floor type might use a layer assembly and thickness. Parameters can be:

• instance parameters, which vary for one object;
• type parameters, which affect every object of a selected type; and
• shared parameters, which allow consistent scheduling or exchange between models.

Parametric modelling improves consistency, but it introduces risks. A type change may alter many elements unintentionally. A family with incorrect reference planes, units or material assignments can generate apparently plausible but wrong results. Every custom object should be tested in plan, elevation, section, schedule and export views before use.

5. Model checking and documentation quality

Model checking combines automated tests with professional review. Automated checks can identify missing values, duplicate elements, elements outside the intended level, unconnected walls, inconsistent types, invalid geometries and clashes. Human review remains necessary because software cannot reliably judge design intent, buildability, clarity or contractual responsibility.

A practical checking sequence is:

1. File check: confirm file name, revision, units, coordinate system and linked references.
2. Geometric check: inspect alignment, offsets, levels, thicknesses, openings and intersections.
3. Information check: confirm material, type, identification, phase and classification fields.
4. Documentation check: verify dimensions, tags, notes, symbols, scales, title blocks and sheet references.
5. Coordination check: compare the model with other disciplines and with survey information.
6. Issue check: confirm that only approved and required information is visible and issued.

The model should be checked at several scales. A zoomed-out view reveals grid and overall alignment problems; a detailed view reveals gaps, overlaps and incorrect junctions. Sections often reveal vertical errors that are invisible in plan.

Basic clash detection

A clash occurs when elements conflict in a way that may prevent construction, maintenance or intended operation. Examples include a service pipe passing through a footing, a drain crossing a beam, a pile cap overlapping an underground tank, or a stair opening conflicting with reinforcement zones.

Clashes may be classified as:

• hard clash: two physical geometries occupy the same space;
• clearance clash: elements do not intersect but required access or clearance is insufficient; and
• workflow or time-based clash: elements may be geometrically compatible but cannot be installed in the required sequence.

A basic clash process includes selecting model sets, defining tolerances and rules, running the test, grouping related results, assigning responsibility and recording status. Every detected issue is not necessarily a design error. A pipe intentionally passing through a sleeve may be an approved condition, while a pipe passing through a footing without a designed penetration is not.

A clash report should identify the location, involved elements, viewpoints, responsible party, priority, proposed action, due date and status. Typical statuses are open, assigned, in progress, resolved, rejected or approved deviation.

6. Common data environments and version control

A common data environment (CDE) is an agreed system for collecting, managing, reviewing and distributing project information. It may be cloud-based or hosted on an organisation’s controlled server. The CDE is more than a folder: it includes permissions, metadata, review processes, revision records and an agreed status system.

A useful information state structure is:

• Work in Progress (WIP): information being developed by its authoring team;
• Shared: information made available for coordination or review;
• Published or Issued: approved information for a defined purpose;
• Archived: superseded or historical information retained for record.

File names should be predictable. A project standard may combine project code, originator, volume or system, level or location, type, role, number and revision. The exact convention varies, but names should be unique, readable and documented.

Version control prevents people from constructing from obsolete information. Each issue should communicate at least the revision, date, status, author or originator, description of change and approval or checking record. Never overwrite an issued file without preserving its previous state. A revision cloud or change description should identify material changes, but minor graphical corrections should not be falsely presented as design changes.

Access control is also important. Users should have permissions appropriate to their role, and sensitive project information should not be copied to uncontrolled personal storage. A CDE should support backups, audit trails and recovery from accidental deletion or corruption.

7. Digital surveying and model integration

Digital surveying may use total stations, GNSS equipment, laser scanning, photogrammetry or mobile mapping. These methods can produce point files, coordinate lists, digital terrain models, registered point clouds and orthographic imagery.

The draftsman must understand the difference between:

• accuracy: closeness to the true or accepted value;
• precision: repeatability of measurements;
• resolution: level of detail captured; and
• registration: alignment of separate scans or datasets into one coordinate framework.

Survey data should be checked for coordinate system, datum, units, control points, coverage, date and stated accuracy. A point cloud may appear detailed while still being incorrectly georeferenced. Existing structures can move, be obscured or be misidentified; digital capture does not remove the need for professional interpretation.

A suitable integration procedure is to import survey control, verify known benchmarks, align the model, compare selected dimensions and document deviations. Survey-derived existing conditions should be clearly distinguished from proposed design elements. If a building is renovated, a scan-to-BIM workflow may convert captured geometry into modelled walls, slabs, columns and services. The conversion level should match the intended use; modelling every irregularity is rarely efficient or necessary.

8. Applied case: foundation coordination for a small community hall

The following is an illustrative case, not a report of a specific real project.

Background

A single-storey community hall was being documented using an architectural BIM model, a structural foundation model and a civil site model. The proposed building had a ground-bearing slab, perimeter strip footings, internal thickened beams, accessible ramps and underground stormwater drainage.

Problem

During coordination, the civil model showed a stormwater pipe crossing the location of an internal thickened beam. The architectural floor plan showed a ramp threshold at a level that did not match the proposed external paving. In addition, the structural model used a different grid origin from the architectural model, causing apparent offsets.

Analysis

The team first checked whether the coordinate difference was a true design discrepancy or merely a shared-coordinate error. A known grid intersection and two survey control points were compared. The structural model was then transformed according to the approved project coordinate strategy. The pipe-to-beam intersection was classified as a hard clash, not a permitted sleeve, because no penetration detail had been designed.

The ramp issue was investigated in section. The finished floor level, threshold, ramp gradient and external level were reviewed together. This demonstrated that the plan alone had hidden a vertical incompatibility.

Approach and solution

The team recorded each issue in the CDE with a viewpoint, responsible discipline and proposed action. The civil designer rerouted the pipe around the beam while maintaining access for maintenance. The structural engineer confirmed the revised beam geometry. The architect adjusted the threshold and paving levels, and the draftsman updated the plan, section, level markers and schedule.

Before publication, the model was checked for residual clashes, correct references, consistent revisions and updated dimensions. The previous issue was archived rather than overwritten.

Outcome

The coordinated issue avoided an unplanned site penetration and reduced the risk of an inaccessible threshold. More importantly, the team established a repeatable procedure for coordinate checking, clash assignment and revision control.

Learning points

• A coordinate discrepancy must be investigated before elements are manually moved.
• Vertical coordination is as important as plan coordination.
• A clash report is useful only when responsibility and status are recorded.
• Model changes must flow into drawings, schedules and details.
• Approved information must be issued through the CDE, not through informal file exchange.

9. Professional, ethical and regulatory considerations

Digital models can create a false impression of certainty. A clean three-dimensional view does not prove that the foundation is structurally adequate, that soil conditions are suitable or that dimensions comply with regulations. Draftsmen must work within their competence and must not alter engineering design without authorisation.

Responsibilities include using current approved information, preserving design intent, reporting suspected errors, protecting confidential data and maintaining an auditable record. Model ownership and liability should be addressed in project agreements. The author of a model element may not be the person responsible for its engineering adequacy; roles must therefore be explicit.

Relevant requirements may include building regulations, accessibility provisions, structural standards, surveying standards, client information requirements and organisational CAD/BIM protocols. The exact requirements depend on jurisdiction and project type. Software checks never replace compliance review by appropriately qualified professionals.

AI-assisted drafting and automated model generation are emerging technologies. They may help classify point clouds, detect repeated objects, suggest annotations or identify possible clashes. However, generated content can contain omissions, hallucinated properties, incorrect units or inappropriate assumptions. AI outputs must be treated as unverified assistance. A competent professional remains responsible for checking geometry, sources, permissions, confidentiality and final decisions.

10. Best-practice checklist

Before starting:

• confirm the latest brief, survey and engineering information;
• establish units, levels, coordinates and naming conventions;
• use the approved template and project library;
• confirm the CDE, permissions and issue procedure.

During production:

• model only information supported by approved sources;
• use consistent layers, categories, types and parameters;
• distinguish existing, proposed and demolished work;
• coordinate plans with sections, details and schedules;
• keep temporary construction aids separate from issued information.

Before issue:

• inspect geometry, levels, dimensions and annotations;
• run discipline and interdisciplinary clash checks;
• verify linked files and coordinate alignment;
• check title blocks, revision, status and approval records;
• publish through the CDE and archive the superseded issue.

Contemporary developments

Contemporary practice increasingly uses cloud collaboration, open exchange formats, automated checking, mobile field verification, reality capture and digital twins. Open standards can improve interoperability between software platforms, although exchange may lose object properties or relationships. Cloud models support distributed teams but require dependable connectivity, access management and clear ownership of synchronisation.

Digital twins extend BIM by connecting an information model to operational data, sensors or maintenance records. For a foundation or floor, this might include inspection history, moisture monitoring, settlement observations or repair records. Such applications are valuable only when data quality, update responsibility and long-term storage are defined.

The fundamental professional skill remains disciplined information management. New technology improves speed and visibility, but it does not replace engineering judgement, surveying control, communication or accountability.

Chapter Summary

CAD provides precise graphical documentation, while BIM connects foundation and flooring geometry with structured information and relationships. Effective digital practice begins with reliable inputs, agreed units, coordinates, levels, templates, layers and naming conventions. Foundation and floor elements should be modelled with suitable parameters, without implying design information that has not been approved.

A complete workflow includes modelling, drawing production, interdisciplinary coordination, checking, controlled issue and revision. Model checking combines automated tests with human review. Clash detection identifies hard, clearance and workflow conflicts, but each result requires professional interpretation. Digital survey data must be checked for datum, units, registration, accuracy and suitability before integration.

A common data environment provides controlled information states, permissions, audit trails and revision history. Ethical practice requires competence, transparency, protection of confidential information and recognition that software and AI cannot replace responsible professional judgement.

Key Terms

CAD: Computer-aided design used to create and modify digital drawings.

BIM: Building information modelling using information-rich objects and coordinated relationships.

Parametric object: A digital object whose geometry or properties respond to defined parameters.

Instance parameter: A parameter that affects one selected object.

Type parameter: A parameter shared by all objects of a selected type.

Template: A prepared project file containing standard settings and content.

Layer: A CAD organisational system controlling visibility and graphical properties.

External reference: A linked file displayed in a host drawing without being permanently copied into it.

Coordinate system: A defined method for locating information spatially.

Level: A defined horizontal elevation used to organise building elements.

Common data environment: A controlled system for managing, reviewing and distributing project information.

Work in Progress: Information being developed and not yet shared for formal coordination.

Published information: Approved information issued for a stated purpose.

Version control: The process of identifying, recording and managing successive information issues.

Point cloud: A collection of spatial points captured by scanning or surveying equipment.

Registration: Alignment of separate survey or scan datasets into a common coordinate framework.

Hard clash: Physical intersection between two modelled elements.

Clearance clash: Failure to provide required space even when elements do not intersect.

Federated model: A coordinated collection of discipline models that remain separately authored.

Digital twin: An information representation connected to data about a physical asset or process.

Review Questions

Short Answer Questions

1. What is the principal difference between a CAD drawing and a BIM model?
2. Why should units and coordinate systems be established before modelling?
3. Distinguish between an instance parameter and a type parameter.
4. What information should be included in a clash report?
5. Name the typical information states in a common data environment.

Long Answer Questions

1. Explain how layers, templates, external references and plotting standards improve foundation drawing production.
2. Describe a complete workflow for producing and issuing coordinated foundation and floor documentation.
3. Explain the role of levels, grids and coordinates in integrating architectural, structural and survey information.
4. Discuss the benefits and limitations of parametric objects in BIM-based drafting.
5. Explain how version control and a common data environment reduce construction risk.

Analytical / Application Questions

1. A stormwater pipe passes through a proposed strip footing. Describe the checks, coordination actions and records required before the drawing is issued.
2. A point cloud appears correctly aligned in plan but differs from known site benchmarks. Analyse possible causes and propose a verification procedure.
3. A revised footing type has unexpectedly changed many foundations in the model. Explain how this could occur and develop a safe correction and checking process.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes BIM from conventional CAD?

A. BIM uses only two-dimensional linework

B. BIM connects modelled elements with structured information and relationships

C. BIM eliminates the need for drawings

D. BIM is used only for architectural visualisation

Correct Answer: B. BIM connects modelled elements with structured information and relationships

Question 2

What is the primary purpose of a CAD template?

A. To conceal uncoordinated information

B. To replace all professional checking

C. To provide approved standard settings and reusable content

D. To automatically design a foundation

Correct Answer: C. To provide approved standard settings and reusable content

Question 3

Which item is most appropriately separated into a non-plotting guide layer?

A. Issued footing outline

B. Structural slab edge

C. Temporary construction guide

D. Required foundation dimension

Correct Answer: C. Temporary construction guide

Question 4

A parameter that changes every object belonging to a selected footing type is generally a:

A. Type parameter

B. View annotation

C. Survey benchmark

D. Revision cloud

Correct Answer: A. Type parameter

Question 5

A pipe physically intersecting a footing is an example of a:

A. Clearance-only clash

B. Hard clash

C. Naming convention

D. Coordinate datum

Correct Answer: B. Hard clash

Question 6

Which CDE state normally contains information approved for a defined purpose?

A. Work in Progress

B. Temporary

C. Published or Issued

D. Unreferenced

Correct Answer: C. Published or Issued

Question 7

Before importing survey data into a project model, which item should be verified first?

A. The drawing colour palette

B. The coordinate system, datum and units

C. The number of title-block logos

D. The rendering brightness

Correct Answer: B. The coordinate system, datum and units

Question 8

What is registration in digital surveying?

A. Assigning a drawing revision letter

B. Aligning separate datasets into a common coordinate framework

C. Deleting duplicate annotations

D. Changing a floor finish type

Correct Answer: B. Aligning separate datasets into a common coordinate framework

Question 9

Why is section coordination important for floor documentation?

A. Sections show vertical relationships that plans may hide

B. Sections remove the need for levels

C. Sections automatically verify structural adequacy

D. Sections are used only for presentation images

Correct Answer: A. Sections show vertical relationships that plans may hide

Question 10

Which action best demonstrates responsible use of AI-assisted drafting?

A. Issuing generated geometry without review

B. Treating generated properties as automatically correct

C. Checking AI outputs against approved information and professional requirements

D. Allowing AI to change engineering design without authorisation

Correct Answer: C. Checking AI outputs against approved information and professional requirements