Monitor
Requested
Samsung Odyssey OLED G8 import check
14Likes
1Dislikes
87%Meter
Live request status board
Community Requests
Follow monitor, brand, guide, and correction requests from submission to listed pages. This board connects public demand, voting signals, editorial review, and final MonitorSuggest links in one transparent workflow.
Request meter
What the community wants next
Requests start as signals. The board becomes useful when each request has status, demand, context, and a final listed link when completed.
3Total requests
1Under review
1Upcoming
53Community likes
Overall queue completion0%
1Submitted
Requests arrive from Suggest a Monitor or Brand.
2Voted
Community likes and dislikes reveal demand.
3Reviewed
Add new requestSubmit monitor, brand, guide, or correction
Editors verify specs, duplicates, country context, and usefulness.
Status board
Request progress by stage
Every column maps to a backend status so future monitor imports, brand tracking, and editorial work stay visible.
Requested 1
Fresh request waiting for community and editor signals.
Under Review 1
Specs, relevance, duplicates, and country context are being checked.
Monitor
Under Review
LG UltraGear 27GP850-B country links
22Likes
2Dislikes
92%Meter
Upcoming 1
Approved request being prepared for a page, guide, or database entry.
Brand
Upcoming
Add MSI brand tracking for India
17Likes
3Dislikes
78%Meter
Listed 0
Completed request with a public MonitorSuggest link.
No requests here yet.
Monitor requests
All Monitor Requests
Brand, model number, use case, country, and demand signals help decide what should become a monitor page next.
Monitor
Under Review
LG UltraGear 27GP850-B country links
Readers want this popular 1440p IPS monitor mapped with exact store links and comparison data.
22Likes
2Dislikes
92%Meter
Monitor
Requested
Samsung Odyssey OLED G8 import check
Needs exact regional model verification before it can be compared fairly against other OLED displays.
14Likes
1Dislikes
87%Meter
Brand tracking demand
All Brand Requests
Brand requests can inform brand profiles, country coverage, after-sales research, and affiliate/store setup priorities.
Brand
Upcoming
Add MSI brand tracking for India
Users want MSI monitor availability, service signals, and model coverage visible in Brands We Track.
17Likes
3Dislikes
78%Meter
Workflow guide
How the community request workflow builds trust
A monitor database becomes genuinely useful only when it reflects the questions buyers are actually asking. Many comparison sites keep repeating the same popular products long after the market has moved. MonitorSuggest uses Community Requests to show what is missing, what deserves review, and which brands need closer tracking.
The workflow is intentionally public. A request starts as Requested when a reader submits a monitor, brand, guide topic, or correction. At that point it is not a recommendation. It is a signal that someone believes the item is missing or important. Other visitors can support the request, and editors can move it through review stages.
Submitted
A reader adds a monitor model, brand, missing guide, or correction with country and use-case context.
Reviewed
Editors check duplicates, model accuracy, available specs, affiliate eligibility, and whether the request fits MonitorSuggest coverage.
Listed
Completed requests connect to a real page, such as a monitor detail page, brand profile, comparison, or guide.
When a request looks useful, the backend status can be changed to Under Review. For a monitor, that can include checking specs, panel type, refresh rate, response time, regional availability, store mapping, and how it fits into Find Monitor or Compare. For a brand, that can include country presence, product lines, service notes, warranty reputation, and after-sales signals.
Upcoming means the request has moved beyond basic screening and is being prepared for coverage. Listed is reserved for completed items, and the backend stores a link so readers never see a completed status that leads nowhere. This creates a clean internal path from user demand to final content.
Moderation is part of the trust system. User-generated requests can become noisy if every submission is treated as authoritative. Here, requests are public signals, not final editorial claims. Admins can adjust status, likes, dislikes, meter values, and listed links from the backend, giving the community a voice without losing editorial quality control.
Frequently asked questions
Community Requests FAQ
Why is Community Requests separate from the suggestion form page?
The suggestion form is built for submitting a new idea. Community Requests is the public status hub where readers can see progress, voting, meters, and listed links.
What do the request statuses mean?
Requested means submitted, Under Review means relevance and data are being checked, Upcoming means coverage is being prepared, and Listed means a public MonitorSuggest link exists.
Who controls the request status?
The backend controls request status. Community votes can influence priority, but editors decide when an item is under review, upcoming, or listed.
Why does a listed request need a link?
A completed request should lead to something useful, such as a monitor page, comparison, brand profile, or guide.
How does the request meter work?
The meter reflects public demand from likes and dislikes. Admins can override it when editorial context matters.
Can brand requests affect other parts of the site?
Yes. Brand requests can feed Brands We Track, after-sales coverage, store mapping, and future monitor imports.
Can monitor requests affect Find Monitor and Compare?
Yes. Once listed, a monitor can sync into filters, compare tables, trending sections, and single monitor pages.
How is request spam controlled?
Public requests are treated as signals, not final claims. Admins can moderate status, meter values, listed URLs, and visibility from the backend.
Can I request a correction?
Yes. Corrections can be tracked alongside monitor and brand requests when the issue affects specs, links, images, or editorial context.