The Catalpa Handbook
  • The Catalpa Handbook
    • Handbook guidelines
  • 1. ABOUT CATALPA
    • 1.1 About Catalpa
    • 1.2 Vision, Values and Strategic Plan 2022
    • 1.3 Governance at Catalpa
    • 1.4 Organisational structure of Catalpa
    • 1.5 Our projects and key contacts for each
    • 1.6 Our key products
      • Bero
        • Content
          • Exams
          • Targeting Content to Users
            • Resizing images for Bero
        • Design
        • Requirements
        • Theming
      • Gathr
      • Openly
  • 2. OUR PEOPLE AND HOW WE WORK
    • 2.1 How we work and the tools we use
      • Google Drive
      • Trello
      • Github
      • InVision
    • 2.2 Communicating internally
      • All Hands Stand-up (weekly / Mondays)
      • Tutorial Tuesdays
      • Show & Tell
      • Guide to Slack
      • Team meetings
      • Other Events
    • 2.3 Mission Driven Teams
    • 2.4 Recruitment and Onboarding
      • Hiring Guidelines
    • 2.5 How we support our people to thrive
      • Onboarding a new hire
        • Onboarding Trello
        • Onboarding buddy guide
        • 30/60/90 Day Plan
      • Goal Setting
      • Regular work/task based 1X1's
      • Quarterly Catch Up's
      • Feedback
      • Managers - Managing Underperformance
    • 2.6 Offboarding
    • 2.7 Leave and public holidays
      • Leave
      • Public Holidays
    • 2.8 Supporting our Mental Health
    • 2.9 Working from home & remotely
    • 3.0. Learning & Development Allowance
  • Page
  • 3. EXTERNAL COMMUNICATIONS
    • 3.1 Guide to Communication
      • Describing Catalpa
      • Guide to photography
      • Guide to social media
      • Writing: style guide
      • Writing: grammar
    • 3.2 Procedures for the collection, storage and use of stories, photos and video
    • 3.3 External Complaints and Feedback Policy
  • 4. PARTNERSHIP AND GROWTH INCLUDING BUSINESS DEVELOPMENT
    • 4.1 Introduction / overview
    • 4.2 Pre-bid stage including networking and partnering
      • Networking
      • Positioning for priority bids
      • Tracking bid opportunities
      • Partnering
        • Partnership brokering
        • Due diligence of downstream partners /subcontracting agencies
        • Pre-bid agreements
    • 4.3 Go / No Go
      • Go / No Go meetings
      • Selection criteria and guidelines
    • 4.4 Tender planning and preparation
      • Project planning and design pre-submission
      • Key templates and links for bid planning and preparation
      • Bid Writing - full proposal or concept note
        • How to appoint an external bid writer
        • Key templates
        • Commonly required building blocks / required materials for tenders
        • Guides
    • 4.5 After a bid has been submitted
  • 5. PROJECT AND PRODUCT CYCLE MANAGEMENT
    • 5.1 Introduction
    • 5.2 Planning and pre-submission design
      • 5.2.1 Monitoring, Evaluation & Learning
        • Project-level M&E
        • Catalpa's organisational approach to MEL
      • 5.2.2 Risk Management
      • 5.2.3 Cross-cutting issues in projects
        • Gender equality
        • Disability inclusion
    • 5.3 Mobilising a new project
      • Handover from BD team to PM team
      • Program Summary Document
      • Team Kickoff Meeting
      • Team Charter
    • 5.4 Post-contract implementation
      • Stage 1 - Learn: Design and Discovery
        • Human Centred Design
        • Our Tools
        • Creating a product
      • Stage 2: Create and Ideate
        • Our model
        • Agile Project Management
          • Getting started
          • Product design and development phases
            • 0. Contracting
            • 1. Learn
              • 1.1. Prepare
              • 1.2. Discovery
              • 1.3 Empathise
            • 2. Create
              • 2.1 Ideate
              • 2.2 Implement
            • 3. Refine
            • 4. Evaluate
          • Product Roadmap
          • Defining releases
          • Create the solution
          • Make a global plan
          • User Stories
          • Prototyping
          • Incremental development
          • UX & UI
          • Conducting tests
      • Stage 3: Refine and Release
        • Introduction and overview
        • Data privacy on a project basis
        • How-tos
          • Retrospective
        • Scrum methodology
          • Daily standup
          • Sprints
          • Sprint prep
          • Sprint meeting
        • Release
          • Epics
          • Epic selection
          • Epic planning
          • Product Q&A, deployment and implementation
          • Make it available
          • Delivery
      • Stage 4: Evaluate
        • Define the maintenance support plan and team
        • Customer support
        • Ongoing user data collection and analysis
      • Glossary of Terms
    • 5.5 Project close-out
      • Product transition and handover
      • Transition to governmen
      • SMA
      • Licenses / handover documents
      • Migrating to Gov owned data-center or cloud hosting
  • 6. POLICIES AND PROCEDURES
    • 6.1 Register of policies and compliance
    • 6.2 Policy Development Procedure
    • 6.3 Code of Conduct
    • 6.4 Data Privacy & Storage Policy
    • 6.5 Human Resources Policies
      • Breastfeeding and Work Policy
      • Occupational Health and Safety Policy
      • Domestic and Family Violence Policy
      • Gender Equality Policy
      • Disability & Discrimination Policy
      • Use of Catalpa Vehicles Policy - PNG
      • Anti-Bullying, Harassment and Discrimination Policy
    • 6.6 Safeguarding Policies, Templates and Training
      • Child Safeguarding Policy
      • Prevention of Sexual Exploitation, Assault and Harassment Policy (PSEAH)
      • Safeguarding templates
      • Safeguarding training
      • Safeguarding procedure for collecting, storing and using images / stories
    • 6.7 Financial and Asset Management
      • Fraud & Corruption Policy
      • Vehicle Use
    • 6.8 Complaints and Feedback
      • Internal Complaints and Feedback Policy
      • External Complaints and Feedback Policy
      • Whistleblower Policy
    • 6.9 Contract Development Procedure
Powered by GitBook
On this page

Was this helpful?

  1. 3. EXTERNAL COMMUNICATIONS
  2. 3.1 Guide to Communication

Writing: style guide

These simple writing guides are intended to create consistency across Catalpa. Our goal is to communicate clearly, concisely and with purpose.

Before beginning any piece of writing, take a moment to consider:

  1. Who am I writing for? (audience)

  2. What do I want this piece of writing to achieve? Is it to inform, persuade, or something else? (purpose)

  3. How can I best engage the reader? Can I choose the format (channel/medium)? Can I structure the information in a way that makes my point clearer or more interesting?

Style tips:

  • We use Lora font for headings, and Montserrat for body text.

  • Keep sentences short! Ideally, most sentences should take up no more than two lines of a Google doc (three at most). Break 👏 it 👏 up 👏.

  • Always remember that we want to write for as wide an audience as possible, and that many of our audience do not speak English as a first language. Try to avoid jargon and use simple language where possible. Whenever there is an easier way to say something, go with that. ‘Use’ instead of ‘utilise’, ‘while’ instead of ‘whilst’, ‘to’ instead of ‘in order to’.

  • Use active voice not passive voice 👊. That means you should put the subject who is doing something at the start of the sentence, not after what they’re doing: Active: ‘Our engineering team will create a Minimum Viable Product (MVP) version of the product’ ✔️ Passive: ‘A Minimum Viable Product (MVP) version will be created by our engineering team’ ❌

  • The first time you introduce an acronym into a piece of writing, write it out in full with the letters in brackets so that the reader knows from there on what you’re referring to, e.g. “Catalpa is working with the Ministry of Health (MoH). We are supporting the MoH in...”. If you’re only using an acronym a few times in the piece of writing and it’s not commonly known (e.g. the UN is commonly known vs. DIMS which is not), it’s better to just write the name out in full. Too many acronyms disrupt the flow and make writing inaccessible (and boring) 🥱.

  • We use Australian English 🇦🇺, not American English (so “organisation”, not “organization” and “centre” not “center” and so on). But if using a name, keep the original spelling (e.g. World Health Organization).

  • We don’t capitalise every word in a title unless they’re major titles (like on the cover page of a report) so instead of Titles Where Every Word Is Capitalised, you’d write a Title that might be bold, but only with the first word capitalised.

  • We also only capitalise proper nouns, i.e. the names of things, so while we may capitalise “the Hamahon Program”, we don’t need a capital when talking more broadly about how “the program achieved A, B, and C”. Same goes for talking about ‘the platform’, ‘the policy’, or ‘the government’.

  • When writing reports, think about how to ‘hook’ your reader in at the very start. Ask yourself, ‘Why is this project important and something that the client should be excited about?’ Then try to answer that question in the first few lines. Spot the difference:

“This Quarterly Progress Report is prepared for and submitted to MFAT and covers the period from August - October. It outlines the progress made against the work plan and complies with the funding agreements set out between MFAT and Catalpa International.” 😴

vs.

“The Pacific eLearning Program is aiming to help create the next generation of leaders in Pacific science. It is changing the way that science is taught to Year 10 students in four countries through Pacific Learn: an app which provides teachers with tools to make lessons relevant to the real issues facing the Pacific. This Quarterly Progress report is prepared for...” 🤩

Often we will still need to include a dry section like the first option which responds to the exact wording in the contract. But where possible, let's try to engage the client so that we can better get our message across.

PreviousGuide to social mediaNextWriting: grammar

Last updated 3 years ago

Was this helpful?

The is a fantastic free tool which will tell you how to make your text more readable! Run important text through it for advice on how to make your writing easier and more enjoyable to read.

Hemingway App