# MapleJockey field worksheets

Choose a worksheet for the decision in front of you. Each includes an original MapleJockey exercise, a fictional example and space for your findings. The sources and their publishers are credited alongside each exercise.

- Cloud procurement: Check the exit terms before choosing a cloud service
- Sales and marketing: Test whether an unsubscribe survives a contact import
- Backup and recovery: Prove a backup can restore a working file
- Research data: Hand off a dataset another researcher can interpret
- First Nations data governance: Establish who can authorize work with First Nations data
- Defence supplier procurement: Check which workspace a federal contract permits
- Domains and DNS: Plan a .ca registrar transfer that keeps email and web hosting running

## Check the exit terms before choosing a cloud service

MapleJockey worksheet · Cloud procurement · Sources reviewed 2026-11-18

Use one workload and one proposed plan to find out what you can retrieve, how long you have and who can still access retained copies.

### Working steps

1. Ask the supplier to point to the clauses covering return of data, the export window, fees and deletion. Record the contract version and the exact plan each answer covers.
2. Trace one record through production storage, backups and support tickets. For each copy, record where it is processed, who can access it, which subcontractors are involved and what happens after termination.
3. Choose one object your team would need on its first day elsewhere. Ask for a sample export and check whether another person can reconstruct that object, including its attachments and relationships.

### Worked example (fictional)

A CRM supplier offers a 30-day contact export. The sample CSV contains names and email addresses, but the account team also needs signed attachments. Record attachment retrieval as an open condition of purchase.

### Decision

Proceed with the purchase review when each essential object has a workable retrieval path and the owner accepts the documented cost, timing and remaining exposure.

### Your record

- **Workload, plan and contract version**  
  ______________________________
- **Copy or object and required format**  
  ______________________________
- **Clause or supplier evidence reference**  
  ______________________________
- **Export window, fee and deletion timetable**  
  ______________________________
- **Unanswered question, owner and decision date**  
  ______________________________

### Sources and credits

- Office of the Privacy Commissioner of Canada and the provincial privacy commissioners’ offices of Alberta and British Columbia. [Cloud computing for small and medium-sized enterprises](https://www.oipc.bc.ca/documents/guidance-documents/1370). This joint 2012 guide includes questions about subcontracting, access and return or deletion of personal information. Use its questions to examine the current agreement.

- Canadian Centre for Cyber Security. [Recommended cyber security contract clauses for cloud services (ITSM.50.104)](https://www.cyber.gc.ca/en/guidance/recommended-cyber-security-contract-clauses-cloud-services-itsm50104). The Cyber Centre explains which security obligations buyers can address in cloud contracts. Its examples give a procurement team a starting point for negotiations.

## Test whether an unsubscribe survives a contact import

MapleJockey worksheet · Sales and marketing · Sources reviewed 2026-11-18

Use a no-send rehearsal to see which contacts would enter a campaign after a CRM or mailing-list move.

### Working steps

1. Make four synthetic cases: a contact with documented consent for the intended message, an unsubscribed contact, a contact with no evidence, and an address that appears on two lists with conflicting statuses. Write the expected audience membership before importing.
2. Keep sending, automations and connected list syncs disabled. Map the source status, consent scope, timestamp, evidence reference and withdrawal history. Hold unknown and conflicting records out of the pilot audience.
3. Build a draft audience and inspect its members without sending. Repeat after importing the same file a second time. Compare each case with its expected result and retain a redacted record of discrepancies.

### Worked example (fictional)

An address is subscribed in the sales export and unsubscribed in the mailing tool. The expected pilot result is exclusion pending review. Seeing that address even once in the draft audience fails the test.

### Decision

Keep sending disabled if a withdrawn, unknown or disputed contact enters the audience, or if the owner cannot trace the result to its source record.

### Your record

- **Synthetic case ID and source lists**  
  ______________________________
- **Consent scope or exclusion and evidence reference**  
  ______________________________
- **Expected audience membership**  
  ______________________________
- **Observed after first import and after repeat**  
  ______________________________
- **Discrepancy owner and release decision**  
  ______________________________

### Sources and credits

- Innovation, Science and Economic Development Canada (index) and Canadian Radio-television and Telecommunications Commission (bulletin). [Federal index of CRTC bulletins, including CRTC 2014-326](https://ised-isde.canada.ca/site/canada-anti-spam-legislation/en/understand-canadas-anti-spam-legislation/understand-canadas-anti-spam-legislation-sub/understanding-canadas-anti-spam-legislation). ISED lists the CRTC’s archived Guidelines to help businesses develop corporate compliance programs. Paragraphs 9 and 10 of the bulletin identify consent evidence, consent logs and actions taken on unsubscribe requests as relevant records under Canada’s anti-spam legislation. MapleJockey supplies the test cases.

- Innovation, Science and Economic Development Canada. [Getting consent to send email](https://ised-isde.canada.ca/site/canada-anti-spam-legislation/en/getting-consent-send-email). The federal consent guide explains what senders should be able to document and how to honour an unsubscribe request.

## Prove a backup can restore a working file

MapleJockey worksheet · Backup and recovery · Sources reviewed 2026-11-18

Measure whether a colleague can recover a usable file in time for a business task. Start with a synthetic fixture and an isolated destination.

### Working steps

1. Choose a file with a known revision and a task someone can perform with it. Agree how old a recovered version can be and how long recovery may take. Keep the expected result and a file digest outside the backup under test.
2. Have the designated recovery operator restore to an empty location. Record the backup timestamp, start time and time the user first completes the task. Compare the restored digest with the expected one.
3. Have the intended reader open the file. Check that an unauthorised test role cannot read it. Mark any access or encryption check you could not exercise as untested and name the evidence still needed.

### Worked example (fictional)

A synthetic budget file restores in four minutes and its digest matches. The finance reader still gets an access error. Stop the timer only when the reader can open the correct version, and record the permission repair.

### Decision

Accept the rehearsal for its stated workload only when the age, timing, integrity and required access checks meet the agreed targets. Keep the original available while exceptions are resolved.

### Your record

- **Fixture, revision and expected digest**  
  ______________________________
- **Maximum acceptable data age and recovery time**  
  ______________________________
- **Backup timestamp, start and usable time**  
  ______________________________
- **Digest, user task and access results**  
  ______________________________
- **Retest owner and next rehearsal date**  
  ______________________________

### Sources and credits

- Canadian Centre for Cyber Security. [Back up and encrypt data](https://www.cyber.gc.ca/en/guidance/back-and-encrypt-data). This short guide for smaller organisations covers encrypted off-site backups, restricted access and regular recovery testing. The timed file exercise is MapleJockey’s application of that guidance.

## Hand off a dataset another researcher can interpret

MapleJockey worksheet · Research data · Sources reviewed 2026-11-18

Test what survives a file move by handing a synthetic dataset and its README to a colleague who did not prepare them.

### Working steps

1. Select a small table and the files needed to interpret it. Write a plain-text README naming the dataset version, creator, file relationships, units, missing-value codes and any software needed to open it.
2. Give a colleague the copied folder. Ask them to find the intended version and interpret one value and one missing observation using only the material in the folder. Record where they had to guess.
3. If repository deposit is planned, list the metadata fields, access conditions and reuse permissions to confirm with the steward. Treat repository deposit as a separate decision from transferring the files.

### Worked example (fictional)

A CSV reproduces byte for byte. A new reader interprets −99 as a measured temperature because the codebook stayed in the old workspace. Add the codebook, link it from the README and repeat the reading test.

### Decision

Accept the handoff when the reader can identify the right version and interpret the sample unaided. Refer access and deposit decisions to the authorised research steward.

### Your record

- **Dataset version, creator and file list**  
  ______________________________
- **Column, unit and missing-value convention**  
  ______________________________
- **Reader’s task, expected answer and observed answer**  
  ______________________________
- **README correction and retest result**  
  ______________________________
- **Steward and proposed access conditions**  
  ______________________________

### Sources and credits

- UBC Library Research Commons. [Create a README File](https://ubc-library-rc.github.io/rdm/content/03_create_readme.html). The workshop includes a downloadable README template and explains how portable documentation complements repository metadata. Workshop authors are Vanessa Choy, Billie Hu, Andrew Li, Paul Lesack and lead author Eugene Barsky. The handoff exercise and example here are original to MapleJockey.
  Source licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).

## Establish who can authorize work with First Nations data

MapleJockey worksheet · First Nations data governance · Sources reviewed 2026-11-18

Before choosing storage or proposing reuse, identify the First Nation whose information is involved and the process it directs.

### Working steps

1. Start with the First Nations Information Governance Centre’s introductory resource. Each First Nation interprets and applies the principles through its own protocols. For Inuit or Métis projects, seek direction from the respective rights holders.
2. Through the project’s established relationship, ask how the Nation wishes to consider the proposed activity and who it designates to speak to it. Confirm whether the activity includes backups, access by support staff or later reuse.
3. Follow the Nation’s directions about what may be documented and where. If permitted, record a reference to the decision, its limits, who can revisit it and what happens when the project ends. Keep community information in the agreed location.

### Worked example (fictional)

A research team proposes moving an archive to a Canadian host. Its agreement addresses storage at the university. The team takes the proposal back through the Nation’s designated process before selecting a destination.

### Decision

Pause movement or reuse until the relevant Nation has directed how to proceed. A completed worksheet records a conversation only to the extent the Nation permits.

### Your record

- **Proposed activity and stage**  
  ______________________________
- **Nation-directed process or authorised point of contact**  
  ______________________________
- **Permitted reference to the decision and its scope**  
  ______________________________
- **Conditions for access, return or further use**  
  ______________________________
- **Next action as directed by the Nation**  
  ______________________________

### Sources and credits

- First Nations Information Governance Centre (FNIGC). [The First Nations Principles of OCAP®](https://fnigc.ca/ocap-training/). FNIGC explains the First Nations-specific principles and how Nations exercise jurisdiction over their information. The linked page includes introductory material and further learning.
  OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC).

## Check which workspace a federal contract permits

MapleJockey worksheet · Defence supplier procurement · Sources reviewed 2026-11-18

Give the company security officer a short list of questions about the proposed change before any contract material enters a workspace.

### Working steps

1. Ask the contract owner to identify the applicable security clauses and Security Requirements Check List. Use permitted document references in the worksheet. Keep contract material in its designated system.
2. Ask the company security officer which approvals cover the existing IT environment and what the proposed change would affect. Include viewing, storage, backups, administrators and subcontractors in that comparison.
3. For a proposed cloud service, ask the client department and company security officer which assessment and sign-off records apply to this contract and environment. Record the point of contact for each unresolved item.

### Worked example (fictional)

An approval letter covers a supplier’s existing system. The proposal adds a hosted workspace and a separate backup location. The security officer asks which approvals cover both changes before either location receives contract files.

### Decision

Keep planning at the level of references and invented examples until the appropriate authorities confirm the permitted environment and handling in writing.

### Your record

- **Permitted contract and annex references**  
  ______________________________
- **Current approval scope and proposed change**  
  ______________________________
- **Activity, location and required authority**  
  ______________________________
- **Evidence reference, open question and owner**  
  ______________________________
- **Permitted next step and date**  
  ______________________________

### Sources and credits

- Public Services and Procurement Canada, CanadaBuys. [Security in contracts](https://canadabuys.canada.ca/en/buyer-s-portal/buyer-s-guide/plan/contract-security-and-privacy-requirements/security-contracts-0). This buyer-side guide explains how the requisition, security checklist and contract clauses fit together.

- Public Services and Procurement Canada. [Information technology security requirements](https://www.canada.ca/en/public-services-procurement/services/industrial-security/security-requirements-contracting/safeguarding-equipment-sites-assets-information/information-technology-security-requirements.html). The sections on inspections and cloud solutions distinguish contract-specific IT approval from the assessments and client-department sign-off required for cloud use.

## Plan a .ca registrar transfer that keeps email and web hosting running

MapleJockey worksheet · Domains and DNS · Sources reviewed 2026-11-18

Establish who manages registration, DNS, the website and mail before a registrar transfer. Use this worksheet while the domain is still at its current registrar.

### Working steps

1. Identify the registrar of record, registrant contact, authoritative DNS host, web host and mail provider. Confirm that the registrant can reach the administrative mailbox. Keep any transfer code in the registrar’s secure workflow.
2. Check the registration date, last registrar change and any administrative bundle against CIRA’s rules. Ask the current provider in writing whether bundled DNS or mail will continue after the transfer.
3. Record the current nameservers and the expected website and mail behaviour. Agree who will verify both after an authorised transfer and whom to contact if bundled service ends. Plan any DNS hosting move separately.

### Worked example (fictional)

A registrar also hosts the organisation’s DNS as a free add-on. The public website is elsewhere, but mail still relies on records in that zone. Obtain confirmation that DNS service continues or arrange continuity before releasing the registration.

### Decision

Schedule the transfer once the owner has confirmed eligibility, renewal arrangements and continuity for every bundled service. Plan for recovery through the responsible providers because another registrar change is generally restricted for 60 days.

### Your record

- **Domain, registrar and registrant contact role**  
  ______________________________
- **DNS, website and mail operators**  
  ______________________________
- **Eligibility date and bundle dependencies**  
  ______________________________
- **Nameservers and expected website and mail checks**  
  ______________________________
- **Continuity owner and provider support route**  
  ______________________________

### Sources and credits

- Canadian Internet Registration Authority (CIRA). [How to transfer domains](https://www.cira.ca/en/how-to-transfer-domains/). CIRA explains the registrant’s transfer workflow and the distinction between changing a registrar and changing nameservers.

- Canadian Internet Registration Authority (CIRA). [General Registration Rules](https://www.cira.ca/en/resources/documents/domains/general-registration-rules/). Section 6 covers .ca registrar changes, administrative bundles and the usual 60-day restrictions after registration or a registrar change. Check the rules for the applicable exception.
