Creating a collection of submitted Changes

%3CLINGO-SUB%20id%3D%22lingo-sub-733740%22%20slang%3D%22en-US%22%3ECreating%20a%20collection%20of%20submitted%20Changes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-733740%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20use%20an%20under-utilised%20Sharepoint%20site%20as%20our%20intranet%20which%20links%20off%20to%20other%20systems%20and%20external%20pages%2C%20however%20we're%20now%20looking%20to%20bring%20more%20into%20Sharepoint%20and%20one%20of%20these%20actions%20has%20made%20me%20unsure%20of%20what%20the%20best%20practise%20would%20be%20to%20implement%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBasically%2C%20the%20operations%20team%20have%20a%20weekly%20call%20every%20Friday%20where%20they%20discuss%20what's%20happened%20through%20that%20week%2C%20what's%20happening%20next%20week%20and%20then%20cover%20any%20notable%20changes%20and%20AOB.%20They%20would%20like%20a%20way%20for%20users%20to%20submit%20content%20which%20would%20then%20be%20grouped%20in%20a%20'pool'%2C%20preferably%20visible%20to%20the%20rest%20of%20the%20group%20and%20the%20chair%20would%20work%20through%20it%2C%20kind%20of%20how%20a%20CAB%20(Change%20Authority%20Board)%20works%20I%20guess.%20At%20present%20it%20is%20all%20done%20on%20a%20spreadsheet%20and%20e-mailed%20to%20the%20chair%20ahead%20of%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20would%20be%20the%20best%20method%20to%20bring%20this%20process%20into%20Sharepoint%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-733740%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737222%22%20slang%3D%22en-US%22%3ERe%3A%20Creating%20a%20collection%20of%20submitted%20Changes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737222%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F369257%22%20target%3D%22_blank%22%3E%40Danny_B1350%3C%2FA%3E%26nbsp%3BI%20would%20use%20a%20list%2C%20you%20can%20then%20add%20columns%20for%20dates%20and%20statuses%2C%20which%20you%20can%20use%20to%20filter%20the%20data%20for%20just%20that%20week%20and%20then%20approve%20or%20reject%20any%20items.%26nbsp%3B%20It%20would%20then%20give%20you%20the%20scope%20to%20use%20Microsoft%20Flow%20in%20the%20future%20if%20you%20need%20to%20automate%20any%20of%20the%20process%2C%20such%20as%20sending%20an%20email%20to%20the%20user%20to%20say%20if%20the%20item%20has%20been%20approved%20or%20rejected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

Hi,

 

We use an under-utilised Sharepoint site as our intranet which links off to other systems and external pages, however we're now looking to bring more into Sharepoint and one of these actions has made me unsure of what the best practise would be to implement it.

 

Basically, the operations team have a weekly call every Friday where they discuss what's happened through that week, what's happening next week and then cover any notable changes and AOB. They would like a way for users to submit content which would then be grouped in a 'pool', preferably visible to the rest of the group and the chair would work through it, kind of how a CAB (Change Authority Board) works I guess. At present it is all done on a spreadsheet and e-mailed to the chair ahead of time.

 

What would be the best method to bring this process into Sharepoint?

 

Thank you

1 Reply
Highlighted

@Danny_B1350 I would use a list, you can then add columns for dates and statuses, which you can use to filter the data for just that week and then approve or reject any items.  It would then give you the scope to use Microsoft Flow in the future if you need to automate any of the process, such as sending an email to the user to say if the item has been approved or rejected.

 

Hope that helps.