Formats and tools
- Unit Description
- Reconstruct the unit from the xml and display it as an HTML page.
- Assessment Tool
- an assessor resource that builds a framework for writing an assessment tool
- Assessment Template
- generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
- Assessment Matrix
- a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
- Wiki Markup
- mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
- Evidence Guide
- create an evidence guide for workplace assessment and RPL applicants
- Competency Mapping Template
- Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
- Observation Checklist
- create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)
- Self Assessment Survey
- A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
- Moodle Outcomes
- Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
- Registered Training Organisations
- Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver CPPBDN4007, 'Store and retrieve building design documentation'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Store and retrieve building design documentation' on fishpond.com.au. This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to ntisthis.com for every purchase, so go nuts :)
Elements and Performance Criteria
Elements describe the essential outcomes. | Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the range of conditions. | ||
1. | Maintain filing system. | 1.1. | Project file naming, storing, saving and version control systems are identified and followed when creating, amending and filing documents. |
1.2. | Hard copy and digital files are reviewed to identify and remove duplicate, outdated and unnecessary documentation, and archived as required. | ||
2. | Manage file requests. | 2.1. | Processes for actioning file requests are identified and followed. |
2.2. | File requests are assessed and confirmed according to workplace procedures. | ||
2.3. | Digital documents are made available to others with appropriate file protections in place according to workplace requirements. | ||
2.4. | Hard copy documents are retrieved, logged as removed from file, and provided to others, photocopied or scanned as necessary. | ||
2.5. | Hard copy files are regularly monitored for missing documentation and logging systems are used to locate and replace documentation. | ||
3. | Back up and archive project files. | 3.1. | Digital files are backed up periodically and stored in a safe and secure location for emergency access. |
3.2. | Hard copy files are collated, scanned where appropriate and saved to relevant electronic project files. | ||
3.3. | Files relating to finalised projects are archived in a safe, secure and accessible manner. | ||
3.4. | Processes allowing for access to archived project files are reviewed and implemented as required. | ||