use ANU Policy Header 2 style for this heading

advertisement
Title (use ANU Policy Title style for the
document title) Select all styles from the styles
toolbar (see below)
Purpose (use ANU Policy Header 2 style for this heading)
Use ANU Policy Statement Text for general body text, including spaces between paragraphs,
throughout the document.
This should be a short statement in the active voice, outlining the purpose of the document, for
example, what the document does
Overview (use ANU Policy Header 2 style for this heading)
Use ANU Policy Statement Text for general body text, including spaces between paragraphs,
throughout the document.
The overview should be a short paragraph or sentence explaining why the document has been
created, and its intention. It should also include any background information that provides
context to the policy, and definitions where necessary.
Scope (use ANU Policy Header 2 style for this heading)
Use ANU Policy Statement Text for general body text, including spaces between paragraphs,
throughout the document.
The scope is the audience to whom the document applies. If there are no exceptions identified,
the scope may be described in the following way: ‘This Policy applies to all ANU staff and
students across the University’.
Policy Statement (use ANU Policy Header 2 style for this
heading)
Use ANU Policy Statement Text for general body text, including spaces between paragraphs,
throughout the document.
This is the core section of the policy document that outlines the underlying principles that
constitute the policy. These policy statements should be short, concise and definite. Policies
are supported by procedures and guidelines.
Policies are mandatory across the University and should be written in a way that is easy to
understand by all staff and students. (See also: Writing Policy Documents—Guidelines.)
<insert document title>
.1.
9 February 2016
Template Tips!
Procedure and guideline templates have the same styles, and follow the same format, as the policy
template, but only include the Purpose and Statement sections.
Templates for policies, procedures and guidelines are available for download from the ANU Policy
website. Correct templates must be used to publish to the ANU Policy website. The templates have
been designed so they automatically convert to HTML for upload.
Using the incorrect template; no template, or changing the style (font or colour) within the template
means your document will not render correctly when published to the ANU Policy website.
Tip: if you cut and paste text into the template from an original document, you may need to change
the style to conform to the correct style in the template. Highlight the text and select the correct
style from the styles ribbon in the toolbar. Ensure all paragraph spacing is also in ANU Policy
Statement Text.
USING IMAGES IN TEMPLATES
Where possible, the use of images should be avoided in templates unless the image is an important
part of the process (policy or procedure) that cannot be referred to as a separate document. The term
‘Images’, in this instance, include: tables; PNG, JPEG, TIFF, or Bitmap images; Word objects, and
embedded metafiles.
Tables
Tables are unstable in templates and should only be used if they enhance, and are essential to, the
policy or procedure. Care must be taken that text and paragraph spacing immediately prior to, and
following the table, must be in the correct style and format. Text within the table must be in the correct
(publishable) style and font, and even then, perfect rendering following HTML conversion cannot be
guaranteed in published documents. Indented bullet points and dashes within tables exacerbate the
rendering problem, and if tables must be included in the document they should be restricted to plain
text, that is, no indents or bullet points or dashes. The policy practitioner should understand that use
of tables may seriously affect document conversion and rendering.
Images
All images should only be used if they enhance, and are essential to, the policy or procedure. PNG,
JPEG, TIFF or Bitmap images may be more stable than tables, Word objects, or embedded metafiles.
Care must be taken that all text and spacing immediately prior to, and following the image, must be in
the correct (publishable) style and format.
Word objects and embedded metafiles
These images should be avoided where possible. Publication of these images cannot be guaranteed
as they do not convert readily to HTML. The policy practitioner should understand that use of these
objects may seriously affect document conversion and rendering.
<insert document title>
2
Download