Weekly Fieldwork

How to participate#

In person is the preferred route. Use the campus teaching pack in the facilitated session, with the supplied apparatus or paper models and the required individual, pair or team responsibilities. Keep your station sheets, predictions, revisions and explanation, plus receiver acknowledgements where the weekly activity requires a handoff. These form the practical record; an additional browser run is not required.

Online, if you cannot attend: use the equivalent activity and control instructions below. The 3D environment supports the same reasoning, rehearsals and evidence requirements. Both routes use this brief’s deliverables and rubric. Label measured, paper-model and simulated results accurately.

Online control guide: keep one useful record per week#

Your task: collect evidence of what you tried, what happened and how you adapted. Fieldwork is a portfolio of the weekly labs, not another separate game.

1. Open the lab for your week and read its Your mission, in plain language section.
2. Complete the practical Practice attempt and read its feedback. Afterwards open After playing · explain and save this attempt, write a brief explanation and select Record attempt in skills passport before switching phases.
3. Try Skill check and Transfer challenge, reading the changed conditions each time. Save the attempts that show your learning, including a useful failure.
4. Use the passport’s export controls to keep a backup outside this browser. For campus work, keep an equivalent dated action or measurement record.
5. After playing, use the fieldwork template to assemble the named output, prediction, trace, changed-situation response, approximately 100-word reflection and declared assistance.
6. Check What you hand over below. Repeat for later weeks; your best ten of twelve records count.

You are finished for the week when: your record identifies the lab and scenario, shows a practical attempt and changed-condition response, and includes your own reflection. Watching the fieldwork example shows the format but does not create your record.

The brief#

Keep twelve individual lab records. Your best ten count; each counted record contributes up to one percentage point to the course total. Game completion alone does not earn the point.

Each record is due at 17:00 Canberra time on its Friday lab date. The final portfolio closes on 28 May 2027 at 17:00. Weekly checkpoints appear in the lab schedule and do not create twelve additional assessments.

What you hand over#

For every record include:

• The named weekly output and its scenario.
• Your initial prediction and relevant action or measurement trace.
• Your response to the changed situation.
• Approximately 100 words of reflection.
• The route used: browser or campus.
• Any hints, assistance or adapted materials.

An exported activity record supplies evidence but does not replace your explanation. Preserve unsuccessful attempts when they show a useful diagnosis or revision. A campus record can use measurements, photographs of your own model, coordinates or a written event trace. No public ranking or speed score is required.

What counts as a completed activity#

Use the completion conditions for that week. An investigated explanation, strategy comparison, tested diagnosis or feasible agreement can be the practical outcome. A receiving handover is required only when the activity names it as part of its skill. Optional scene delivery adds practice but carries no extra academic credit. Record a useful failed attempt with its diagnosis rather than inventing a success.

How fieldwork accumulates#

The first four records support A1. Records five to eight support A2. Council, sensor and revision work prepare the final recovery mission. You may revisit any published lab; mark a later attempt clearly so its provenance remains understandable.

Missed sessions and feedback#

Best-ten marking accommodates two missed records. A student who misses the campus session can complete the browser route or supplied equivalent within the published arrangements. See policies for individual access and extension needs.

Rule-based feedback is immediate. Use the final fifteen minutes of each lab for peer or tutor discussion. Open-ended reflection is reviewed by a teacher; the site does not assign an academic grade to it.

Criterion-specific performance standards#

Demonstrated skill — 40%#

• Outstanding: Accurate performance or precise diagnosis supported by a reproducible activity trace.
• Competent: The main skill is demonstrated with minor unexplained gaps.
• Developing: A result is supplied but its relationship to the skill is unclear.
• Insufficient: No usable performance evidence or a fundamental unexamined rule error.

Transfer — 40%#

• Outstanding: Applies the principle in the changed scenario and explains what must be reconsidered.
• Competent: Adapts to the supplied change with a broadly sound explanation.
• Developing: Repeats the practice answer without addressing an important changed condition.
• Insufficient: No changed-situation attempt or no connection to the taught principle.

Reflection — 20%#

• Outstanding: Identifies a specific error or limit and a credible improvement grounded in the attempt.
• Competent: Explains one relevant success or difficulty.
• Developing: General statements with little connection to the record.
• Insufficient: Reflection missing or presented as someone else’s experience.

Format, export and access#

Use the downloadable template, retain editable source and export a readable record. The website provides downloads and local practice; it does not submit to an institutional system. The browser and campus routes assess the same concepts and problem-solving outcomes. Neither automatically certifies physical dexterity.

All due times use 17:00 Canberra time on the published date. Policies and support explain attribution, accessible alternatives, contribution disputes, saving and extensions.