Collecting ideas is the easy part of improving software. The hard part is keeping the context of an idea, letting a person decide whether it matters, and being able to trace the change that came out of it back to the problem that prompted it.
A suggestion box that remembers where you were
The OAS console has a "Suggest an improvement" control. Members of the OAS team can use it to save an observation about OAS itself, with up to three screenshots.
Along with the words, it records a cleaned-up note of where the observation was made: which part of the console, the page with any record identifiers replaced by placeholders, which record the page was about, and which release of OAS was running. It never stores the page's title or anything typed on the page. Screenshots are stored privately, and only the person who sent them and an administrator can open them.
Contractors using the OAS client portal can send a suggestion too. It reaches the same inbox and can include up to three screenshots; submit-only, the portal shows no history or status of what they sent.
Saving an idea is not deciding to build it
Sending a suggestion and deciding what happens to it are separate permissions. Team members can send one; only an administrator can triage it, moving it from New to Reviewed to Closed. A closed suggestion records one outcome: implemented, declined or duplicate.
Accepting a suggestion does not authorise anyone to build it. Engineering work starts as its own tracked issue, with its own scope, and a person links the two by hand. A suggestion cannot be closed as implemented without a reference to the change and a note saying how it was verified, and the database refuses the record without both.
The change that came out of it
Someone on the OAS team was looking at a client's page in the console and wanted to go straight to that client's leads. The page only offered a link to the client's full lead list at the bottom of one section, and only when the client had more leads than that section shows. Otherwise it meant opening the leads list and filtering it by hand. A small gap, but one that came up every time.
They saved it as a suggestion from that page. After review it became a scoped issue: add a way from the client page to that client's leads, reusing the existing leads list and filter, with no new navigation system. The result is a "Leads" button in the client page header that opens the leads list already filtered to that client. Only team members allowed to see leads see the button.
The change went through our usual path before it merged in early October 2026: an automated code review, the automated test suite, and a separate review of the changed screen against its approved screenshots by a reviewer who did not write it.
A suggestion is worth more when the change it produced can be traced back to the task that prompted it.
Where this story stops
Our process has seven steps: notice a problem, save it with its context, triage it, admit it as development work, ship it, verify it, and close the suggestion with the evidence. A merge covers everything up to shipping the change. The last two steps belong to a person, because a merge is not proof.
For this change, both have now been done. The administrator who saved the suggestion triaged it and admitted it as development work. After the change had been reviewed and merged, it was running on the production system. They then used it there against the original observation: on a client's page, the Leads button in the header opened the leads list with that client already selected and the filter matching, and Back returned to the client page. That check was made on the evening of 10 October 2026, US Eastern time. The next day they closed the suggestion as implemented, with a reference to the change and a note of what they had checked. The database would not have accepted the closure without both.
That is one observation, followed from the console to the live system and back to its record. It was made by someone on our own team, not by a customer, and it is a small change. It shows that the loop can be completed, and what completing it leaves behind. It is not a claim that the rest of our engineering process has been verified to the same standard.
If you run a contracting business and want to see how OAS works, get in touch.