These are clickable sketches of the screens we are designing. They are not the finished product: the names and numbers are made up, and nothing you enter is saved. Click one to try it. Source files: the project files ↗.
A nonprofit posts a need with an example product that shows no package size or unit. Quantity and Unit stay separate, and the nonprofit always chooses them itself.
A nonprofit posts a need and picks an example product from rich search results shown right inside the form. Type “tar” in Item Name, choose Tarps, then pick an example product and set Quantity and Unit separately.
A nonprofit reviews supplier offers against its needs. A matching offer goes straight through; one with a different size or quantity is flagged, so the nonprofit can accept anyway, message the supplier or decline.
A nonprofit sets up its own partner network on one screen: name it, pick a disaster template, adjust the members and send invitations. Try picking a template to see the member list and supply lists fill in.
A member of a partner network sees what suppliers have made available inside it, which orders have moved, who the members are and what the network is asking for. Try the month and since-opening views, and export the month's orders.
A nonprofit opens Partner Networks and creates an invite-only network for one event. It can bring in members from a past network and use a response template, then lands on the new network's home. Switch between the example states at the top.
The home page of a partner network, as the person who set it up and as a nonprofit member. The member opens a shared resource and moves it to the regular cart, with the network shown on the cart line.
One walkthrough of Partner Networks, from creating a network to inviting, joining, sharing and managing members. Choose a step at the top, then an example state, or use Viewing as to switch organizations.
The Partner Networks walkthrough with partner networks only, in development, updated with GIK’s October 26 revisions: onboarding, the role-based Overview and setup guidance.
The Partner Networks walkthrough after the October 13 review: search on the Networks page, inviting organizations first on a new network, an event’s type and stage, three-part need progress, clearer sharing, and private networks marked pending.
The full Partner Networks walkthrough: several networks, a Networks page with a full-width map, a partner or private choice when creating, and each network’s home page, which fills in as members join and needs come in. Choose a page, then an example state.
The standard Partner Networks walkthrough, where invitations get their own full page with Find on GIK and Invite by email tabs. Choose a step at the top, then an example state.
The full Partner Networks walkthrough with its current network home page, unchanged, so it can be compared with three new versions over the same network and data. Switch versions from the bar at the top.
The Networks page that replaces the follow directory. It shows the organization's own network first, then waiting invitations, then a card for each partner network, ordered by what is waiting on the organization. Switch between the example states at the top.
One network's page, the same for a partner network and a private one: Overview, Needs, Resources, Events, Members or Locations, and Impact with example stories. Switch between the example states at the top.
How a supplier shares its resources with networks: from its Resources screen to several networks at once, or from inside a network. Each share either sets aside an amount for that network or is first come, first served. Switch between the example states at the top.
A nonprofit creates a partner or private network on one short page, then invites organizations by searching GIK, from its other networks, or by email. The example states include a warning when no supplier is invited.
A network adds an event, from a GIK disaster or another kind of response, and posts a need that only its members can see: items, how much, and where and when. Switch between the example states to try the choices and the editing limits.
Any network member drafts an impact story from completed orders. The platform drafts from those facts and shows its sources, the writer edits, and every organization named approves. Switch between the example states at the top.
An event has two pages: the event inside one network, with its needs, map, impact, stories, activity and orders, and for an event tied to a GIK disaster, the event across your networks. Switch between the example states at the top.
Any organization on GIK can open Disasters to see the ones it is part of, a map of every active disaster, and a page for each one with needs, totals and stories. Switch between the example states at the top.
A nonprofit invited to a partner network sees who else was invited and what the network is asking for, then accepts or declines. It is not in the network until it accepts.
The person who set up a network invites organizations already on GIK, or others by email. Members of a past network are already picked. Switch between the example states, from searching to pending invitations.
A nonprofit reads its invitation to a partner network, including that its open needs may show up there, and accepts into the network home. The example states also show a declined invitation.
A supplier picks inventory to make available to a partner network, chooses who can see it, and sets how much and for how long. Switch between sharing with partners and with this network only to compare the two lists.
A side-by-side look at two meanings of the word network: businesses that trade with each other, or organizations gathered around a disaster. Product owners can compare them and record which one GIK means.
A network admin creates a trading network with a name, a short description and a choice of who can see it. Create it to see the invitation-first screen that follows, since a network of one does nothing.
A supplier chooses what it shares with each network: which items, how much, at what price and on what terms. It shares nothing by default, and it must preview its listing as a partner would see it before publishing.
A buyer searches every network it belongs to at once, and each result shows which network it came from. Add items from different suppliers to the cart to see it split into one order per seller.
A seller works through partner orders: accept, adjust or decline each one. Stock is set aside only when the seller accepts, and the page lays out every state an order can reach.
A network owner manages members as businesses, not people. It shows roles, suspending a member before removing it, what stays after a business leaves, and what happens if the owner leaves.
A supplier in a partner network chooses which of its resources to share, previews what members will see, and shares them with that network only. Select bottled water and tarps to follow along.
A supplier invited to a partner network sees what the network is asking for and who else was invited. Joining does not mean agreeing to send anything; choosing what to make available is a separate step.
Four ways a business can get into a network, what an invited business can and cannot see before it joins, and the limits that keep invitations from turning into spam. Each path shows how costly it would be to build first.
A supplier sees its invitation to a partner network, reads what joining means, and accepts without promising to supply anything. The example states also show what happens if it declines.
A government organization signs up as its own type and gets the nonprofit experience. Its type shows as Government wherever an organization's type appears. Step through sign-up, after sign-in, where the Government label shows, and an existing organization changing type.
A running list of everything people and systems did on the marketplace, newest first. GIK staff can search and filter it, then follow any event back to the events that led to it.
GIK staff see offers that have waited too long before anyone ordered, with both sides and how long they have waited. Try the filters, then nudge the waiting party, flag the offer or move it on.
GIK staff see orders that stopped moving after an offer was agreed: placed but not shipped, shipped but not received, or a delivery problem. Write a reason, then nudge the waiting party, mark the order received or cancel it.
GIK staff look up an organization and correct its record on its behalf: details, verification, members and limits on who it can deal with. Pick an organization, then write a reason to turn on Save.
GIK staff see when a partner's software is the reason nothing moves: messages GIK could not deliver and keys that keep failing. Try retrying a delivery, pausing it, messaging the partner or issuing a new key.
The earlier version of network setup, where only GIK staff could set up a network. Kept for the record; the Nonprofit portal screen replaced it and now serves both GIK staff and nonprofits.