Give Relevant Context and Authorised Sources

Work through the explanation, apply it to the example, and complete the quick check before continuing.

Context answers the questions behind the task

Useful context may include:

• Why the work is needed.
• What happened before.
• Terms that have a special meaning in this situation.
• Decisions already made.
• The time period, location, product, or group in scope.
• Material the output must use.

Without context, a system may fill gaps with general patterns or unsupported guesses.

Separate instructions from sources

Instructions say what to do. Sources provide material or evidence.

Instruction:

Compare the two options against cost, setup time, accessibility, and maintenance.

Sources:

Use the approved requirements table and the two vendor proposals attached below.

Keeping these roles clear helps the reviewer see whether the output followed the method and used the right evidence.

Name authorised sources

Do not write only use reliable sources when you can identify what counts.

Examples:

• Use only the supplied approved policy dated 10 June.
• Use the current page published by the responsible government department.
• Use columns A-D of the supplied synthetic dataset.
• Use no outside facts; mark missing information as Not provided.

If outside research is allowed, define its scope and evidence standard. A generated citation is not proof that a source exists or supports the claim.

Use only permitted information

Module 3 taught that task suitability and data suitability are separate.

Before supplying context or files:

1. Classify the information.
2. Confirm that the proposed system is approved for it.
3. Remove unnecessary personal, confidential, or prohibited details.
4. Use fictional or synthetic material for practice.

More context is not always better. Irrelevant material can distract the system and make review harder.

Mark source boundaries

When several documents are supplied, label them clearly.

For example:

Source A: approved event details. Source B: required email style. Do not treat the example email as evidence about this event.

This prevents an example from being mistaken for a factual source.

Worked example

Task:

Draft a summary of a proposed office move.

Useful context and sources:

The summary is for staff who know the current office but have not seen the proposal. Use only Source A, the approved move proposal dated 2 July, for dates, costs, and facilities. Use Source B only for the organisation’s writing style. If Source A does not answer a question, write Not stated in the proposal. Do not use general web information or add assumptions about transport.

Remember

• Give context that changes how the task should be done.
• Name permitted and authoritative sources.
• Separate instructions, evidence, and examples.
• Say what to do when information is missing.
• Supply only authorised, necessary information.

Next, we will set constraints and boundaries before predictable failures happen.