User feedback plays a crucial role in shaping the future of G.J. Software. The built-in feedback portal allows you to browse existing feature requests, vote on ideas that matter most to your workflow, and submit new suggestions directly to the product team. This article explains how to access the portal, search for existing ideas, and submit well-structured feature requests.
Accessing the feedback portal from G.J. Software
To open the feedback portal from within G.J. Software:
On the top navigation bar, click the Help icon.
Select Send Request to Support. A chat interface will open.
In the chat window, scroll down to the Give feedback section.
Direct access
You can also access the feedback portal directly at feedback.gjgardner.com. This portal allows you to:
View the product roadmap — Track the development progress of upcoming features and improvements.
Interact with feature requests — Browse the full list of existing features to vote on ideas or submit your own suggestions.
Access the application changelog — Review a log of recent updates and new releases published for G.J. Software. You can even subscribe to the changelog to receive automatic email updates as new entries are published.
Note: The feedback portal requires you to sign in with your Google Account.
Browsing existing feature requests
Before submitting a new idea, you should review existing requests to avoid duplicates and to add support to ideas that already align with your needs.
The feedback portal provides the following tools for browsing:
Filter by rating — Narrows the list to requests with a specific vote count or popularity level.
Filter by status — Narrows the list to requests at a particular stage (e.g., under review, planned, or completed).
Filter by category — Narrows the list to requests for a specific product area, such as Sales or Eastimating.
Search bar — Allows you to search for requests by keyword.
Checking for similar ideas
Before creating a new request, you should check whether a similar idea already exists:
Click the + icon on the feedback portal.
Select a category for the idea (e.g., Job Administration or Scheduling).
Type a title for the idea. The system automatically suggests similar existing ideas as you type.
Review the suggested ideas. If a match exists, you can vote on or comment on the existing idea instead of creating a duplicate.
Voting and commenting on existing ideas
When you find an existing idea that aligns with your needs, you can add your support in two ways:
Vote — Click the Vote button on the idea to increase its priority ranking. Each vote signals to the product team that the idea has broad demand across the franchise network.
Comment — Click the idea title to open its detail page, then add a comment describing a specific use case, additional context, or a variation on the original idea.
Note: Voting or commenting on an idea makes you a watcher of that request. Watchers are automatically notified whenever the product team posts a comment or question, or when the status changes (for example, when a request moves to Planned, In Progress, or Completed).
Submitting a new feature request
If no similar idea exists after searching and reviewing suggestions, you can proceed to submit a new request:
Click the + icon on the feedback portal.
Select a category for the idea.
Type a descriptive title for the idea. Review any similar ideas the system suggests.
If no existing idea matches, continue creating the new request.
Enter a Description — provide enough detail to explain the problem, the workflow affected, and the desired outcome. The more context provided, the easier it is for the product team to evaluate the request.
Submit the idea.
Tips for writing effective feature requests
A well-written feature request helps the product team understand the need, assess its impact, and prioritise it appropriately. The following guidelines improve the quality and visibility of a request.
Be clear and specific
Describe the desired feature in concrete terms. Vague requests are harder to evaluate and implement.
Vague: "Make reports better."
Specific: "Add a 'Client Email' column to the 'Jobs in Progress' report."
Explain the "why"
Describe the problem the feature solves or the pain point it addresses. Context helps the product team understand the urgency and relevance of the request.
Describe the "who"
Identify which roles or user groups benefit from the feature. For example, a request might primarily benefit franchise owners, site supervisors, sales staff, or office administrators.
Highlight the value or benefit
Explain the tangible outcome the feature delivers, such as saving time, reducing manual errors, improving client communication, or eliminating duplicate data entry.
Focus on one idea per request
Each request should address a single feature or improvement. Bundling multiple ideas into one request makes it difficult to track, vote on, and prioritise each idea individually.
Check existing ideas first
Search the feedback portal before submitting a new request. Voting on an existing idea that matches your need is more effective than creating a duplicate, because consolidated votes carry more weight with the product team.
Optionally suggest a solution
If you have a specific implementation in mind, you can include it in the request. However, the request should still clearly describe the underlying problem so the product team can evaluate alternative approaches.
Feature request template
The following template helps structure a feature request clearly and consistently:
As a [Role], I want [feature], so that [benefit].
Example:
As a Job Administrator, I want a 'Client Email' column added to the 'Jobs in Progress' report, so that I can quickly contact clients about construction updates without switching to the client record.
User feedback and ideas are crucial for improving G.J. Software for all G.J. Gardner Homes franchises. This article outlines the process for submitting feature requests directly through the application and provides tips for making requests clear and impactful.