Change Requests
A guide to requesting modifications to existing features in your application.
What is a Change Request?
Understanding when to use a change request.
A change request modifies something that already exists in your system. It's not adding new functionality - it's adjusting how current functionality works.
Think of it like renovating a room rather than building a new one. The structure is there, you're just changing how it looks or works.
Examples of change requests:
- Change the "Submit" button text to "Place Order"
- Make the customer list sort by name instead of date
- Update the email template wording
- Move the search bar to the top of the page
- Increase the maximum upload file size
How to Describe Your Change
The clearer your request, the faster we can implement it.
Describe current vs desired
The most helpful format is: "Currently X happens, but I'd like Y instead."
Currently:
"The report shows all orders from the past month"
Desired:
"Show only orders from the past week by default"
Be specific about location
Tell us exactly where the change should happen. Screenshots are incredibly helpful here.
Instead of:
"Change the button colour"
Try:
"Change the 'Add to Cart' button on the product page from grey to blue"
Explain why (optional but helpful)
Understanding the reason behind a change helps us suggest better solutions. Sometimes there's an easier way to solve the underlying problem.
Example: "Customers are missing the checkout button because it blends into the background. Could we make it more prominent?"
Change, Feature, or Bug?
Choosing the right task type.
| Type | Use When... | Example |
|---|---|---|
| Change | Something works, but you want it to work differently | "Make the logo bigger" |
| Feature | You need something that doesn't exist yet | "Add a dark mode toggle" |
| Bug | Something is broken or not working as intended | "Form won't submit on Safari" |
Tip: If you're unsure, just pick your best guess. We'll recategorise it if needed - it won't slow anything down.
Frequently Asked Questions
Common questions about change requests.
All work is billed at the standard rate. What seems like a "small change" often involves more than meets the eye - testing, deployment, documentation. That said, small changes are quick, so they don't cost much.
It's better to submit each change separately. This makes it easier to track, review, and approve them individually. If one change needs revision, it won't hold up the others.
Sometimes a seemingly simple change reveals hidden complexity. If that happens, we'll let you know before proceeding. You can then decide whether to continue or find an alternative approach.
Yes. If you don't like how a change turned out, submit a new change request to revert it or adjust it further. This is why we have the staging review step - so you can catch issues before they go live.
Absolutely! Screenshots are incredibly helpful, especially for visual changes. After submitting your task, click on it to upload images. You can annotate them to show exactly what you mean.
Ready to submit a change?
Head back to your project and click the "Change Request" button to get started.
Back to Portal