Choose one mark-up tool and file format

Pick the tool the team will use and write down the version. A PDF mark-up in a shared viewer is different from a takeoff file inside a specialty application, and mixing the two creates duplicate marks. Name the file format the team must return, such as the original PDF with a separate annotation layer.

The reviewer should be able to open the file without installing an unfamiliar tool. Keep the source drawing unchanged and put every mark on a new layer or in a separate copy. That rule protects the issued drawing and makes the mark-up removable.

It also lets a reviewer compare the clean sheet with the marked sheet. If the tool cannot preserve layers, use a clearly named copy and record the original file name in the takeoff log. Decide how the team will show text, leaders, and dimension marks before the project starts.

A standard that covers only color misses the labels that make a mark readable. The takeoff specialist page describes the support model this standard supports, and the task brief guide shows where to record the rules. The AACE recommended practices treat a documented estimate basis as part of the estimate, and a mark-up standard is part of that basis.

Keep the standard to one page and store it beside the bid folder. A long manual is opened once and then ignored, while a one-page card can be pinned beside the screen.

Include a small sample of each mark so the team can copy the look without interpreting a description. The sample is often the part people use most.

Assign meaning to each color

Limit the palette to four or five colors and give each one a single meaning. A common scheme uses red for scope included in this takeoff, blue for scope excluded or by others, yellow for a question, and green for a verified check. Write the legend on the first sheet of every mark-up packet.

A color that means two things will be misread by the second reviewer. Avoid colors that disappear on a grayscale print or a dark background. Test the palette on a black-and-white copy of a drawing before the team uses it.

If the drawing set contains colored architectural finishes, choose mark-up colors that contrast with the background rather than blending into it. Legibility matters more than a fashionable palette. Use line weight and dash pattern as a second signal, not as a replacement for color.

A dashed line can mean a dimension taken from a grid, while a solid line can mean a field measurement. Record both conventions in the legend. That redundancy helps a reviewer who prints the sheet and loses the color.

Standardize symbols and labels

Define the symbols for a counted item, a linear measurement, an area, and a deduction. A door count and a door deduction should not use the same mark. Add a short label with the item code and the quantity beside each symbol.

The label lets a reviewer audit a count without tracing every mark on the sheet. Use the same item code that appears in the estimate workbook. If the workbook calls a line HM-01, the mark-up should not call it hollow metal 1.

That shared code is the difference between a mark-up that can be reconciled and one that has to be translated. Put the code list beside the color legend so the team works from one reference. Place labels outside the room or assembly where possible.

A label written over a door swing or a dimension string hides the evidence the reviewer needs. Use a leader line to a clear area when space is tight. Consistent placement makes a stack of marked sheets easier to scan.

Handle revisions with one cloud convention

Mark revised work with a revision cloud and the addendum or revision number. Do not erase the original mark, because the reviewer may need to see what changed. If a quantity was removed, strike it through and add the replacement beside it.

The mark-up should tell the story of the revision without a separate explanation. Keep one revision log that lists the sheet, the change, the date, and the person who made the mark. The log and the cloud should agree.

A cloud without a log entry is hard to audit, and a log entry without a cloud is hard to find on the drawing. Both take less than a minute per change. When a sheet is replaced, copy the old marks forward only after checking the new sheet against the old one.

A replacement sheet can shift a detail or remove a note that the mark depended on. Carry forward the quantity only when the geometry still matches. Otherwise treat the item as a new measurement and record why the old mark was retired.

Check the standard before the first batch

Run a one-sheet test before the team starts the full takeoff. Ask each person to mark the same small area and compare the results. Look for differences in color, label placement, line weight, and deduction treatment.

Correct the standard once, then use the corrected version for the batch. The test is faster than fixing fifty sheets later. Add the test result and the standard version to the bid file.

When a new person joins, give them the same test before they touch a live sheet. A standard that only lives in a training session fades quickly. A written version with a short test keeps the team aligned across bids and staff changes.

Mark-up standard elements
ElementRule to write downWhy it matters
Tool and formatOne viewer, one return format, original preservedPrevents duplicate or unreadable marks
Color legendFour or five colors, one meaning eachStops scope and questions from blending
Item codeSame code as the estimate workbookMakes the takeoff reconcilable
Revision cloudCloud plus addendum number and log entryKeeps changes auditable

Frequently Asked Questions

Should the mark-up standard be the same on every project?

Keep the core color and label rules the same, then add project-specific symbols in a clearly marked section. A stable core helps new team members and reviewers, while a project section handles unusual scope. Do not rewrite the whole standard for each bid.

Can the team use a different PDF tool?

Only if the tool preserves the annotation layer and returns a file the reviewer can open. Test the round trip before the batch starts. If the tool flattens the marks or changes the sheet size, choose a different tool or require a separate marked copy.

How often should the standard be reviewed?

Review it after each bid where a mark-up caused a question or a rework. Update the version and note the change. A yearly review is enough when the team and the tool set are stable, but a new client format may require a sooner update.

Construction EstimatingConstruction EstimatingCost Support