Project Scoping, Planning & Safety Review — Drafting / CAD / BIM

Objective. Given a written project brief for a manufacturing component or marine structure, the student will produce a fully approved project plan — including scope statement, deliverables list, software assignments, milestone schedule, and file management protocol — that the instructor signs off before production work begins.

Why Project Scoping Comes First

Every successful drafting, CAD, or BIM project begins long before the first line is drawn. Scoping is the process of defining exactly what you will produce, what tools you will use, and what limits you must work within. Without a signed-off scope statement, teams waste hours drawing the wrong views, using the wrong software, or missing a code requirement that forces a complete redo. In this capstone, your scope statement is a gate: production work cannot begin until your instructor approves it.

A scope statement answers four questions: What are the deliverables? What software will produce each one? What constraints apply — scale, sector standard, sheet size, file format? What is explicitly out of scope? Keeping the last question in mind is just as important as the first three. If your brief asks for a 2D deck plan and a 3D hull model, a rendered marketing image is out of scope unless stated. Documenting what you will not do prevents scope creep, which is the most common reason student projects run over time.

Reading and Annotating a Project Brief

A project brief is the client's written description of their need. In industry it may be called a statement of work, a design request, or a project initiation document. When you receive a brief, read it twice before writing anything.

On the first read, highlight every noun that could be a deliverable: drawings, models, schedules, bills of materials, title blocks. On the second read, circle every constraint: tolerances, material callouts, applicable standards (ASME Y14.5 for GD&T in manufacturing; ABYC standards for recreational marine electrical and structural work), scale requirements, and required file formats. If a term is unfamiliar, look it up in the reference sheets provided before writing your scope statement.

For a manufacturing brief you might see references to ASME drawing standards, machined-part tolerances, and SolidWorks file deliverables. For a marine brief you may see references to ABYC guidelines, hull lines conventions, and AutoCAD or Revit deliverables. Note which standards apply — you will list them in your scope statement under "constraints."

Writing the Scope Statement

Your one-page scope statement must contain five sections:

1. Project summary — two or three sentences describing the component or structure.

2. Deliverables list — each drawing, model, or document you will produce, with software assigned to each (AutoCAD, Revit, SolidWorks, etc.).

3. Constraints — scale, sheet sizes, applicable standards, sector (manufacturing or marine), file-naming convention, and any client-stated limits.

4. Out of scope — anything the brief does not require that someone might assume is included.

5. Acceptance criteria — how the instructor or simulated client will judge that each deliverable is complete.

Keep language specific. "Two orthographic views" is better than "some drawings." "SolidWorks part file (.SLDPRT) and neutral STEP export" is better than "3D file."

Building the Milestone Schedule

Once the scope is approved, break the 142 remaining production hours into named phases on a Gantt chart. A Gantt chart shows tasks as horizontal bars plotted against a calendar. Each bar's left edge is the start date; the right edge is the end date. Tasks that must finish before another can start are called dependencies.

Typical capstone phases include: research and reference gathering, 2D layout and sketching, 3D modeling or BIM authoring, annotation and dimensioning, title block and sheet setup, peer review, revisions, and final submission. Assign realistic hour estimates to each phase. If annotation always takes you longer than modeling, budget accordingly. Your schedule becomes your contract with yourself and your instructor.

Use MS Project, Google Sheets with a Gantt template, or any equivalent tool your instructor approves. The tool matters less than the habit of tracking planned versus actual progress each week.

File Management Protocol

Every file you create must follow the program's file-naming and folder-structure standard issued by your instructor. A typical convention looks like: `[ProjectCode]_[Discipline]_[Description]_[Revision].ext` — for example, `CP01_MFGR_Baseplate_Rev01.SLDPRT`. Consistent naming means any team member (or your future employer) can find any file without asking you. Create your folder structure before you save a single working file.

Safety Review for the Drafting Lab

Before production work begins, every student completes a pre-project safety checklist. The drafting lab is a lower-hazard environment than a machine shop, but real hazards exist.

Ergonomics: Adjust your chair so your feet rest flat and your forearms are parallel to the floor. Position monitors at arm's length with the top of the screen at or slightly below eye level. Take brief breaks to reduce repetitive-strain risk during long CAD sessions.

Electrical safety near plotters and large-format printers: These machines draw significant current. Never reach into a plotter while it is powered. Report damaged power cords immediately. Keep liquids away from all electrical equipment.

Lockout/Tagout (LOTO) awareness: If your program provides access to CNC routers, laser cutters, or other fabrication equipment for prototype output, OSHA's lockout/tagout standard requires that energy sources be isolated and locked before any maintenance or clearing of jams. As a CAD student you are unlikely to perform LOTO yourself, but you must know: never attempt to clear a jam or open a guard on powered fabrication equipment. Alert the instructor or a qualified technician. Understanding LOTO protects you and your classmates.

OSHA 10 General Industry awareness covers hazard recognition, fall protection, electrical safety, and PPE — all relevant even in an office-adjacent drafting lab. Your completed safety checklist must have no unanswered items before your instructor will sign off your project plan.

The Gate Check

Three documents must receive instructor approval before you move to Lesson 2: the scope statement, the safety checklist, and the Gantt schedule. All three must be approved — there is no partial credit on this gate check. This mirrors real industry practice, where a project kickoff meeting ends with written sign-off before any billable production hours are charged.

Key terms9

Scope statementA written document that defines a project's deliverables, software assignments, constraints, out-of-scope items, and acceptance criteria, serving as the baseline agreement before production begins.

DeliverableAny specific output — drawing, model, document, or file — that must be produced and handed off to satisfy the project brief.

ConstraintA limit imposed on the project by the client, a code, or a standard — such as required scale, sheet size, file format, or applicable sector standard.

Scope creepThe gradual expansion of a project beyond its agreed boundaries, usually caused by adding work that was never in the original scope, leading to missed deadlines and wasted effort.

Gantt chartA bar chart that represents project tasks as horizontal bars plotted against a calendar, showing start dates, end dates, and dependencies between tasks.

DependencyA scheduling relationship in which one task cannot begin until a preceding task is complete; for example, annotation cannot start before geometry is finalized.

Lockout/Tagout (LOTO)An OSHA-required safety procedure that isolates and locks hazardous energy sources on equipment before maintenance or jam-clearing, preventing accidental startup or energy release.

File-naming conventionA standardized pattern for naming digital files — typically including project code, discipline, description, and revision number — so that files can be located and version-tracked without confusion.

Gate checkA formal approval point at which specific documents must be accepted by an authority (instructor or client) before the next phase of work may begin; used in this capstone for scope statement, safety checklist, and schedule.

In class: Read and annotate two sample project briefs (one manufacturing, one marine), then select or receive an assigned brief and write a one-page scope statement identifying deliverables, software tools, and constraints such as scale, code references, and sector standards. · Complete a pre-project safety checklist covering OSHA 10 general industry awareness items relevant to the drafting lab environment — including ergonomic workstation setup, electrical safety near plotters and large-format printers, and lockout/tagout awareness for any CNC or fabrication equipment accessible during the project — then discuss findings in a small-group debrief. · Build a project milestone schedule using a Gantt-style planning tool (MS Project student edition, Google Sheets, or equivalent), breaking the 142 remaining production hours into named phases with due dates, and present the draft schedule to the instructor for approval before moving to Lesson 2.
Materials: Assigned project brief documents; OSHA 10 General Industry awareness card or equivalent reference; Gantt chart template (digital); program file-naming and folder-structure standard issued by instructor; Autodesk, Dassault Systèmes, and ABYC/ASME reference sheets as applicable to the chosen brief
Check: Instructor sign-off on scope statement (all required deliverables identified), safety checklist submitted with no unanswered items, and Gantt schedule approved — all three must be approved before student advances; no partial credit on gate check.

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.