Home / Commons / Templates

Templates

Templates to copy, adapt and use.

Editable starting points for the paperwork good security depends on: a policy, a checklist, two logs and an inventory. Download them, change them, make them yours.

FreeNo sign-upCC BY 4.0

Template 01

Acceptable use policy (small organization)

Sets out, in plain words, how staff and volunteers should use the organization’s accounts, devices and data, and what to do when something goes wrong.

How to adapt it

Replace everything in [square brackets]. Delete rules that do not apply rather than leaving them in. Read it through with a manager and, if you employ people, check it against your employment contracts and local law before you adopt it.

Preview the text
ACCEPTABLE USE POLICY
=====================

[Organization name]
Version [1.0], adopted [date] by [board or director]. Next review: [date].

  How to use this template: replace everything in [square brackets], delete anything that does not apply,
  and keep it short enough that people will read it. This is a starting point, not legal advice.
  Check it against your employment contracts and local law before adopting it.

1. Why we have this policy
--------------------------

We hold information about the people we serve, our staff, volunteers and supporters. They trust us to keep it safe.
This policy explains how everyone who works with us should use our accounts, devices and data, so that one mistake
does not put that trust at risk.

2. Who it applies to
--------------------

Everyone who uses [Organization name]'s accounts, devices or data: employees, volunteers, trustees or board members,
contractors and interns. It applies wherever you work, including at home.

3. Accounts and passwords
-------------------------

- Use your own account. Never share your password or let someone else sign in as you.
- Use a different password for every work account. Use [the password manager we provide / a password manager].
- Turn on multi-factor authentication (a second step after the password) wherever it is offered. It is required for
  email, [banking], [our client database] and [other systems].
- If you think anyone else knows your password, change it and tell [name or role] straight away.

4. Devices
----------

- Lock your screen when you step away. Devices must lock automatically after [a few] minutes.
- Leave automatic updates switched on. Restart when asked.
- Work devices must have disk encryption switched on. [Name or role] can check this for you.
- If you use a personal phone or computer for work, it must have a screen lock, receive security updates and
  [other requirements]. Keep work files in [approved places], not on the device itself.
- Report a lost or stolen device to [name or role] immediately, day or night, on [phone number].

5. Email, messages and calls
----------------------------

- Be suspicious of unexpected messages asking you to sign in, open an attachment, pay something or keep a secret,
  even if they appear to come from someone you know.
- Never change bank or payment details because of an email alone. Call back on a number you already had, and have a
  second person approve the change.
- If you clicked something you should not have, say so straight away. Reporting quickly matters far more than the
  mistake, and nobody will be blamed for reporting.

6. Information about people
---------------------------

- Store personal information only in [approved systems, e.g. our case management system and shared drive].
- Do not forward work email to personal accounts, or copy personal information to personal devices, USB drives or
  personal cloud storage.
- Share only what the other person needs. Check the recipient before you press send.
- Do not leave printed personal information on desks or printers. Shred it when it is no longer needed.

7. New software and online services
-----------------------------------

Ask [name or role] before signing up for any online service that will hold the organization's information, even if
it is free. This lets us keep track of where our data is and close accounts when people leave.

8. Personal use
---------------

Reasonable personal use of work devices and accounts is [allowed / not allowed], as long as it does not interfere
with work, break the law or put our information at risk. [Add any specific rules.]

9. Monitoring
-------------

[Describe honestly any monitoring the organization does, for example security alerts on sign-ins or filtering of
malicious websites, and why. If you do not monitor, say so. Any monitoring must be lawful and proportionate.]

10. When you leave or change role
---------------------------------

Return all devices, documents and keys on your last day. Your accounts will be closed or handed over, and shared
passwords you knew will be changed. Do not take copies of the organization's information with you.

11. Reporting a problem
-----------------------

Tell [name or role] on [phone number] or [email] as soon as you notice anything wrong: a lost device, a suspicious
message, a mistake, or something that just seems odd. Out of hours, call [phone number].

12. If this policy is not followed
----------------------------------

Breaking this policy may lead to [access being removed / action under our disciplinary procedure]. Honest mistakes
that are reported promptly are treated as a chance to learn.

Acknowledgement
---------------

I have read and understood this policy.

Name: ______________________________

Signature: __________________________   Date: ______________

------------------------------------------------------------
Template by Moraph for Good (https://moraph.org/commons/templates). Free to copy and adapt under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attribution: "Moraph for Good".

Template 02

Joiners, movers and leavers checklist

Makes sure people get the access they need when they start, lose what they no longer need when their role changes, and lose all of it on the day they leave.

How to adapt it

Replace the system names with your own (email, file storage, finance, client database, building access). Keep one completed copy per person with your records. Add the person responsible for each step.

Preview the text
JOINERS, MOVERS AND LEAVERS CHECKLIST
=====================================

Use one copy per person. Keep the completed copy with your records.

  How to use this template: replace [system names] with the systems your organization actually uses, and name who is
  responsible for each step. Old accounts are a door nobody is watching, so the leaver section matters most.

Name: ______________________________   Role: ______________________________

Manager: ___________________________   Staff / volunteer / contractor: ____________

Joiner
------

Start date: ______________

Before day one:
- [ ] Agree what access the role needs, and nothing more. Owner: ________
- [ ] Create their email account with multi-factor authentication required. Owner: ________
- [ ] Add them to [file storage], [client database], [finance system] at the right level. Owner: ________
- [ ] Prepare a device: updates on, disk encryption on, screen lock on. Record it in the inventory. Owner: ________
- [ ] Add them to the incident contact list and phone tree. Owner: ________

First day:
- [ ] They set up multi-factor authentication and a password manager. Owner: ________
- [ ] They read and sign the acceptable use policy. Owner: ________
- [ ] Show them how to report a suspicious message, a lost device or a mistake. Owner: ________
- [ ] Give keys, building passes or alarm codes, and record them. Owner: ________

First week:
- [ ] Check they can reach everything they need, and nothing they do not. Owner: ________

Mover (change of role)
----------------------

Date of change: ______________   New role: ______________________________

- [ ] List the access the new role needs. Owner: ________
- [ ] Remove access the old role needed but the new one does not. Owner: ________
- [ ] Add or remove administrator rights. Administrators use a separate admin account. Owner: ________
- [ ] Change shared passwords for anything they no longer need. Owner: ________
- [ ] Update the inventory, the incident plan and the contact list if their responsibilities changed. Owner: ________

Leaver
------

Last day: ______________   Leaving on good terms? [ ] Yes [ ] No (if no, remove access before telling them, where lawful)

Before the last day:
- [ ] List every account, device, key and system they use, including services they signed up for themselves. Owner: ________
- [ ] Agree who takes over their files, email and responsibilities. Owner: ________
- [ ] Hand over anything only they know how to do, in writing. Owner: ________

On the last day:
- [ ] Disable their email and every other account. Owner: ________   Time done: ________
- [ ] Remove them from administrator groups, shared mailboxes and distribution lists. Owner: ________
- [ ] Sign them out of all sessions and remove their multi-factor devices. Owner: ________
- [ ] Change every shared password they knew (Wi-Fi, shared accounts, alarm codes). Owner: ________
- [ ] Collect devices, keys and passes. Owner: ________
- [ ] Remove them from bank mandates, payment approvals and authorised contacts with suppliers. Owner: ________

After they leave:
- [ ] Forward or archive their mailbox as agreed, then close it after [period]. Owner: ________
- [ ] Wipe and reassign or retire their device. Update the inventory. Owner: ________
- [ ] Update the incident plan and contact list. Owner: ________
- [ ] Transfer ownership of any services they signed up for, or close them. Owner: ________

Completed by: ______________________   Date: ______________

------------------------------------------------------------
Template by Moraph for Good (https://moraph.org/commons/templates). Free to copy and adapt under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attribution: "Moraph for Good".

Template 03

Backup and restore log

A simple record that your backups exist, are kept where ransomware cannot reach them, and have actually been restored. A backup you have never restored is a hope, not a plan.

How to adapt it

Use the spreadsheet (.csv) for the log itself; it opens in Excel, Numbers, Google Sheets or LibreOffice. Add a row every time you check a backup or test a restore, and note anything that went wrong.

Preview the text
BACKUP AND RESTORE LOG
======================

[Organization name]

  How to use this template: add a row every time you check a backup or test a restore. Test restores regularly:
  restore something real, check it opens, and write down how long it took. The example row is there to show the
  format; delete it.

What we back up
---------------

System or data         | How it is backed up           | Where the backup is kept      | Can ransomware reach it? | Who can restore it
-----------------------+-------------------------------+-------------------------------+--------------------------+-------------------
[Shared files]         | [Nightly to an offline drive] | [Office safe, swapped weekly] | [No: disconnected]       | [Name]
[Finance system]       | [Supplier's own backup]       | [Supplier's data centre]      | [Ask the supplier]       | [Supplier]
[Email]                | [ ]                           | [ ]                           | [ ]                      | [ ]
[Client database]      | [ ]                           | [ ]                           | [ ]                      | [ ]
[System configuration] | [ ]                           | [ ]                           | [ ]                      | [ ]

Log
---

Date         | System or data | Backup type     | Where kept    | Checked by | Restore tested? | What was restored    | Time taken   | Result   | Problems and follow-up
-------------+----------------+-----------------+---------------+------------+-----------------+----------------------+--------------+----------+-----------------------
[2026-01-15] | [Shared drive] | [Offline drive] | [Office safe] | [Name]     | [yes]           | [One finance folder] | [20 minutes] | [worked] | [None]
             |                |                 |               |            |                 |                      |              |          |
             |                |                 |               |            |                 |                      |              |          |

------------------------------------------------------------
Template by Moraph for Good (https://moraph.org/commons/templates). Free to copy and adapt under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attribution: "Moraph for Good".

Template 04

Incident contact sheet

Every number you might need when systems are down, in one place, on paper. The longer companion to the one-page incident plan.

How to adapt it

Fill in every row you can, delete the ones that do not apply, and check each number out of hours. Print it and keep copies away from the office network.

Preview the text
INCIDENT CONTACT SHEET
======================

[Organization name]. Last checked: [date] by [name].

  How to use this template: fill in every row you can and delete those that do not apply. Call each number once,
  out of hours, to check it works. Print it and keep copies somewhere other than your office network.

Role                                    | Organization or person | Phone | Out-of-hours phone | Email or website | Reference             | Notes
----------------------------------------+------------------------+-------+--------------------+------------------+-----------------------+------------------------------------------------
Incident lead                           |                        |       |                    |                  |                       | Makes decisions in the first hour
Deputy                                  |                        |       |                    |                  |                       | Decides if the lead cannot be reached
Cyber insurer (claims line)             |                        |       |                    |                  | Policy number:        | Many policies require a call before hiring help
IT support                              |                        |       |                    |                  |                       |
National cyber security agency          |                        |       |                    |                  |                       | Where to report an incident
Police (cybercrime or non-emergency)    |                        |       |                    |                  |                       |
Bank (fraud line)                       |                        |       |                    |                  | Account:              |
Lawyer                                  |                        |       |                    |                  |                       |
Data protection regulator               |                        |       |                    |                  |                       | If personal data may be involved
Email and productivity platform support |                        |       |                    |                  | Account or tenant ID: |
Key software vendor                     |                        |       |                    |                  |                       |
Internet provider                       |                        |       |                    |                  | Account:              |
Board chair or director                 |                        |       |                    |                  |                       |
Communications or press contact         |                        |       |                    |                  |                       |
Funders to inform                       |                        |       |                    |                  |                       |

Staff phone tree
----------------

Who calls whom if email is down. Keep personal numbers here only with each person's agreement.

Caller          | Calls  | Phone
----------------+--------+------
[Incident lead] | [Name] |
[Name]          | [Name] |

------------------------------------------------------------
Template by Moraph for Good (https://moraph.org/commons/templates). Free to copy and adapt under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attribution: "Moraph for Good".

Template 05

Device and account inventory

A list of every device, online account and service the organization uses, who has administrator access, and where sensitive records live. You cannot protect, update or recover what you have forgotten exists.

How to adapt it

Use the two spreadsheets: one for devices, one for accounts and services. Start with what you know, then ask staff and volunteers what they signed up for. Review it when people join or leave.

Preview the text
DEVICE AND ACCOUNT INVENTORY
============================

[Organization name]. Last reviewed: [date] by [name].

  How to use this template: list every device and every online account or service, including ones volunteers or
  former staff signed up for on the organization's behalf. Note who has administrator access to each. Review it when
  people join or leave, and a few times a year. The example rows show the format; delete them.

Devices
-------

Label    | Type      | Make and model | Assigned to | Operating system   | Still gets updates? | Auto updates on? | Encrypted? | Screen lock? | Where kept | Notes
---------+-----------+----------------+-------------+--------------------+---------------------+------------------+------------+--------------+------------+---------------------------------------
[LAP-01] | [Laptop]  | [ ]            | [Name]      | [ ]                | [yes]               | [yes]            | [yes]      | [yes]        | [Office]   |
[PHN-01] | [Phone]   | [ ]            | [Name]      | [ ]                | [ ]                 | [ ]              | [ ]        | [ ]          | [ ]        |
[Router] | [Network] | [ ]            | [-]         | [Firmware version] | [ ]                 | [ ]              | [-]        | [-]          | [Office]   | [Admin password changed from default?]

Accounts and services
---------------------

Service                 | Used for          | Holds personal data? | Account owner | Administrators | MFA on? | Who pays | Signed up by | Last access review | How to get data out
------------------------+-------------------+----------------------+---------------+----------------+---------+----------+--------------+--------------------+--------------------
[Email platform]        | [Email, files]    | [yes]                | [Role]        | [Names]        | [yes]   | [ ]      | [ ]          | [ ]                | [ ]
[Bank]                  | [Payments]        | [yes]                | [ ]           | [ ]            | [ ]     | [-]      | [ ]          | [ ]                | [-]
[Domain registrar]      | [Website address] | [no]                 | [ ]           | [ ]            | [ ]     | [ ]      | [ ]          | [ ]                | [-]
[Client database]       | [ ]               | [ ]                  | [ ]           | [ ]            | [ ]     | [ ]      | [ ]          | [ ]                | [ ]
[Social media accounts] | [ ]               | [ ]                  | [ ]           | [ ]            | [ ]     | [ ]      | [ ]          | [ ]                | [ ]

Where sensitive records live
----------------------------

What records        | Where they are | Who can see them | Backed up?
--------------------+----------------+------------------+-----------
[Client case notes] | [ ]            | [ ]              | [ ]

------------------------------------------------------------
Template by Moraph for Good (https://moraph.org/commons/templates). Free to copy and adapt under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Attribution: "Moraph for Good".

Pairs well with

Two tools that fill in the gaps.

The incident plan builder turns your contact sheet into a one-page first-hour plan. The self-assessment tells you which of these templates to start with.

Need more than a template?

Shield gives eligible organizations a security review and help putting these into practice. A person reads every application.