What to Put in a Service Requirements Form

The requirements form is the first thing a customer sees after paying for a service. A good one gets you everything you need to start. A bad one starts a week of back-and-forth emails.

Ask only what this service needs

A health check needs a store URL and a short description of the problem. A copy rewrite needs the product links and who buys them. Asking for brand colours on a payment setup order only slows the customer down.

Give an example in the help text

Under each question, show what a good answer looks like. "For example: payments stuck as pending, slow orders screen" gets you better answers than an empty box.

Never ask for passwords in the form

Ask the customer how they will share access instead, and set up a separate user for the job. You can remove it when the order is complete.

Keep it under five questions

If you need more, the service is probably two services. Split it, and each form stays short.

Leave a Reply

Your email address will not be published. Required fields are marked *