Project · Stakeholder Input
Route /project/feedback Menu Project → Feedback

Feedback

Manage feedback templates and campaigns with response visibility across projects.

Feedback templates, campaigns, and response tracking for project stakeholders.

Stakeholder input

Templates and campaigns on live projects

Feedback manages templates and campaigns with response visibility across projects. Responses attach to delivery you already run — they are not a separate CRM of opinions.

Projects → Feedback Route /project/feedback Project Manager · Admin

The job of this console

Pick a template, run a campaign, read responses, and act on the project or task. Do not store the only copy of a decision only inside a survey if it changes scope — update the task.

Seat at the table

PMs and admins. Respondents may be clients or team depending on the campaign.

The working rhythm

Create or reuse a template, launch on a project, watch responses, follow up on delivery screens.

Moments that bring you here

Sprint review. Client pulse. After a milestone. When a campaign had zero responses.

ⓘ
Campaigns, not a second project
Feedback does not replace Task or Project as the place scope lives.

Overview

Feedback workflows collect structured stakeholder input and can be launched from module-level page or project details.

Screen layout

Header: Create/configure actions, filters, search.
Body: Templates/campaign list and summary indicators.

Header & filters

Use campaign status and date filters where available to focus active collection windows.

Summary & charts

Summary cards typically highlight active campaigns, response rates, and pending requests.

Main content & actions

Launch campaigns and share external document routes for respondents who do not need full app access.

Complete feature list

Every control, panel, and workflow on this screen.

  • ✓
    Luxury UI shellEmerald-themed glass cards, sticky gradient header, module sidebar, and responsive layout.
  • ✓
    Documentation searchHeader search indexes all guide pages (docs site).
  • ✓
    Feedback registerSubmitted feedback items with status.
  • ✓
    CREATE feedbackNew feedback linked to project/deliverable.
  • ✓
    Rating captureScore and comment fields.
  • ✓
    Filter by projectScope list to engagement.

Before you start

💡
Milestone retro
CREATE feedback within 48 hours of deliverable complete while context fresh.
ℹ️
Account QBR
Export resolved feedback for quarterly business reviews.

Who uses this screen

Project managers and client liaisons capturing structured feedback — ratings, comments, status, linked to projects and deliverables.

ℹ️
Client feedback register
Log feedback after milestones — links to project context for retrospective and account reviews.

Key concepts

Feedback register

Items with rating, comment, status, project/deliverable link.

CREATE feedback

New entry with score and narrative.

Rating capture

Numeric or star score per org config.

Status workflow

Open → acknowledged → resolved.

Project filter

Scope list to engagement.

Permissions

RoleAccess on this screen
Project managerCreate and resolve feedback on owned projects.
Account managerCreate/view for client accounts.
Team memberSubmit internal feedback if enabled.
Client (external)Submit via portal if licensed — not this register.
📝
Administrator override
Org administrators and service accounts configured in the Admin console may bypass row-level scopes shown above. When in doubt, confirm access with your Tracopus administrator.

Controls reference

ControlDescriptionNotes
CREATE feedbackNew feedback modal.Requires project link.
Rating fieldScore input.Required on create.
CommentFree text narrative.Rich text if enabled.
StatusOpen/acknowledged/resolved.PM updates.
Project filterDropdown scope.—
Row detailFull thread/history.—
ExportFeedback list.QBR input.

Common mistakes

⚠️
Anonymous harsh feedback
Use constructive template — identifiable entries improve follow-up.
⚠️
No project link
Orphan feedback useless in account review — always link project.
⚠️
Leaving status Open
Resolve after action taken — Open queue grows unbounded.

FAQ

Who sees feedback?

Project members and account managers — not all company.

External client submissions?

May arrive via portal into same register with badge.

Rating scale?

Org config — typically 1–5 or 1–10.

Link to deliverable?

Optional — helps tie to milestone retros.

Workflows

  1. Create or edit feedback template.
  2. Launch campaign for project/stakeholder set.
  3. Track responses and follow up.
  4. Review project detail Feedback tab for context.

Tips & best practices

Tip: Keep question sets concise; shorter templates usually improve response completion rates.

More guidance

💡
Remember
Items with rating, comment, status, project/deliverable link.
ℹ️
Who sees feedback?
Project members and account managers — not all company.