Free Browser Prompt Tool

Browser Workspace Audit Template

Audit your browser workspaces, recurring tabs, extensions, saved sessions, and context-switch triggers with a practical checklist you can reuse.

How to use this audit

Run it with your browser open. Inspect what is active now, not the system you meant to build. Mark each item only after you verify it.

CadenceMonthly, or after a major project ends
Time needed20 to 30 minutes
Target outcomeFewer ambiguous places for active work
RuleKeep only what has a defined job

1. Workspaces

2. Pinned and recurring tabs

3. Extensions

4. Saved sessions

5. Context-switch triggers

6. Close the audit

Choose a small set of actions you can finish now. A browser audit is complete when the environment changes, not when the checklist is full.

DecisionItemActionDue
Keep________________Define its permanent job________
Merge________________Move into canonical home________
Archive________________Name, date, and close________
Remove________________Delete or uninstall________
Automate________________Create startup or shutdown rule________

Copy-paste markdown template

Copy the full template into your notes, project system, or team documentation.

markdown
# Browser Workspace Audit

Date:
Auditor:
Browser(s):
Next review date:

## Audit rules

- Verify the browser as it exists now.
- Keep only items with a defined job.
- Separate active work, reference material, and archives.
- Finish with concrete changes and owners.

## 1. Workspaces

- [ ] Inventory every workspace or profile: name, purpose, owner, and included work.
- [ ] Flag overlapping workspaces that hold the same project, client, or responsibility.
- [ ] Flag orphaned workspaces with no active purpose or no activity in 30 days.
- [ ] Confirm personal, company, client, and sensitive identities are separated where needed.
- [ ] Rename vague spaces so their purpose and next action are obvious.
- [ ] Write one boundary rule for each workspace: what enters and what never enters.

### Workspace inventory

| Workspace / profile | Purpose | Owner | Boundary rule | Keep / merge / archive |
|---|---|---|---|---|
| | | | | |
| | | | | |
| | | | | |

## 2. Pinned and recurring tabs

- [ ] List every pinned, auto-opening, and daily recreated tab.
- [ ] Assign each tab a job: communication, command center, reference, queue, or production.
- [ ] Remove duplicate recurring tabs and keep one canonical instance in the correct workspace.
- [ ] Unpin items used fewer than three times per week unless they serve monitoring or emergencies.
- [ ] Confirm startup tabs open only where and when needed.
- [ ] Define a maximum number of permanent tabs for each workspace.

### Recurring-tab inventory

| Tab | Workspace | Job | Use frequency | Keep / unpin / remove |
|---|---|---|---|---|
| | | | | |
| | | | | |
| | | | | |

## 3. Extensions

- [ ] Export or list enabled and disabled extensions across every profile.
- [ ] State the current problem solved by each enabled extension.
- [ ] Remove overlapping extensions unless the difference is documented.
- [ ] Review access to page data, downloads, history, and sensitive accounts.
- [ ] Disable extensions unused in 30 days; remove them at the next review if nothing breaks.
- [ ] Record publisher and update status for extensions trusted with sensitive work.

### Extension inventory

| Extension | Profiles | Function | Sensitive permissions | Last used | Keep / disable / remove |
|---|---|---|---|---|---|
| | | | | | |
| | | | | | |
| | | | | | |

## 4. Saved sessions

- [ ] Inventory built-in restore, tab managers, reading lists, bookmark folders, and saved windows.
- [ ] Open a sample of saved sessions and verify they still load.
- [ ] Give every active session a next action.
- [ ] Give every archived session a descriptive name and date.
- [ ] Delete duplicate crash restores and unnamed windows after checking for unique material.
- [ ] Define what deserves a saved session instead of a bookmark, note, task, or closed tab.
- [ ] Close and restore one noncritical session to test recovery.

### Saved-session inventory

| Session | Location | Status | Next action or archive date | Keep / merge / delete |
|---|---|---|---|---|
| | | | | |
| | | | | |
| | | | | |

## 5. Context-switch triggers

- [ ] Observe one 30- to 60-minute work block and tally every switch.
- [ ] Label each trigger: notification, missing information, unclear next action, wrong workspace, waiting, habit, or interruption.
- [ ] Record tab pairs or sequences repeated more than twice.
- [ ] Identify tabs, extensions, and web apps allowed to interrupt active work.
- [ ] Record failed searches for tabs, logins, files, or prior context that need a fixed home.
- [ ] Add one prevention rule for each frequent trigger.

### Trigger log

| Time | From -> to | Trigger | Intentional? | Minutes lost | Prevention rule |
|---|---|---|---|---|---|
| | | | | | |
| | | | | | |
| | | | | | |

## 6. Decisions and actions

| Decision | Item | Exact action | Owner | Due date | Done |
|---|---|---|---|---|---|
| Keep | | Define its permanent job | | | [ ] |
| Merge | | Move into canonical home | | | [ ] |
| Archive | | Name, date, and close | | | [ ] |
| Remove | | Delete or uninstall | | | [ ] |
| Automate | | Create startup or shutdown rule | | | [ ] |

## Closeout

- Workspaces before / after:
- Pinned tabs before / after:
- Extensions before / after:
- Saved sessions before / after:
- Most common switch trigger:
- One rule to test before the next audit:
- Next review date:

Keep the audit honest: a checked box means you inspected the live browser and made or recorded a decision.