Projects for a team at work

If I could get every team to use one feature first, it would be projects. You set one up once, and every chat starts with the context instead of a blank page.

What a project is

Most people still start every chat from scratch and paste in the same background, or don't bother and get a generic answer. A project fixes that. ChatGPT and Claude both have them, and they work much the same way.

A project is a space for one body of work. It holds three things:

  • Instructions. How you want it to work every time: who it's for, the tone, the format, what to check.
  • Files. The documents it should draw on: past examples, your standards, the facts it needs.
  • Chats. Every conversation for that work, kept together.

Each project also keeps its own memory, separate from your other work. Start a new chat in the project and it already knows the background. Nobody has to paste the price list in again.

Why it matters for a team

  • Consistent answers. Everyone works from the same instructions and the same files, so the output sounds like your organisation, not like whoever typed the prompt.
  • New staff start ahead. Someone new opens the project and has the context on day one.
  • Fewer "where's the latest version?" emails. The current files live in one place.

Good first projects

  • Tenders and submissions. Past winning responses, your capability statement, staff CVs, insurances and policies.
  • Proposals. Your services, a few past proposals you were proud of, your house style.
  • Board papers. The template, recent papers and the board's standing requests.
  • One key client. Their briefs, contracts, meeting notes and what they care about.
  • Staff questions. Your policies and procedures, so people can ask instead of hunting.

Setting one up

  1. One job per project. "Tender responses" works. "Work stuff" doesn't.
  2. Keep the instructions short. A paragraph or two beats two pages. Say who it's for, the tone, the format and what it must not do.
  3. Add a handful of current files. Quality beats quantity. Put the date in the file name so everyone knows what's current.
  4. Test it on a real task. Run something you did last month through it and compare.
  5. Give it an owner. Someone who keeps the files current and tidies the instructions.

A sample set of instructions

Here's the kind of thing I'd put in a tender project:

You help our bid team draft tender responses for [organisation]. Write in Australian English, plain and direct, no marketing language. Use only the evidence in the project files. If something a criterion asks for isn't in the files, say so rather than fill the gap. Answer each criterion in the order asked, within any word limit, and list the files you drew on at the end.

The line that does the most work is the one telling it not to fill gaps. That's what keeps it honest.

Sharing with your team

On the business plans you can share a project with colleagues. A few things to know:

  • Anyone with edit rights changes the instructions and files for everyone. Keep edit rights to the owner and one or two others.
  • People who can see the project can see its files. Leave out anything not everyone should read.
  • The project holds a copy of the files you added. If the real document changes, update the copy in the project.

Common mistakes

  • Too broad. One project for everything ends up good at nothing.
  • Old files. Last year's capability statement quietly gets quoted as current.
  • Too many files. Fifty documents of mixed quality give mixed results.
  • Long, rambling instructions. If a person couldn't follow them, neither will the AI.
  • Set and forget. Without an owner, a project goes stale in months.

Where projects stop

A project holds context for one body of work. It isn't a shared memory for the whole team, and it doesn't run anything by itself. For a process you repeat across many jobs, save it as a skill. For a job that should happen every Monday, use a scheduled task. Projects are where to start, because the other two work better once your context is in order.

If you're still choosing a tool, see ChatGPT or Claude for work?

Where I come in

I run in-house workshops built around your team's own documents, weighted to whichever tool your organisation uses. My public course, Claude and ChatGPT at work, covers both tools side by side.

Workshops for your team · See the course · Or call 0412 724 412

Questions people ask

Do we need a paid plan?

Both tools offer projects on their free plans, with limits. For work, use a business plan: that's where sharing with colleagues and the stronger privacy defaults are.

Is it the same in Copilot?

The habits are the same: one job per space, short instructions, current files and an owner.

How is a project different from a custom GPT or a skill?

A project holds the context for one body of work. A custom GPT or a skill saves a way of doing a task so you can reuse it anywhere.

More guides

All guides · Agentic workflows, step by step