Each event request created repetitive folder, naming and schedule administration.
One source submission produces a predictable workspace and matching schedule entry; collateral generation is not claimed.
01Form→02Category→03Year→04Month→05Safe event name→06SharePoint workspace→07Schedule record
Problem
Each event request created repetitive folder, naming and schedule administration.
What was built
A Microsoft Forms and Power Automate workflow that routes the request, creates the SharePoint workspace and writes the aligned schedule record.
Result today
One source submission produces a predictable workspace and matching schedule entry; collateral generation is not claimed.
01 / Starting point
A request started another manual setup chain.
Folders, naming and schedule records had to be recreated for recurring event work.
02 / The decision
Translate the filing rules into one routing model.
Category, year, month and safe event naming determine both the workspace path and schedule record.
Options
Create workspace and schedule separatelyUse one structured source response
Decision · Use one structured source response
03 / What was built
A Forms, Power Automate, SharePoint and schedule workflow.
The requester supplies the known event context while the flow handles the controlled operating structure.
04 / Result today
A validated one-submit workflow.
The demonstration reconstructs verified logic with representative names and does not execute against the live organisation system.
System X-ray
See the invisible work behind the experience.
01IntakeMicrosoft Forms event requestSYSTEM MAP02WorkflowPower Automate classification and naming logicSYSTEM MAP03DataCategory, year, month and safe event referenceDEMO04WorkspaceSharePoint folder structureDEMO05ScheduleAligned planning recordDEMO
03 / System + Explore
Follow the operating flow.
Select a node to change the proof stage. Open the detail drawer when you want the deeper technical explanation.
DEMOWorkflow
Receive one structured request
The form captures the event type, date, title and owner needed for routing.
What this changes
One source response begins both outputs.
Ownership change
01One structured intake→02Controlled SharePoint workspace→03Aligned schedule record
Interactive demonstration
Run the operating logic safely.
The interaction uses representative data and never touches the protected source system.
DEMOVerified workflow logic · representative event name
01FORM SUBMISSION→02CATEGORY→03YEAR + MONTH→04SAFE EVENT NAME→05SHAREPOINT WORKSPACE→06SCHEDULE RECORD
One representative request demonstrates the route into a controlled workspace and aligned schedule entry. No live automation is executed here.
Technical evidence index
Read the implementation detail without opening a control.
DEMOWorkflowReceive one structured request
The form captures the event type, date, title and owner needed for routing. One source response begins both outputs.
SYSTEM MAPClassificationChoose the controlled root
Event type determines the verified local or international routing path. The folder root follows a consistent rule.
DEMOWorkspaceCreate the predictable SharePoint path
Year, month and safe event naming build the workspace structure. The team receives the correct place to work.
DEMOScheduleWrite the aligned planning record
The same response creates the corresponding schedule entry. Files and planning start from the same source.
05 / Result today
One source submission produces a predictable workspace and matching schedule entry; collateral generation is not claimed.
Designed by Krste for event operations: a Microsoft 365 workflow that turns one request into the correct SharePoint workspace and a live schedule entry.
