{"id":1643,"date":"2025-10-09T11:29:46","date_gmt":"2025-10-09T11:29:46","guid":{"rendered":"https:\/\/journal.matchmyproject.org\/?p=1643"},"modified":"2025-12-03T15:07:39","modified_gmt":"2025-12-03T15:07:39","slug":"feedback-updates-part-1","status":"publish","type":"post","link":"https:\/\/journal.matchmyproject.org\/index.php\/2025\/10\/09\/feedback-updates-part-1\/","title":{"rendered":"Feedback updates: Part 1"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

On Match My Project, second to matching, feedback is one of the most important parts<\/strong> of the project lifecycle. <\/p>\n\n\n\n

Not only does it help you know that what’s pledged has been delivered<\/strong>, but it gives an indication of what was donated<\/strong> during the project and provides a check on user behaviour<\/strong>.<\/p>\n\n\n\n

We saw opportunities to improve the integrity and effectiveness<\/strong> of feedback, thanks to user insights from across the platform, importantly the Authority User Group.<\/p>\n\n\n\n

Now, recent updates mean you can get more accurate data<\/strong> and more timely feedback<\/strong>, making it easier for you to effectively oversee and track the impact<\/strong> of the matches in your network.<\/p>\n\n\n\n

\u2705 Due dates make matches easier to track<\/strong><\/h3>\n\n\n\n

Now, you can track matches more easily with the addition of a provisional due date, which is created when organisations match.<\/p>\n\n\n\n

This means that you’ll always be able to see when a match is meant to be completed – just go to the header of the project or offer in progress. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

\ud83d\udca1 How it works<\/strong><\/p>\n\n\n\n

The organisation that accepts the request to match is asked how many weeks the project should take.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This allows a provisional due date to be created.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This date is displayed in the project header (below the title) and can be edited by the community organisation or supplier involved in the project. <\/p>\n\n\n\n

If the date is edited, the other organisation gets a notification.<\/p>\n\n\n\n

\u2705 Less chasing for authorities thanks to better feedback reminders<\/strong><\/h3>\n\n\n\n

Now that there’s a due date for new projects, users are automatically sent new tailored reminders to complete feedback<\/strong>, to help reduce the amount of chasing you have to do to get projects completed. <\/p>\n\n\n\n

\ud83d\udca1 How it works<\/strong><\/p>\n\n\n\n

Users are notified halfway<\/strong> through the project and the day after<\/strong> the estimated due date so that they can either complete feedback or amend the due date.<\/p>\n\n\n\n

Projects created before estimated timescales were introduced have had their notifications upgraded too: they now get a fortnightly reminder<\/strong> asking them to add feedback or add an estimated due date.<\/p>\n\n\n\n

And if one organisation has already given feedback<\/strong>, the other organisation is notified and sent multiple reminders to complete their feedback.<\/p>\n\n\n\n

Better visibility, less admin.<\/p>\n\n\n\n

\u2705 More confidence in the data <\/strong><\/h3>\n\n\n\n

To give you more confidence in the metrics being shared, both parties<\/strong> will be able to input or verify the value of resources<\/strong> that were given as part of a match. Previously VCFSEs had to input these values when sharing feedback.<\/p>\n\n\n\n

At the moment authorities can see both sets of figures. Very soon, you’ll be able to choose which figures to use in your data.<\/p>\n\n\n\n

\ud83d\udca1 How it works<\/strong><\/p>\n\n\n\n

The user who is first to give feedback enters what was given.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The organisation that is second to give feedback confirms these figures or adds their own.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

\u27a1\ufe0f Coming soon\u2026 more flexibility<\/strong><\/h3>\n\n\n\n

1. Choose public figures for more accuracy<\/strong><\/p>\n\n\n\n

Be confident in the figures that are publicly displayed (hours, value of resources and donations). Where community organisations and suppliers report different amounts you can choose which to use.<\/p>\n\n\n\n

2. More control over what is displayed<\/strong><\/p>\n\n\n\n

You’ll be able to show and hide data points from feedback one by one. If one piece of feedback incorrect, the rest can still be displayed while the incorrect feedback is edited.<\/p>\n\n\n\n

3. More editing controls so corrections can be made<\/strong><\/p>\n\n\n\n

At the moment, feedback can only be edited for a month after it\u2019s given. But we know that sometimes updates are needed after that window closes. Soon, users will be able to request changes to feedback<\/strong> even after the edit period has passed.<\/p>\n\n\n\n

\n\n\n\n

See <\/strong>Feedback Updates: Part 2<\/b><\/strong><\/a>\u00a0here.<\/b><\/span><\/p>\n\n\n\n

\ud83d\udca1 Have suggestions for future updates? We\u2019d love to hear them. Email us at support@matchmyproject.com<\/a><\/strong>.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

On Match My Project, second to matching, feedback is one of the most important parts of the project lifecycle. Not only does it help you know that what’s pledged has been delivered, but it gives an indication of what was donated during the project and provides a check on user behaviour. We saw opportunities to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28,23,15],"tags":[],"class_list":["post-1643","post","type-post","status-publish","format-standard","hentry","category-guidance","category-authority","category-product","entry"],"_links":{"self":[{"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/posts\/1643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/comments?post=1643"}],"version-history":[{"count":8,"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/posts\/1643\/revisions"}],"predecessor-version":[{"id":2005,"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/posts\/1643\/revisions\/2005"}],"wp:attachment":[{"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/media?parent=1643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/categories?post=1643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/journal.matchmyproject.org\/index.php\/wp-json\/wp\/v2\/tags?post=1643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}