How to Request Work or Raise an Issue

When you need something from us, or when something isn't right, you should never have to wonder how to tell us. This article covers the simple, reliable way to request work or raise an issue, so nothing gets lost in a hallway conversation or buried in an email thread.

Use the channel we set up

At kickoff, we establish a clear way for you to send requests and flag issues, a single, agreed channel, so everything lands in one place and gets tracked. Using it (rather than catching someone in passing) matters for one reason: things that go through the channel don't get forgotten. Things mentioned casually sometimes do. The channel exists to protect your requests.

What makes a request easy to act on

You don't need to write a formal spec, but a few details help us move faster:

• What you need, described in terms of the outcome you want, not necessarily the technical fix.
• Why it matters, the context or the problem behind the request. This often changes the best solution.
• How urgent it is, so we can prioritize honestly against everything else in flight.

Even a rough version of these turns a request around faster than a one-liner with no context.

Raising an issue

If something's broken, confusing, or just not what you expected, tell us plainly and early. We'd genuinely rather hear "this doesn't feel right" while it's small than discover a bigger problem later. Describe what you're seeing and what you expected instead, that contrast usually points straight at the fix.

What happens next

Once a request or issue is in, we acknowledge it, sort out priority against the rest of the work, and tell you what to expect, including if it's a change in scope (see "How We Handle Scope & Change Requests"). You'll always know we've got it and roughly when it'll be handled. The whole point is that nothing you raise disappears into a void.