On this page
Short answer: "works offline" can mean three different things: a desktop app with its own data, a web app that caches a few pages, or edits that wait and sync later. Only the first and third let you do real work without a connection. Before you pick a tool, ask what happens when two people change the same item while apart.
Who actually needs it
- Site and field teams in areas with poor coverage.
- Travelling consultants on planes and in client buildings that block outside access.
- Secure environments where the network is separated from the internet.
- Anyone who wants the tool to keep working when the connection or the vendor's service is down.
If your whole team is always online, you may not need it. Be honest about that.
The three kinds of "offline"
| Kind | What works without a connection | The catch |
|---|---|---|
| Cached web page | You can view what you already opened | You cannot change anything, or changes are lost |
| Desktop app with local data | Everything, because the data is on your PC | You need a way to share it with the team |
| Sync later | Edits are queued and sent when you reconnect | Conflicts must be handled |
A good offline tool is a mix of the second and third: your own copy of the data, plus reliable syncing.
What happens when two people edit the same thing
This is the real test. Ask the vendor:
- If we change different fields of one item, are both kept?
- If we change the same field, which wins, and is the loser kept anywhere?
- Is there a history, so that nothing is silently lost?
- Who decides what a person is allowed to change when their edits come back?
How NUSK works offline
NUSK's desktop installer (Windows, macOS, Linux) keeps each user's data on their own PC, so you can plan and update work with no connection. To work as a team, one install acts as the hub, and the others sync with it when they connect.
- Same office or VPN. The project admin turns on hosting for the team in Roles & access > Sharing and sync. Teammates reach the hub across the network.
- Different homes. Build the project locally, then publish it to a server or domain that runs NUSK and share that address.
- Joining. The admin invites a person with an email and an access level, and gives them a one-time key that expires in seven days. They choose Join a project, enter the hub address and the key.
- What syncs. Work items, RAID registers, milestones, custom fields, comments, documents and their files, roles and members. Some things stay local: procurement, quality, RACI, stakeholders, metrics, chat, notifications and the audit log. Passwords never sync.
- Conflicts. Different fields of the same item merge. If the same field is edited twice, the latest edit wins and the history keeps the older value. The hub re-checks every change against the sender's role.
- Revoking. An admin can revoke a person. Data already downloaded to their PC stays there, which matters for sensitive projects.
Protecting a single laptop
When data lives on one PC, the backup is your responsibility. NUSK provides a backup page that downloads a point-in-time copy of the database, or a zip with the database and every uploaded document. Schedule a copy to a second location.
Setup, in outline
- Install the desktop app and create your admin account.
- Create or import a project.
- In Sharing and sync, turn on hosting, or publish to a server.
- Invite a teammate and have them join with the key.
- Disconnect one machine, edit, reconnect, and check the result.
Step 5 is your own test. Do it with a deliberate conflict before you trust any tool.
When NUSK is not the right choice
- You need real-time collaboration at all times and a good mobile app for offline field use. A dedicated mobile-first field tool may suit you better.
- You need large file syncing while offline.
Get the desktop app · Start free
See it with your own project
Import a plan or a Jira project into a free NUSK workspace and judge it on your own data.