Resources / Project recovery inventory worksheet
Project recovery inventory worksheet
Use these questions to list what you have and what still needs checking. The summary can help you prepare for a project review. It does not inspect the code or decide whether to repair or rebuild.
Do not enter passwords, tokens, account identifiers, source code or personal data. This worksheet uses fixed choices only. Answers stay in this tab’s memory, are never uploaded and are not saved in browser storage. Refreshing clears them. The worksheet sends no answers or summary text.
Your summary
Choose what you know. Unanswered items will be marked unknown.
Review the text before sharing it. Downloading creates a file on your device. Clear answers removes this tab’s answers and summary; it cannot remove files you have downloaded.
What the inventory can and cannot tell you
An unknown answer means something still needs checking. It does not mean a file is lost or a rebuild is necessary. Even a complete set of answers needs to be reviewed against the actual code, accounts and important tasks.
If account control or the right to use the software is unclear, mention that in the review. The account owner, provider or an appropriate adviser may need to help resolve it.
Use the summary to plan a review
Read what to recover when a developer disappears for the order of investigation. Once the recovered version and necessary user actions are understood, compare repair and replacement options.
Turn the inventory into an assessment request
Use the listed questions to agree what a reviewer will inspect and what depends on an owner or provider decision. Read project rescue services or ask about the missing handoff. Share only the general situation in the first inquiry.