Using the DoView® Name, Marks, and Badges

When you can and can’t use the DoView® trademark and material

DoView® Planning Attribution & Trademark Use Policy

1. The DoView® Marks

In this policy, the DoView® Marks include DoView®, DoView, DoViews, DoView Planning, DoView Boards, DoView Board, DoView strategy/outcomes diagrams, DoView Strategy/Outcomes Models, DoView Theories of Change, DoView Intervention Logics, DoView Program Theories, See. Plan. Do.™, DoView® logos, the DoView® Badge, the Official DoView® Badge, and related DoView names, marks, badges, terms, or branding.

The DoView® Marks identify the DoView Planning approach, DoViews, DoView Boards, related outcomes-theory resources, and official materials developed by Dr Paul Duignan and/or made available by DoView Corporation Limited.

DoView® is a registered trademark of DoView Corporation Limited.

This policy is intended to allow broad, accurate, and descriptive use of the DoView® Marks, while at the same time allowing us to identify what is officially endorsed, certified, approved, quality-assured, produced, or affiliated with Dr Paul Duignan, DoView Corporation Limited, or any official DoView® body.

2. Relationship to open-source licences

Extensive developer resources for using DoView Planning, DoView Boards, and related methodologies and tools have been released, and may continue to be released, under Apache-2.0 or another open-source licence.

Apache-2.0 is a permissive open-source licence. It is intended to allow broad reuse of the relevant code or materials, including commercial reuse, subject to its terms. Other open-source licences we use may also allow broad reuse.

These licences include permission to use copyright-protected material and, where applicable, patents in the relevant code or materials.

This Trademark Use Policy is separate. It does not reduce the permissions given under Apache-2.0 or any other open-source licence that applies to particular code or materials.

However, those open-source licences do not by themselves give permission to claim official DoView® status, endorsement, certification, approval, quality assurance, affiliation, or badge rights.

Specific use of official DoView® logos, the DoView® Badge, the Official DoView® Badge, certification marks, approval marks, endorsement claims, and similar official-status wording is covered in this policy.

3. General permission to refer to DoView

You are encouraged to use theDoView® Marks in a fair, accurate, and descriptive way to say that your work uses, refers to, supports, implements, builds on, extends, or is compatible with DoView Planning, DoViews, DoView Boards, or related DoView-based models.

For example, you may say:

• “This project uses the DoView Planning approach.”

• “This board is based on DoView Boards.”

• “This app supports DoView Boards.”

• “This tool creates DoView-compatible boards.”

• “This platform implements the DoView Boards minimum standard.”

• “Training in the DoView Planning approach.”

• “Consulting using DoView Planning and DoView Boards.”

This permission applies to ordinary descriptive use, including use of DoView® with the registered trademark symbol where appropriate.

You may also use DoView in the name or description of your own product, service, app, platform, integration, repository, training, consulting, or other work, provided your use is accurate and please do not suggest official endorsement, certification, approval, quality assurance, affiliation, or production by Dr Paul Duignan, DoView Corporation Limited, or any official DoView® body unless we have agreed to this in writing. Get in contact if you want to.

4. Terminology and acknowledgment

When referring to the approach, we encourage you to use the term DoView Planning.

When referring to the diagrams, boards, or models, we encourage you to use terms such as DoViews, DoView Boards, DoView Strategy/Outcomes Models, DoView Theories of Change, DoView Intervention Logics, DoView Program Theories, or similar terms, where the approach you are using draws on the DoView Planning approach or methodology.

Please acknowledge DoView Planning and Dr Paul Duignan when you use the approach or create DoViews, DoView Boards, or related DoView-based models.

A suitable acknowledgment is:

This work uses the DoView Planning approach and DoView Boards developed by Dr Paul Duignan. See DoViewPlanning.org.

For software, apps, platforms, or developer tools, the acknowledgment may appear in any reasonable and practical location, such as:

• an About page

• documentation

• help material

• licence or notice material

• an acknowledgments page

• a settings or information screen

• a README or repository notice

We encourage you to say when your work uses DoView Planning, supports DoView Boards, creates DoViews, uses DoView-based models, or is DoView-compatible, provided this is accurate.

Just please do not imply endorsement, certification, approval, affiliation, or official status unless we have agreed in writing. Get in touch if you want to do so.

5. What you may do

You may useDoView Planning, DoViews, DoView Boards, and related DoView tools and methodologies in your own work, including:

• internal planning

• strategy and implementation planning

• project planning

• evaluation and monitoring

• outcomes planning

• theories of change

• intervention logics

• program theories

• public-sector, nonprofit, community, business, and educational work

• reports and presentations

• PowerPoint, Google Slides, and other presentation tools

• consulting and paid client work

• training and facilitation

• teaching and research

• websites and publications

• software, apps, platforms, systems, and AI tools

• integrations with other planning, project management, evaluation, or agentic systems

You may build, adapt, extend, or integrateDoView-compatible boards, tools, features, and methodologies into any other tools, apps, platforms, or systems.

You may charge for your own services, products, training, consulting, software, apps, platforms, or systems that use DoView Planning, DoViews, DoView Boards, or related DoView tools or methodologies, just as long as you follow this policy.

6. Developer use of DoView Boards and the legacy DoView app

Developers are encouraged to implement, extend, and buildDoView-compatible boards, apps, platforms, plugins, integrations, AI tools, and systems.

You may build features of the current DoView Boards app, the legacy DoView app, or related DoView tools and methodologies into your own apps, platforms, or systems. You just need to include appropriate attribution and make clear that your work is not affiliated with or endorsed by DoView® unless we have agreed in writing. Get in contact if you want such affiliation or endorsement.

You may describe your software as supportingDoView Boards or being DoView-compatible just as long as that statement is accurate.

A suitable software acknowledgment is:

This software supports DoView Boards using the DoView Planning approach developed by Dr Paul Duignan. See DoViewPlanning.org. This software is not affiliated with or endorsed by DoView®.

Please just do not imply that your software, app, platform, plugin, integration, AI system, or developer tool is official, endorsed, certified, approved, quality-assured, affiliated with us, or produced by us unless we have agreed in writing.

7. Please do not imply official DoView status or endorsement

Unless we have given written permission, please do not say or imply that your work, product, service, board, app, training, consulting, platform, system, or organisation is:

• official

• endorsed by us

• approved by us

• certified by us

• quality-assured by us

• produced by us

• affiliated with us

• a formal DoView partner

• entitled to use the DoView® Badge

• entitled to use the Official DoView® Badge

• entitled to use any other DoView® compliance, standards, certification, or approval badge

We encourage you to say that your work uses DoView Planning, supports DoView Boards, creates DoViews, uses DoView-based models, or is DoView-compatible, just as long as the statement is accurate and does not imply endorsement, certification, approval, affiliation, or official status. Get in touch if you want endorsement or certification.

8. DoView-compatible use terms you may use

You may use descriptive wording such as:

• DoView-compatible

• DoView-based

• DoView-enabled

• compatible with DoView Boards

• supports DoView Boards

• based on DoView Planning

• implements the DoView Boards minimum standard

• creates DoView-style boards

• creates DoViews

• uses DoView Strategy/Outcomes Models

• uses DoView Theories of Change

• uses DoView Intervention Logics

• uses DoView Program Theories

• uses the DoView Planning approach

Just please do not use wording about what you are doing with DoView Planning, DoViews, DoView Boards, or related DoView-based models in a way that suggests official endorsement, certification, approval, partnership, badge status, or affiliation. Get in contact if you want this.

For example, “DoView-compatible” is welcome when it is accurate. Just please do not use wording such as “Official DoView Certified Platform” unless we have given written permission.

9. Official DoView® Badge and similar badges

Use of the DoView® Badge, Official DoView® Badge, and any similar DoView® badge, quality mark, standards mark, certification mark, or compliance mark is reserved.

Please do not use, copy, display, adapt, or imitate any of the following unless we have given written permission:

• DoView® Badge, Official DoView® Badge, or Official DoView Badge, with or without the ® symbol

• DoView® Standards Badge

• DoView® Compliance Badge

• DoView® Certified Badge

• DoView® Approved Badge

• DoView® Quality Badge

• any badge or mark suggesting official DoView status

• any badge or mark confusingly similar to an official DoView badge

You are welcome to say that your board, app, platform, or system implements the DoView Boards minimum standard where that statement is accurate. However, that does not by itself give permission to use the DoView® Badge, Official DoView® Badge, or any similar official badge.

Use of an official badge requires written permission. Get in touch if you want this.

10. Logos and visual identity

You may use text-based references to DoView, DoView Planning, DoViews, and DoView Boards in accordance with this policy.

However use of official DoView® logos, official badge designs, and official visual identity elements is reserved just where their use could suggest official endorsement, certification, approval, quality assurance, affiliation, or production by us.

Please do not use official DoView® logos, badges, or visual identity elements in a way that suggests your work is official, endorsed, certified, approved, quality-assured, affiliated with us, or produced by us unless we have agreed in writing.

This means please do not, unless we have agreed in writing:

• alter official DoView® logos or badges

• use DoView® logos or badges as your own product logo

• use DoView® logos or badges as your organisation’s brand identity

• place DoView® logos or badges in a way that suggests official endorsement or certification

• use DoView® logos or badges in a misleading way

• create a confusingly similar logo, badge, or visual identity

The purpose of this section is not to stop accurate references to DoView. It is just to keep official DoView visual signals clear.

11. Product, service, company, and domain names

You are welcome to use DoView, DoView Planning, DoViews, or DoView Boards in the name or description of your product, service, company, app, platform, domain name, social media account, repository, training, consulting, or other work, provided your use is accurate and not misleading.

For example, you may use names or descriptions such as:

• DoView Cloud

• DoView AI

• DoViewCloud

• GetDoView

• MyDoView

• DoViewPro

• DoView-compatible board editor

• DoView Boards plugin

• “A planning tool that supports DoView Boards”

• “A plugin for creating DoView Boards”

• “Training in the DoView Planning approach”

• “Consulting using DoView Planning”

Just please make clear that your work is yours, not ours, where that could otherwise be unclear.

Unless we have given written permission, please do not use names or descriptions that suggest your product, service, company, app, platform, domain name, social media account, repository, training, consulting, or other work is official, endorsed, certified, approved, quality-assured, affiliated with us, or produced by us.

For example, unless we give written permission, please do not use names such as:

• Official DoView App

• Official DoView Platform

• Official DoView Training

• Official DoView Certification

• DoView Certified

• DoView Approved

• Certified DoView Provider

• Approved DoView Partner

• Official DoView Academy

• DoView Corporation

• DoView Corporation Limited

The key rule is that using DoView or DoView® in a name is welcome where it accurately describes your work, but it should not suggest official DoView endorsement, certification, approval, quality assurance, affiliation, or production unless we have agreed in writing. Get in touch if you want endorsement.

12. Teaching, training, consulting, and paid services

You may teach, train, consult, facilitate, or provide paid services using DoView Planning, DoViews, DoView Boards, and related DoView tools and methodologies.

Please acknowledge DoView Planning and Dr Paul Duignan.

A suitable acknowledgment is:

This work uses the DoView Planning approach and DoView Boards developed by Dr Paul Duignan. See DoViewPlanning.org.

You may accurately describe your services, for example:

• “Facilitation using DoView Planning”

• “Training in the DoView Planning approach”

• “Consulting using DoView Boards”

• “Project planning using DoView-compatible boards”

• “Training using DoView strategy/outcomes diagrams”

• “Consulting using DoView-based models”

Just please do not imply that your training, consulting, facilitation, certification, course, credential, or service is official, endorsed, approved, certified, quality-assured, affiliated with us, or produced by us unless we have agreed in writing.

Please do not issue official DoView certificates, badges, credentials, or qualifications unless we have agreed in writing. Get in contact if you want to do so.

13. Website, handbook, and other full materials

Please do not copy or republish the DoViewPlanning.org website or the full DoView Planning and Outcomes Theory Handbook without permission from us. Get in contact if you want to do this.

You may use reasonable extracts with attribution, provided your use is fair, accurate, and not misleading.

Please direct people to DoViewPlanning.org, or to the relevant book listing DoViewPlanning.org/book, for the full materials.

This section does not limit any rights you may have under applicable law, such as fair dealing, fair use, quotation, review, criticism, education, or research rights where those apply.

14. No misleading, harmful, or confusing use

Please use the DoView® Marks accurately and in a way that does not mislead people about what is official, endorsed, certified, approved, quality-assured, affiliated with us, or produced by us.

Please do not use the DoView® Marks in connection with:

• false or misleading claims

• deceptive products or services

• unlawful activity

• abusive, hateful, or discriminatory activity

• malware, spyware, phishing, or deceptive technology

• materials that falsely suggest official endorsement, approval, certification, affiliation, or responsibility by us

This section is not intended to prevent fair comment, criticism, review, research, education, comparison, or accurate public discussion of DoView Planning, DoViews, DoView Boards, or related DoView materials.

15. Quality and accuracy

If you say that your work uses DoView Planning, supports DoView Boards, creates DoViews, uses DoView-based models, or implements the DoView Boards minimum standard, that statement should be accurate.

DoView Boards are intended to follow a clear structure and purpose. If your board, app, platform, or system significantly departs in a major way from the DoView Boards minimum standard, please do not describe it as implementing that standard.

You may still say that your work was inspired by DoView Planning, draws on DoView Planning, or uses a modified DoView-based approach if that is accurate.

16. Revocation of trademark permission

We may revoke permission to use the DoView® Marks, logos, badges, or other brand identifiers if your use does not comply with this policy or risks serious confusion, harm, dilution, or misleading association.

This applies to trademark, badge, logo, endorsement, certification, approval, quality-assurance, affiliation, and official-status permissions.

It does not revoke any copyright or patent permissions separately granted under an open-source licence such as Apache-2.0 for code or materials released under that licence.

However, even if you have rights under an open-source software licence, you must still follow this policy when using the DoView® Marks, official logos, official badges, or official-status claims.

17. No endorsement or liability

Permission to use the DoView® Marks under this policy does not mean that Dr Paul Duignan, DoView Corporation Limited, or any official DoView body endorses, approves, certifies, warrants, supports, quality-assures, or takes responsibility for your work.

You are responsible for your own products, services, boards, training, consulting, software, platforms, systems, representations, and claims.

18. Contact

If you want to use an official DoView® logo, DoView® Badge, Official DoView® Badge, certification mark, compliance mark, quality mark, approval mark, or similar official-status wording, please contact us first.

We are very keen to recognize, review, approve, quality-assure, or collaborate on products, services, standards, and materials where that would be useful.

Just get in contact and also see our Collaboration page.

19. Changes to this policy

We may update this policy from time to time.

The version published on DoViewPlanning.org is the current version.