Neat Writing Prevents Project Mistakes

First Published:

Last Updated:

Have you ever passed a marked-up drawing around the office, asking people to help you read one handwritten comment?

Someone thinks it says “remove”. Someone else thinks it says “review”. The person who wrote it is unavailable, and the designer needs an answer before continuing.

A comment that took seconds to scribble has now interrupted several people’s work. And you still don’t know what it says.

Problem: Messy Writing Wastes Time and Causes Mistakes

Neat writing matters whenever someone else needs to use your notes. That includes drawing markups, site records, inspection sheets and handwritten comments on reports.

If the reader cannot make out a word, they have to stop and ask. If they think they can make it out, they may carry on with the wrong instruction. That second outcome can be much worse.

A poorly written dimension might be read as 150 instead of 750. An unclear comment could lead to the wrong item being ordered or work being changed unnecessarily. Depending on the instruction, the consequences could include rework, delays or a safety issue.

Writing quickly may save the writer a little time, but it transfers the effort to everyone who has to read it. Scanning the page and emailing it to ten people does not make the handwriting any clearer.

Solution: Make Your Notes Easy for Others to Read

Set the expectation and lead by example

Tell your team that comments and instructions must be legible to the people using them. As project manager, apply the same standard to your own writing.

Write large enough to read, leave space between comments and make numbers and units clear. On drawings, show exactly which item each comment refers to. Use a separate numbered comment list if the available space is too small.

Explain who uses the document and why. Someone marking up a drawing should understand that another person may need to act on those notes without being able to ask them questions.

Return unclear writing for clarification

If you receive correspondence or a drawing with writing you cannot read, return it to the writer. Ask them to resubmit the unclear comments either typed or written clearly.

Be specific and polite: “I cannot read comments 3 and 5. Please clarify them before we update the drawing.”

Don’t guess or quietly rewrite what you think they meant. If you clarify something by phone, record the agreed wording and get the writer to confirm it in an email or similar permanent record. Make sure the people using the original notes receive the clarification too.

Use electronic comments where practical

Typed comments remove the difficulty of deciphering handwriting. For example, Adobe’s guide to annotating PDFs explains how to add text boxes, notes and other markups.

If someone regularly struggles with handwriting, agree that they will type their comments. Provide access to the necessary software and show them how to use it. The team needs a practical way to meet the standard.

However, some people still prefer reviewing a physical document. A senior manager may ask you to bring a printed report so they can write comments on it. Read through those comments with them before leaving, while they can explain anything unclear.

Scan the marked-up document, check that every comment is readable and store it in your project document system. Keep any confirmed clarifications with that record. A faint or cropped scan can make even neat writing difficult to use.

Lesson: Write So Other People Can Use Your Notes

Treat legible writing as a basic project communication requirement. Set the expectation, lead by example and ask people to correct unclear notes before anyone acts on them.

Spending a little longer writing a clear comment is worthwhile if it saves several people from stopping work, chasing an explanation or correcting a preventable mistake.

Leave a comment