Day 27: Choose Your Best Work

1. b. A portfolio curates representative evidence and explains its value.

2. b. A clear reason and visible evidence make the selection useful.

1. b. A score is one signal only.

2. b. A portfolio curates evidence, explains it, and points to the next step.

One possible original model, not a required list:

1. Report: range and process findings.
2. Proposal: audience and benefits plus risks.
3. SOP: practical voice and sequence.
4. Review: balance and judgment.
5. Blog: public argument and voice.

Possible swaps: email for proposal, or CV for SOP, if Annisa's real work gives stronger evidence.

This is not a public learner portfolio.

b. Range means useful difference, not random variety.

Strong pair example: report plus SOP, because one organises findings and one guides action.

Another pair: CV plus blog, because one proves credentials and one argues a public point.

b. Growth needs a visible problem and a newer writing move.

Model: an earlier opinion-only paragraph becomes a later paragraph with a position, relevant evidence, and a reason.

1. b. Style changes with reader and purpose.

2. a. A report is usually more objective.

Voice is Annisa's clear choices adapted to the task.

b. Clear voice and visible improvement give stronger portfolio evidence than a score with no context.

Apply the same principle to Annisa's fifth choice.

b. A score is evidence only when Annisa explains what it shows.

The score does not decide range, voice, audience fit, or the full value of a text.

b. A focused revision should improve a useful text for its reader.

Choose one problem: delayed position, missing link, unclear instruction, weak transition, or irrelevant detail.

b. Reader-facing structure comes before surface editing.

Ask: What is the task? Where is the main point? Which evidence supports it?

Example plan for a blog opening:

• Keep the Pertamina RU IV moment.
• Move the safety position to the first paragraph.
• Add why the moment matters to future engineers.
• Check that the position appears early and the evidence supports it.

Use Annisa's actual selected text.

The successful joint revision identifies one reader need, makes one clear structural change, and keeps Annisa's voice.

Use the improved version in Activity 13 as the independent attempt.

The original model appears only after Annisa writes.

During a 30-day heat-exchanger audit at Pertamina RU IV, one safety question changed how I read a process report. I learned to treat a number not only as a result, but as a warning that may affect people, equipment, and the wider plant. My K3 safety certificate supported this lesson, but the strongest evidence came from using safety questions while reading real process data.

This experience leads to a wider argument. Safety should be a core thread in every engineering degree, not a separate topic students meet only at the end. If safety is connected to maths, chemistry, and design from the beginning, learners can ask what could go wrong and how a safer design can reduce the risk.

One limited counterpoint is that degrees already have limited time. The answer is not a long list of extra rules. Safety can be taught through real cases, lab decisions, and design reviews. Engineers create systems that affect real people, so safety must be part of engineering thinking from the start.

This is an original model blog opening, not a public learner artefact. Replace details with Annisa's real selected text.

All seven checks should be present.

A strong revision may keep most sentences while changing the order, evidence link, or clarity of the main point.

The error-list row must show the original problem, a better model, and Annisa's new attempt.

Save both versions for Day 28.

All seven checkpoint items should be visible.

The five selected texts may differ from the original model map. Annisa's own evidence and range decide the final set.

The next action names one text, one change, and one reader check.

Day 28 uses this portfolio for the final independent writing project.