A SharePoint form can carry its own conversation. The Comments control in Ultimate Forms places SharePoint's native comment feed directly inside your modern form: threaded replies, @mentions that notify colleagues by email, and the same underlying storage SharePoint itself uses, so nothing lives in custom columns or outside systems. Unlike the built-in comments pane, which sits apart from the form, the control is a form element you position anywhere, next to the approval section, under the review details, wherever the discussion belongs. This guide covers what the control does, where it earns its place, and how it combines with rules. For the full set of form capabilities it joins, see the ten must-have features.
The conversation that leaves the record
Watch what happens around any shared list item that people actually work on. An approver needs a clarification, so an email goes out. The requester replies, copying someone. A follow-up lands in Teams. By the time the item is approved, the reasoning behind it is scattered across three tools, visible to the participants and to nobody else, and findable by no one in six months.
The cost is not the messages; it is the separation of the conversation from the record. When the discussion about an item lives apart from the item, every future reader gets the decision without the reasoning, every auditor gets the what without the why, and every handover loses the context that made the case make sense.

SharePoint's own comments pane was built for exactly this, and it works, with one limitation that matters to form builders: it is a pane, outside the form, in a fixed position, indifferent to your layout. A carefully designed process form with tabs, sections, and permission rules ends up with its conversation bolted to the side rather than placed where the discussion happens. The Comments control closes that gap: the same comments, as a first-class form element.
What the control provides
Native storage. The control reads and writes SharePoint's own comments, using the same mechanism as the built-in pane. Comments added through the form appear in the pane and vice versa, nothing is duplicated, and no custom columns or external services hold the data. Compatibility with the rest of the Microsoft 365 ecosystem comes free.
Mentions. Typing @ resolves colleagues the familiar way, and SharePoint notifies the mentioned person by email. A question aimed at a specific approver reaches that approver, not a distribution list, which is what turns a comment feed from a noticeboard into a working channel.
Notifications. New comments and mentions generate notifications through SharePoint itself, so participants stay informed without polling the form.
A readable feed. Comments display chronologically with authors, timestamps, and threaded replies, so a newcomer to the item can read the discussion top to bottom and arrive informed.
Placement anywhere. The control drops onto the form canvas like any other element: inside a tab, beside a section, under the decision block. Because it is a form element, it participates in the layout system, containers, tabs, and columns, rather than floating outside it.
Lists and libraries alike. Support tickets, expense reports, policy documents, inspection records: anywhere modern forms run, the conversation can run with them.
Where the control earns its place
Help desk. A technician needs more information, posts a comment, and mentions the requester. The requester is notified, answers in the same feed, and the exchange stays attached to the ticket permanently. The next technician to open the ticket reads the whole history; nobody forwards an email chain.
Onboarding. HR and the hiring manager settle start dates and equipment in the form itself, mentioning IT when access needs a decision. Each party sees the full discussion, and the onboarding record carries its own coordination trail.
Expense review. An approver queries a receipt in a comment rather than an email; the employee clarifies in place. The approval machinery records the formal decisions; the comments hold the informal back-and-forth that preceded them, and the pairing is the complete story of the expense.
Document review. Legal and compliance reviewers flag concerns against the document's record in the library, creating a lightweight internal audit trail alongside the content itself.
Projects and inspections. Status updates, field clarifications, and supervisor answers accumulate on the task or inspection item. An inspector who tags a supervisor from the field gets an answer in the record, not in a text message that evaporates.
The common shape across all five: the comment thread is for dialogue, questions, context, and reasoning. It complements the structured columns rather than replacing them, which leads to the one design rule worth writing down.
Comments are not columns
A comment feed is seductive, and the failure mode is letting data migrate into it. "Approved, see my comment" is a process smell: decisions belong in status and decision columns where rules, views, and reports can read them, while the comment holds the reasoning behind the decision. The same split governs dates, amounts, and assignments. Anything a rule might ever need to react to goes in a column; anything a human might need to understand goes in the thread. Forms that keep this discipline get the best of both: machine-readable state and human-readable context, side by side.
The inverse discipline also pays: when a clarification in the comments changes the facts, the columns get updated too. The thread explains; the columns record. A reviewer should be able to trust the columns without reading the thread, and enjoy the thread without re-deriving the columns.
Combining comments with rules
Because the control is a form element, the rule engine treats it like one, and the combinations are where it becomes process machinery rather than a chat box.
Permission rules show or hide the feed by role, stage, or data: a sensitive HR case can restrict the discussion to the case team; a procurement form can reveal comments only once the item leaves Draft, so the record stays clean while the author is still composing it. Placed inside a tab, the control inherits the tab's permissions, so a Review tab visible to approvers naturally scopes its conversation to approvers.
Layout does the quieter work. Putting the feed beside the section it discusses, the comments next to the decision block on an approval form, means the approver reads the request, the history, and the open questions in one eyespan, which is the usability argument for inline placement in the first place. And for the formal record, versioning and audit history run underneath as always: the comments narrate the item's life while the logs prove it.
Getting it onto a form
The build is one move: open Form Designer from the list's Design button, drag the Comments control from the control pane to its place on the canvas, and publish. Mentions and notifications need no configuration, because SharePoint's own mechanism carries them. The design time goes where it should, into deciding placement and whether any permission rules should scope the feed, which the sections above cover. Users need no training at all: the feed looks and behaves like comments everywhere else in Microsoft 365, which is precisely the point of building on the native mechanism. Adoption, for once, is not a project; it is a drag and a publish.


