What Spectivon does
Spectivon is an environmental due diligence, permitting, and compliance platform for renewable energy. It reads a project's documents where they sit in your SharePoint and returns environmental, permitting, and compliance risks, permits, permit conditions, and schedule dates, each cited to the exact source document and page. It is built for renewable energy developers and IPPs, private equity and infrastructure funds, project finance lenders, environmental insurance underwriters, and owner-operators, and it covers a project from acquisition review or early development through construction and operation on one record.
The platform: your documents, read in place
Spectivon connects to each project's SharePoint folders with your own Microsoft sign-in and reads the documents where they already live. Nothing is migrated, re-filed, or copied into another system.
Reads your project folders in place
Connect one or more SharePoint or OneDrive folders per project by pasting their links. Spectivon reads with your own Microsoft 365 sign-in, read-only, so it can open only the files you can already open. It never sees your password: it holds an encrypted access token, the standard way Microsoft 365 apps read files on your behalf, which you can revoke at any time. The files themselves are never saved; only the extracted text, its embeddings, and the results derived from it are kept.
Handles real project files
PDF (including scanned TIFF images), Word, Excel, PowerPoint, email files, and ZIP archives, with OCR for scanned and image-based pages. Very large PDFs are processed in stages rather than skipped. Photos, CAD drawings, and GIS files are listed but not read.
Classifies every document
Each document is automatically classified by type (Phase I and Phase II ESAs, biological surveys, cultural resources studies, SWPPPs, Section 404 applications, USFWS Section 7 letters, BLM right-of-way applications, state permits, interconnection studies, and more) and marked as seller-produced, independent, or ambiguous when the classification is not confident enough to say.
Shows coverage openly
Every document shows what share of it was scanned, and any page left out is listed by page number. Some pages are left out on purpose: pages that are contact lists, such as public-meeting sign-in sheets, are excluded to keep personal information out of Spectivon, and email addresses and phone numbers are removed from the stored text. An expected-versus-present checklist shows which document types a project is missing, and each run lists any file that was skipped and why.
Flags file quality issues
Documents that look like they belong to a different project, read as drafts or superseded versions, or cover only gen-tie scope get an informational flag. Flags can be dismissed, and flagged documents are still indexed and scanned.
File Audit across your whole library
Point File Audit at the SharePoint folder that holds all your project folders. For every project it shows which of 26 expected study types are present (final, draft only, or missing) and whether GIS or CAD files exist, and it flags files that may belong to another project, sit in the wrong folder, are duplicates, or are drafts with no final. Each document gets a readable title and its dates, with the wording they came from. File Audit never moves or changes a file, every flag can be dismissed, and it comes with either module.
Controls what gets indexed
A preview step lists every file in the folder before indexing so you can uncheck any you do not want read. Any indexed document can be excluded later, and the expected-documents checklist accepts a manual "covered by" override when one document serves more than one purpose.
Stays current automatically
A daily check reprocesses only new or changed files. When something changes, a fresh risk scan runs, and for Asset Management customers permit and schedule-date extraction run too. You can also check for updates on demand or index every project at once. A What Changed view records every new or updated finding, permit, condition, and document with a source and timestamp, per project and across the portfolio.
Never silently deletes or overwrites
A finding that a rescan no longer reproduces is marked superseded, not removed, and is restored if it reappears. A removed source document is flagged on everything that cited it. A permit condition that a re-extraction no longer reproduces is flagged as possibly removed for review. Your manual edits are never overwritten by a later automatic scan.
Projects and portfolios
Deals under review and projects you hold sit in the same projects table, grouped into portfolios, with sorting, filters, custom columns, search that includes a project's former names, and a notes feed. Cross-project views cover findings, Q&A, permits, the compliance calendar, schedules, and visuals.
Document Chat: ask a project's documents a question
Available with either module.
Answers with citations
Ask a question about a project and get an answer with links to the exact source document and page; PDFs open at the cited page. Answers come from the documents themselves, and when they do not state a number you ask about, chat says so rather than inventing one. Each person's chat history is saved with the project and is there the next time they sign in.
One click to the Q&A log or risk register
With the Due Diligence module, one click turns a chat answer into a buyer question for the Q&A log or a finding for the risk register. Spectivon drafts the entry in the right format for you to review and save, so nothing has to be copied or retyped.
Knows the findings
Chat reads the project's documents and also sees its risk findings, including set-aside ones that bear on an active finding, so answers reflect the review already done.
Due Diligence module: from data room files to a ranked risk register
The Due Diligence module turns a seller's data room files, once copied into your SharePoint, into a ranked, cited risk register as soon as they are indexed and scanned.
Findings, not summaries
Every environmental, permitting, and compliance risk is reported with severity (High, Medium, or Low), probability and impact in ISO 31000 and PMI register style, a category from a closed 18-category taxonomy, a recommended action, a register ID and owner discipline, and a citation to the source document and page.
Every finding checked against its source
Every finding quotes the passage it rests on, and Spectivon confirms that passage appears word for word on the cited page before the finding reaches you. It is the safeguard against AI reporting something the documents do not actually say.
Ranked by a triage pass
All findings are reviewed together after the first pass: duplicates across documents are merged, routine items are set aside (still viewable with Show filtered), severity is recalibrated where warranted, and the three to six top risks for each project are surfaced with a written rationale.
Document conflict detection
When two documents disagree about the same fact, Spectivon surfaces it as a conflict instead of quietly picking one.
Conditional findings stay conditional
A finding that only applies under a stated condition, such as "if the project is located on prime farmland", keeps that condition attached instead of being flattened into an unconditional statement.
Reviewed, clean confirmations
When an expected document type was reviewed and produced no findings, it is marked as such. That is an explicit confirmation, not just an absence of results.
Deal phase and configurable deal gates
Findings are tagged by the transaction stage they matter for (closing condition, pre-close, post-close, operational, or informational) and, where your organization has configured them, by the deal gate they must clear, such as before PPA execution or before NTP. A gate set by hand survives later rescans.
Seller estimates are labeled
A finding sourced from a seller-produced document carries a "Seller estimate, unverified" badge.
Reads maps, figures, and diagrams
Pages that are mainly maps, figures, or diagrams are read as images, and what they show is cited by page and figure caption.
Work the register
Each finding has a status, can be edited, commented on, and linked to a permit. You can add your own findings, which are protected from rescans. Filter and search by severity, category, deal phase, gate, and document, and send a colleague a link to a single finding.
Due diligence memo
Generate a due diligence memo from the current findings. Upload your own Word template in Settings and the memo follows your format, and you can include a list of the indexed documents as an appendix. The memo discloses partial document coverage, lists reviewed-clean confirmations, and counts outstanding seller questions.
Structured seller Q&A log
One log for every buyer question and answer instead of Excel, Teams, and email disagreeing with each other. Spectivon drafts a question for you from a finding or a chat answer, each question records who asked it, and statuses are tracked. Seller responses can be imported from Excel and the log exports to Excel, so it works with whatever the other side sends.
Portfolio view and visuals
See every active deal's risk level, stage, and findings in one view, with charts for findings, coverage, and compliance across the pipeline. Switch the view between All, Owned / Pipeline, and Potential Acquisitions in one click.
Asset Management module: permits, obligations, and schedule
The Asset Management module covers every project you hold, from early development through construction and operation, whether you developed it or acquired it. It keeps permits, conditions, and the schedule current from the project's own documents, and a project reviewed in Spectivon before acquisition carries its diligence record forward.
Permit and condition extraction
Spectivon extracts permits (name, agency, number, dates, status, jurisdiction) and their conditions from the indexed documents, each with source document and page.
Every value traced to the document's own words
A permit number, date, or status is recorded only when the document's own words state it for that permit. Spectivon confirms the quoted wording is on the page and that it refers to that permit, so a date from an unrelated letter is never attached to the wrong one. If the documents do not support a value, it is left blank rather than guessed.
Human review before anything becomes record
Extracted results never enter the permit matrix automatically. They arrive as New Permits Found, Proposed Updates, or Ambiguous Matches for a person to accept, reject, or resolve. Rejections are remembered across later extractions.
Same permit, different wording
Matching recognizes the same permit under different names, agency spellings, and number formats across documents, while keeping genuinely different permits separate. When documents disagree, the more authoritative source wins, so an agency letter outranks a passing mention.
Permit Matrix
Every permit across every project in one filterable view, with status, agency, dates, condition counts, and a page-anchored link to the source of the status. Each permit is classified as an authorization, a required deliverable, or an analysis document; the classification is shown as a badge and never used to hide a row. Deleted permits and conditions are recoverable, and duplicates can be merged.
Permit conditions with real trigger logic
Conditions are tracked by trigger type: a fixed date, a recurring requirement, a date relative to a project milestone, or an ongoing obligation with no end date, along with phase, condition type, responsible party, source document and page, and a reviewed flag. Extracted conditions can be edited, deleted and restored, or merged.
Compliance Calendar
Upcoming and overdue obligations, including permit renewal dates, across your whole portfolio, filterable by jurisdiction, phase, type, and responsible party, with a separate panel for obligations that cannot yet be scheduled to a date. Click through to the exact condition and its source.
Jurisdiction checklist
For a project's state and type, Spectivon can list the permits typically required there (US jurisdictions only), kept separate from anything extracted from your own documents.
Critical-path project schedule
Tasks, dependencies, constraints, and milestones, with the critical path and float worked out the same way MS Project and Primavera P6 do it. If the work cannot finish by a fixed date such as a contractual COD, the schedule shows by how many days it will miss, instead of quietly showing the date as met. Tasks that cannot be scheduled, for example because of circular logic, are listed separately rather than dropped or given invented dates.
Baselines, variance, and exports
Freeze a baseline and see how far each date has drifted from it, with slip flags. Start from a standard solar development template or an Excel import, and export to MS Project XML, Excel, or PDF.
Schedule dates from your documents
When a scanned document states an actual start or finish for a task, Spectivon proposes that date for review, with the passage it came from. It is never applied automatically, confirmed or manual values take precedence over later suggestions, and tasks whose source documents may have changed are flagged as possibly stale.
Ask about the schedule
A chat panel answers questions about dates and float, and runs what-if scenarios, using the same computed schedule shown in the Gantt view. Benchmarks show how long permit types have actually taken to move through stages in your own history.
How Spectivon earns trust
The design principle is that nothing is asserted without evidence you can check.
Every result is cited
Every finding, extracted permit field, permit condition, and document-derived schedule date links to the specific document and page it came from.
Nothing reported that the documents do not say
Each risk finding is checked word for word against the cited page before you see it. A permit number, date, or status is recorded only when the document's own words state it for that permit. Where the text is not there, Spectivon leaves the value blank rather than guessing.
Gaps are shown, not hidden
Partial document coverage, unestablished quantities, unschedulable tasks, conflicting documents, and unverified seller estimates are all surfaced as such.
People stay in control
Extracted permit and schedule data goes through human review, manual edits are protected, and the history of every permit field is kept.
Security and data handling
- You sign in with your own Microsoft 365 account. Spectivon never sees your password; it keeps an encrypted access token, the standard way Microsoft 365 apps read files on your behalf, which you can revoke at any time. Your document files are never saved: Spectivon reads them where they sit in your SharePoint and keeps only the extracted text, its embeddings, and the results derived from it.
- Spectivon asks only for standard, read-only Microsoft 365 permissions on your own account, so it can open only the files you can already open. Your IT team can review or revoke that access in Microsoft Entra ID like any other Microsoft 365 app.
- Each company's data can be read only by that company's users, enforced by row-level security on every database table.
- Microsoft access tokens are encrypted before they are stored (AES-256-GCM). Connections, indexing, scans, and memos are recorded in an audit log. All of your data is deleted within 30 days of contract termination or a written request.
- Accounts are provisioned by Spectivon for each organization. There is no self-serve signup.
- Spectivon runs on infrastructure providers that hold SOC 2 Type II attestations, including Microsoft Azure and Anthropic. Spectivon's own SOC 2 certification is planned, not yet held.