From proposal to governed project

Enterprise plan Portfolio Manager

Approving a proposal is not the end of governance, it is the handover. When a proposal passes the right gate, Onplana creates the delivery project automatically and keeps the two linked, so the project always carries its approval history with it.

The automatic project

When a proposal passes your organization’s configured project creation gate, the project is created in the same step as the approval:

Named after the proposal, with its description, budget, and currency carried over.
Status Planning, classified as strategic work.
Timeline derived from the proposal’s estimated duration in weeks.
Owned by the proposal’s author, unless a different project owner was named on the proposal; the author keeps manager access either way.
Any document libraries and tables gathered in the proposal workspace move to the new project automatically.

The submitter is notified that the project exists, and the sponsor receives the same notification.

Choose when the project is created

By default the project is created when the proposal passes Proposal Review, so teams can start preparing early while the later gates continue. Stricter organizations can move this later:

Open Organization Settings, go to the Governance tab, then the Classification section.
Under Project Creation Gate, choose the gate that should trigger creation: Proposal Review, Business Case Review, Plan Review, or only once the proposal is fully Approved.

How the link shows up

On the project: the Overview tab shows a Governance Origin banner with the linked proposal, its current stage, the sponsor, and the gate reviews. If the proposal is ever deleted, an archived snapshot of this information remains.
On the Projects page: governed projects carry a Governed badge on their cards, so it is obvious at a glance which work went through the pipeline.
On the proposal: once linked, the proposal shows the project’s live status, and it moves to Active alongside the delivery work.

Governance metadata on the project

Managers and above see a Governance Metadata section when editing a governed project, covering Priority, Risk Level, Department, Strategic Alignment, Sponsor, Expected Benefits, and Business Justification. Saving updates the project first and then the linked proposal, so the governance record never drifts from the project. Project members below manager level do not see this section, governance details stay with the people who run the pipeline.

Best practices

Pick the Project Creation Gate by your org’s appetite for parallel work. Default (Proposal Review) lets the project team start preparing while later gates run — good for fast-moving orgs. “Only on Approved” defers all work until full approval — better for compliance-driven orgs where pre-approval activity is risky.
Capture a baseline immediately when the project is created. The proposal’s plan IS the baseline. Once the project lands, take a baseline of the imported tasks/dates/budget so every future change is visible against it. See Capture and compare baselines.
Treat the Governance Origin banner as durable evidence. It survives proposal deletion via the archived snapshot. Anyone reviewing the project can confirm “this work went through gates” — useful for stakeholder confidence.
Use the Convert to Project button when a proposal is approved without an auto-created project. Some orgs deliberately set the creation gate to “Approved only” and then convert selectively, picking the moment that fits their resource availability.
Watch for proposal-side metadata drift. Project managers can edit governance metadata from the project; it syncs to the proposal so they stay aligned. But if the proposal is updated separately later (during a hold + resume, for example), the project metadata may need a refresh.

Troubleshooting / common pitfalls

My proposal is approved but no project appeared. Check the Project Creation Gate setting. If it’s set to “Approved only”, the project lands at the Approved stage, not at the earlier gate’s pass. If approved + no project, click the Convert to Project button on the proposal.
The new project landed without the right owner. The proposal’s named project owner is used; if none was named, the proposal’s author becomes the owner. If the named owner left the org, ownership falls back to the author so the project is never orphaned. To change post-creation, the owner can transfer ownership via the project’s Members tab.
The Governance Origin banner shows a “deleted proposal” notice. The proposal was deleted from the Recycle Bin after the project was created. The banner shows an archived snapshot of the original proposal so the project still has its governance history. This is by design.
Sponsor isn’t receiving project notifications. The sponsor was notified at project creation but doesn’t automatically subscribe to ongoing project events. Add them as a project member if you want them notified of task-level updates.
Governance metadata changes on the project aren’t reflected on the proposal. Sync runs in one direction (project edits update the proposal). If the proposal needs to change independently, edit it directly and re-save the project to re-sync.

How this combines with other features

Project creation + Baseline. Capture a baseline the moment the project is created. The proposal’s estimated duration + budget becomes the baseline’s “what we agreed to” reference. See Capture and compare baselines.
Project creation + CCB. Any changes to scope, schedule, or budget on the resulting project should route through the CCB. The proposal approved a specific plan; CCB protects that plan going forward. See Run a Change Control Board.
Project creation + Classification. Governed projects are auto-classified as Strategic. The badge surfaces this on the Projects page; the type filter lets you slice the portfolio by it. See Classify strategic vs operational work.
Project creation + EVM. Earned Value math uses the proposal’s budget as Budget at Completion. The baseline captures this; EVM reports variance against it as the project executes. See Read the EVM dashboard.

Coming from another tool

Tool	Mapping
MS Project Online	Proposal-to-project handoff is similar; PWA does it through workflow stages
ServiceNow PPM	Demand-to-project handoff with linked records; same concept
Spreadsheet + manual project creation	Onplana automates the handoff with a baked-in audit trail
Smartsheet Control Center	Project-from-template ≈ project-from-approved-proposal in Onplana
Jira “Demand” project	Jira lacks the auto-creation flow; teams manually clone

FAQs

Who owns the new project? The proposal’s author, unless the proposal named a different project owner. If that named owner has since left the organization, ownership falls back to the author so the project is never orphaned.

Does rejecting the proposal later remove the project? No, and you cannot reject an approved proposal at all. Stopping a live initiative means cancelling the project itself; the proposal record stays for the audit trail.

Do gate scores follow the project? Yes. The average review score from the proposal’s gates is synced to the project as its governance score, visible to managers in project health views.

Can I un-link a project from its proposal? Not directly. The linkage is durable evidence for compliance. If a project genuinely needs to be a fresh start, create a new project and archive the governed one.

Will tasks from the proposal workspace become tasks on the project? Documents and tables move; tasks (if any were drafted in the proposal’s workspace) don’t. The project starts with a clean task list, ready for the team to populate per the approved plan.

Can two proposals create the same project? No. Each proposal creates at most one project. If two proposals genuinely converge on the same work, approve one and reference the other in its description.

What happens to the sponsor’s role on the new project? The sponsor is notified at creation but isn’t automatically a project member. Add them as a project member (with whatever role fits) if they should see ongoing project events.

Submit a proposal — the entry to this flow
Capture and compare baselines — the right next step after project creation
Run a Change Control Board — protect the approved plan going forward

Was this helpful?