Help Article

Submit Profile Update Requests the Right Way

How institution users should prepare profile update requests so they are easier to review and approve.

Best for

Claimed institution accounts

Primary outcome

Higher-quality update requests

Core principle

Evidence beats explanation

Students standing together near a campus building.
Students studying together.

Research Workspace

Structured review usually beats reactive browsing when students are making important education choices.

Students on campus.

Campus Overview

CampusPin articles pair practical guidance with visuals that help readers interpret decisions more clearly.

Decision diagram

Clarify the question

The best update requests are specific, supported, and limited to what actually changed.

Evaluate with evidence

Protected fields require stronger documentation and review discipline.

Take the next step

Clean requests help CampusPin keep public data trustworthy.

Key takeaways

The best update requests are specific, supported, and limited to what actually changed.
Protected fields require stronger documentation and review discipline.
Clean requests help CampusPin keep public data trustworthy.

Article details

Category

Institutions

Updated

Read time

4 min read

Audience

Institution representatives

Write update requests like a reviewer has to verify them

  • Name the field that needs to change clearly.
  • State the current value and requested value precisely.
  • Explain why the change is needed in plain language.
  • Reference supporting evidence whenever possible.

Keep the request narrow and factual

Large bundled requests are harder to validate quickly. When possible, separate distinct updates so each one stays easy to review.

Best practice

If a change affects published tuition, admissions, or other protected fields, provide the clearest supporting evidence you can rather than relying on a general explanation.

Frequently asked questions

Can I update every field directly?

No. Some fields are protected and require review in order to preserve data quality and source integrity.

What makes a request slower to review?

Vague descriptions, unclear evidence, and bundled changes that mix unrelated updates usually slow the process down.

Related resources

Keep going

View all