Wayfinder AI
  • About
  • Blog
  • Research
  • Contact
  • Access Compass
Access Compass
CompassOverviewFeaturesPricingGuides
Wayfinder AI
© 2026 Wayfinder AI. All rights reserved.
Products
  • Compass
  • Lens (Coming soon)
  • Chart (Coming soon)
  • Radar (Coming soon)
Company
  • About
  • Blog
  • Contact
Resources
  • Glossary
  • Guides
  • Comparisons
  • Free Tools
  • Pricing
  • Privacy Policy
  • Terms of Service
All Guides

Projects & organisation

How to use the project management features in Compass to organise your workflows

3 min readGetting Started

What are projects?

Projects are containers for your audits. Each project typically represents one website or one client.

Why use projects:

  • Keep audits organised by site
  • Track progress over time for each domain
  • Separate client work from your own sites
  • Compare results across audit runs

Creating a project

  1. Click New Project on the dashboard
  2. Enter a project name (e.g., "Acme Corp Website" or "My Blog")
  3. Enter the primary domain (e.g., acme.com)
  4. Click Create

That's it. You can now run audits within this project.

Naming tips

  • Use client names for agency work
  • Use site names for your own properties
  • Be specific enough to tell projects apart at a glance

Running audits within a project

When you open a project and click New Audit, Compass pre-fills the domain for you. You can still change the URL if you want to audit a specific page.

All audits run from within a project are automatically associated with that project.


Sub-projects

For larger sites or clients with multiple properties, you can create sub-projects within a main project.

When to use sub-projects

  • A client has multiple domains or subdomains
  • You want to track different sections of a large site separately
  • You're auditing staging vs production environments

Example structure

Project: "Acme Corp"

  • Sub-project: "Main Website" (acme.com)
  • Sub-project: "Blog" (blog.acme.com)
  • Sub-project: "Help Center" (help.acme.com)

Creating a sub-project

  1. Open a project
  2. Click Add Sub-project
  3. Enter a name and domain
  4. Sub-projects have their own audit history but live under the parent project

You can have up to 10 sub-projects per project.


Audit history

Each project keeps a complete history of all audits run. This lets you:

Track progress

Compare scores over time. After making changes to your site, run a new audit and see if your score improved.

Identify regressions

If you notice a score drop, you can pinpoint when it happened by reviewing the audit history.

Document changes

Use audits as checkpoints - run one before and after major site updates.


Managing projects

Rename a project

Click the menu (⋮) on any project card → Rename

Delete a project

Click the menu (⋮) → Delete

Deleted projects are archived and no longer visible, but data is retained for 30 days in case you need to recover it.

Archive a project

Click the menu (⋮) → Archive

Archived projects are hidden from your main view but remain accessible in read-only mode. Useful for completed client work or old sites you're no longer actively auditing.


Workflow suggestions

For agencies

Create one project per client. This keeps their audits separate and makes it easy to share results.

Example structure:

  • "Client A - Main Site"
  • "Client A - Blog"
  • "Client B - E-commerce"

For in-house teams

Create projects by property or by purpose.

Example structure:

  • "Marketing Site"
  • "Documentation"
  • "Customer Portal"

For consultants

Create a project for each engagement, even if it's the same client.

Example structure:

  • "Acme Corp - Q1 2026 Audit"
  • "Acme Corp - Post-Redesign Audit"

Usage & Billing

Compass uses a token-based billing model. Each task in an audit consumes 1 token.

How tokens work

  • An audit with 5 tasks uses 5 tokens
  • An audit with 20 tasks uses 20 tokens
  • Tokens reset monthly based on your billing cycle

Checking your balance

View your remaining tokens in Account → Billing. You'll see:

  • Tokens remaining this month
  • Token usage history
  • Plan details and upgrade options

Plan limits

Plans differ in monthly token allowances and project limits. Check the pricing page for current tier details.

Note: We operate a "fair use" policy on project structure. You are encouraged to use a project for a single brand/site, with sub-projects for subdomains, competitors, or deep-dives. But unless you are abusing the system there are few hard limits on how you choose to structure your account.

Team plans (coming soon)

  • Shared token pool across team members
  • Role-based access to projects

Next steps

Next Steps

Your first audit — run one nowNavigating the interface — find your way around
PreviousNavigating the interfaceNextUnderstanding audit results