Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

How to classify what type of messages should've a fullstop/period and what should not?

Because there are certain error/warning/success/info messages (be it a dialog, banner, contextual or ones in a separate page that appears between a workflow) that needs to be framed in two or more sentences that obviously requires a full stop.

MS Windows generally in their alert dialogs have two parts - an alert message coupled with an informative message. The alert message will be succinct and in a single sentence that won't have a fullstop. But the informative message will have at its end.

share|improve this question
Use exclamation marks, all the time!!! –  DesignerGuy Mar 14 '12 at 6:58
lol@DesignerGuy !!! Also use superfluous spaces !!! –  Bart Gijssens Mar 14 '12 at 9:02
I asked a similar question on English.SE and got beat up for it for reasons I still don't understand. english.stackexchange.com/questions/37659/… –  I. J. Kennedy Aug 25 '13 at 5:29

4 Answers 4

The only place where you don't use a full stop is in titles (such as in the title bar of a window). In all other cases, you need proper punctuation.

Compare it to a book: the title of the book does not end with a period, all sentences inside do end with punctuation. Except the titles of the chapters, which are titles again. I remember in elementary school putting a period at the end of the title of your paper was considered an error by the teacher, resulting in a lower grade.

You are stating: "MS Windows generally in their alert dialogs have two parts - an alert message coupled with an informative message."

Could you please post a screenshot of such a message? I cannot think of any example to be honest...

Update: taking into account krishnajay's comment, this should be the correct answer:

enter image description here

share|improve this answer
Refer msdn.microsoft.com/en-us/library/windows/desktop/aa511267.aspx for windows messages –  krishnajay Mar 14 '12 at 18:45
Here is the rule... //Don't include final periods if the instruction is a statement. If the instruction is a question, include a final question mark.// –  krishnajay Mar 14 '12 at 18:48
@krishnajay: what is your source? Do you have a reference for that? –  Bart Gijssens Mar 15 '12 at 6:51
You are right. Mind that this is only for the "main instruction", not for the "supplemental instructions". Most of the time, when using standard messageboxes, there is not main instruction. –  Bart Gijssens Mar 15 '12 at 6:57
So does it mean all messages should've a main instruction and it shouldn't be in multiple sentences. If there is a need for multiple sentences, is it supposed to be split? Moreover does it apply for contextual messages such as the ones displayed below the input fields –  krishnajay Mar 15 '12 at 7:26

If it's a proper sentence, give it proper punctuation.

share|improve this answer

Though Bart was pretty spot on with his answer,here are some guidelines given by MSDN with regards to Error and Informational messages. To quote them:

  • Identify the problem, indicate the cause if helpful, and provide a solution if possible.
  • Write phrases instead of complete sentences to conserve space. For example, write "Save using a different name" instead of "Save this document using a different file name." Use title caps in the title bar of the message box and sentence caps in the message body text.
  • Title caps rules specify that all words are capitalized with the exception of articles, coordinating conjunctions (and, but, for, not, or, so, and yet), and prepositions containing four or fewer letters.
  • Sentence caps rules specify that only the first word and any proper nouns are capitalized.
  • Bold command names instead of using quotation marks.
  • When there may be a consequence of a user's action, preface the error message with the word "Warning." For example, write "Warning: If you synchronize now, duplicate items may appear in your Inbox."
  • Do not use exclamation points.
  • Do not write content that implies that applications can think or feel.
  • Avoid using the word please. Also, use the following alternative terms for abort, boot, and reboot.

Also if you go by the Error Messages guidelines for Windows,the only place where periods are supposed to be used is when

Don't include final periods if the instruction is a statement. If the instruction is a question, include a final question mark.

You might also want to see what MSDN recommends for Capitalization and Punctuation Guidelines

End punctuation (. ? !) : Use ending punctuation only in instructional text.

share|improve this answer
Yes I've gone through their guideline. But how about Apple? Do they follow a similar approach? –  krishnajay Mar 19 '12 at 11:10

This is what the Apple Human Interface Guidelines for iOS have to say about this:

If you must provide an optional alert message, write a short, complete sentence. If possible, keep the message short enough to be displayed on one or two lines. If the message is too long, it will scroll, giving users a poor experience. Use sentence-style capitalization and appropriate ending punctuation in the message.

Note that in all the screenshots in the HIG for both OSX and iOS, the explanation text is a sentence and ends with a period. See the appropriate section in the OSX HIG for amore examples.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.