Full feature reference
ViewTwo lives in your Windows tray and works across one pipeline — naming a fresh export, advancing it through revision, getting it to a colleague for review, recording the issue and, if needed, stripping the filename down to code for cloud-based issue. Nothing here renames or overwrites your originals unless you explicitly confirm it.
Right-click any freshly exported file and give it a compliant name for the first time — picked field by field, never typed from memory.
No AI, no guessing. Every field is picked by you, from real data — never inferred, never auto-repaired.
No AI also means no token cost and no API bill — what you pay for ViewTwo is what it costs, without usage-based surprises.
Level, type, role and revision are chosen from dropdowns sourced from real ISO 19650 field data — you never type or memorise a code, and you can't typo a field that doesn't exist.
A contractor's naming convention doesn't match your firm's defaults? Import their Level, Type and Role codes for just that project number, and Re-Name's dropdowns offer them alongside your own built-in set — without changing what any other project sees.
Covers drawings alongside non-drawing types — Calculations, Method Statements, Risk Information, Programme, Forms, Sketches, and Contract Particulars — so it's not just for drawing sheets.
A new export keeps the revision already in its name — a drawing exported as C1 is named at C1. With no revision in the name, ViewTwo takes it from the sheet's own revision table; with neither, it begins at the first working-draft revision — P01.01, or P0.01 if your office uses one-digit numbering. If the name and the sheet disagree, you're told before anything is pushed.
Open Re-Name on a file that already carries a drawing code — say, one the sheet check flagged — and every field is filled in from its name, revision included. You only change what's wrong.
Level is always part of the name — XX when no level applies, ZZ for several, as the UK National Annex sets out. Only a project on a contractor's non-ISO numbering can leave it out, and ViewTwo remembers that choice for that project.
Right-click a file anywhere and choose ViewTwo › Re-Name / Review In Place: Create Named Copy leaves a correctly named copy beside the file and never touches the original. Rename and Queue renames the file itself where it sits and sends it straight into Awaiting Issue — but only after a box tells you exactly what will happen and you click Yes. Once issued, that file goes to the Recycle Bin (on a network drive, which has none, it is left where it is).
Add a plain-English description alongside the compliant code, so the name stays meaningful to a human as well as valid to the standard.
See the actual PDF page or image you're naming, right inside the wizard, so you're never naming a file blind or guessing which one you've got open.
Your originator code is remembered across sessions and pre-filled next time, so repetitive fields don't need re-entering on every single file.
Not limited to drawings — images, Office documents, and email attachments can all be given a compliant name the same way.
Create Named Copy and To Issue always make new, correctly named copies. The one time ViewTwo renames or recycles a file you exported is Review In Place’s Rename and Queue, and only after a box tells you exactly what will happen and you click Yes.
Advance an already-named file through its revision lifecycle, with the next code computed for you at every step.
You pick what you're doing — draft, share, or publish — and ViewTwo computes the correct next code. You never type a revision number yourself.
Every file shows its drawing number and title, its real filename, and its current status and revision at a glance — no need to decode a long filename in your head.
For a PDF drawing, ViewTwo reads the sheet's own title block and revision table. It fills in the revision description for you and locks the push if the drawing number on the sheet disagrees with the filename, or the sheet's revision doesn't match the revision being issued — so a stale sheet can't go out under the wrong name. Rename or re-export and it checks again by itself.
UK National Annex numbering by default (P01, P02… then C01, C02…), or one-digit if that's your office's way. After a construction issue the next shared issue carries on from the last P — P03, C01, P04 — and a drawing always keeps the width it started with.
A simple green/amber/red indicator shows whether a filename fully conforms, is missing a field, or can't be parsed at all — instantly, without opening the file.
Attach a plain-English description to any file, purely for your own reference. Display-only — it's never written into the file itself.
ViewTwo tracks the last revision issued for each file, so the next issue continues correctly instead of re-reading a static filename every time.
Select several already-issued drawings at once and move each straight to its own next revision — WIP to the next draft, Shared to the next issue, Published to the next construction issue — with a full preview before anything is written.
A default local staging folder for files you're actively working on, kept separate from your live project folders until you're ready to issue.
When you're ready to issue, pick a destination root and ViewTwo deposits into a dated subfolder — always a new file, never an overwrite, and always shown to you before it writes anything.
Click the ? in the push window for what each revision code means and which status codes the drawing can use. It always lists the codes actually in use — including your firm's own — and its window grows so none are hidden.
Working with a contractor whose status codes are their own, just for the life of one job? Import a codes workbook against that project only — it replaces that project's status codes with exactly what's in the file, leaving your firm-wide defaults and every other project untouched.
The name you give a drawing at push time lands in the actual filename too, not just the register — switch it off per project if you'd rather keep filenames to the bare code.
Most cloud drawing platforms expect bare ISO 19650 filenames with no free text. Select the pushed files, right-click, and get code-only copies ready to upload — recorded in the register as a new issue if you want.
Sending to a client who doesn't want BIM codes? Right-click and get copies named just the project number, drawing number, revision and title — 007 0100 P01 Ground Floor Plan.pdf — into the same dated issue folder, recorded in the register if you want.
Copied some exports in Explorer? Click in To Issue and press Ctrl+V — or right-click and choose Paste into Repository — and they land in your Pre-Issue Repository: copied, or moved if you cut them, and never over a file already there.
To Issue fills the panel when you need it and steps aside for your pins when you don't — the orange To Issue button at the foot of the panel swaps between them and shows how many files are waiting.
Get a file or folder to a colleague, without opening email or hunting for a shared-drive path.
Right-click any file or folder and send it directly — no need to have ViewTwo's panel open first.
Tick multiple recipients in one go, rather than repeating the send for each person individually.
ViewTwo resolves the path across shared storage automatically, and warns you clearly if a location isn't reachable rather than failing silently.
The sender's name is built into the shortcut that arrives, so nobody has to guess who shared a file with them.
For a file that isn't on shared storage, or a snapshot you want them to keep, Send Copy to Colleague puts a dated, named copy in their Drop Clips folder — and doesn't send it twice if they already have it.
Shortcuts live in the Drop inbox, copies in Drop Clips. ViewTwo sorts anything that lands in the wrong place, reminds you weekly if Drop Clips needs a tidy, and never deletes a thing.
Save or export into your Pre-Issue Repository and ViewTwo takes it from there — no right-click needed.
Your Pre-Issue Repository is a single, dedicated location — nothing to pin, configure, or set up beyond it.
Which extensions trigger it is set in Settings — defaults cover PDF, DWG, RVT, DXF, DOCX and XLSX.
Save or export a matching file there and it waits in Awaiting Issue, counted on the panel’s For ISSUE button — one click opens Re-Name on it, ready for you to fill in the fields.
ViewTwo recognises a re-export of a drawing you've already issued and renames it in the Repository to match, automatically — ready to push straight away, no naming step at all.
Export a whole sheet set into the Repository in one go and Re-Name opens on each file in turn — never several naming windows piling up on screen together.
If automatic recognition ever misses which existing file a re-export continues, Replace Issued File looks for it, shows you what it found and asks first. If it finds nothing, or you say no, you point it at the right one directly.
One button that walks you through everything sitting in your Pre-Issue Repository, one file at a time, until it's empty.
Shows exactly one file at a time — name it or push it, then it moves you straight to the next. No free browsing, no risk of leaving something half-done.
Already named and ready to push? Straight to the push screen, fields pre-filled from the last time you issued it. Still raw? One click opens naming for it.
No manual copying into your project's Issued folder — Awaiting Issue creates the dated destination folder, moves the file there, and updates your issue sheet, all in one step.
Clear the queue and leave it open — drop another file into the Repository and it appears automatically, no need to reopen anything.
A real drawing register, kept automatically, one row per drawing — not a log of every push.
Each drawing gets a single row. Every time you re-issue it, a new date column captures that revision — the row grows sideways as the drawing's history grows, exactly like a real project register.
Built from a real drawing register template, right down to the fonts and column layout — and a revision column that always shows each drawing's latest issue, computed automatically as new dates are added.
The top of the sheet has two boxes side by side for a logo or company details — use either one, or both. Set it up once and it carries onto every page automatically.
A big job doesn't stay on one page forever — once a sheet's issue dates fill up, ViewTwo starts a new tab with the full drawing list and your header repeated, exactly like copying the tab by hand for page 2, 3, 4…
Each row records exactly what you'd expect on a formal issue sheet — a real ISO 19650 status code, not a simplified label. Ships with the 2021 UK National Annex set (S0–S5 and A codes) ready to use, or your own project-defined codes if the international standard's own approach (leaving status codes to each project's Information Standard) suits your work better — see International vs UK for the difference. B codes are deprecated in the 2021 UK annex, so they aren't built in; add them in Settings if your project still uses them.
ViewTwo keeps a ready-made workbook of your Functional Breakdown and status codes in your Default Templates folder. Add your firm's codes, drop it into your Pre-Issue Repository, and they're imported — nothing is ever removed by a file. The workbook always matches Settings, so the two never drift apart. Remember to update the status codes on your Drawing Issue Sheet legend to match: by itself it only explains S0–S5 and A.
After a push, ViewTwo asks if you'd like to open it — say yes and a real .xlsx spreadsheet is generated and opened for you, no setup or Power Query required.
Every push updates both an unfiltered Audit Trail — the complete history, every issue, WIP included — and a second, filtered Drawing Issue Sheet for whoever the drawing actually goes to. Both come from the exact same data, so they can never drift apart from each other.
Every push belongs to an issue set — several can go out on one day — and each set can carry a purpose of issue (For Planning, For Tender, For Construction…) from a grouped list you can edit, plus a short note. The Audit Trail's Issue Log tab lists each set with its date, purpose, note and drawings. A purpose picked by mistake can be corrected afterwards, and the log keeps what it was.
Draft-stage revisions — BS EN ISO 19650-2's P{major}.{minor} tier — are hidden from the Drawing Issue Sheet automatically. Turn it on per project if you genuinely want WIP visible to whoever receives it; Shared and Published revisions always show either way.
Both documents are named with the project's own number — e.g. "412 - ViewTwo_Issue Audit.xlsx" and "412 - ViewTwo_Drawing Issue Sheet.xlsx" — unmistakable in a folder full of other projects.
Every update also writes a tab-separated .txt version alongside each spreadsheet — readable without Excel, and easy to link straight into your own register.
Space for 10 names and companies sits at the very bottom of every page, automatically shifting down as the drawing list grows beneath it — type them in once, on the first page, and ViewTwo carries them onto every later page for you.
Required to use your firm's own register layout? Map its columns once, drop the pair into your Pre-Issue Repository, and every push fills it in automatically alongside ViewTwo's own Audit Trail and Drawing Issue Sheet — matched by drawing number, backed up before every write, covered by the same Undo Last Push. Add the optional [PURPOSE] marker and each date column shows that issue's purpose too — at the head or the foot of your sheet, wherever your layout has it. Full setup steps →
One click to everything you actually use, every day — and one click to hand that whole setup to a colleague. No server, no sync software, no account to create. Just point ViewTwo at folders you already have. Illustrative estimate: roughly 2 hours saved in a typical 37-hour working week, not spent re-navigating to folders you use every day.
Stop re-navigating the same six-folder-deep network path every morning. Right-click any folder or file once, pin it, and it's one click away from the tray for good.
Already copied the folder or file? Click Paste Shortcut on the panel and it's pinned — no right-click menu needed at all.
Export your pins as a single file and send it to a teammate — they import it and instantly have the same organised set of shortcuts you do. No shared server, no synced database, nothing to configure on their end.
Local drives, mapped network drives, UNC paths, OneDrive or SharePoint-synced folders — pin any of them exactly as they already exist. No proprietary storage, no migration, no new technology for your team to learn.
Pins are grouped by drive and project with collapsible headings, so the panel stays tidy even with dozens of pins spread across several live projects.
Pin View steps your pins through list, cards and a project-tabs view — the button names the one you are in (Pin View List, Pin View Cards, Pin Visibility). In Pin Visibility, click a project's tab to hide it (it turns white) or show it again. A hidden project disappears from the panel and the Explorer ViewTwo folder — nothing is unpinned, and pinning something new into a hidden project brings it back.
File the emails you receive and the emails you send — the email itself and its attachments — into the project's Correspondence folder in a click, without Outlook's save-as dialog for every file. Works with classic desktop Outlook only — not the new Outlook, and not Outlook on the web.
Select emails in Outlook and click File Messages, or pick from the last 20, 50, 100 or 200. Choose Received or Sent, and tick Include emails without attachments to file an email thread on its own. Several emails for one folder? Tick Save the remaining ones the same way and they file in one go.
Each email gets its own dated folder in the project's Correspondence folder, named date [sender] [subject] (or To recipient for one you sent), so the folder sorts by date — with the email itself (.msg) and its attachments inside, together. ViewTwo picks the project from a number in the subject, or the one you last used, and says why. A project without a Correspondence folder? It says so and offers to make one.
Every save also writes a standalone "<date> [from] [subject].txt" file alongside the attachments — the full headers and body — so the folder reads on its own without going back into Outlook.
The destination folder is pinned to your panel the moment the save completes — one click away next time, instead of hunting back through Outlook or a shared drive.
Leave Also send to To Record ticked and the saved attachments appear in the panel's To Record list too, knowing who the email was from or to and its date — so logging them is a single confirm. Nothing is recorded until you say so.
ViewTwo checks which Outlook you're running and asks you to switch to Classic first if you're on the new Outlook — so nothing silently fails partway through.
See what a consultant has sent you without opening a single drawing, then log it — who sent what, and when — in the project's own log. What you send can be logged too, marked Sent. A dated, per-project record of what came in and went out, supporting the Building Safety Act's golden thread.
Paste files into To Record, right-click a pin and choose Send to To Record — a whole folder, subfolders too, email files left out — or file an email's attachments with Also send to To Record ticked. ViewTwo reads each sheet's title block and lists the title, drawing number and revision beside the file name, in orange where the sheet and the name disagree.
To Record only reads. Your files stay exactly where they are — never copied, moved or renamed — and nothing is recorded until you press Record It. A file you don't want logged? Right-click it and choose Don't record.
ViewTwo works out which project the files belong to the way it does for issuing — from where they sit, or from its index for a file pasted from Downloads. Recording them against a different project needs a firm yes: you type that project's number.
Each row says whether the file was Received or Sent, and From / To whom. The sender is read from the originator code in the file names and the date from the folder they were filed in — or, for attachments saved from an email, taken from the email itself — both shown for you to confirm. Each row carries the revision note from the sheet's own revision table.
The first time, ViewTwo asks where the project keeps the files it receives — Incoming, Inbox, whatever your office calls it, as long as it's inside the project. Its Received Log is kept there as its own workbook, shared by everyone who records for that project.
The exact same file is recorded once, wherever it sits. A later revision of a drawing gets its own row and marks the earlier one superseded, so the log always shows what's current.
Undo Last Record takes back exactly what your last recording added, after showing you the rows. Anything older is marked Recorded in error — struck through in the log with who, when and why — never quietly deleted.
A couple more things that support everything above.
Behind the FIND (Index) button: search by file type and up to two keywords, each matching a filename or the extracted content of the file, combined together to narrow results fast. Deleted and moved files drop out of the results by themselves.
ViewTwo starts with Windows and sits in the tray until you need it — one click on its icon opens the panel, another closes it. No separate app to remember to open.
Every feature above follows the same rule, without exception.
Every feature runs free for a 30-day trial from install. After that, it's £4.99 a user a month or £49.99 a user a year.
See pricing