How do you all handle project intake — before anything hits the plan?

Started by Melvin Jose · 1 month, 3 weeks ago · 1 reply · 98 views
Melvin Jose Participant
1 month, 3 weeks ago

We finally got tired of project requests landing in our laps through every channel imaginable — hallway chats, emails, the occasional sticky note — so we built an actual front door. Every new project now starts as a form submission, which we can open to the whole workspace or lock down to specific people depending on who should be raising requests.

Behind that form sits an approval workflow — and it can run multiple levels deep when a request needs a few sets of eyes before it's blessed. The nice part is what happens after: once it's approved, it flows straight through into our live projects list through automation, carrying the key details across the next table. No re-typing, no requests. This ensures that the key details are not missed and avoids the need to enter the same details again.

I'd love to hear how other teams are running intake. Is it a form-and-approval setup like ours, or something more lightweight? And where do you draw the line on how many approval levels is 'enough' before it starts feeling like bureaucracy?

1 Reply
1 month, 2 weeks ago

Oh this is basically us a year ago — requests coming from everywhere and no clean way to say yes or no. We went with a single-level approval to start because we were nervous about slowing people down, but honestly I think we'll add a second level soon now that leadership wants more visibility on budget sign-off. The auto-creating-the-project-record part is what I'm jealous of, we're still copying that over manually. How painful was it to wire up that automation?

Viewing 1 replies (of 1 total)

About this topic

  • Replies 1
  • Views 98
  • Participants 2
Fabric Plan
Enterprise planning, integrated with PowerTable and Intelligence, native to Microsoft Fabric. Co-engineered with Lumel.
BUILT ON MICROSOFT FABRIC
CERTIFIED BY
Fabric Planning is certified by IBCS
Microsoft, Azure, Copilot, Excel, Fabric IQ, Microsoft Entra, Microsoft Fabric, Microsoft Teams, OneLake, Outlook, Power Automate, Power BI and SharePoint are trademarks of the Microsoft group of companies. IBCS is a registered trademark of IBCS Association. All other trademarks are the property of their respective owners.

This community is operated independently by Lumel. Nothing on this site constitutes a representation or warranty by Microsoft.