How to set and manage project requirements

In this article

• What are project requirements?
• How long do clients have to provide mandatory requirements, and what if they don't?
• Why do projects include requirements for clients?
• When does the project clock officially start?
• Can I update my requirements later?
• Tips for writing strong client requirements
• Examples of good vs. vague requirements

What are project requirements?

Project requirements are the things you need from a client before you can start working. Think: files, brand assets, business details, tone preferences — basically, anything that helps you deliver exactly what they’re expecting.

You set these up when creating your project in the Catalog. You can label each one as:

• Mandatory: The project can’t begin without it
• Optional: Helpful to have, but you can work without it

How long do clients have to provide mandatory requirements, and what if they don't?

Once the client places an order, they have 48 hours to provide the mandatory requirements. If they don’t, we'll automatically cancel the project and refund the client’s money. 

Optional requirements won’t affect the start or deadline of the project.

Why do projects include requirements for clients?

Good requirements do a few things:

• Give you a clean starting line — so you’re not chasing clients for missing info mid-project
• Help clients get organized — it sets expectations before they buy
• Make your project look more professional — because clients can see your requirements upfront while browsing

When does the project clock officially start?

It starts when your client sends you the mandatory requirements — not at the time of purchase.

For example, if a client sends you the requirements at 11:15 a.m. Monday and your promised delivery time is three days, the project is due at 11:15 a.m. on Thursday.

Can I update my requirements later?

Yes. You can edit your requirements for the project on Project Catalog, which will take effect with future purchases. This won't impact projects you're already working on. As you do more projects, you’ll naturally learn what’s missing or what could be clarified.

Tips for writing strong client requirements

Here’s how to make your requirements do the heavy lifting for you:

• Be clear and specific

  Instead of saying: “I need your logo”

  Try: “Please upload your logo as a high-resolution PNG or SVG file. If you have brand color codes, please include those too.”

• Use checklists or bullet points
  That helps clients know exactly what to send and prevents back-and-forth.

• Ask the right questions

  For example, if you’re creating a blog article, you could ask:

  • Who’s the target audience?
  • What’s the tone? (Formal, friendly, etc.)
  • Are there keywords you’d like me to include?
  • Do you want me to follow a specific style guide? (AP, MLA, etc.)
• Use optional requirements for extras
  Like inspiration examples or competitor links — anything that would help but isn’t essential.

Examples of good vs. vague requirements

Example 1: Logo design

Too vague:

Describe the logo you want

Better:

Please include:

• Brand name
• Tagline (if any)
• Business overview (services, audience, competitors)
• Color preferences
• Logos you like (optional)
• Any sketches or concepts you have (optional)

Example 2: Website copywriting

Too vague:

Tell me about your business

Better:

Please answer the following:

• What does your business do?
• What are your key products or services?
• Who is your ideal customer?
• What tone do you prefer for your website? (e.g. casual, professional, witty)
• Do you have existing brand guidelines or a content style guide?