In Oregon, a digital seal and signature on a final engineering document must be a true cryptographic signature. A pasted image of your seal or a scan of a wet-ink signature does not qualify. The signature must be unique to you, under your sole control, verifiable by a third-party Certificate Authority, and tied to the document so that any later change breaks it. Nevada also allows digital signatures, but its board treats the topic in its own guide and rules.
This guide is for engineers, designers, and drafters who send wood-frame residential calculations and plans to building departments in Oregon and Nevada. It covers what the rules say, where submittals get rejected, and how to build a signing step into your shear wall workflow.
TL;DR
- Oregon accepts a "digital seal and signature" on final electronic documents only when it is independently verifiable by a third-party Certificate Authority and invalidated by any change to the document. Facsimile images are not accepted.
- Merging PDFs after signing breaks the signatures. Compile first, then sign the final master file.
- "Certifying" or locking a PDF is not the same as digitally signing it, and it can block reviewer comments. Nevada's board guidance warns about this.
- A digital signature carries the same responsible charge and disciplinary exposure as a wet-ink one.
- ShearWise Pro produces clean, reviewer-friendly PDF reports. You apply your seal and certificate-based signature to the final document.
Table of Contents
- What Oregon requires for a digital seal and signature
- What does not count as a digital signature
- Compile first, sign last
- Oregon firm licensing and out-of-state teams
- Nevada: what changes
- Where signing fits in a shear wall workflow
- Our perspective on digital signatures and calculation reports
- Try the report workflow
- Pre-submittal signature checklist
- FAQ
- Sources
What Oregon requires for a digital seal and signature
The rule is Oregon Administrative Rule 820-025-0010. The full text of OAR 820-025-0010 defines a digital seal and signature as an authentication process attached to an electronic document. It is not a photocopy, a scan, or a facsimile of a hard-copy seal. It is also not a computer-generated image of a seal and signature. Those are not allowed on final documents.
The Oregon State Board of Examiners for Engineering and Land Surveying (OSBEELS) summarizes the working requirements on its seals and signatures page. A valid digital signature must be:
- Unique to the registrant. It identifies you and no one else.
- Under your sole control. Nobody else holds the key or the password.
- Independently verifiable. A third-party Certificate Authority can confirm it.
- Linked to the document. Any modification to the data invalidates the signature.
The same page states that a digital seal must be at least 2 inches from point to point when the page is printed at full size. Check that on a test print before you submit.
What you attest when you sign
Sealing is more than a formatting step. By applying your seal and signature, you attest that your license is active and that you were in responsible charge of the engineering work. OSBEELS states this on the same page. The board's position is that a digital signature is just as binding as ink, with identical exposure if the work is wrong.
For a shear wall package, "responsible charge" means you reviewed the wall lines, openings, hold-down forces, and story drift checks well enough to stand behind them. A calculator can organize the numbers. It does not transfer that responsibility.
Why the state cares about the cryptography
The Oregon Department of Transportation frames digital signatures as a document integrity tool. Its digital signatures page describes the signature as providing signer authentication, document authentication, and efficiency. In practice, if someone alters a calculation after you sign, the signature shows it. That is the property a picture of a stamp cannot provide.
What does not count as a digital signature
Most rejections come from a handful of habits that look reasonable on screen.
| Common practice | Accepted on Oregon final documents? | Why |
|---|---|---|
| Scan of a wet-ink signed and stamped sheet | No | It is a facsimile of a hard-copy seal |
| Pasted JPG or PNG of your seal and signature | No | It is a computer-generated image without cryptographic validation |
| "Certify" or lock command in PDF software | Not by itself | It is not a Certificate Authority-backed signature, and it can block review comments |
| Certificate-based signature from a third-party Certificate Authority | Yes, if all four requirements are met | It is verifiable and breaks on any change |
The Nevada Board of Professional Engineers and Land Surveyors raises the "certify" point in its Electronic Submittal and Digital Signature Guide. Certifying a document in software is a common misconception for a digital signature. It can also prevent the comments and corrections that building departments need to make. The goal is a cryptographically secure signature on a file that stays open to reviewer mark-ups until final approval.
Compile first, sign last
The most common workflow error is signing individual files and then combining them. Per OSBEELS, compiling separate files into one master document invalidates existing digital signatures. You have two correct options:
- Apply your digital signature to the final compiled document.
- When several disciplines contribute, have each professional re-apply their signature to the combined master file after compilation.
Submitting pre-compiled signed files without re-signing is a known cause of rejection, so build the order into your checklist.
A signing order that works
- Finish calculations and drawings. Confirm every revision is in.
- Generate the final PDF set, with calculations, shear wall schedule, and any supporting sheets.
- Compile into the single file you will submit.
- Apply your certificate-based digital seal and signature to that file.
- Open the signed file in a fresh viewer and confirm the signature validates.
- Check the printed seal size and the file against the building department's file rules.
That last step matters because many departments set their own file requirements on top of the board rules. Our posts on keeping each trade PDF under 50 MB for permit review and electronically signing structural calculations for U.S. permits go through those details.
Oregon firm licensing and out-of-state teams
If you work across state lines, one point simplifies things. According to OSBEELS's applications page, Oregon does not require firm licensure. Only the individual engineer or architect signing the documents needs to be licensed. There is no separate Certificate of Authorization for the business entity. The signer still has to hold an Oregon license, though. Board rules say no one may practice or offer to practice engineering in Oregon unless registered there.
If you are earlier in that process, the board's licensing overview says you apply online through MyOSBEELS. You provide proof of qualifying education and experience and of passing approved exams. The board describes typical timing of two to four months, depending on meeting dates and a complete application. Applications received by October 1, for example, are considered for the November meeting.
Nevada: what changes
Nevada's rules sit in a different place and read differently. Nevada Administrative Code 625.610 covers stamps, seals, and signatures. The text of NAC 625.610 allows a licensee with responsible charge to apply an electronically prepared seal and digital signature to a document that is submitted electronically. For physical stamps, it describes a seal of approximately 1.7 inches in diameter. It also requires the licensee to validate the seal with a signature and the date.
The practical differences to plan for:
- Nevada's board publishes a dedicated guide with its own terminology: stamp image, electronic signature, and digital signature are separate terms. Read it before you set up your template.
- Seal dimensions differ between the two states: at least 2 inches point to point for Oregon digital seals, about 1.7 inches in diameter for Nevada's stamp.
- Local building departments in Nevada may add their own submittal rules. Confirm with the department before you submit.
If you also submit in California, the rules and the reviewer expectations differ again. See our California signature checks for engineers.
Where signing fits in a shear wall workflow
For 1-story and 2-story wood-frame projects, the signed PDF is the last step of a longer chain. Reviewers rarely reject a package only for the signature. They also reject it for gaps in the calculations. A reliable sequence looks like this:
- Set the lateral basis. Confirm seismic and wind inputs for the site. Our explainers on Oregon seismic design category and Oregon building code lateral design cover the inputs.
- Define wall lines and openings. Identify full-height segments and the openings that break them up.
- Size shear walls and connections. Work out hold-down forces and transfer straps, then check roof information and story drift.
- Build the schedule. A clear shear wall schedule is the page reviewers read first.
- Generate the report, compile, and sign. Compile everything into one file, then sign once.
- Plan for resubmittals. One missing sheet can restart review, as we explain in permit resubmittal packages.
For a wider view of what plan checkers want in the calculation package, read what U.S. reviewers require for permit structural calculations. For Oregon residential projects, the 2026 Oregon residential structural design checklist gives a pre-submittal list.
Our perspective on digital signatures and calculation reports
We build ShearWise Pro for one kind of project: 1-story and 2-story wood-framed buildings. That focus shapes how we think about signing.
The signature is the engineer's act, not the software's. The rules for Oregon and Nevada put the licensee in responsible charge. So we design reports to be easy to review before you sign. Wall lines, openings, full-height segments, hold-down forces, transfer straps, roof information, and story drift checks are organized in a consistent order. You can verify the numbers faster, and a plan checker can follow them.
We also treat the PDF as a working document until it is final. A report that reviewers can open, read, and mark up is better than one locked early. That matches the Nevada board's warning about certifying documents before review is done. When the package is final, compile it, then apply your own certificate-based signature to the master file.
One caution from experience with submittal workflows: do not treat a clean-looking seal image as a shortcut. It looks finished, and it fails the Oregon definition. A five-minute check of your signing tool and certificate saves a rejection cycle.
— Evalin
Try the report workflow
If you prepare shear wall calculations for Oregon or Nevada permits, the ShearWise Pro shear wall design program lets you start with a free three-report trial. Trial reports are watermarked. Paid access is $29 per month on Professional Monthly or $250 per year on Professional Annual. You can also look at the validation library with calculation examples to see how results are laid out before you commit.
Pre-submittal signature checklist
Print this section or paste it into your office checklist.
- Your license is active in the state where the project is located.
- You were in responsible charge of the work you are sealing.
- Your certificate comes from a third-party Certificate Authority, and you alone control it.
- The package is compiled into the single file you will submit.
- You signed after compiling, and each other discipline re-signed the master file if there are several.
- The signature validates when you reopen the file in a fresh viewer.
- You did not use "certify" or lock in a way that blocks reviewer comments.
- Seal size is correct on a full-size print.
- File size and file name meet the building department's rules. For Bakersfield-area work, see our post on 35-character file names for structural ePlan review.
FAQ
Can I paste an image of my stamp into a PDF for an Oregon submittal?
Not on a final electronic document. OAR 820-025-0010 excludes computer-generated images of a seal and signature, as well as scans of signed hard copies. You need a digital signature that a Certificate Authority can verify and that breaks if the file is altered. Check with the reviewing agency for how it treats preliminary or non-final documents.
Do I need a separate digital signature for each page?
A single signature on the final compiled document is the cleanest approach. Compiling files after signing invalidates earlier signatures, so sign the master file last. Some agencies set their own rules, so confirm with the department that will review your package.
Does Oregon require my engineering firm to be licensed?
No. OSBEELS says only the individual engineer or architect who signs the documents needs to be licensed in Oregon. There is no separate firm authorization. The person signing must still be registered in Oregon.
Is Nevada's digital signature rule the same as Oregon's?
No. Nevada allows an electronically prepared seal and digital signature under NAC 625.610, and its board publishes its own guide with its own terms. Read that guide and the local building department's requirements before you set up your template. Do not assume an Oregon-compliant file meets Nevada's requirements.
Does ShearWise Pro apply my digital signature?
ShearWise Pro generates organized PDF reports for 1-story and 2-story wood-framed projects. You apply your seal and certificate-based signature to the final compiled document with your own signing tool, as the board rules require.
Sources
- OSBEELS: Seals and Signatures
- OAR 820-025-0010, Digital Seal and Signature for Electronic Final Documents
- Oregon Department of Transportation: Digital Signatures
- Nevada Board of Professional Engineers and Land Surveyors: Electronic Submittal and Digital Signature Guide
- OSBEELS: Applications
- OSBEELS: Obtaining a License
- Nevada Administrative Code 625.610