Produced by Claude following agent-instructions.txt and the invented Banksia policy, November 2026. Blind run: the assistant saw only the instructions and the policy. Not captured from Copilot.

## Conversation 1

**User:** Someone started on 15 March this year. Are they in this year's annual review?

**Assistant:**

**Answer:** No. They started after 1 March, so they are first reviewed in the next annual review.

**Clause:** 3.2: "Employees who start after 1 March are first reviewed in the next annual review."

**User:** What about a retention payment for someone we are worried about losing?

**Assistant:**

**Answer:** The policy is silent on this.

**Clause:** None.

**Silent or unclear:** The policy does not mention retention payments. The nearest clauses are 4.1, which says "An out-of-cycle base pay adjustment may be considered where one of these applies" and lists three cases (a change in role size, pay below range or out of line with colleagues, or an error), and clause 7, which covers variable pay. A retention concern is not one of the three cases in 4.1, and clause 7 does not mention retention. I have not stretched either clause to cover it.

**Who decides:** The policy names no one for this decision, so a senior member of the remuneration team.

## Conversation 2

**User:** Draft a reply to this manager. Today is 14 November. Context from us: the team member is Level 4, currently at 96% of the reference point, last annual review effective 1 July this year, no earlier out-of-cycle adjustment.

Manager's email: "Hi Reward team, one of my analysts has a competing offer from another company that is well above her current pay. I would like to give her an out-of-cycle increase to match it, as soon as possible, otherwise I will lose her. Can you confirm by Friday? Thanks."

**Assistant:**

**Draft reply**

Hi [manager's name],

We can't confirm an out-of-cycle increase by Friday. The policy does not allow one to be considered at this point.

An out-of-cycle adjustment is not considered within six months of the employee's last annual review effective date, unless an error has occurred (clause 4.3). The last annual review took effect on 1 July this year (clause 3.1). Today, 14 November, is inside that six months.

Out-of-cycle adjustments may be considered only in three cases. The role has permanently changed in size without a promotion. Pay is below the bottom of the range, or clearly out of line with colleagues in the same role and level. Or an error has occurred (clause 4.1).

If you believe an error has occurred, send the request in writing with a business case (clause 4.2).

Please do not tell your team member that an adjustment is being sought, or discuss any figure, until it is approved (clause 4.5).

Regards,
[your name]

**For you, not part of the reply**

- Clauses relied on: 3.1, 4.1, 4.2, 4.3, 4.5.
- Date arithmetic: the last annual review took effect on 1 July this year (given by you, and matching the 1 July date in clause 3.1). Six months from 1 July is 1 January next year. Today is 14 November, which is 4 months and 13 days after 1 July (1 July to 1 November is 4 months, plus 13 days). That is less than 6 months. Days left until 1 January: 17 days from 14 November to 1 December, plus 31 days in December, which is 48 days. I left the exact end date out of the reply because the policy does not say whether the six months ends on 31 December or 1 January. It does not change the answer today.
- Flag for a senior team member:
  - The policy is silent on matching a competing outside offer, and on retention. A competing offer is not one of the three cases in clause 4.1. Nothing you gave me suggests an error under 4.1(c).
  - Whether to treat this as an exception to clause 4.3 is a judgement call. The policy gives exceptions to the Head of Reward (clauses 1.3 and 8.1). I did not mention exceptions in the draft.
  - If an adjustment were ever considered, the approver depends on the resulting position in range: Reward Manager up to 100%, Head of Reward above 100% and up to 120% (clause 8.1). The resulting position cannot be worked out because the manager has not given a figure. The current position you gave me is left out of the draft, as the data rules require.
  - The clause 4.4 limit (one out-of-cycle adjustment in 12 months) is not engaged, because you told me there has been no earlier adjustment.

## Conversation 3

**User:** Check this proposal. Role: Senior Analyst, Level 5, Finance. Level 5 reference point from our range table: $120,000. Proposed base pay: $117,600. I do not have the positions of existing Senior Analysts at Level 5. Manager's note: "I rang the candidate in October and told her we could do $117,600. She has said yes verbally." This is the first time it has come to the Reward team.

**Assistant:**

| Requirement | Clause | Result | Why |
| --- | --- | --- | --- |
| Base pay must not be above 120% of the reference point | 2.4 | Complies | 120% of $120,000 = 1.2 x $120,000 = $144,000. $117,600 is below $144,000. |
| The Reward team must have sized the role before any offer is made | 2.6 | Cannot tell | The role is shown as Level 5, but nothing shows the Reward team sized it before the offer was made. |
| The Reward team must review a proposed offer before anyone discusses a figure with a candidate | 5.1 | Breaches | The manager told the candidate $117,600 in October. This is the first time the offer has come to the Reward team, so the review had not happened. |
| The proposal must state the role and level, proposed base pay, proposed position in range, the highest position held by an existing employee in the same role and level, and the reason for any offer above 100% | 5.2 | Cannot tell | Role, level and base pay are given. The manager did not state the position in range. I calculated it: $117,600 divided by $120,000 = 0.98 = 98%. The highest existing position is not given. No reason is needed for an offer above 100%, because 98% is not above 100%. |
| Offers are normally between 90% and 100% of the reference point | 5.3 | Complies | Position in range = $117,600 divided by $120,000 = 98%. That is between 90% and 100%. |
| An offer must not place a new hire higher in the range than any existing employee in the same role and level, unless the Head of Reward approves | 5.4 | Cannot tell | The proposed position is 98%. The positions of existing Senior Analysts at Level 5 are not given, so it cannot be compared. |
| An offer is conditional until the approval required by clause 8.1 is recorded | 5.5 | Cannot tell | The manager's note says "we could do $117,600" and does not say whether the candidate was told it was conditional on approval. No recorded approval is shown. |
| The approver in the table must approve in writing before the decision takes effect | 8.1, 8.2 | Cannot tell | An offer at up to 100% needs the hiring manager's General Manager, after Reward team review. The Reward team review is only starting now, and no written approval is shown. |

**Missing information:**

- The highest position in range held by an existing Senior Analyst at Level 5 (clauses 5.2 and 5.4).
- Whether the Reward team sized the Senior Analyst role to Level 5 before the offer was made (clause 2.6).
- Whether the candidate was told the offer was conditional on approval (clause 5.5).
- Whether anyone has approved the offer in writing (clauses 8.1 and 8.2).

**Questions to ask the manager:**

- What is the highest position in range held by an existing Senior Analyst at Level 5?
- What exactly did you tell the candidate in October, and did you say the offer was subject to approval?
- Has anyone else discussed a figure, a range or expectations with the candidate?
- Has anyone approved this offer in writing?
- Do you know whether the Reward team sized the Senior Analyst role before the candidate was contacted?

**Approval route:** Position in range = base pay divided by reference point = $117,600 divided by $120,000 = 0.98 = 98%. For an offer up to 100%, clause 8.1 names the hiring manager's General Manager, after Reward team review. If the existing positions show clause 5.4 applies, clause 5.4 says the Head of Reward must approve.

**Flag for a senior team member:**

- Clause 5.1 has already been breached, because a figure was discussed with the candidate before the Reward team review. The policy is silent on what happens after a breach of 5.1 and on the effect of the candidate's verbal yes. It names no role for that decision, so a senior member of the remuneration team decides.
- If the proposal is to go ahead despite the breach, that would be an exception to clause 5.1. The policy gives exceptions to the Head of Reward (clauses 1.3 and 8.1).

A person on the remuneration team makes the decision.
