
Share your insights and expertise
PACC is looking for authors who can write engaging, original, and accurate content that has a direct connection to privacy, access, and data governance.
Before submitting an article, research case study, or other writing, please read this page before sending in your submission.
Content Quality Requirements
PACC publishes articles written by members, by industry insiders, and by experts in related fields.
We look for original material that is well researched with lots of practical tips, including insight, advice, and educational resources that are relevant to our readers who are privacy, access, and governance professionals, and members of affiliated professions such as cybersecurity, law, and compliance.
What Readers Want and Deserve
- Interesting, timely, and thought-provoking original content that has a clear connection to privacy, access, and data governance.
- Credible information backed up by verifiable data, research, and examples.
What Readers DO NOT Want (and we do not accept)
- Content that is unrelated to the profession.
- Veiled sales pitches, branding exercises, or self-serving promotional content.
- Recitations of statistical information or annual report content that is readily available elsewhere.
- News and opinions available elsewhere.
- Material that is generated by artificial intelligence.
Guest Post Guidelines
To increase the likelihood that your contribution will be more likely to catch our attention:
- Make sure that your guest post is original content that has not been published elsewhere, especially on other websites or social networks.
- Ensure your content does not contain material that was generated by artificial intelligence.
- If your article presents a unique perspective on a timely topic, or is about something in the news that doesn’t, on the surface, relate to access or privacy — and you can make a clear connection — that’s even better.
- Write thought-provoking content that challenges traditional wisdom, proposes better ways of doing things, or identifies problems and offers solutions.
- Include complete references and sources, fully footnoted, using plain text links (not hyperlinks).
- Familiarize yourself with content published on the PACC website to get a feel for the voice and style we use. The issues surrounding access and privacy are important to everyone in Canada and beyond, so articles should appeal to our members across the access and privacy community in the public, private, and non-profit sectors, and to the general public as well.
- Every public and private sector organization has access and privacy governance obligations. Many of the governance professionals in those environments are PACC members. Please remember that we prefer to support the people and organizations that support the PACC as members.
How to Submit a Guest Post
To submit your guest post, email it as part of the body of an email (not as an attachment), and send it to Editor (at) PACC-CCAP (dot) CA and include:
- Complete contact information
- Organizational affiliation
- Links to other content you have published
- A short bio (150 words max)
- High resolution headshot
- Links to your website and your social media handles
- Graphics and screenshots to illustrate examples
- Attribution details for all graphics and photos, including your headshot
If your submission includes a PDF or other attachment, it will catch our attention — but not the kind you want.
What Happens Next
Our editors will review your submission and contact you within two weeks if it is accepted for publication.
We might edit or adapt your contribution to polish it up or make sure it fits with our style. We might also modify submissions to include calls to action and links to PACC content such as newsletters, guides, and standards. And there might be a need to update or delete it in the future, which we do as part of our routine review and refresh.
Once your article has been accepted, don’t be modest: tweet, post, and share your good news with the world. We’ll also spread the word through our social media channels.
