Assessment sharing, decisions and approvals - Product News

This entry follows The Help Centre and guided tours and covers the changes since. Screens use Backed's default words; if your organisation has renamed any of them under Settings > Organisation > Terminology, you see your own words instead.

Share assessments. Assessments > Sharing shares the assessments you choose with assessors, an applicant or a verifier, with or without the scores and the assessor's name. Only the fields ticked Shared Assessment on the form are shown, here and among other assessors' assessments in an assessor's PDF. See Assessment sharing.
Assign by answer. Assign by rule gains a By answer mode that gives chosen assessors every application whose answer matches, such as each one from the North region, and Bulk Assign gives chosen assessors chosen applications at once. See Assignments.
From a round's assignments. Sharing on an assessor's row lets them read assessments of this round or an earlier one. See Assignments.
In the portals. Assessors, applicants and verifiers find Shared Assessments in their menu once something is shared with them: a read-only copy of only what you chose to share. See Shared assessments, for assessors and Shared assessments, for applicants.

Funding decisions

Decline reasons. Keep categories of decline reasons under Settings > Decision Reasons, each with the applicant's wording and a reporting code. Every declined application needs one, and a Letter of Decline can include it. See Decline reasons.
Decision rationale. Record why each application was approved or declined; the applicant never sees it. A round's Require rationale says which need one, and the probity checklist now checks them. See Funding decisions and The probity checklist.
Decline queue. A round can hold sent declines for up to 90 days. Nothing reaches the applicant until a decline is released on time or with Release now, or it is cancelled. See Decline queue.
The decision record. Export decision record on an application's Decision panel makes a PDF, and a CSV, of how the decision was reached, each fact citing its audit entry. See The decision record.

Approvals and access

Approval limits. Set each administrator's Decision, Contract and Milestone approval limits. Sending or approving above a limit is refused, and Request Review or Request Reviewer passes it to someone whose limit covers it. See Approval limits.
Field reviews. A change to a round's funding amount or date that you mark for review waits for a second person to approve it. See Field reviews on a funding round.
Admin Groups. Users > Admin Groups lists your groups with their members and Data Access Rules; editing them on screen follows later. Conflict of interest alerts now reach only reviewers whose access covers the round. Six common set-ups, from a read-only auditor to separate payment approvers, are checked before every release. See Admin groups.
Exports need a report permission. A payment batch export or bank file, an assessment round's ranking or draw, and the disposal record now also need Can generate reports or Can generate document reports. See Payment permissions and separation of duties.

Milestones and payments

Holds and versions. A milestone named by an open budget variation request can't be paid, and its page says why. Its History opens every submitted version, the approved one marked. See Milestones and batches.
Each amount in its own currency. A batch export has a Currency column, a Dashboard figure in two currencies is shown once for each, and a bill outside your accounting system's base currency stops as Currency not supported. See Exports and bank files and Accounting sync errors.
Contact changes reach your accounting system. Approving a contract request that Changes the primary contact updates the contact in Xero, MYOB or QuickBooks Online; a failure keeps the change in Backed and emails your sync-error contacts for Xero and MYOB. See Accounting sync errors.

API

Applicants. GET /api/v2/registration_entities lists your registered organisations and individuals, and /:id returns one with its members. See API access.
Milestones. GET /api/v2/milestones lists milestones with their status, amount, payment date and answers, filtered by ids, tags or an answer; /:id returns one. See API access.

Also

Behind-the-scenes work on data reports, collaborators, scoring matrices, independence rules, committee records, outcomes frameworks, reporting schedules, milestone commitments, bank account verification, refunds, cashflow, in-kind awards and indexation.

Was this helpful?