Week 3

Document and Submit the Final Product

Use the Week 3 workbook to document the database, check the final product and prepare evidence for LMS submission.

Starting Workbook

Use this workbook as the model for documentation quality, final evidence tracking, common errors and LMS submission checks.

Documentation ExampleEvidence TrackerCommon ErrorsReadiness ChecklistSample Records
Download workbook

Learning Goals

  • Complete a data dictionary
  • Justify the primary key
  • Explain forms, queries and reports
  • Check the final product against the rubric
  • Prepare the evidence DOCX, Excel export and share link correctly

Lesson Sequence

1

Study the documentation example and draft your own database documentation.

2

Check the database foundation against the rubric.

3

Check query views and report views against the rubric.

4

Review common errors and complete the readiness checklist.

5

Submit the final evidence document, Excel export and Microsoft Lists share link.

Weekly Checkpoint

Be ready to submit the evidence DOCX, Excel export and Microsoft Lists share link. WA Day may reduce class time, so prioritise final evidence and LMS submission readiness.

Final LMS Submission

Submit A Complete Evidence Package

Upload the final product through the LMS. Attach the DOCX evidence document and Excel export, then paste the Microsoft Lists share link into the LMS submission comment box.

Evidence document

CSCGT_Task3_2026_Surname_FirstName_Evidence.docx

Completed documentation template with screenshots and short explanations in rubric order.

Data export

CSCGT_Task3_2026_Surname_FirstName_DataExport.xlsx

Microsoft List exported to Excel so fields, records, LoanID values and sample data can be checked efficiently.

Microsoft Lists share link

Paste into the LMS submissioncomment box

Shared with the teacher so forms, saved query views, report views and interface choices can be verified live.

Detailed Lesson Build Pathway

Lesson 1

Write database documentation

Explain the database structure and design decisions clearly enough for assessment evidence.

Documentation ExampleSample Records
  1. Download and open the Week 3 workbook.
  2. Read the Documentation Example sheet from top to bottom before writing your own.
  3. Write the database purpose and intended users: who uses it, what it stores and what decisions it supports.
  4. Complete a data dictionary for every field: field name, data type, example value, required status and purpose.
  5. Justify LoanID as the primary key equivalent. Explain that borrower names and item names can repeat, but each loan record needs one unique identifier.
  6. Describe the form: what fields appear, which fields are required and how the form supports accurate data entry.
  7. Describe each query and report view by naming the purpose, filter or sort, and how the output helps the user.
  8. Add limitations and improvements, such as manual LoanID checking if unique values are not available or limited automation in Microsoft Lists.

Evidence: A complete draft of database documentation matched to your actual list.

Lesson 2

Foundation evidence check

Check the database structure and sample records against the rubric before final evidence is captured.

Evidence TrackerSample RecordsReadiness Checklist
  1. Open your final Task 3 Equipment Loans list.
  2. Check the required columns and suitable column types against the readiness checklist.
  3. Check that LoanID values are unique and consistently formatted.
  4. Check that your records include returned, unreturned, overdue, Year 12 and damaged or follow-up examples.
  5. Check LoanID uniqueness, required fields, choice options, date columns and currency fields.
  6. Record missing evidence and corrections in the Evidence Tracker.

Evidence: A completed foundation evidence check showing errors found and corrections made.

Lesson 3

Views and reports evidence check

Check that saved query and report views answer the scenario and are ready for screenshots.

Evidence TrackerCommon Errors
  1. Open Current Loans, Overdue Loans, Year 12 Loans and Damaged or Follow Up views.
  2. Open Weekly Loan Summary and Replacement Cost Review report views.
  3. For each view, check two visible records and one hidden record to prove the filter is working.
  4. Fix any view that is just a copy of the full list.
  5. Capture final screenshots only after each view has been checked.
  6. Record any corrections in the Evidence Tracker.

Evidence: Six saved views plus evidence notes explaining any corrections.

Lesson 4

Common errors and readiness check

Find and fix the mistakes that commonly cost marks in the final submission.

Common ErrorsReadiness Checklist
  1. Open the Common Errors sheet and compare each error with your own practice list.
  2. Check for missing fields, weak field names, wrong data types, duplicate LoanID values, empty required fields and unsaved views.
  3. Open each saved view and confirm it still works after new records were added.
  4. Use the Readiness Checklist sheet to mark each requirement as Ready, Needs Fixing or Need Help.
  5. Fix the highest-impact issue first: missing required fields, wrong data types and missing views matter more than cosmetic changes.
  6. Prepare the evidence you would submit: evidence DOCX screenshots, Excel data export and Microsoft Lists share link.

Evidence: A readiness checklist with all major items marked ready or corrected.

Lesson 5

Final submission

Submit the completed Task 3 database product with clear structure, working views and supporting documentation.

Readiness Checklist
  1. Re-read the scenario and rubric before finalising your Microsoft List.
  2. Identify the table purpose, required fields, data types and key field.
  3. Build the list structure before spending too long entering data.
  4. Create enough accurate records to test all required views.
  5. Build query views and report views, then check the outputs against the scenario.
  6. Finish by adding screenshots to the evidence document, exporting the list to Excel and copying the Microsoft Lists share link.
  7. Use the final five minutes to check names, data types, LoanID values, required views, documentation completeness, Excel export and LMS share-link comment.

Evidence: Final assessment submission: evidence DOCX, Excel export and Microsoft Lists share link in the LMS comment box.

Key Build Steps

Documentation order

  1. Purpose and users.
  2. Data dictionary.
  3. Primary key justification.
  4. Form and data entry explanation.
  5. Query view descriptions.
  6. Report view descriptions.
  7. Testing evidence, limitations and improvements.

Timed practice order

  1. Build columns first.
  2. Enter sample data second.
  3. Create views third.
  4. Test filters and data types fourth.
  5. Document, export to Excel and copy the share link last.

Student Checklist

  • I can build the list foundation without copying my old list.
  • I can create all required views from a scenario prompt.
  • I can explain my data dictionary and LoanID choice.
  • I can identify and fix wrong data types, duplicate keys and unsaved views.
  • I know I must submit the evidence DOCX, Excel export and Microsoft Lists share link.

Common Mistakes to Avoid

Writing documentation for an ideal database instead of the one actually built.

Documentation must describe your real fields, views and limitations.

Leaving the primary key explanation vague.

State why LoanID is unique and why other fields are not reliable identifiers.

Only checking visible records in a filtered view.

Also check records that should be hidden so you know the filter is excluding correctly.

Running out of time before evidence is saved.

Reserve the final five minutes for screenshots, the Excel export and the LMS share-link comment.

Quick Start Instructions

  1. Download this week's workbook and open the sheets listed at the top of the page.
  2. Open Microsoft Lists in the browser at https://office.com/launch/Lists.
  3. Build from Excel if the option is available. If not, create a blank list and follow the workbook field order manually.
  4. Complete each lesson task in order. Do not skip the evidence checks because they match the final assessment expectations.
  5. Use the Task 3 guides when you need help with fields, forms, query views, report views, interface or documentation.