
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Service Request Management</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1624966</link>
<description></description>
<lastBuildDate>Sat, 6 Jun 2026 23:56:37 GMT</lastBuildDate>
<pubDate>Mon, 26 Jul 2021 17:16:09 GMT</pubDate>
<copyright>Copyright &#xA9; 2021 itSMF UK</copyright>
<atom:link href="https://itsmfuk.site-ym.com/forums/topic_rss.asp?id=1624966" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>Service Request Management</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1624966</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1624966</guid>
<description><![CDATA[<p>Has anyone uncovered any 'standardised' Service Request forms which could be re-used by our organisation?</p><p>I recognise that every Service is different but there are quite a few common elements which every request must contain.</p><p>Any feedback would be most welcome and appreciated.</p><p>&nbsp;</p><p>Thanks</p><p>&nbsp;</p><p>Mark</p>]]></description>
<pubDate>Thu, 22 Jul 2021 16:45:07 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1625405</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1625405</guid>
<description><![CDATA[Hi Mark, most companies generate the forms in the ITSM tool they are using, i.e. ServiceNow, Remedy etc.  However it is true that a number of attributes will be common across all businesses.<br /><br />Most common attributes, I can think of straight away are:<br />Name<br />Dept<br />Cost Code<br />Contact Details<br />Description of item or service being requested<br />Approval (Approver, Job Title etc)<br /><br />Clearly there would need to be a number of attributes pulled from the Service Catalogue such as Item Name, Part Number, Supplier, Cost etc<br /><br />Hope this helps as a starter for ten]]></description>
<pubDate>Mon, 26 Jul 2021 18:16:09 GMT</pubDate>
</item>
</channel>
</rss>
