Digital UNV — User Guide

How digital demands move from submission to delivery
← Back to Tracker Open full SOP (SharePoint) ↗
This page summarizes the official SOP-ICTS-100.1 (Standard Operating Procedure for Digital Demands)

It explains what each status in this tracker means, who is responsible at each stage, and how requests get prioritized. This is a working summary for quick reference — the SharePoint document above is the authoritative, signed-off version.

What the app can do

Digital is a live, read-only window on the Salesforce demand report, combined with ClickUp time, PPM budget and purchase orders. It never writes anything back to Salesforce. Everything below is one click from the menu at the top.

The menu in one picture

The menu is on the left. In order: Digital at a glance (The DGG, Your UNV apps, AI in UNV, Digital Strategy, Roadmap, Demands Overview, DGG Dashboard), Governance (Pipeline, Priority ranking, Strategy mapping, ICT Leadership, Finance, SOPs & policies, Workplan, Communication), Demands (Table, Kanban, Matrix, Data Quality), Operations (Maintenance, My notes, Team Management, Expenses analysis, Service Desk, Quantum, ClickUp, Licenses, Roles & access) and Adds-on (Demand popularity, Meeting cost calculator). Finance holds three buttons: Finance (budget, purchase orders and expenses together), Budget and Purchase Orders. Priority ranking shows the current priority rank of the open demands, one column per application, and downloads what is shown as a CSV file. The Maintenance notice is a button of the Maintenance page. The descriptions below keep the older grouping.

Everyday tasks

Find a demand

Use the filters (application, department, status, size, focal point, process flags), the free-text search or “Ranked only”. Clear filters resets everything.

Share a view

Copy link gives the exact filtered view to send to a colleague.

Export

Export CSV for the rows on screen; the admin can also export every field for an AI assistant.

On each demand

Icons on every row: Decision Log, case overview, Chatter, approval history, timeline (days in each status). The rank badge shows the DGG priority; the Effort & $ column shows the T-shirt size and cost.

Stay informed

The bell, a digest e-mail and phone notifications tell you about new demands, status, budget, effort, launch dates and new decisions — each says who did it. Checked every 3 minutes.

On a phone

A compact view: one card per status, tap to see its demands. Open the full site brings the normal pages back. Add the site to your Home Screen for phone notifications.

Dark mode

Account button (top right) → Appearance: System, Light or Dark.

Accessibility

Works with the keyboard, Skip to the main content on the first Tab, readable colours in both themes (WCAG 2.2 AA).

Sign in

Your @unv.org e-mail: one click on the link (or type the code of the same e-mail). A first sign-in is approved by the admin.

Help

The ? icon at the top right of the app opens this guide at any time.

Who sees what

RoleWhat you see
UserDigital at a glance only (the default role).
Super user · DGGThe whole app: dashboard, governance, demands and the operations pages.
Custom roleThe pages chosen for it on Roles & access.
AdministratorEverything, including the 🔒 pages, uploads and roles. The administrator can preview another role with View as.
Full reference text (every page and option described)

What it is. Digital UNV is a live, read-only window into the Salesforce DGG demand report — it never writes anything back to Salesforce — combined with ClickUp delivery time, PPM budget lines and purchase orders, so one place shows where each demand stands and what it costs.

Header and menu. The top bar has the app name (Digital UNV — Digital Management), the notification bell, the refresh button and, at the right, your account menu (your initials): your e-mail and role, the Salesforce connection status and Sign out (the administrator also finds View as there). Under the bar, the menu has Dashboard and three groups that open a sub-menu: Governance (Pipeline, Strategy, Budget, SOPs & policies, ICTS workplan, Public stories), Demands (Table, Kanban, Matrix, ClickUp) and Operations (Data Quality, Team Management, Service Desk, Meeting cost calculator and — depending on your role — Roles & access and Maintenance). The group of the page you are on is highlighted; an entry you are not allowed to use is simply not shown.

Dark mode, accessibility and phones. Open the round account button at the top right and choose Appearance: System (follows your device), Light or Dark. The choice is remembered in this browser. The app follows WCAG 2.2 level AA: everything works with the keyboard (Tab, Enter, Esc closes a window), a Skip to the main content link appears on the first Tab, the keyboard focus is always visible, colours keep a readable contrast in both themes and animations stop if your device asks for reduced motion. On a phone the pages fit the screen width, windows open full screen and buttons are large enough to tap.

Who sees what. A person with no role (the default User role) only sees the pages of Digital at a glance (The DGG, Digital Strategy: the pillars of the Digital Strategy 2026–2029 as illustrated cards, with the number of demands under each (delivered, being built, coming next), the list of those demands and, gathered from their Impact Assessment, what they say about their impact, grouped by theme (each demand shows its pillar tags; whoever may edit the strategy mappings, the administrator, has an Edit pillars button to tick several pillars); Your UNV apps; Demands Overview; and The DGG: the members of the Digital Governance Group with their function, a summary of its Terms of Reference and of the Prioritization Working Group's, and the pillars of the Digital Strategy 2026–2029, with links to the documents); the roles Super user, DGG and the custom roles give the whole app, the administrator chooses, for each role, which pages it can open on Roles & access (a table of pages by role). Pages. Digital at a glance (for every UNV colleague: what the digital team has completed, what is being built now and what comes next — each demand as a card with its focal point, its size, its stage and, for what comes next, its priority rank, with a link to its Salesforce case and the description behind it; links to the Strategic Framework, the Digital Strategy, the SOP and the UVP release notes; and a like button on every demand); DGG Dashboard (headline numbers such as active demands, demands waiting on Section Chief or DGG Chair approval and the DGG Prioritization queue, the pipeline and the applications, a Demand pressure section at the top (is more demand coming in than the team can deliver? — see below) and — at the bottom, collapsed until opened — Trends (demands per month, average time in each status), Workload by focal point and, with the right permission, Usage); Pipeline (an amber alert and a ⏳ Pending DGG approval pill flag the demands whose approval is waiting on the DGG Chairs; with the DGG Cleared status shown, a red alert and a No PO pill flag the cleared demands without a purchase order; a Prioritization overview tab (next to DGG Prioritization and All statuses) shows the current priority ranking of each application, with ▲ / ▼ to move a demand one place, or drag it by its handle to another place — as many demands as you like — and press the final OK to apply all the moves at once (nothing is saved before it, and the tab is not reloaded); the demands in DGG Prioritization, DGG Cleared, Req vetting or Tech implementation that hold no rank yet are at the end of their application's list, to drag into the ranking or put last; every change is recorded as a fast track of the DGG Prio Group (“Rank update”) and each demand has its Decision Log button for a classic, detailed decision (the demand number opens the case in Salesforce) and a Ranking history of every change (when, who, from where to where); a Prio group tick keeps only UVP and UVP-Quantum, the Prioritization Group's own applications; a Tech implementation tick includes or leaves out the demands already in Tech implementation; clicking a status of the pipeline graph keeps only the demands of that status in the lists below (click it again, or press Clear, to see them all); a Prioritization by dropdown of ticks (All / DGG Prio Group / DGG) shows all the demands, those prioritized by the DGG Prio Group (the applications UVP and UVP-Quantum) or those prioritized by the DGG (all the other applications); with DGG Cleared or Tech implementation shown, the list is ordered by priority rank; a Document generation dropdown makes DGG Prio. Group updates (Word: the pipeline and what each status means, then only the demands cleared by the DGG (status DGG Cleared, or Req Vetting as they passed the clearance) of UVP and UVP-Quantum — the Prioritization Group's scope — with their description and Decision Log, and the demands sent back after a decision; a window lets you untick demands first), Request for DGG prioritization (Word: the pipeline and what each status means, then 1. the demands in DGG Prioritization outside UVP and UVP-Quantum, put to the DGG for approval, 2. the demands cleared by the DGG Prio Group (DGG Cleared and Req Vetting), 3. the demands sent back after a decision; a window lets you untick demands first), the DGG status update (PowerPoint), the ICT handover (Word: the demands cleared by the DGG that are with ICT — those in DGG Cleared, for ICT to start the Requirements vetting, and those in Req Vetting, for ICT to continue finalizing the Definition of Ready document and get it signed off) and the Demand summary (Word, all demands except Draft and Canceled, with links to each demand's description and Decision Log) and the DGG scoring form (Word: the demands in DGG Prioritization with no rank, three to a page, each with its Salesforce link, for a DGG member to give their name, group, date, the scores of the seven criteria and the rationale — printed or typed; the administrator then enters the ratings in the demand's Decision Log under Members' ratings, which works out the collective score, and the Collective ratings button of the Pipeline shows the proposed ranking); the demands of any status picked in the pipeline graph — DGG Prioritization first — with estimated cost, rank and the Prioritization Group's recommendation, which a Group by list can group by application (the default) or by unit, with a button to fold each group); Strategy (the map from the UNV Strategic Framework and its results matrix, through the Digital Strategy pillars, down to the demands linked to them, with the governance documentation); Budget (a Forecast tab, in purple, shows next year's planned budget uploaded by the admin, linked to demands by Project + Task ID, tagged NY and not compared with this year's lines; summary cards — total budget, committed, disbursed, expenditure, balance — for the lines shown, then the PPM budget lines (filter them by project, by activity — as many activities as you tick — and by budget scope), each with the demands and purchase orders booked on it, and the PO tracker (which also has the link to the Purchase Order BI report and, for administrators, the upload of the PO file — the Maintenance page keeps it too)); Table (sortable, with resizable columns and the per-demand icons described below; a Group by list groups the demands by application, department, status or effort estimate (with Collapse all / Expand all buttons while grouped) — inside each group they are always ordered by priority rank, the unranked at the end — and Export CSV follows that order; the Export prioritized demands button makes a Word document for all UNV users — the demands that hold a priority rank, by application and in priority order, with an overview and then each demand described, without costs or internal decisions); Kanban (one card per demand, grouped by status); Matrix (Status × Application and Focal Point × Status pivots); ClickUp (two modes: the tickets linked to demands, and ClickUp lists — pick any of the lists the team tracks time on, such as the UVP backlog with its releases, to see tickets, sub-tickets, time and actual cost); Data Quality (demands with missing or inconsistent information, before they stall) Team Management (under Operations: the ClickUp developers — everyone who logged time in ClickUp, with hours and cost overall, per year and per month and the tickets they spent most on — the Internal ICT team, for those who may see it, Staff leave, and the list of the DGG members); the Meeting cost calculator; SOPs & policies (the strategy documents, the Standard Operating Procedures and the UNDP policies, each with a short summary and the link to open it); and, for the administrator, Roles & access and Expenses (the PPM project transactions — expenses and commitments — uploaded from the PPM Project Transactions report, with a reminder every two weeks, linked to the budget lines by project and activity and checked against the budget file; a click on a transaction shows everything in the line; a Staff tab lists the salaries and entitlements of the people on the ICT team's projects, by activity (post) and by person, month by month — they are left out of the other tabs; its SLA tab shows the cost recovered on our projects and, in Agency invoices, every UN agency's SLA invoices read from the Power BI invoice list, with totals by agency, year and month).

Finding and sharing. Filter by application, department, status, effort estimate, focal point (several people at once) and process flags, show only demands that have a priority rank, or search free text; one click on Clear filters resets everything; copy a link to the exact filtered view to share it; export the current rows to CSV; or export every field for every demand — with their ClickUp tickets — to use with an AI assistant.

On each demand. Icons open the Decision Log (the record of DGG prioritization decisions — admins log new ones, in full or as a rank-only fast track, and — only the admin — edit an entry (deciding body, date, decision, rationale), delete a mistaken one (it cannot be undone), or remove the demand's priority rank (the other demands of the application then move up so the ranks stay 1…n). A fast track records no deciding body (it stays blank until edited), and editing or deleting an entry does not change the rank in force; the number on the icon is how many are logged), the case overview, the Chatter feed, the approval history (a demand with an approval still open in Salesforce also has an amber hourglass: click it for the approval, the step, who it is assigned to and since when, with the link to approve or reject in Salesforce, above the history) and the milestone timeline with days spent in each status. The priority rank badge shows where the DGG placed it. The Effort & $ column shows the T-shirt size with its estimated cost, a note of why that size was chosen, and the Financials popup: the Salesforce budget, the estimated cost, the actual vendor expenses (ClickUp time × day rate, with a per-developer breakdown) and the demand's PO number(s) — each matched to its purchase order lines from the PO file, with suggestions based on the demand's project and activity. The ClickUp column shows the real cost and opens the demand's tickets.

Staying informed. The notification bell, a digest e-mail and — if you turn it on — notifications on your phone report new demands, changes to status, budget, effort, focal point, launch and sign-off dates, project/task ID and effort description, and new Decision Log entries. Each one says who made the change; for a status change the name is the person recorded in Salesforce's own field history. The app looks for changes every 3 minutes, whether or not anyone has it open. (Chatter posts and comments do not notify; the Chatter feed of a demand is still one click away.) Phone notifications: on an iPhone open the site in Safari, use Share → Add to Home Screen (iOS 16.4 or later), open Digital UNV from the new icon, sign in (type the code of the sign-in e-mail: a link in the mail opens Safari, which is a different app and a different session), tap the bell and Turn on phone notifications; Send a test checks the chain. Android should work the same way from Chrome. Phone view: on a phone the app shows a compact page — one card per status with its number of demands, a tap lists that status's demands, a tap on a demand opens its details — with Open the full site at the bottom to get the normal pages back.

Access and administration. Sign in with your @unv.org email (a one-click link, no password); a first-time sign-in is approved by the admin. If a link does not work (mail scanners can open a one-time link before you do), request a new one, or use The link brings me back here? Sign in with the code of the e-mail on the login screen and type the code that comes in the same e-mail. For support and adoption tracking, whoever has the permission can see on the Dashboard (Usage section) when each account last signed in and which pages of the tracker it uses (page names and counts only — never the demands you look at or search for). The admin also has a Maintenance page showing the live status of every connection (Salesforce, ClickUp, Supabase, Netlify, GitHub), where the PO file, the PPM budget export and the developer day-rate sheet are uploaded, with a reminder every 5 days to keep them current (plus a weekly reminder to feed the app's data to the ChatGPT daily brief), and a diagram of how everything connects. This User Guide summarizes the Digital Demand SOP alongside.

App rules & definitions

How the app works things out — worth knowing when a number, a flag or a missing demand surprises you. All of this is automatic; the tracker only reads Salesforce and never writes to it. Some figures come from files that an admin uploads, so they are only as current as the last upload (the page always shows when).

Click a title to open it.

Where the data comes from, and how fresh it is
DataHow it gets inHow fresh
Demands (Salesforce report)Read live from the Salesforce DGG demand reportLive each time you open or refresh the page
ClickUp tickets, time and costRead from ClickUp once a day (05:30 UTC) and stored; an admin can press Refresh from ClickUp at any timeThe ClickUp page says "ClickUp data as of …"; time logged since then shows after the next refresh
Purchase orders, PPM budget, developer day ratesFiles uploaded by the admin on the Maintenance page (PO file from Power BI, budget export, NTT Data day-rate sheet)As of the last upload — the admin is reminded every 5 days
Decision Log and priority ranksEntered in the app by those allowed to (the administrator by default; fast-track ranks by every user)Immediate
The internal ICT team (people, position, contract, grade, country and duty station, nationality, gender, age)The HR export (Power BI report) imported on Team Management → Internal ICT team, or uploaded on the Maintenance page; a monthly reminderAs of the last import
Proforma costs of the grades (meeting cost calculator, daily rates of the ICT team)The three 2027 proforma files of the Office of Financial Management (PA and FTA staff, IPSA, NPSA) uploaded on the Meeting cost calculatorAs of the last upload
Staff leaveThe leave export of the HR system (.csv or .xlsx) uploaded on Team Management → Staff leaveAs of the last upload
Long text fields (problem statement, description…)Salesforce reports cut them at 255 characters, so the app fetches the full text from the demand itself (case overview and the AI export)Live
Filters and process flags
  • Application, Status, Focal Point and Process flags accept several selections (a demand matches if it fits any of the ticked values); Only ranked keeps demands that have a priority rank; Clear filters (n) resets everything, search included.
  • Pending any approval — any approval step still open in Salesforce, whoever it is assigned to. These demands also carry a small amber hourglass next to the demand number (Table, Kanban and the DGG Prioritization page; the row is also tinted amber): click it for the approval process, the open step (for example Approval by ICTS Chief), who it is assigned to and since when, with the link to approve or reject in Salesforce, above the demand's approval history.
  • Pending SC clearance / Pending DGG chair approval — an approval step is open and assigned to the Section Chief / the DGG Chairs.
  • Pending Req assessment while status DGG-chair Approved — approved by the DGG Chair but not yet moved into Req Assessment (a bottleneck, not an approval).
  • Pending DGG prioritization — status is DGG Prioritization or DGG Cleared.
  • DGG cleared without Decision Log — the demand reached DGG Cleared at some point (even if it has moved on since) and has no Decision Log entry. Not raised while the current status is Completed, DGG Prioritization or a "completed" status.
  • Stale — an active demand with no update for more than 25 days. Draft demands, demands in Tech implementation (that work happens in ClickUp, not as Salesforce updates) and Completed / Request Canceled ones are never stale.
  • Urgent — marked urgent in Salesforce (these demands also carry a red dot next to their case number in the Table and on Kanban cards, and the Urgent only checkbox keeps just them). Compliance — marked as a legal/compliance demand. The two are separate.
  • No PO — no purchase order number is recorded on the demand. No PO after DGG Cleared — the same, but only for demands that are not cancelled and have reached DGG Cleared at least (now DGG Cleared, Req vetting, Tech implementation or Completed, or recorded as DGG Cleared at some point): the ones that should already have a PO. Missing project/activity — the Project Id or the activity (Task Id) is empty.
Priority ranking and the Decision Log
  • Only admins log decisions. Every decision stays in the history unchanged; the demand's live priority rank (the Priority column, the #N badge) is kept separately.
  • Ranks are per application, #1 being the highest priority. Giving a demand rank N puts it there and moves every demand at or below N down one place. A rank is freed when the demand is Completed or Request Canceled, when it drops out of the Salesforce report the tracker reads, or when a later decision on it carries no rank. The ranking is always kept contiguous (1, 2, 3 … with no gaps): freed numbers close up, and asking for a rank beyond the end of the list gives the next free place.
  • Score (ToR v2.3) = the average of the seven criteria, each scored 1–5 (decimals allowed — use the members' average). All seven or none. Effort / complexity (1–5, prefilled from the T-shirt size: XS 1, S 2, M 3, L 4, XL/XXL 5) is a delivery factor shown next to the score; it is not part of it.
  • Suggested rank — from the score, compared with the other scored demands already ranked in the same application: directly below the lowest-ranked one that scores at least as high (a tie keeps the existing demand above), or #1 if none does. Ranks given under the earlier scoring formula can't be compared. It is only a suggestion: See the current ranking & where this fits shows the ranked list and lets the group move the demand up or down before saving.
  • Fast track — open to every signed-in user (other users see only this rank-only form; the full decision form, edit, delete and remove-rank stay with the admin). Switch it on to enter only a priority rank (and an optional note). It is recorded as a Prioritized decision by the DGG Prio Group dated today, with the method Fast track and a "Fast track" badge, so it is never mistaken for a fully documented decision.
Project, activity and purchase orders
  • A demand's Project Id and Task Id (the activity) tie it to budget lines and purchase orders. They must match exactly as written — only spaces, upper/lower case and leading zeros of the project id are ignored; there is no partial matching. A typo means no match: the Financials popup then offers a "did you mean …" when one character is off, and the fix is made on the demand in Salesforce.
  • The PO file is exported at distribution level (PO line.distribution), so a PO can span several project/activity combinations. A demand can have several POs; the popup shows each with its supplier, description, ordered / delivered / open amounts (USD) and highlights the lines on the demand's own project and activity. Admins record and remove PO numbers.
  • Clicking a demand's activity (Table or Kanban card) lists every demand on the same project and activity — completed ones included, as long as they are in the report.
  • Data Quality also flags a demand whose project/activity isn't in the budget file (when the file covers that project, or the pair is one typo away from a known one).
Budget page
  • The ICT projects (00125109 and 00118859) show all their activities (a _P task is investment, the others operations); 00118856 is the staff budget (every task is personnel); in project 00134427 the OUTP_GOE task (ICTS_OUTP_GOE) is operations and every other task is personnel. Every other project shows only the activities the team follows (EXOCRMVMF, EXOVRA, KPTECH, CONSLT_OPS, CSPARWEB_ICT, CSPARWEB_ICT_MNT). The budget pages cover eight projects: 00125109, 00101696, 00118473, 00118478, 00118482, 00118856, 00118859 and 00134427. CSPARWEB_ICT_MNT (ERCS) and CONSLT_OPS (00101696) are digital operations; the other followed tasks of the non-ICT projects are investment.
  • Investment or operations: on the ICT projects an activity with a _P or _IP segment (e.g. COE_BPS_P, COE_DATA_P1) is investment budget, anything else is operations; all other projects count as investment. Tick Investment and/or Operations to filter, or Investment with no demand to list the investment lines that no demand points at yet.
  • Each line shows the demands and the POs booked on exactly that project + activity (with counts), and each project has its own colour.
ClickUp: tickets, lists and releases
  • A ClickUp ticket belongs to a demand when it is tagged digital-demand and its DigitalDemandId field holds the demand's case number. Time on a master ticket includes its sub-tickets.
  • ClickUp lists shows the tickets of one list at a time — the UVP backlog, the other lists the team tracks time on and every list in the UVP Maintenance folder — limited to tickets updated in the current calendar year, with sub-tickets under their master (a sub-ticket whose master wasn't updated this year is listed on its own). For the UVP backlog only tickets that have a Release value are shown.
  • A top-level ticket without a DigitalDemandId is flagged "⚠ missing"; sub-tickets are not expected to carry one.
  • Current release: release lists carry their planned dates in the name, but a delayed release must stay current. A release counts as deployed when at least 90% of its active tickets are done or in post-deployment monitoring (cancelled and duplicate tickets don't count). The earliest recent release that isn't deployed yet is the current one — marked "delayed" once its planned end has passed — later ones are upcoming, deployed ones are past. When the current release is fully deployed, the next becomes current by itself.
  • The figures bar above the page always describes the tickets listed (after the release, list and search filters): number of tickets, time, actual cost and, for the UVP backlog, how many are deployed.
How costs are worked out
  • Estimated cost comes from the T-shirt size (the sizing table in section 4); cancelled demands are left out of the totals.
  • Real / actual cost = ClickUp time entries × the person's day rate ÷ 8 hours, using the NTT Data day-rate sheet. UNV staff (@unv.org) always cost $0. Someone on the sheet costs the sheet's rate — a sheet row at $0 stays $0. An outside person who isn't on the sheet is costed at the average day rate of the sheet's resources and marked "avg" (an estimate). People are matched by name, or by the name in their e-mail address when ClickUp shows a different spelling.
  • A demand's real cost covers its linked tickets and sub-tickets. In the ClickUp lists, a ticket's actual cost is all the time ever logged on it, not just this year; click the amount to see the time entries and cost per person.
Strategy map and governance
  • Who owns what: the Executive Office owns the UNV Strategic Framework 2026–2029 and its results matrix; the DGG owns the Digital Strategy 2026–2029 that delivers it; and the DGG runs demand management as its workplan — every request goes through the SOP for Digital Demand and is scored and ranked by the DGG Prioritization Working Group, whose recommendation the DGG endorses.
  • The Strategy mapping page opens with its figures (demands in view, linked, not linked yet, suggested) and the actions — include Completed / Canceled, download the status update for the DGG, accept all suggestions (admin) — and then the blocks, all collapsed until opened (click a block's title, or use Show / hide blocks to tick the ones to open), in this order: Quick edit (admin — every demand with a pillar selector, see below); the Digital Strategy pillars (summary, primary metric, priorities, key outcomes and linked demands); Strategy at a glance (heatmaps first, then flow, paragraph coverage and the trace tree); Documentation on governance and strategy (how demands trace back to the organization's results, who owns what, the governance bodies and mechanisms, and the documents). The top filters apply.
  • Pillar priorities and key outcomes: every pillar name (in the pillars block, the trace tree, the heatmaps, the demand tables and the Quick edit groups) opens a window with that pillar's text from the Digital Strategy document — summary, primary metric, strategic priorities and key outcomes by 2029 (the document gives 2029 as the horizon), the Strategic Framework paragraphs behind it, and the source page.
  • Quick edit (admin): the Quick edit — digital pillar per demand block lists every demand in view with a pillar drop-down of tick boxes (several pillars allowed), grouped by each demand's primary pillar (completed and cancelled ones included); each group can be collapsed or expanded, or all at once. Change rows one by one, or tick several and tick pillars in Pillars… to Set, Add or Remove them, or use Use recommendation / Confirm as shown; filter to the demands not confirmed yet, without a pillar or changed. Changes are only staged (highlighted) until Save stores them all at once; Discard drops them. A demand whose pillar changes goes back to that pillar's own outcome/output and paragraphs; one saved with the same pillar keeps its manual ones. The Outcome / output mode of the same block does the same for the results-matrix items: each demand gets a drop-down of tick boxes (several outcomes/outputs allowed, starting from its pillar's alignment), and for the selected demands you can Replace, Add, Remove the ticked items or Reset to pillar default; the Strategic Framework paragraphs then follow the items. A demand needs a pillar first.
  • Strategy at a glance: the "Strategy at a glance" block offers three pictures (the heatmap is shown first). Flow: Strategic Framework paragraphs → outcomes/outputs → Digital Strategy pillars → demand phase, ribbon width = number of demands or estimated cost (hover a box to follow its path, click for details). Heatmap in two versions, chosen with the selector next to the tabs: Pillar × outcome / output (hatched where the Digital Strategy is aligned but no demand exists yet) and SF paragraph × pillar (which paragraphs each pillar serves; click a paragraph to read its text, a cell for its demands). SF paragraph coverage: the 27 paragraphs shaded by how many demands serve them, amber for substantive paragraphs no demand serves. All three are in the downloadable status update.
  • Linking a demand: each demand traces to one or several Digital Strategy pillars (the first is the primary one), to the Strategic Framework outcome / output (results matrix) and to the Strategic Framework paragraphs behind them. Every demand is recommended a pillar automatically and shows as auto until the admin acts. The recommendation follows fixed rules: anything AI related always goes to P2, then by application: BI Report → P3 Data & Operational Intelligence; Cybersecurity, Infra and Identity → P6 Cloud, Records & Cybersecurity; UVP, UVP Quantum and VRA → P1 Volunteer Management; AURA and Document AI → P2 AI & Responsible Automation; Knowledge Portal, Salesforce and UNV Website → P4 Service/Partner Experience. Other applications are guessed from keywords in the subject. In the Table view a small strategy icon at the end of each row (coloured by pillar; hover for pillar, outcome/output and paragraphs; click to open) opens a modal where the admin can apply the recommendation or set the pillar, the outcome/output items and the paragraphs by hand (items and paragraphs follow the pillar's alignment unless unticked). The same Strategy… button is on every demand row of the Strategy page.
  • Trace tree and automatic mapping: the first block of the Strategy page reads top-down — the Strategic Framework text (official paragraphs) → the outcome / output and its results-matrix indicators → the Digital Strategy pillars serving it → the demands under each pillar. Every demand is mapped automatically (pillar suggested from its application and subject, framework items from the pillar's alignment) and marked auto until the admin confirms it with Link or changes it with Framework…. The DGG Terms of Reference are linked next to the SOP.
  • Status update for the DGG: the Download status update for the DGG (PPTX) button on the Strategy and DGG Prioritization pages produces a PowerPoint deck (16:9, one topic per slide, long lists paged over several slides; it needs an internet connection for the PowerPoint library, otherwise you get the report as an HTML file): the title; where we stand with the estimated cost of completed, in-implementation and pipeline demands; DGG Prioritization — requested, cleared and consolidated, with cost, pillar, rank and the Prioritization Group's recommendation; demands per month (chart); demands by status and by requesting unit, with the average days in each status (chart and table) and the three longest stays per status; what is in technical implementation and completed; the pipeline; every demand per digital pillar (one slide series per pillar with its outcomes/outputs and paragraphs — a demand serving several pillars appears under each); the alignment heatmaps and paragraph coverage; and proposed points for the DGG. The top filters apply; completed and cancelled demands are always included (cancelled ones are left out of the figures). Pillars not confirmed yet are marked auto.
  • Framework and paragraph override: by default a demand traces to the Strategic Framework / results-matrix items its pillar is aligned with. The admin can override that per demand (Framework… button): tick the outcomes, outputs, indicators or enablers it really contributes to, or go back to the pillar default. Overridden demands are marked override and counted under the items chosen (and their parent outcome). Every item, indicator and pillar has an SF text link, and every framework chip is clickable: it opens the official paragraphs of the Strategic Framework (DP/2026/9) behind it.
  • Per pillar the page adds up the linked demands, how many are active, their estimated cost, real cost (ClickUp time × day rate) and how many hold a priority rank — so spend and progress can be read against the strategy.
  • The Strategy page's Governance & strategy panel (under the ownership chain) summarises the governance bodies (Executive Office, the DGG, the Prioritization Working Group, the Digital Champions Network, ICTS and its two delivery portfolios, business owners, the UNDP bodies UNV plugs into), the mechanisms (intake path, two-stage governance, scoring and ranking, intake and portfolio decisions, the AI governance gate, change control, transparency) and links to the documents: Strategic Framework, results matrix, Digital Strategy, DGG ToR, SOP for Digital Demand and Prioritization Group ToR.
Purchase Orders page
  • The Purchase Orders page (Governance menu) lists every PO of our projects — the projects of the Budget page — with its supplier, status, date, ordered / delivered / open amounts and delivered %. Each PO row shows how many demands it has, split into completed, being built now and coming next, and their estimated cost; Show demands lists them and the PO lines, each with its own demands. The PO number opens the full PO. A card shows the demands without a PO (DGG Cleared or later) and opens the list. A select keeps only the investment or only the operations lines.
  • A demand counts for a PO when the PO number is entered on its Financials popup (PO field) or when its project + activity is booked on one of the PO's distributions (activity). Filter by search text, PO status, or POs that still have an open amount.
Pipeline page (Governance › Pipeline)
  • The Pipeline page covers every status. Important: when demands currently in the status DGG Cleared have no priority rank, a red bar at the top says how many (and their estimated cost) with a Show them button; their Rank cell reads a red No rank, a red card counts them, and the same demands are a Data Quality issue. It shows the pipeline graph (counts per status, as on the Dashboard); click a status to list its demands below — it opens on DGG Prioritization, the demands waiting for the DGG — or press All statuses. Clicking the chosen status again shows every status. Each demand shows its estimated cost (from the effort size), digital pillar (colour pill), status, priority rank (yellow pill — click to open the Decision Log), a red Urgent pill when it is marked urgent, how long it has been in the status, its last-modified date (Modified, sortable), focal point and the Prioritization Working Group's recommendation (the latest Decision Log entry: decision, rank, score, body, method, date and rationale, or "No recommendation yet"). Next to each demand number are the Table's row icons (Decision Log, case overview, timeline) and a small document icon that opens the description recorded at Requirements Assessment (the effort estimate's description, in full, with the effort size and estimated cost) in a small window; Application and Unit are separate columns, and every column sorts. Cards and summary tables add up the estimated cost of the list shown (the three summary tables sit in a block you can fold away with its title bar, so the list below gets the whole screen — it stays folded or open as you sort and switch status), by recommendation, digital pillar and application — click a row of them to filter the list (one of each at a time; a line above the list shows the filter and a Reset filter link clears it). The button DGG status update (PPTX) downloads the deck for the DGG, which has the DGG Prioritization requested / cleared slides. The top filters apply.
Demands per month (Dashboard › Trends)
  • The Dashboard's Trends section (open it at the bottom of the Dashboard) shows, for each of the last 12 months, how many new demands were opened, how many were in progress (in any status from DGG Cleared up to and including Tech implementation, at any time in that month), of which in Tech implementation, and how many were completed (moved to Completed in that month). It comes from each demand's Salesforce status history, so it follows the top filters; a demand with no history that is in progress now only counts for the current month. The same table is in the DGG status update (section 3) and in the AI export (dgg-demands-per-month).
Dashboard › Demand pressure

The section at the top of the Dashboard answers one question: is more demand coming in than we can deliver? It follows the top filters.

  • Temperature check — Balanced, Under pressure or Overheated, from four indicators, each green, amber or red: intake against starts (new demands a month ÷ demands reaching Tech implementation, last 6 months; amber from 1.15×, red from 1.5×); the approved queue in months of delivery (the estimated cost of demands in DGG Cleared and Req vetting ÷ the cost delivered a month in ClickUp, last 3 months with data; amber from 3 months, red from 6); work in progress (demands in Tech implementation ÷ demands completed a month; amber 3, red 6); and the share of the approved queue waiting more than 60 days (amber 20%, red 40%). Two reds make it Overheated; one red, or two ambers, Under pressure.
  • Charts (last 12 months) — new demands, demands started in Tech implementation, demands completed and the waiting backlog; and the estimated cost of new demands against the delivered cost (ClickUp time × day rates), with the cost of the backlog. Both costs are rough guides: the estimate comes from the T-shirt sizes, the delivered cost from the time logged in ClickUp.
  • Approvals and reviews before Tech implementation — for each stage from Draft to Req vetting: the demands there now and their estimated cost, the average time spent in the stage, the longest wait now, the demands with an approval open in Salesforce and the demands canceled there; the stages that are approval gates are tagged. A short narrative sums it up: the slowest stage, the biggest queue, the longest wait, which approval steps are open, and the median time from request to the start of Tech implementation with the share of it spent waiting in approval stages.
Team Management

Operations › Team Management has a switch at the top: ClickUp developers (hours and cost per developer, as before), Internal ICT team, Staff leave (only for those allowed to see it) and DGG members (the eleven members of the Digital Governance Group, with a button to copy their e-mail addresses).

  • ClickUp developers — click a month heading of the table to order the developers by that month's cost, highest first; Collapse all / Expand all fold the groups; under the table a summary lists every developer with the day rate, the cost of the period and roughly how much they worked (hours, days, weeks, months; the projection of the future months is included when ticked); click a developer for their window: choose the year and a month (or click a month of the per-month table, which can also be sorted by amount) to see the total and the tickets worked on that month, by ClickUp list. The tickets of a single month are available once the ClickUp data has been refreshed after this feature was added.
  • Internal ICT team — one table of the team: name, position title and open demands; click the number to open the person's demands (estimated cost, urgent flag, hourglass for a pending approval, how each is assigned; every column sortable; Reassign… where you may). Every application has default owners, so all its demands are theirs by default; a single demand can be reassigned to someone else. A demand nobody delivers is in the Not assigned row. People with the right permission also see the contract, grade, country, nationality, gender, age, the proforma cost per day (click it for the year, month, day and hour), cost cards for the whole team and the share of women, and can import the team from the HR export, assign applications and demands (Assign demands…) and manage the defaults.
  • Where the daily rate comes from — the 2027 proforma files: the person's grade, country and duty station (from the HR export) are looked up in the three proforma files; the daily rate is the yearly cost ÷ 261 working days (21.75 a month), the hour ÷ 8.
  • All resources — the ClickUp developers and the internal ICT team in one list (for those who may see the team's costs): type, day rate, the cost per month of the current year and the total, with cards for the number of people and the yearly cost. External developers cost the hours they report in ClickUp × their day rate; the internal team costs its proforma (yearly cost ÷ 12 a month).
  • Staff leave — the leave export of the HR system, analysed: cards (leave days, people, days per person, annual and sick leave, longest absence, the most people absent on the same day), a short written analysis (for example whether sick leaves start on Mondays and Fridays more than chance would), leave by type, by month (chart and table) and by person (home leave is a kind of annual leave: it is shown as such and not counted twice), each with a drill-down to the leaves behind the number, and the upload of a new export. Personal and health-related data: only for the people allowed to see it.
ICT Leadership

ICT Leadership (the first link of the Governance menu, visible to the administrator only) is the cockpit of the ICT lead: five vital signs, what needs attention now (each item opens the page that deals with it), and one card for each domain — Digital strategy, Demand management and delivery, DGG, Budget, Procurement, Team management, Workplan, Service desk and IT support, ICT communication, SOPs and policies — with its live figures, an insight and the links to the app's pages and to the key documents.

UVP release notes

Governance › UVP release notes shows what each UVP release brought: one card per release, newest first, with its version, its date and its highlights; Show the whole release opens the full text, Open in SharePoint goes to the original article. A year filter and a search (a release or a feature) help to find one. The content is read from the UVP release notes of the SharePoint site and kept by the app; the administrator presses Refresh from SharePoint to read it again.

ICTS workplan

Governance › ICTS workplan (for roles that have the permission) shows the ICTS activities of the 2027 workplan from the SharePoint workplan list of the Executive Office: results linkage, priority results, activity, Quantum task id, fund code, GOE details, the information technology amount, the ICs amount, the Other amount and the year, with the totals of the information technology, ICs and Other columns and of the three together (the total budget) above the table, following the filters. A second tab, Comparison with the forecast budget, matches each Quantum task id of the workplan with the Task ID of the 2027 forecast budget and tells whether it is found and whether the amounts agree (information technology + ICs + Other against the forecast budget), with the differences and the task ids found on one side only. The activities are grouped by priority result (change the grouping, fold or unfold the groups, search, and choose the columns with the Columns button). The page shows the stored copy; the administrator updates it with Refresh from SharePoint.

Public stories

Governance › Public stories lists the ICT stories published on the public website (unv.org, tag information and communications technology): the date, the story with its link, the contributor and an overview. The list is sorted by date, newest first (click a column heading to sort by it), and can be filtered by year and searched. The administrator updates it with Refresh from the website or Import a list (a CSV or JSON file with the columns Title, Link, Date, Contributor, Summary), because the website refuses automated reads unless the web team allows them.

Service Desk

Operations › Service Desk (for roles that have the permission) shows the Salesforce cases that are not demands. Under the ICT Team cards, a Top requestors table shows who opens the most ICT Support cases in the period — cases, open ones, average satisfaction and average time to solve — and each team member's window has the same table for their own ICT Support cases. Choose first a type of case (Service Desk, Payment, ICT support …): each type has its own status path and its own fields. The page then shows the cases created in the chosen period plus every case still open, with cards (cases, open, closed, average and median resolution time, oldest open case), the status path with the number of cases in each step and the average time spent there (click a step to filter), filters (search, open/closed, status, queue, priority, origin, creation dates), statistics (time in each status, cases created and closed per month, age of the open cases, tables per queue, priority, origin and owner — they follow the filters) and a sortable table (click a heading; shown a page at a time) that can be exported to CSV. Click a case to see its timeline, its fields, the contact details, the description and the comments, with a link to the case in Salesforce. The page opens on the current year (choose another year, or one month — or click a month of the trend). At the top an executive summary tells in a few sentences what happened for the chosen case type, with the top ICT performers (ranked by cases solved and by satisfaction, internal ICT team only) and a temperature check (are cases closed as fast as new ones arrive?) and a trend of new cases against closed cases per month. For the support tiers of the Enquiry type (L1 = the business; L2/L3 = IT, when the case owner is a member of the ICT team or the queue UVP-Tech resolved, UVP-Technical or SF-tech) it shows the share of L1 cases that move on to L2/L3 and of the L2/L3 cases that come back to L1, a table per tier and the IT agents. For the Enquiry and ICT Support types, a panel shows every ICT team member who owns at least one case in the period (with their open and closed cases and satisfaction); click a person to see their performance (cases received and solved per month, speed, satisfaction, position in the team) and all their cases of the period. The first card, ICT Team, combines the Enquiry and ICT Support cases and shows only these people (and the two technical queues UVP-Technical and UVP-Tech resolved as virtual members), with the Employee of the month of the current and the previous month (cases solved, solved against received, satisfaction and, for ICT Support, time to solve). When the case type has a satisfaction score, the table shows it for each case, a card gives the average, and a table gives each agent's average, minimum and maximum score (the agent is the case owner when it is a person). The cases owned by a member of the internal ICT team are highlighted in amber with an ICT badge, counted in a card, and an owner filter shows only those. Because there is a lot of data, the page shows what was stored at the last refresh and never reads Salesforce when it opens: press Refresh from Salesforce to update the case types and the type you are looking at (the time of the last refresh is shown).

Meeting cost calculator

Operations › Meeting cost calculator gives the cost of a meeting: choose the country (Germany, Bonn by default; where a country has several duty stations, the duty station), the duration (type the hours or use 30 min … full day) and the number of participants for each grade (P, D, G, NO, IPSA, NPSA). The cost per hour of a grade is its yearly proforma cost (all funding sources, from the 2027 proforma files) ÷ 261 working days ÷ 8 hours. The summary shows the total, the cost per participant, per minute and per hour of meeting, a table of the grades chosen with subtotals, and a button to copy it. Those allowed to can upload a new version of the three proforma files on the page and run a simulation that prices the internal ICT team person by person in a one-hour meeting.

Data Quality checks

Completed and Request Canceled demands are left out of every check. Beside each check, at the top of the page, a number says how many demands it flags now (red when something is to fix, green at 0); click the number to keep only those demands in the list below, and click it again (or Show all issues) to see everything.

  • Missing Project ID or Activity ID — once the demand is past DGG Cleared; one issue whichever of the two (or both) is empty.
  • Missing Focal Point; stale (more than 25 days without an update, as defined above).
  • A status that disagrees with the approval process (pending DGG Chairs approval despite DGG-chair Approved, pending Section Chief approval despite SC Endorsed).
  • Recorded on multiple POs — more than one PO number is recorded on the demand; check it (the Purchase Orders page shows where, and lets you unlink).
  • Missing estimated launch date — the demand has completed its requirement assessment (DGG Prioritization or later) but its Launch Date is empty in Salesforce.
  • Not linked to a Digital Strategy pillar — the demand has no confirmed link to a pillar (the suggested one does not count); link it from the Table or the Digital Strategy page, which open the same window.
  • DGG Cleared without a priority rank — the demand's current status is DGG Cleared but it holds no priority rank in the Decision Log. It is also a Process flag (DGG cleared without priority rank), and the Pipeline page shows it prominently.
Export for AI

The admin's Download the AI export button (Maintenance page, with the link to the ChatGPT daily brief) downloads everything the app knows as files for an AI assistant: every demand with all its fields (full text, priority rank, ClickUp time and cost) plus its digital pillar(s), Strategic Framework outcomes/outputs and paragraphs, estimated cost, process flags, pending approval, purchase orders and latest decision; the ClickUp tickets with sub-tickets; the UVP backlog tickets with their release lists; the Digital Strategy pillars (priorities, key outcomes, alignment, demand counts); the Strategic Framework (all 27 paragraphs and the results matrix with baselines and targets); the Decision Log; the purchase orders; the budget lines; and a README that explains the files, columns and rules to the AI. Your browser may ask once to allow several downloads. The admin feeds these files weekly to the ChatGPT scheduled task "UNV DGG Daily Brief", which writes the daily DGG brief.

Who can do what — roles and permissions

Anyone signed in with an approved @unv.org address can read the shared demand data (Dashboard, Table, Kanban, Matrix, Budget, ClickUp, Strategy, SOPs & policies). What a person can do, and which sensitive pages they see, depends on their role: a role is a named set of permissions, and every user has one.

  • User — the default role. It can read everything above, fast-track a priority rank, open Team Management (the ClickUp developers and the internal ICT team, without the personal and cost details), reassign the demands the person delivers themselves and use the Meeting cost calculator.
  • Administrator — everything, always held by the owner of the app; it cannot be changed or locked out. Beyond the User role it can, among others: log, edit and delete Decision Log entries and remove a priority rank; record PO numbers; upload the PO, budget, forecast, day-rate, ICT team, proforma and leave files; refresh ClickUp on demand; see the Maintenance page, the usage table and the Staff leave page; see the contract, personal and cost details of the ICT team; manage the team and its assignments; map demands to the Strategy; connect Salesforce; approve users; and manage roles.
  • Custom roles — created on Operations › Roles & access: a matrix of permissions by role (tick what a role may do, save), roles can be created, renamed and deleted, and each user is given a role in the users table below it. Examples set up from the start: Team leads (the User permissions plus managing the ICT team's assignments) and DGG (the User permissions plus the full Decision Log). Sensitive permissions are tagged in the matrix. Whether someone may sign in at all stays with Manage all users in the bell of the access requests.
  • View as — the administrator can see the app as another role: View as in the account menu (not on a phone). The pages, menus and buttons, and what the server answers, are then exactly those of that role, a yellow banner says so and Back to my own view ends the preview. A preview never gives more power than the role has.

1. Purpose & scope

The SOP defines the end-to-end lifecycle for change requests to UNV systems — from intake and prioritization through development, acceptance testing, and delivery — so that every demand is treated through the same governance mechanism, with visibility into how digital budget is consumed.

In scope

Out of scope

2. Status pipeline — what each stage means

This is how the statuses shown in the Kanban board map to the SOP's process steps:

Draft
Request captured in the Digital Demand form but not yet submitted for endorsement. SOP §3.1
SC Endorsment
Awaiting the requester's Section Chief to endorse: confirms section priority alignment, a named budget owner/funding source, and UAT commitment. SOP §3.2
SC Endorsed
Section Chief has endorsed the request; it now goes to the DGG Chair for initial screening. SOP §3.2 → §3.3
DGG-chair Approved
DGG Chair confirmed completeness, business sponsor and funding source, and approved the request for assessment (not yet for delivery). Moves to ICTS feasibility review. SOP §3.3
Req Assessment
ICTS is assessing technical feasibility and producing a rough T-shirt size effort estimate. SOP §3.4
DGG Prioritization
Needs DGG prioritization group action
Ready for the Digital Governance Group to prioritize against strategic alignment, business value, urgency, dependencies, budget and effort. This is the queue the DGG prioritization group needs to work through. SOP §3.5
DGG Cleared
Approved and prioritized by DGG. Moves into detailed requirement refinement. SOP §3.5 → §3.6
Req Vetting
Requester and ICTS jointly document detailed functional requirements, producing the Definition of Ready (DoR) for sign-off. SOP §3.6
Tech implementation
DoR is signed off and the request is scheduled into a development cycle: build, internal QA, UAT, stabilization and production deployment. SOP §3.7 – §4
Completed
Delivered to production, or completed without delivery (e.g. superseded, withdrawn). SOP §4.4 The tracker always shows this status as Completed — a demand that Salesforce still labels "Closed" appears under Completed.
Request Canceled
Rejected at DGG Chair screening or DGG prioritization, or withdrawn. A rejection automatically closes the request; reconsideration requires a new submission with materially new information. SOP §3.3, §3.5
Status wording above matches the shorthand used to sort this tracker's Kanban board. Actual Salesforce picklist labels may differ slightly (e.g. capitalization/hyphenation) — the tracker matches them automatically.

3. Submitting a demand

All requests must go through the Digital Demand form in Salesforce — ICTS will not assess, estimate, refine, prioritize, develop, or schedule anything submitted through another channel. The form captures:

Requests missing mandatory fields cannot be submitted. Bug reports are not submitted this way — email support@unv.org instead.

4. Effort sizing (T-shirt sizes)

ICTS estimates every request on a rough garment-size scale during Req Assessment:

SizeImplementation effortEstimated cost*Typical examples
XS1–2 days$300 – $1,000Minor UI/text tweak, a typo fix, single-field correction
S3–5 days$1,000 – $3,000New form field + report, simple notification, minor bug fix
M6–10 days$3,000 – $8,000New dashboard with a few sources, multi-step approval workflow
L11–20 days$8,000 – $19,000New module, complex data migration, major 3rd-party integration
XL> 20 days> $19,000Major initiative/epic — must be broken down before it can be prioritized
XXL2 months+> $60,000Mega module / project — needs its own budget & governance

*Assumes developer day rates of $300–$650. ICTS owns the estimate and may revise it after requirement refinement.

5. DGG prioritization

Everything sitting in DGG Prioritization status is waiting on the DGG prioritization group. Use the "DGG Prioritization only" filter in this tracker's Kanban view to see exactly what needs a decision.

The DGG prioritizes based on the business case and a high-level effort estimate — not detailed specifications, which would waste effort on requests that might never be built. Evaluation criteria:

If rejected, DGG must record a reason; rejection automatically closes the request. If requirement refinement later changes cost, complexity, value or scope materially, the request returns to DGG for reconfirmation before development begins. Every DGG decision is recorded in the Decision Log, right in the Tracker — click the clipboard icon on a demand's row (or "Decision Log" in its Details popup) to view its history or, for admins, log a new decision.

DGG membership: ICTS, VSS, VSC, ROs. The detailed decision-making process is defined in the DGG Prioritization Group ToR ↗ (see also §10 Related artifacts).

6. Definition of Ready (DoR) & requirement refinement

Once cleared by DGG, the requester and ICTS jointly produce the Definition of Ready — the binding agreement on what will be built. It includes:

No delivery slot is reserved until the DoR is complete and signed off by the requester. If the refined effort estimate jumps a size category (e.g. M → L), the request goes back to DGG for re-approval.

7. Delivery: development, UAT, deployment

8. Roles & responsibilities

Requesting Unit / Section

  • Submits the request & names a focal point
  • Participates in requirement refinement
  • Assigns UAT personnel, performs UAT & sign-off
  • Owns expected business value / ROI

ICTS Team

  • Feasibility analysis & effort estimation
  • Plans, schedules, develops & tests
  • Supports UAT, manages delivery & deployment

DGG Chair

  • Screens requests for completeness, sponsor & funding
  • Approves for assessment (not for delivery)

Digital Governance Group

  • Prioritizes requests (DGG Prioritization stage)
  • Approves cycle-level scope
  • Confirms reprioritization on material scope change

9. Emergency exceptions

A highly restrictive emergency process exists for truly critical, unforeseen issues that pose an immediate severe risk (e.g. a security vulnerability, a legal/compliance deadline, a critical outage, data corruption) and cannot wait for the next release cycle.

Leadership preference, a missed internal deadline, or convenience do not qualify — those follow the standard process above.

10. Related artifacts

ArtifactPurpose
UNV Digital Strategy 2026–2029 ↗Overarching digital strategy this demand process supports
SOP for Digital Demand ↗Full standard operating procedure this guide summarizes
TOR — DGG (Change) Prioritization Group ↗DGG membership & detailed decision-making process
SOP — ICT Procurement ↗How ICT purchases are procured & the steps that follow once a demand is approved and needs to be bought
Decision Log (in the Tracker)Record of every DGG prioritization decision & rejection reason — per demand, via the clipboard icon or Details popup
Digital Delivery Framework (DDF)Operating principles & cycle-based methodology
Digital Demand form (Salesforce)Structured request submission, problem/impact description, UAT sign-off
Definition of Ready (DoR) DocumentRequirements completeness & sign-off
UAT Sign-Off DocumentTest execution, defect logging, requester sign-off before deployment