bannerd

Each PAT needs to have a simple structure that can be used by project teams. To ensure this reusability aspect, Assets will be created and saved as Word, Excel, or other editable format, not as a PDF. 

Each should have a simple minimalist structure for the user to embellish as they see fit. Specifically: 

Standardizing the template includes the following items:

  • No logos or other Header information in the template. If a project wants that, they can apply it themselves.
  • Header block with the following items at a minimum:
    • Dates of use (example Audit Dates)
    • Project
    • User name (example: Auditors) – people filling out or using the template in the project
    • Some indicator for the version of the template. This can be version number or version date
  • Usage instructions – minimal instructions for the user when filling out / using the template
  • Table of checklist items, steps, or other list items with some form of
    • Col 1 - numbering system for the checklist
    • Col 2 - instruction or item 
    • Col 3 - acknowledgement of use (example Yes/No)
    • Col 4 - Comment area
    • Col 5 - Initials of the user (optional)
  • Other customizations are optional such as:
    • Heading styles
    • Colorizing table areas
    • Addition of summary or comment areas
  • Naming PAT item preparing it for attachment to individual PAT pages. examples
    • PAT-001 - FCA Checklist
    • PAT-002 - PCA Checklist
  • Each attachment is affixed to the appropriate PAT page
  • PAT pages are children of the PAT Database page under SITE:Home page
  • See "Add a New Pat" for instructions on building a PAT page. 
  • No labels