BP-SCOPE-01
GuidedSupported jurisdiction only
The workflow starts by selecting a configured lane instead of claiming all-state coverage.
Published quality checks
This page documents the controls the product is designed around. Some are automated, some are guided prompts, and some remain explicit user-review steps before filing.
Automated checks
Guided checks
User-review checks
BP-SCOPE-01
GuidedThe workflow starts by selecting a configured lane instead of claiming all-state coverage.
BP-SCOPE-02
GuidedMulti-location, multi-county, and multi-jurisdiction filings are stopped.
BP-SCOPE-03
GuidedThe user confirms the packet is for ordinary owned business assets before continuing.
BP-SCOPE-04
GuidedThe product asks whether assets were in the jurisdiction on the relevant January 1 snapshot.
BP-SCOPE-05
GuidedAppeals, disputes, and corrected assessments are outside scope.
BP-SCOPE-06
GuidedExemption claims are stopped or routed to official forms.
BP-TX-01
GuidedThe Texas packet is framed around the official business personal property rendition lane.
BP-TX-02
GuidedThe output reminds the user that filing happens with the applicable local appraisal district.
BP-TX-03
GuidedThe asset register collects asset descriptions and categories for review.
BP-TX-04
GuidedThe workflow preserves original cost where the lane asks for cost history.
BP-TX-05
GuidedThe workflow captures purchase or acquisition year for the asset register.
BP-TX-06
GuidedUser-entered values remain user-reviewed and are not an appraisal opinion.
BP-FAIRFAX-01
GuidedSupported Fairfax categories are kept narrow and visible.
BP-FAIRFAX-02
GuidedComputer equipment uses the supported county category context.
BP-FAIRFAX-03
GuidedThe workflow asks for original capitalized cost rather than inventing a value.
BP-FAIRFAX-04
GuidedThe purchase year is collected for county depreciation schedule context.
BP-FAIRFAX-05
GuidedVehicle-only cases and personal property relief questions are not merged into the packet.
BP-FAIRFAX-06
GuidedThe final packet keeps the official county filing channel visible.
BP-MULT-01
GuidedThe Multnomah lane is limited to simple renewal-style cases with an existing account context.
BP-MULT-02
GuidedOwner real market value is user-supplied or user-confirmed, not determined by the product.
BP-MULT-03
GuidedThe product warns that CPPR schedules require user review before filing.
BP-MULT-04
GuidedLeasing company workflows are outside the simple lane.
BP-MULT-05
GuidedIndustrial manufacturing and special property return paths are stopped.
BP-MULT-06
GuidedLate penalty information is shown as official-source context, not as a tax bill.
BP-VALUATION-01
User reviewThe output does not claim to determine official market value.
BP-VALUATION-02
User reviewValues entered by the user remain visible for review rather than hidden behind a score.
BP-VALUATION-03
User reviewThe packet emphasizes source records for cost, acquisition year, and asset descriptions.
BP-VALUATION-04
User reviewAssets may still need review even when they are fully depreciated for federal books.
BP-VALUATION-05
User reviewLeased, consigned, fiduciary, and property-owned-by-others cases are outside the simple lane.
BP-VALUATION-06
User reviewIndustrial, utility, railroad, pipeline, oil and gas, aircraft, watercraft, and similar classes are excluded.
BP-OUTPUT-01
User reviewThe output is a draft packet for the owner to review before using an official channel.
BP-OUTPUT-02
User reviewThe product does not sign or submit the return.
BP-OUTPUT-03
User reviewThe packet points back to the local authority for submission.
BP-OUTPUT-04
User reviewThe product leaves a reusable asset-register passport for the next filing year.
BP-OUTPUT-05
User reviewHard stops and review warnings are kept in the packet posture.
BP-OUTPUT-06
User reviewThe output is not presented as an official assessment, bill, or receipt.
BP-PRIV-01
GuidedThe user can prepare the local draft workflow without creating an account.
BP-PRIV-02
GuidedAsset drafts are designed to live in browser storage by default.
BP-PRIV-03
GuidedLocal authority portal credentials are not collected.
BP-PRIV-04
GuidedThe MVP avoids storing signed returns, government credentials, and bank details.
BP-PRIV-05
GuidedThe product fee is separated from government or local tax payments.
BP-PRIV-06
GuidedSupport stays with workflow and source explanation, not appraisal, appeal, or exemption advice.
BP-BOUNDARY-01
User reviewThe product does not determine official market value or produce an appraisal opinion.
BP-BOUNDARY-02
User reviewAppeal strategy, assessment disputes, and corrected assessment cases are outside the product.
BP-BOUNDARY-03
User reviewExemption claims are routed to official forms or professional review.
BP-BOUNDARY-04
User reviewUnclear situs or allocation questions stop the simple packet lane.
BP-BOUNDARY-05
User reviewThe product does not contact assessors, appraisal districts, or counties for the user.
BP-BOUNDARY-06
User reviewThe product routes valuation, exemption, appeal, and special-property cases out.
BP-SOURCE-01
GuidedThe homepage and guides expose official local sources used for the MVP.
BP-SOURCE-02
GuidedSource notes include the review date used for the current product copy.
BP-SOURCE-03
GuidedGuide structured data cites the official source URLs behind the article.
BP-SOURCE-04
GuidedThe public About page identifies the publisher and the self-preparation operating pattern.
BP-SOURCE-05
GuidedThe published checks page is linked in navigation and sitemap.
BP-SOURCE-06
GuidedGuide and authority pages expose a named author profile in JSON-LD.
BP-CONSENT-01
User reviewThe price is presented as a software fee, not a local tax payment.
BP-CONSENT-02
User reviewLocal property taxes, penalties, interest, and authority fees are not collected by the product.
BP-CONSENT-03
User reviewThe checkout flow keeps the self-help software boundary visible.
BP-CONSENT-04
User reviewThe product does not promise acceptance by any local authority.
BP-CONSENT-05
User reviewThe product does not promise a lower assessment, lower bill, or appeal result.
BP-CONSENT-06
User reviewThe user remains responsible for reviewing every output before filing.