0403EE · MINOR DIGITAL SKILLS · YEAR 4 · 7 EC INDIVIDUAL ASSESSMENT EVIDENCE PORTFOLIO Student name / ID: Team / venture: Assessment opportunity: Submission date / version: Live website: Repository or source workspace: Evidence folder accessible to the assessor: Use this structure to prepare one individual portfolio document (PDF), with evidence links and supporting files. Upload it to the designated Year 4 assignment on the university’s Connect platform and complete its submission action. A public project link, a saved draft, a leaderboard score or an agent report alone is not a final portfolio submission. Use the deadline shown on that assignment. The sections below organise evidence. They do not add new grading components or weights. Shared project artefacts are allowed; your contribution and reflection must be identifiable. A. STARTING POINT AND MY CONTRIBUTION What already existed before I worked on it in this course: Baseline date and evidence (commit/version, screenshot, previous deployment or project record): Existing features, templates, AI-generated code and other people's work I reused: Sources/credits and teammates' responsibilities: The problem or user need I worked on during this course: My own tasks and changes: Current version / commit / deployment date: What I can demonstrate and explain myself: What remains uncertain or undocumented: If a baseline was not recorded, say so. Use available history and clearly label retrospective recollections. Never backdate records or invent prompts, tests or customer feedback. B. MY WORK AND AI PROMPT TRAIL Repeat for each substantive task or improvement. Select evidence that demonstrates learning; a huge chat export without explanation is not enough. If AI was not used for a task, state that and explain your actual method. Task / date / official component supported: Starting state / relevant file or artefact: What I was trying to achieve and why: Tool / model used (if applicable): My actual prompt and relevant context, with secrets removed: Relevant output excerpt / screenshot / transcript reference: What I accepted, rejected or corrected, and why: My revised prompt or manual change: Before/after evidence and commit/version link: Test performed / expected result: Actual observed result, including failures: What I learned / limitation / next step: My individual contribution versus the team's: C. ACTIVE PARTICIPATION — 15% Session/date: Activity / discussion / practical task: My specific contribution or feedback: Evidence or instructor observation: What I learned or helped others learn: Attendance or approved absence/make-up information, if applicable: A commit or website link does not establish attendance. The Field Expert assesses participation from the relevant records and observations. D. DIGITAL PRESENCE — 30% D1. WEBSITE AND USER JOURNEY Audience / offer / useful visitor action: Live URL and relevant source/version: What works, what is simulated and known limitations: Steps the assessor should follow (start page, action, input, expected confirmation): A dated screen recording or screenshots of the actual journey: Test log (date/version, device, steps, expected result, observed result, evidence): Failure found, correction and retest: D2. GOOGLE ANALYTICS Implementation evidence / configuration reference: Dated evidence of my test visit and a meaningful action/event appearing in the correct property: Event name / what it measures / why it matters: What the observation shows and does not show: Additional analytics tools, if used: The supplied university brief specifically requires Google Analytics. PostHog, Hotjar, Clarity or Vercel Analytics may support classroom work but do not automatically replace that requirement. A package name or tracking snippet alone does not prove data is received. D3. SOCIAL PROFILES AND DATED ACTIVITY For each account: platform / profile URL: Evidence of logo, hero image, description and contact details: Activity period (start/end dates): Dated post index (date, link or screenshot reference, purpose, my contribution): Actual number of posts in the documented period: What I learned / changed: The full product target is at least three properly set up accounts, each with at least 12 posts over a month. The published grade bands describe sufficient and good work with less evidence; consult those bands rather than treating a checkbox count as a grade. Report actual activity; do not invent or backdate posts. E. DIGITAL ADVERTISING — 20% For each campaign: platform / campaign identifier (redacted where appropriate): Business objective / audience definition / targeting: Creative and copy / landing page / intended action: Dated setup evidence: Initial observations and period covered: Optimisation log (date, observation, change, reason, subsequent result): What I personally set up or changed: Limitations / what was not run or not measurable: The full product target names Facebook Ads and Google Ads. The grade bands distinguish campaign completeness and ongoing optimisation, including lower bands describing one campaign. An ad mockup or campaign URL alone is not evidence of an optimised campaign. Label drafts, simulations and live activity accurately. F. EXPERIMENTATION — 35% Use the supplied university requirements for day trading, cryptocurrency, blockchain, NFTs and DeFi. The AI practice log alone does not fulfil this component. Topic / platform / account context: Concept I can explain and how the evidence relates to it: Action actually performed / date: Own-account screenshot or short recording reference: NFT creation/upload evidence, where applicable: Day-trading action evidence, where applicable: Cryptocurrency purchase and sale evidence, where applicable: Result / limitations / risks I identified / what I learned: What is live, simulated, only an account setup, or incomplete: The source's full product target and its lower-band descriptors differ. Submit truthful evidence of the stage reached; the Field Expert applies the published bands. This template is not investment advice or an instruction to take financial risk. Ask the Field Expert about permitted alternatives if you cannot meet a requirement. Never upload passwords, API keys, seed phrases or private keys. Redact irrelevant balances, identifiers and third-party personal data; retain enough context for the assessor to evaluate the work. G. INDIVIDUAL REFLECTION AND EVIDENCE INDEX What I can now do or explain that I could not demonstrate at the start: One specific decision I made and the evidence behind it: One mistake or failed attempt, correction and learning: My most important course-period contribution: Next improvement and how I would test it: Evidence index (repeat): Evidence ID / file name: Official component and claim supported: Date / project version: Link or attached file: My role / collaborators / original source: Assessor access checked: H. AGENT FEEDBACK AND RESPONSE (SUPPORTING EVIDENCE) Review date / project version / report reference: Utility finding: Did I verify it? What was the result? Change made / commit / successful retest, or reason for rejecting the advice: Design suggestion used, if relevant: Remaining checks the agent could not perform: Utility and AI practice scores are formative feedback, not official university marks. Design feedback never determines passing or failing. The agent does not establish authorship or replace the portfolio. FINAL SUBMISSION CHECK [ ] My name, ID, course, project and version are present. [ ] Pre-existing work and my course-period contribution are distinguished. [ ] Actual prompts, outputs, corrections and tests are traceable where AI was used. [ ] All four official components have evidence or an explicit statement of gaps. [ ] Shared work is attributed and the reflection is my own. [ ] Links open for the assessor; attachments are clearly named and indexed. [ ] Sensitive details are removed; actual and simulated results are distinguished. [ ] I uploaded the portfolio and supporting evidence to the Year 4 assignment on the university’s Connect platform. [ ] I completed the submission action, checked its submitted status/receipt and kept a dated copy. Completeness is not a pass. Official marks are awarded separately for participation, Digital Presence, Digital Advertising and Experimentation. Each must be at least 5.5/10.