projectdoc Toolbox

Publish key results to achieve in order to pursue an objective to share with your colleagues.


Key results are typically associated with objectives and support making advancement (or the lack of it) measurable.


The document type key result provides the following properties:


Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.


Specify the type of the key result to organize them.

Use the key result type to define types of key results.


List stakeholder that own the key result. Consult these people when there are questions or you are looking for support when pushing objectives related to this key result.


The start date when the pursuing of this key result begins.

The start is typically referring to the parent's start date. Note that the Start property is hidden and rendered as part of the Cycle property.


The end date when this key result ended.

The end is typically referring to the parent's end date. Note that the End property is hidden and rendered as part of the Cycle property.


For brevity and to save space the start and end date are rendered with the Cycle property as a period.


Log the date the key result is planned to be achieved.

The deadline allows to order key results and provide a more fine-grained structuring within the defined cycle.


If you need to prioritize the key results, then use the Sort Key property.

OKR Priority

Reference a priority to related this key result's importance to other key results.

Predicted Score

Log the predicted value scored by the end of the period. The format of the value is a decimal value between .01 (or .05) and 1.



In case the short description is not enough, the description section provides room for more detailed information about the key result.


Describe why this key result is useful for your business. State the problem to be solved.


Describe who is involved in the key result.

List the stakeholders that will support the key result. There may be stakeholders who will work against it. Also specify the stakeholders taking advantage or taking disadvantage even if they do not have power to influence the outcome.


Describe how the key result will be pursued.


Describe the (high-level) deliverables (aka output) required to achieve the outcome.


List check-ins related to this key result.

Check-ins added to this key result as child documents are automatically listed.

Supporting Key Results

List all key results that support this key result.

All key results that declare this key result as their logical parent are automatically listed.

Subordinate Key Results

In case you need to organize key results in a hierarchy then add additional key results as children to this key result. Subordinate key results will then be automatically listed.

Since key results are typically short lived, there is probably no need to organize them for one iteration in this way.


These are internal notes that are usually not exported and only visible to team members with write access.

But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.


The text of notes sections is also indexed.


For a document the references section contains pointers to resources that prove the statements of the document.

Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.


For further information please refer to References and Resources.


The resources section provides references to further information to the topic of the document.

This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.


For further information please refer to References and Resources.

Related Doctypes

Document the result of a OKR check-in.
Publish an objective to share with your colleagues.
Strategic Theme
Publish a strategic theme to group objectives and to share them with your colleagues.
Track what you have achieved and the reasons why. Check what you have learned and find areas where you can improve.