Editorial approach
Useful planning advice, with its limits in view.
The Critical Path library is published by the team behind the product. Its purpose is to help you make better decisions about priorities, capacity, calendar time, and follow-through—even if you use a different tool.
Who is speaking
Articles carry an organizational byline: Critical Path. This is product-owned educational content, not an independent review publication. The library is prepared with AI assistance and checked against the application implementation and any linked documentation. Blog perspectives present our reasoning and recommendations, not measured customer outcomes or external research unless explicitly sourced. We do not present an invented expert, customer testimonial, or personal experience with a competing product.
What counts as evidence
Product instructions follow the implemented workflow. External product claims link to official documentation or current product pages. A comparison based on documentation is labelled as such; it is not a measured benchmark. Pricing, platform availability, and integration permissions can change, so verify the current official terms before buying or migrating.
Worked schedules, action items, organizations, and outcomes in these articles are fictional examples. They illustrate decisions, not customer results. We do not publish private workspace data, calendar subjects, or customer identities. A scheduling rule is not a promise that a third-party calendar can never change or fail.
How to use the library
Each guide should leave you with a usable next step: a worked calculation, a decision checklist, or an editable worksheet. Downloads do not require an email address. Our comparisons explain why another planner may be the better choice. Account links are invitations to use the current web application, not offers of an unimplemented paid plan or timed trial.
Dates, revisions, and corrections
Publication and update dates represent editorial changes, not an automatic daily freshness stamp. When a capability or a cited source changes, the affected guide needs a substantive review. Current in-product connection status and provider documentation take precedence over an old walkthrough. An article that depends on a capability we cannot verify should be corrected or withdrawn, not left online with stronger marketing language.
If a step does not match your application, stop before sending invitations or changing calendar events. Use the official source linked in that section and the account-support contact listed in our terms. Share the public article URL and the unclear step; do not send passwords, authorization tokens, or private calendar links.