Skip to content
Current/ Help Center

Building projects in your PSA from a template or won quote

2 min read · Updated Jul 18, 2026

Current doesn't currently have an AI feature that reads a scope-of-work document and drafts a project from it. What it does have — and what most teams actually reach for at this step — is a one-click Build flow, named for your PSA ("Build in Autotask" or "Build in ConnectWise"), that takes a project you've already structured in Current (from a cloned playbook or a won quote) and creates the matching phases and tasks in your PSA for you, instead of typing them in by hand.

From a won quote

When a quote closes as won — in ScalePad Quoter or ConnectWise CPQ — the win-quote wizard walks you through turning it into a real project: map the quote to a project, lay out its phases and tasks, review charges, and then build it in your PSA. Current creates the Current project first, adds any standard day-one tasks, schedules everything backward from your target date, and only then pushes the structure across.

From a cloned template

If you cloned a playbook as a PSA-synced project (see "Project templates and PMI playbooks"), the same build step runs as part of that clone. If it doesn't finish in one pass — a PSA API only accepts so much new structure per request — Current automatically resumes and keeps going until every phase and task has been created.

  1. 1
    Open the project
    If it hasn't fully built yet, you'll see a banner: "Not built in Autotask yet" / "Not built in ConnectWise yet", or "N of M tasks haven't synced."
  2. 2
    Select the Build button
    It's named for your PSA, and shows Building… while it works.
  3. 3
    Let it finish
    For large plans this can take a few rounds — Current paces itself against your PSA's limits automatically. You don't need to keep clicking.
  4. 4
    Check for a rejection message
    If your PSA refused something specific, Current shows exactly what it said, so you know what to fix.
Heads up
This only runs for projects meant to sync
Current refuses to build a Current-native project into your PSA unless you explicitly confirm the conversion through one of these flows. A stray or accidental request can't push a project into a PSA that was never meant to be synced.

See "Project modes: PSA-synced or Current-native" for how to decide which type a new project should be, and "Project templates and PMI playbooks" for how the clone step that precedes this one works.

Was this helpful?
← Previous
Project templates and PMI playbooks
Next →
Logging time and how it reaches your PSA's billing