Announce or explain something formally inside Nexus — purpose, details, action required.
Resources
Templates library
Copy a template and make it your own. Filter by category or search, then open a template to see the full format. Clear, consistent documents make us look professional and save everyone time.
Showing all 56 templates
Emails & letters
Formal correspondence to someone outside Nexus, in the standard letterhead layout.
Nexus Group Pty Ltd Level 14, 420 Collins Street, Melbourne VIC 3000 [Date] [Recipient name] [Recipient address] Dear [name], Re: [subject] [Opening — why you're writing.] [Body — the detail, in clear paragraphs.] [Closing — next steps or a polite call to action.] Yours sincerely, [Your name] [Your role], Nexus Group
The standard Nexus email signature block — set it up once in your mail client.
[Your Name] [Your Role] | Nexus Group P: 03 9012 [xxxx] | M: 04xx xxx xxx E: firstname.lastname@nexusgroup.example.com W: www.nexusgroup.example.com Connecting people, technology and care.
A clear ask or FYI to a colleague — main point first, action and deadline included.
Subject: [Action needed / FYI / Decision required]: [topic] [by date] Hi [name], [The main point or what you need, in the first line.] [Any detail, in short paragraphs or bullets:] • [point] • [point] [What you need them to do, and by when.] Thanks, [Your name] [Your role]
Update a customer on an enquiry or order, with the next step and a date.
Subject: [Your enquiry / order [ref]] — update Hi [customer name], Thanks for your patience. [What's happening and the next step, with a clear date or timeframe.] [Apologise briefly if there's been an inconvenience.] If [date/time] doesn't suit, reply or call me on [phone] and I'll help. Kind regards, [Your name] [Your role], Nexus Group
Formal email to a client or external contact, with the full Nexus signature.
Subject: [Project / matter]: [purpose — e.g. progress update, revised proposal] Dear [name], [Open with the relationship or engagement — e.g. "Following our recent work on [engagement]" or "Thank you for meeting with us on [date]".] [The detail — short paragraphs, leading with what matters most to the client.] [The next step — what happens now, who does it, and by when.] Please let me know if you have any questions — I'm happy to talk it through. Kind regards, [Your name] [Your role] Nexus Group Pty Ltd P: 03 9012 [xxxx] E: firstname.lastname@nexusgroup.example.com W: www.nexusgroup.example.com
Answer a customer enquiry — what's happening, by when, and how to reach you.
Subject: Re: [your enquiry — ref [number]] Hi [customer name], Thanks for getting in touch about [restate their enquiry in one line]. [The answer, or what's being done:] • [key point or step] • [key point or step] [When they'll hear from us or see the result — a clear date or timeframe.] Your reference number is [number] — quote it if you contact us again. If anything here doesn't look right, just reply to this email or call us on [phone] and we'll sort it out. Kind regards, [Your name] Nexus Group Customer Service
Respond to an unhappy customer — acknowledge, apologise, fix and follow up.
Subject: Re: [issue] — ref [number] Dear [customer name], Thank you for letting us know about [the issue, in the customer's words]. I'm sorry this happened — it's not the experience we want you to have. [What happened, if known — briefly and without excuses.] Here's what we're doing about it: • [action] — by [date] • [remedy or goodwill gesture, if offered] I'll follow up with you by [date] to confirm it's resolved. Your reference number is [number]. If you're not satisfied with this response, let me know and I'll arrange for it to be reviewed. Kind regards, [Your name] [Your role], Nexus Group
Report project status to stakeholders — progress, what's next, risks and decisions.
Subject: [Project name] update — [date / milestone] Hi all, Status: [On track / At risk / Delayed] for [key date or milestone]. Since the last update: • [what's been completed or decided] • [what's been completed or decided] Coming up: • [what happens next, and when] Risks / decisions needed: • [risk or decision — who needs to act — by when, or "nothing this period"] Next update: [date]. Questions welcome any time. [Your name] [Your role]
Meetings & discussions
The general-purpose combined agenda and minutes format for any meeting.
MEETING AGENDA Meeting: [name] Date/time: [date, time] Location: [room / video link] Chair: [name] Minute-taker: [name] 1. Welcome & apologies 2. Minutes of previous meeting 3. [Item] — led by [name] — [time] 4. [Item] — led by [name] — [time] 5. Other business 6. Next meeting MINUTES Present: [names] Apologies: [names] Decisions: [what was agreed] Actions: [action — owner — due date]
Plan the questions for a conversation, capture the answers and review how it went.
QUESTION PLAN Issue I'm looking into: [short description] Who I'm asking: [name, role] Why them: [what they know that I need] Date/time: [when] Mode: [in person / phone / Teams / email] Style I'll use: [funnel / inverted funnel / direct / conversational] What I need to walk away knowing [The one thing this conversation has to tell me.] My questions (broad first, detail after) 1. [Open] [ ] 2. [Open] [ ] 3. [Probing] [ ] 4. [Closed] [ ] 5. [Clarifying][ ] Checked with: [name] Date: [date] Changes they suggested: [ ] Responses | # | What they said | Follow-up I asked | Still to confirm | |---|----------------|-------------------|------------------| | 1 | [ ] | [ ] | [ ] | | 2 | [ ] | [ ] | [ ] | Summary played back to them: [what you said / their confirmation] Review — how did it go? Worked well: [ ] Would change next time: [ ]
A standing agenda for the weekly team meeting, from wins to action review.
TEAM MEETING AGENDA Meeting: [team] weekly meeting Date/time: [date, time] Location: [room / video link] Chair: [name] Minute-taker: [name] 1. Welcome & wins from last week — [5 min] 2. Safety moment — hazards, near misses, wellbeing — [5 min] 3. Round the table — progress and blockers — [15 min] 4. Priorities & workload for the week ahead — [10 min] 5. Action register review — [what's open — owner — due] — [10 min] 6. Other business — [items raised on the day] 7. Next meeting — [date, time]
The monthly executive meeting running order — performance, finance, people, WHS.
EXECUTIVE MEETING AGENDA Meeting: Executive team — monthly Date/time: [date, time] Location: [boardroom / video link] Chair: [name] Minute-taker: [name] Attendees: [executive team members] 1. Apologies & conflicts of interest — [5 min] 2. Minutes of previous meeting & actions — [5 min] 3. CEO overview — [10 min] 4. Stream performance — [Retail / Tech / Consulting / Care] — [20 min] 5. Finance report — [results, cash position, exceptions] — [10 min] 6. People & culture — [recruitment, engagement, development] — [10 min] 7. WHS & compliance summary — [incidents, actions, obligations] — [10 min] 8. Strategic items — [item — sponsor] — [15 min] 9. Decisions & actions recap — [5 min] 10. Next meeting — [date]
Keep a project meeting on track — status, milestones, risks and decisions.
PROJECT MEETING AGENDA Project: [project name] — [phase] Date/time: [date, time] Location: [room / video link] Chair: [name] Minute-taker: [name] 1. Status vs plan — [On track / At risk / Delayed] — [5 min] 2. Milestone review — [milestone — due — status] — [10 min] 3. Budget & effort check — [spend vs estimate] — [5 min] 4. Risks & issues — [new, changed, closed] — [10 min] 5. Change requests — [what's proposed and its impact] — [10 min] 6. Decisions needed today — [decision — who decides] — [10 min] 7. Actions recap — [action — owner — due] 8. Next meeting — [date, time]
Standing items for the WHS Committee — incidents, hazards, inspections, consultation.
WHS COMMITTEE AGENDA Meeting: WHS Committee — [month] Date/time: [date, time] Location: [room / video link] Chair: [name] Minute-taker: [name] Attending: [committee members and health & safety representatives] 1. Previous minutes & open actions — [5 min] 2. Incident & near-miss review — [what happened, causes, actions] — [10 min] 3. Hazard register review — [new hazards, controls, overdue items] — [10 min] 4. Workplace inspections — [pre-start themes, walkthrough findings] — [10 min] 5. Items raised by teams and HSRs — [consultation items] — [10 min] 6. Training, first aiders & wardens — [coverage, refreshers due] — [5 min] 7. Emergency procedures & drills — [next drill, learnings] — [5 min] 8. Environmental items for the Sustainability Working Group — [5 min] 9. Other business 10. Next meeting — [date] (Hazard register and consultation records live on the portal: /whs)
Structure a client meeting — progress, feedback, agreed actions on both sides.
CLIENT MEETING AGENDA Meeting: [engagement / project] — client meeting Client: [organisation — attendees] Date/time: [date, time] Location: [client site / Nexus office / video link] Chair: [name] Notes: [name] 1. Welcome & introductions — [5 min] 2. Purpose of today — [what we need to achieve] — [5 min] 3. Progress against the agreed scope — [10 min] 4. Walkthrough — [deliverable / findings / recommendations] — [15 min] 5. Client feedback & questions — [10 min] 6. Scope or next-phase items — [anything new or changing] — [10 min] 7. Agreed actions — [action — owner (Nexus / client) — due] 8. Next meeting — [date, time]
Record a work conversation — what was said, confirmed and changed after feedback.
DISCUSSION NOTES Talking with: [name, role] Date/time: [date, time] Mode: [in person / phone / Teams] About: [topic] What was communicated • [key points you raised or were given] • [decisions or requests made] Questions and feedback • [what was asked, suggested or queried — by you or by them] What was confirmed • [points both of you agreed were correct or settled] What changed after feedback • [what you adjusted and why] Follow-up • [action — who — when] Copy shared with: [name] on [date]
Updates & handovers
A quick done / next / blockers progress note to your manager.
Hi [supervisor], Quick update on [job / project]: • Done: [what's complete] • Next: [what you're doing next] • In the way: [any blockers or risks — or "nothing right now"] [On track / at risk] for [deadline]. I'll flag early if that changes. [Your name]
Raise a problem you can't resolve yourself, with impact and what you need.
ISSUE ESCALATION To: [supervisor / team] From: [your name] Date: [date] Priority: [Low / Medium / High] Issue: [what the problem is, in one or two sentences] Impact: [who/what it affects and how urgent] Tried: [what you've already done] Need: [the decision or help you need, and by when]
Pass work to the next person — done, in progress, outstanding and anything urgent.
HANDOVER NOTE From: [name] To: [name] Date/time: [date, time] Done today: • [what's complete] In progress / watch: • [what's underway, and anything to keep an eye on] Outstanding / for you to pick up: • [item — any deadline] Anything urgent: [yes/no — detail]
A short note to your team or channel — progress, what you need, blockers.
TEAM NOTE To: [team / channel] From: [your name] Date: [date] About: [topic — e.g. knowledge base refresh] Where we're at: [progress in a line or two] What I need from you: [who, what, by when] Anything blocking us: [or "nothing right now"] Next check-in: [when]
Planning & priorities
Track who's doing what by when after a meeting or piece of work.
ACTION REGISTER — [team / meeting] — [date] Ref | Action | Owner | Due | Status ----|--------|-------|-----|------- 1 | [what needs doing] | [name] | [date] | Open 2 | [what needs doing] | [name] | [date] | In progress 3 | [what needs doing] | [name] | [date] | Done Notes: [anything to add]
Plan your week — priorities, time estimates, due dates and risks.
WORK PLAN — [your name] — week of [date] Priorities this week: 1. [most important] 2. [next] 3. [next] Work item | Est. time | Due | Notes ----------|-----------|-----|------ [work item] | [hrs] | [date] | [notes] [work item] | [hrs] | [date] | [notes] Risks / help needed: • [anything that could go wrong, or where you need support]
Ask another team for something specific — records, rooms, supplies — with the details they need.
WORKPLACE REQUEST To: [team / person] From: [your name, role] Date: [date] Request: [what you need — e.g. update a record, book a room, order supplies] Details: [the specifics: names, dates, quantities, account codes] Needed by: [date] Approved by (if required): [name]
Sort your list by urgent and important to decide what to do first.
PRIORITY MATRIX — [your name] — [week/date]
URGENT | NOT URGENT
IMPORTANT | Do first: | Schedule:
| • [item] | • [item]
| • [item] | • [item]
----------- ------------------------ ----------------------
NOT | Do quickly / pass on: | Drop or do last:
IMPORTANT | • [item] | • [item]
Notes / what moved and why: [ ] Close out the day — what got done, what carries over, tomorrow's top three.
END-OF-DAY REVIEW — [date] Done today: • [item] • [item] Not finished (carry over): • [item] — [why / new date] Got in the way: • [interruptions, blockers, delays] Top priorities for tomorrow: 1. [ ] 2. [ ] 3. [ ]
Pin down exactly what you've been asked to do before you start.
WHAT I'VE BEEN ASKED TO DO Requested by: [name] Date: [date] [ ] What's needed (the output): [ ] [ ] What "done" looks like: [ ] [ ] Who it's for / purpose: [ ] [ ] Due date (and anything needed sooner): [ ] [ ] Format / template to use: [ ] [ ] Where to save it: [ ] [ ] Anyone else involved: [ ] Checked my understanding with the requester? [Yes / No] Questions to ask: [ ]
Plan a communication — purpose, who's involved, channels, approvals and timing.
COMMUNICATION PLAN Prepared by: [your name, role] For: [manager / requester] Date: [date] 1. Purpose [What the communication needs to achieve, and the work outcome it supports.] 2. Who's involved | Name | Role | Contact / consult / inform | Why they're included | |------|------|----------------------------|----------------------| | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | 3. Channels | Channel | What it will carry | Why it suits this | |---------|--------------------|-------------------| | [email / Teams / meeting / phone] | [ ] | [ ] | | [ ] | [ ] | [ ] | 4. Approvals needed [What needs sign-off before it goes out, and who approves — see the approval procedure.] 5. Timing [When each message goes out, and in what order.] 6. Advice received [Guidance from your manager on the approach, and what you changed as a result.]
Reports & records
Log a customer complaint — what happened, action taken and any escalation.
CUSTOMER COMPLAINT RECORD Logged by: [name] Date: [date] Customer: [name] Contact: [email / phone] Stream: [Retail / Tech / Consulting / Care] Channel: [Phone / Email / In person / Online] What happened (customer's words where possible): [description] Action taken / requested: [what was done, or what the customer wants] Escalated to: [name, if applicable] (Log it on the portal: /customer-service/feedback)
A short report structure: purpose, background, findings, recommendations, next steps.
[REPORT TITLE] Prepared by: [name, role] Date: [date] For: [audience] 1. Purpose [Why this report exists, in a sentence or two.] 2. Background [What the reader needs to know.] 3. Findings • [point, with a figure or fact] • [point, with a figure or fact] 4. Recommendations • [what you suggest and why] 5. Next steps [Action — owner — due date]
Plan an online search, log sources and checks, and hand over what you found.
INTERNET RESEARCH RECORD — [research topic] Prepared by: [name, role] Requested by: [name, role] Due: [date/time] File name: [YYYY-MM-DD_Topic_Version] 1. Research brief Work task / question: [what must be researched] Objective: [what the research must establish] Audience and purpose: [who will use it and what decision/action it supports] Required presentation: [report / comparison / email / other, including level of detail] Limits: [time, budget, location, number of options, authority or privacy limits] Stakeholder consultation: [who was consulted, date and what was clarified] 2. Search plan Approved application and search engine: [browser and search engine] Potential source types: [government / regulator / manufacturer / supplier / other] Planned search terms: • [search phrase] • [refined or alternative phrase] • [site, location or date limiter] 3. Search and source log | Search terms used | Source title and organisation | URL | Date accessed | Key information | Source check / limitations | |-------------------|-------------------------------|-----|---------------|-----------------|----------------------------| | [ ] | [ ] | [ ] | [ ] | [ ] | [relevance, authority, currency, accuracy, purpose] | | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | Help function or issue record: [help used, issue and outcome / not required] 4. Findings [Summarise the information collected. Compare options where required. Keep verified facts separate from assumptions and note any missing or conflicting information.] 5. Result for the stakeholder Conclusion or recommendation: [what the evidence supports and why] Conditions / cautions: [price, availability, exclusions, verification still required] Delivered to: [stakeholder] Channel: [email / Teams / shared drive / meeting] Delivered on: [date/time] Supervisor review required/completed: [details / not required] Saved to: [approved Nexus location]
Plan your slides — one idea per slide, from the hook to next steps.
PRESENTATION OUTLINE — [topic] Audience: [who] Length: [minutes] Goal: [what they should know/do after] Slide 1 — Title: [title, your name, date] Slide 2 — Why this matters: [the hook / problem] Slide 3 — Key point 1: [+ one visual or example] Slide 4 — Key point 2: [+ one visual or example] Slide 5 — Key point 3: [+ one visual or example] Slide 6 — Summary & next steps: [what you're asking for] Slide 7 — Questions / contact: [your email] Tips: one idea per slide, few words, large readable text, proofread before you present.
Match the cash book to the bank statement and list what explains the gap.
BANK RECONCILIATION Account: [account name / number] As at: [date] Prepared by: [name] Date: [date] Balance as per cash book (general ledger): $[amount] Add/less reconciling items: • [unpresented payment / deposit not yet shown] $[+/- amount] • [bank fee not yet in cash book] $[+/- amount] Adjusted cash book balance: $[amount] Balance as per bank statement: $[amount] Reconciled? [Yes / No] If no, list the difference(s) to investigate: [ ]
Record a figure that doesn't match — expected, recorded, difference and action.
DISCREPANCY LOG Ref: [DSC-...] Date found: [date] Logged by: [name] Related entry: [INV/CP/CR/account ref] Type: [transposition / wrong amount / quantity mismatch / overdue / duplicate] Description: [what doesn't match] Expected: $[amount] Recorded: $[amount] Difference: $[amount] Risk: [Low / Medium / High] Action taken / recommended: [ ] Escalated to: [name, if approval needed] Status: [Open / Resolved]
Work a problem from facts to cause to options to a recommendation.
PROBLEM-SOLVING RECORD Issue: [short description] Raised by: [name] Date: [date] Prepared by: [your name, role] Affects: [who / what / how often] 1. The problem [What is actually happening — facts, not assumptions. How often, since when, who it affects.] Facts I've confirmed: [ ] Assumptions still to check: [ ] 2. Technique applied Technique: [Five Whys / cause and effect / brainstorming / pros and cons] Who was involved: [ ] Date: [ ] What it showed: [ ] [Copy this block for each technique you use.] 3. Cause [The cause you can actually do something about.] 4. Options considered | Option | Pros | Cons | Effort | |--------|------|------|--------| | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | 5. Recommendation Recommended option: [ ] Why: [ ] Needs approval from: [name] — see the approval procedure. 6. Blockers I hit [Anything that got in the way — missing information, assumptions, time pressure — and what you did about it.] 7. Feedback received From: [name, role] Date: [date] On my questions: [ ] On my questioning style: [ ] On my technique: [ ] Improvements I'll make: [ ] Saved to: [location] File name: [YYYY-MM-DD_Topic_Version]
Safety & sustainability
Report resource usage against targets — printing, power, waste and recycling.
RESOURCE USAGE REPORT — [month/year] Metric | This period | Last period | Note -------|-------------|-------------|----- Printing (pages) | [n] | [n] | [trend] Paper (reams) | [n] | [n] | Electricity (kWh) | [n] | [n] | Landfill (t) | [n] | [n] | Recycling (t) | [n] | [n] | Progress against targets: • [target] — [where we're at] Issues / actions: • [environmental hazard or improvement] — [owner] — [due]
Write up a hazard you've spotted, its risk and a suggested control.
HAZARD REPORT Reported by: [name] Date: [date] Location: [site / area] Hazard: [what you saw] Risk: [Low / Medium / High] Immediate action: [what you did to make it safe, if anything] Suggested control: [how it could be fixed] (You can also log this on the portal: /whs/report)
Record an injury, near miss or property damage clearly and quickly.
INCIDENT REPORT Reported by: [name] Date/time: [date, time] Location: [site / area] Type: [Injury / Near miss / Property / Other] What happened: [describe clearly — what, where, who] People involved: [names] First aid / action taken: [details] Supervisor notified: [name, time] (In an emergency, call 000 first. Log via /whs/report)
A daily once-over of your workstation and shared areas before you start.
PRE-START CHECK — [name] — [date] Workstation: [ ] Chair adjusted and supportive [ ] Monitor at eye level, arm's length away [ ] Keyboard/mouse comfortable, wrists straight [ ] Cables tucked away Area: [ ] Lighting adequate, minimal glare [ ] Walkways clear [ ] Leads/power boards undamaged Shared spaces: [ ] Printer area clear [ ] Kitchen clean and dry [ ] Exits clear; first aid kit location known Anything to report? [note + log via /whs/report]
Log stationery, printing and e-waste through the month for the working group.
RESOURCE USAGE LOG — [site] — [month] Date | Item | Quantity | Notes -----|------|----------|------ [date] | Stationery order | [n] | [reason] [date] | E-waste collected | [n items] | [type] [date] | Printing (pages) | [n] | [team] Summary: [totals / anything to flag for the Sustainability Working Group]
IT & systems
Set out an IT problem or request with category, priority and what you've tried.
IT SUPPORT REQUEST Name: [your name] Location: [site] Category: [Access / Hardware / Software / Network / Mobile / Security] Priority: [Low / Medium / High / Critical] Subject: [short summary] Details: [what's happening, and what you've already tried] (Log it on the portal for a reference number: /it/service-desk)
Plan a small tool in pseudocode — inputs, outputs, steps and test ideas.
ALGORITHM PLAN — [tool name]
Goal: [what the tool should do, in one sentence]
Inputs: [what it reads or is given]
Outputs: [what it produces]
Steps (pseudocode):
START
GET [inputs]
FOR each [item] in [list]
SET priority based on rules:
IF [condition] THEN priority = [value]
ELSE IF [condition] THEN priority = [value]
ELSE priority = [value]
SET timeframe for that priority
BUILD message = [ID] + priority + timeframe
DISPLAY message
END FOR
END
Test ideas: [list the cases you'll check, including edge cases] Hand a finished tool to its requester with testing results and usage notes.
HANDOVER NOTE — [tool name] From: [your name] To: [requester] Date: [date] What it does: [one or two lines] Meets the spec? [Yes / No — note anything outstanding] Testing: • Test cases run: [all / which] • Result: [all passed / issues] • Known issue fixed: [yes — short description] How to use it: [a line or two] Notes / things to watch: [ ]
Ask a manager to sign off on a change, with cost, risk and options considered.
APPROVAL REQUEST To: [approver / manager] From: [your name, role] Date: [date] Re: [what you need approved — e.g. grant folder access, reinstall software] What: [the change, briefly] Why: [the reason / who it affects] Cost/risk: [any cost, downtime or risk] Options considered: [the alternatives and why this one] Approved? [ ] By: [name] Date: [ ]
Plan a change step by step, including who's affected and how to back out.
IMPLEMENTATION PLAN — [change] Owner: [name] Planned date/time: [when] Approval: [ref, if needed] Steps: 1. [step] 2. [step] 3. [test step] Who's affected / who to tell: [ ] If it goes wrong (back-out): [how you'll undo it]
Confirm a fix worked, nothing else broke, and the record is closed off.
EVALUATION — [what you changed] [ ] The original problem is fixed (tested) [ ] Tested with the user / against the expected result [ ] Nothing else broke as a result [ ] User confirms it's resolved [ ] Cause and fix recorded on the ticket/record [ ] Ticket closed / follow-up booked Notes: [ ]
Career & wellbeing
A clean layout for your profile, key skills, experience and training.
[YOUR NAME] [Phone] | [Email] | [Suburb, State] PROFILE [2–3 lines: who you are, your strengths and what you're looking for.] KEY SKILLS • [skill] • [skill] • [skill] • [skill] WORK EXPERIENCE [Role] — [Organisation] [Start]–[End] • [What you did and a result, starting with an action word.] • [What you did and a result.] EDUCATION & TRAINING [Course / certificate] — [Provider] [Year] REFEREES Available on request.
Rate your confidence across key skills and pick what to build next.
SKILLS CHECK-IN — [your name] — [date] Rate yourself: 1 (new to this) – 5 (very confident) Skill / area | Now (1–5) | Want to build? -------------------------------------|-----------|--------------- Communication (written & verbal) | | Working in a team | | Customer service | | Digital tools / software | | Time management & priorities | | [Role-specific skill] | | Top 2 things I'd like to build next: 1. [ ] 2. [ ] Bring this to your next development chat with your manager.
Set growth goals with steps, support and review dates, agreed with your manager.
DEVELOPMENT PLAN Name: [your name] Manager: [name] Review date: [date] Goal 1: [what you want to achieve] Why it matters: [link to your role or where you're heading] Steps: [what you'll do] Support/learning: [course, mentoring, on-the-job] By when: [date] Goal 2: [what you want to achieve] Steps: [ ] Support/learning: [ ] By when: [ ] Agreed by: [you] / [manager] — [date]
Put your hand up for an internal role — why you're interested and what you bring.
EXPRESSION OF INTEREST — INTERNAL ROLE To: [hiring manager / People & Culture] From: [your name, current role] Role: [role you're interested in] Date: [date] Why I'm interested: [A few lines on why the role appeals and how it fits your goals.] What I bring: • [relevant strength or experience] • [relevant strength or experience] I've discussed this with my current manager: [Yes / Not yet]
Prepare for a conversation with your supervisor about what's affecting you at work.
WELLBEING CONVERSATION PLAN Prepared by: [your name, role] Date: [date] Talking to: [supervisor name, role] This plan is yours. You don't have to share it with anyone. 1. The factors affecting me List both directions — what's helping as well as what isn't. Mark each [W] workplace or [P] personal. Making things harder | Helping / worth keeping • [W] [ ] | • [W] [ ] • [W] [ ] | • [P] [ ] • [P] [ ] | • [P] [ ] 2. How they connect to my role [Which workplace factors relate to the job I actually do, and how the personal ones interact with them. The chain, not the list — e.g. "late study nights + reception interruptions -> errors in the pack -> rework -> staying back".] Effect I can point to: [what's actually changed in my work] 3. Sorting them Mine to change: [ ] My supervisor's to change: [ ] Nobody's to change right now: [ ] 4. My communication approach Style I'll use: [assertive] Why it suits this: [ ] Styles I'll avoid: [passive — because ... / aggressive — because ...] 5. My method How I'll ask for it: [Teams / one-to-one / calendar invite] Where we'll talk: [private room — not the desk] When: [date, time] How long: [~15 min] Why this method: [ ] How I'll confirm it: [short email after] 6. What I'll say Opening line (one sentence, says what it's about): [ ] The facts — what, since when, how often: [ ] The positives — what's working, what I want to keep: [ ] The effect — on my work and on me: [ ] My ask (one clear thing, or two options): [ ] Question I'll finish with: [e.g. "What would you suggest?"] Good outcome: [ ] I'd settle for: [ ] 7. If I get a negative response Likely response | What I'll say | Fallback ask "[ ]" | [ ] | [ ] "[ ]" | [ ] | [ ] Ground rules for myself: stay factual, no blaming, don't apologise my way out of it, ask a question rather than defend myself, don't escalate on the spot. If it's still unresolved: [People & Culture ext. 4100 / grievance process] 8. After the conversation Date held: [ ] Outcome / what we agreed: [ ] Confirmed by email: [Yes / No] Follow-up date: [ ] Review — how did it go? Did they understand what I raised? [ ] Did I stay assertive? [ ] Was the method right? [ ] Did I get an outcome, and is it happening? [ ] What I'd do differently next time: [ ]
Compare support options and record how to access the ones you choose.
WELLBEING RESOURCE ACCESS NOTE Prepared by: [your name, role] Date: [date] 1. Resources I reviewed | Resource | Formal / informal | What it offers | Suits my situation? | |----------|-------------------|----------------|---------------------| | [ ] | [ ] | [ ] | [Yes/No — why] | | [ ] | [ ] | [ ] | [Yes/No — why] | | [ ] | [ ] | [ ] | [Yes/No — why] | | [ ] | [ ] | [ ] | [Yes/No — why] | 2. Selected — formal resource Resource: [ ] Why I chose it: [what it gives me that the others don't] How to access it: [the actual steps — number to call, code, site, who to ask] 1. [ ] 2. [ ] Cost: [ ] Confidential? [ ] Do I need approval or to tell anyone? [ ] Available: [hours / wait time] Accessed on: [date] What happened: [ ] 3. Selected — informal resource Resource: [ ] Why I chose it: [ ] How to access it: [the actual steps — who, where, when] 1. [ ] 2. [ ] Anything I need to arrange first? [ ] Accessed on: [date] What happened: [ ] 4. Why both [What the formal one does that the informal one can't, and the other way round.] 5. Keeping it handy Where I've saved this: [ ] Anything to book or repeat: [ ] Source: Wellbeing Support Policy (/hr/policies/wellbeing-support)
Separate your values from your attitudes, and work out how both show up at work.
ATTITUDES AND VALUES REVIEW Prepared by: [your name, role] Date: [date] This is yours. You choose what you share and with whom. 1. Attitude or value? — getting the difference straight In your own words: A value is: [ ] An attitude is: [ ] Two examples from my own work: | One of my values | One of my attitudes | How I can tell them apart | |------------------|---------------------|---------------------------| | [broad, stable, no target — e.g. accuracy] | [specific target — e.g. "figures without a source can't be trusted"] | [scope / stability / where it came from] | Differences that matter here: Scope: [value = broad ... attitude = about one thing] Stability: [ ] Where it came from: [ ] How visible: [ ] 2. My values — worked out from evidence, not from a list | Moment from the last month | What I did | Attitude behind it | Value underneath | |-----------------------------|------------|--------------------|------------------| | [something that went well] | [ ] | [ ] | [ ] | | [something that annoyed me] | [ ] | [ ] | [ ] | | [where I dug my heels in] | [ ] | [ ] | [ ] | My top three values at work: 1. [ ] 2. [ ] 3. [ ] 3. The role of values and attitudes here Nexus values (see /about/values) and where I see each one in my own work: | Nexus value | What it asks of my role | Where I see it in what I do | |--------------------|-------------------------|------------------------------| | Customer first | [ ] | [ ] | | Better together | [ ] | [ ] | | Do the right thing | [ ] | [ ] | | Keep improving | [ ] | [ ] | | Safe and well | [ ] | [ ] | Where my values and Nexus's line up: [ ] Where they pull differently, and what I do about it: [ ] Attitudes I hold about specific parts of my work, and their effect: | The thing | What I think | What I feel | What I do | Effect on my work or others | |-----------|--------------|-------------|-----------|------------------------------| | [ ] | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | [ ] | 4. How my values and attitudes connect Chain (read it backwards from the behaviour): Behaviour I noticed: [ ] Attitude behind it: [ ] Value underneath: [ ] Where one value produced two opposite attitudes: [ ] Where two of my values collided, and which won: [ ] What I want to keep, and what I want to change: [ ] 5. Other people's values and attitudes | Who I spoke to | What they said they value | How it shows in their work | How it differs from mine | |----------------|---------------------------|----------------------------|--------------------------| | [name, role] | [ ] | [ ] | [ ] | | [name, role] | [ ] | [ ] | [ ] | What the difference gives the team: [ ] Where it causes friction, and what helps: [ ] What talking to them showed me about myself: [ ] Effect of this mix on the working environment: [ ] Source: Attitudes and values at work (/it/knowledge-base/attitudes-and-values)
An honest read on how adaptable, motivated, committed and resilient you actually are at work.
WORK-STYLE SELF-ASSESSMENT Prepared by: [your name, role] Date: [date] Covering: [period, e.g. the last three months] 1. What makes my work effective Rate each: 1 (rarely) - 5 (consistently). Add the evidence, not just the number. | Factor | 1-5 | Evidence from real work | Me or the conditions? | |-------------------------|-----|-------------------------|-----------------------| | Knowing what's expected | [ ] | [ ] | [ ] | | Skill and knowledge | [ ] | [ ] | [ ] | | Planning and sequencing | [ ] | [ ] | [ ] | | Attention and focus | [ ] | [ ] | [ ] | | Accuracy and checking | [ ] | [ ] | [ ] | | Motivation | [ ] | [ ] | [ ] | | Energy and pacing | [ ] | [ ] | [ ] | | Asking for help | [ ] | [ ] | [ ] | | Tools, access and setup | [ ] | [ ] | [ ] | | Workload fit | [ ] | [ ] | [ ] | Strongest two: [ ] Weakest two: [ ] Of the weak ones, what's mine to change: [ ] What needs my manager: [ ] 2. Adaptability and flexibility | Change that landed | What I actually did | Adaptable or rigid? | Effect on the team's goal | |--------------------|---------------------|---------------------|---------------------------| | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | How willing I am to change direction (not just able): [ ] Impact of that on organisational goals — good and bad: [ ] Where flexibility should stop, and what I escalate instead: [ ] 3. What motivates me | Feature | Mine | |---------|------| | Source — intrinsic or extrinsic | [ ] | | Direction — towards, or away from | [ ] | | Main drivers (achievement / mastery / autonomy / belonging / security / recognition / purpose) | [ ] | | Intensity — where it's strong, where it's flat | [ ] | | Consistency — steady or in bursts | [ ] | | Triggers that switch me on | [ ] | | Drains that flatten me | [ ] | Where my motivation and the team's goals line up: [ ] Where they don't, and what I'll put in place instead of willpower: [ ] What this means for the development I should ask for: [ ] How knowing this changes how I plan my own goals: [ ] 4. Commitment and resilience Commitment — where I follow through, and where things quietly slip: Follow through: [ ] Slips: [ ] What I do when the work stops being interesting: [ ] Role commitment plays in my team: [ ] Resilience — the recovery, not the absence of trouble: | Setback | How I reacted | How long to get functional | What I'd do differently | |------------------|---------------|----------------------------|-------------------------| | [an error] | [ ] | [ ] | [ ] | | [hard feedback] | [ ] | [ ] | [ ] | | [a busy stretch] | [ ] | [ ] | [ ] | Role resilience plays in my workplace: [ ] Signs I'm wearing thin, and what I do then: [ ] 5. What I'd conclude Two things about how I work that I hadn't put into words before: [ ] What I want to check against someone else's view: [ ] Source: Knowing how you work (/it/knowledge-base/self-awareness-at-work)
Turn what you have noticed about yourself into goals, strategies, evidence and review dates.
SELF-AWARENESS ACTION PLAN Name: [your name, role] Manager: [name] Version: [v1] Date: [date] 1. Starting picture | Strength | How I know (evidence, feedback, role profile) | Where it's useful | |----------|----------------------------------------------|-------------------| | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | | Weakness / gap | How I know | Where it shows up | Strength overused? | |----------------|------------|-------------------|--------------------| | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | Blind spot someone else pointed out: [ ] What this tells me about my self-awareness: [ ] 2. Goals — two or three, no more Goal 1 Situation: [when and where this applies] Behaviour: [what I'll visibly do differently] Standard: [how well, how often, by when] Evidence: [what will exist afterwards] Goal 2 Situation: [ ] Behaviour: [ ] Standard: [ ] Evidence: [ ] Goal 3 (optional) Situation: [ ] Behaviour: [ ] Standard: [ ] Evidence: [ ] 3. Strategies | Goal | Strategy (the mechanism, not "try harder") | Type | Starts | |------|--------------------------------------------|------|--------| | 1 | [ ] | [trigger-response / structural / checklist / reflection / practice / feedback loop / learning] | [ ] | | 1 | [ ] | [ ] | [ ] | | 2 | [ ] | [ ] | [ ] | | 3 | [ ] | [ ] | [ ] | 4. Support I need | Who | What I need from them | Asked? | Agreed | |-------------|-----------------------|--------|--------| | [manager] | [ ] | [ ] | [ ] | | [colleague] | [ ] | [ ] | [ ] | Learning, access or time required: [ ] 5. Evidence and review | Goal | Evidence I'll keep | Where it's saved | Check-in dates | Review with | |------|--------------------|------------------|----------------|-------------| | 1 | [ ] | [ ] | [ ] | [ ] | | 2 | [ ] | [ ] | [ ] | [ ] | | 3 | [ ] | [ ] | [ ] | [ ] | 6. Feedback on this plan | Who | Date | What they said | What I'm changing | Not changing — why | |-----|------|----------------|-------------------|--------------------| | [ ] | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | [ ] | The one piece I didn't want to hear: [ ] Loop closed — told them what I changed: [Yes / No, date] 7. Revision history | Version | Date | What changed | Prompted by (feedback / work change / goal met) | |---------|------|---------------|------------------------------------------------| | v1 | [ ] | First version | [ ] | | v2 | [ ] | [ ] | [ ] | | v3 | [ ] | [ ] | [ ] | 8. Monitoring | Goal | Date checked | Being used? | Evidence to date | On track / adjust | |------|--------------|-------------|------------------|-------------------| | 1 | [ ] | [ ] | [ ] | [ ] | | 2 | [ ] | [ ] | [ ] | [ ] | | 3 | [ ] | [ ] | [ ] | [ ] | 9. Where I got to My ability to improve my own performance — what the evidence says: [ ] What worked, and why: [ ] What didn't, and why: [ ] Goals closed out: [ ] Ongoing development I'll pursue next, and why it fits what motivates me: 1. [opportunity — stretch work / cover / working group / shadowing / short course / EOI] 2. [ ] Next review date: [ ] With: [ ] Agreed by: [you] / [manager] — [date] Source: Writing a self-awareness action plan (/it/knowledge-base/self-awareness-action-plans)
One short entry per piece of work — what you noticed about yourself, what you did, what happened.
WORK REFLECTION LOG Name: [your name, role] Log covering: [dates] Write each entry the same day. A week later you'll have edited the memory. ENTRY 1 Date: [ ] The work: [what it was — name it specifically] Goal it relates to: [from my action plan] What I noticed about myself at the time: [reaction, thought, pattern] What I did — old habit or new strategy? [ ] What happened as a result: [ ] Anything anyone said: [ ] What I'd do differently: [ ] Improvement since last time on this kind of work: [ ] ENTRY 2 Date: [ ] The work: [a different piece of work] Goal it relates to: [ ] What I noticed about myself at the time: [ ] What I did — old habit or new strategy? [ ] What happened as a result: [ ] Anything anyone said: [ ] What I'd do differently: [ ] Improvement since last time on this kind of work: [ ] ENTRY 3 Date: [ ] The work: [a third, different piece of work] Goal it relates to: [ ] What I noticed about myself at the time: [ ] What I did — old habit or new strategy? [ ] What happened as a result: [ ] Anything anyone said: [ ] What I'd do differently: [ ] Improvement since last time on this kind of work: [ ] WHEN SOMETHING CHANGED ON ME | Date | What changed, and how late | My first reaction | What I did with it | Result | |------|----------------------------|-------------------|--------------------|--------| | [ ] | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | [ ] | Was my reaction the one I wanted? [ ] What I'll do next time the plan moves: [ ] WORKING WITH OTHERS | Date | Who | What I noticed about how I came across | What I adjusted | How it landed | |------|-----|----------------------------------------|-----------------|---------------| | [ ] | [ ] | [ ] | [ ] | [ ] | | [ ] | [ ] | [ ] | [ ] | [ ] | ACROSS THE WHOLE LOG Pattern that shows up in more than one entry: [ ] Where I improved, and what the evidence is: [ ] Where I didn't, and what I think is behind it: [ ] What goes back into the action plan: [ ] Source: Writing a self-awareness action plan (/it/knowledge-base/self-awareness-action-plans)
No templates match. Try a different word or switch back to All.
Writing to a customer? See also the customer scripts & templates.