Discover with context
Review county and property information, then bring selected opportunities into your working list. Check the source status before treating a listing as ready for a bid.
Evidence packs
Updated · Accrella product team
Tax Lien Evidence Packs for Review and Handoff
A usable file should let another person understand a decision without rebuilding your research. Keep original records and the context that explains how they were used.
A tax lien evidence pack is an organized collection of source records and supporting documents associated with a certificate or matter. Accrella supports evidence packs, retained acquisition evidence, controlled item access and export records.
Approve the strategy
Review diligence and approve each bid strategy. The county CSV export is blocked when a selected matter lacks the required diligence or still needs strategy approval.
Keep the operating record
Retain acquisition evidence with the matter so the team can inspect the facts behind a decision as the position progresses.
Controlled product demonstration
Inspect the record behind a fictional Broward certificate
Captured September 6, 2026 in the actual Accrella application running locally at product revision 394e58c. Certificate DEMO-PUBLIC-FL-001, its parcel, amounts and dates are synthetic. This is a reproducible software demonstration, with no real taxpayer, customer outcome, auction purchase or external delivery.
Annotated screenshot walkthrough
This silent 36-second video presents two genuine product screenshots with explanatory captions. It is a still-image walkthrough, not a continuous recording or replay of actions.
Read the complete video transcript
0–9 seconds: Annotated screenshot walkthrough using two actual local product captures. DEMO-PUBLIC-FL-001 is fictional. No real parcel, taxpayer or purchase is represented.
9–18 seconds: Overview shows freshness unavailable, unknown auction status and no linked lien. Awarded records a manually entered fictional scenario, not verified ownership.
18–27 seconds: Acquisition shows Awarded, Action Required and Missing documentation. The illustrated awarded rate is 8 and total winning amount is 850 USD.
27–36 seconds: Asset type is Unknown; determination is Manual Review; requirements remain open. No certificate instrument, legal verification or external delivery is demonstrated.
Follow the input and output
- Save source provenance. The product saves an explicitly fictional source reference, capture time and certificate identity. The example.test address is a placeholder, not a retrieved county record. No county scraping or AI analysis ran.
- Record manual bid assumptions. The scenario uses an 18% starting rate, 8% floor and $850 exposure cap. These are illustrative inputs, not verified auction terms or expected returns. The native generic CSV is a review file; RealAuction upload-ready bid sheets are unsupported in this version. Its bid amount is blank for this interest-rate strategy; the saved matter JSON retains the rate assumptions.
- Inspect an acquisition and certificate record. A manually entered fictional win creates an Awarded acquisition with retained source fields, open requirements and missing documentation. A separate supported import accepts the same fictional certificate into the owned portfolio. That import does not automatically link ownership back to this awarded matter. Neither action verifies a real purchase.
- Keep deadline evidence distinct from entered dates. The product saves a September 8, 2026 manual review date and a source reference. An illustrative September 1, 2028 redemption date is also entered during import. Neither date is a statutory calculation or verified deadline. Acquisition requirements without evidence retain unknown due dates.
- Retain a review note and inspect the native outputs. The evidence API retains a manual operator note with metadata, a content hash, access policy and retention date. Its native JSON response and timeline CSV expose the record. The ZIP combines 20 captured API responses, inputs and provenance in a manually assembled handoff sample; it is not a one-click product ZIP export.
Download the actual outputs
- Complete controlled demonstration packet (ZIP)
- Native bid review CSV
- Native evidence-pack JSON
- Native evidence timeline CSV
Inspect dates, requests and response hashes · Inspect synthetic-data provenance and rights
What this demonstration leaves open
No official certificate instrument, verified deadline source, attorney approval, delivery receipt or legal conclusion is supplied. The pack remains open with no recorded exports, and its evidence checklist remains incomplete. Some checklist identifiers differ from the local evidence-type registry; this sample makes no completeness claim. Inline note metadata is returned in the JSON; it is not a signed object-storage download. Instrument storage and external drafting/signature services were not configured or exercised. The import also warns that an owner name is missing for notices and attorney packets. Nothing was sent to counsel or filed.
For real source research, begin with the Broward source guide or the Florida resource guide. Explore Accrella’s software workflow and start your workspace.
01
What the product supports
The evidence workflow supports a shared review record. The completeness of that record still depends on the documents collected and the actions recorded.
Pack and item organization
Create an evidence pack and append supporting items. The acquisition view can show retained evidence associated with a matter, giving the reviewer a place to inspect the file.
Controlled access
Evidence operations are scoped to authorized fund access. Document-access requests record the actor and purpose before issuing a time-limited access link.
Export records
Record an evidence export against its pack so the handoff has a corresponding record. Check that the receiving reviewer has the relevant documents and context.
02
A practical pack checklist
Use this as a completeness checklist, not a claim that every item is collected automatically.
Original acquisition source
Include the official list or source reference, parcel and certificate identifiers, sale date, and relevant receipt if the position was acquired.
Research and decision
Include the diligence inputs, open issues and bid assumptions that explain the decision. Keep the original evidence alongside any generated summary.
Later documents
Add relevant correspondence and subsequent documents as the matter develops. Check which facts have changed and what needs further review rather than treating the first pack as final.
03
Worked example: a reviewer questions the bid
Illustrative workflow; no investor result or completed transaction is implied.
Locate the source
The reviewer matches the certificate identifier to the source document and confirms it refers to the intended sale.
Inspect the assumptions
The reviewer checks the diligence inputs and proposed bid against unresolved issues. Missing evidence is flagged for follow-up.
Record the handoff
The team gives an authorized reviewer access to supporting items and records the export where appropriate. It verifies that the file contains what the review actually requires.
FAQ
Frequently asked questions
Answers to common questions about the workflow and what to verify before using it.
Does an evidence pack certify a clean title?
No. It organizes supporting information. Title and legal questions still require the appropriate research and professional review.
Are evidence packs automatically complete?
No. A pack can contain only the records that have been collected or added. Check required items, source dates and unresolved questions before a handoff.
Who can access the documents?
Evidence operations require authorized access to the relevant fund. Item access uses a time-limited link and records the actor and purpose of the request.
Product information is not investment, legal or tax advice. Confirm current county requirements before acting. Software availability does not establish current inventory or auction readiness.