How it works
Four steps, and then it keeps running.
Setting up takes an evening. After that the work is answering requests and dropping in documents as they arrive.
- 1
Profile the entity
Tell us what the company is: LLC, C-Corp, S-Corp, when it was incorporated, who owns it and where they live, what it is registered for. You can answer in your own words, or hand over the incorporation pack and let PortalHQ read the facts out of it for you to confirm.
- 2
Derive the calendar
Those facts drive a versioned rule set maintained by practising professionals. Out comes every obligation the entity actually carries — annual, event-driven, and the conditional ones most tools miss — each with an owner, a due date, and a definition of what evidence closes it.
- 3
Collect the evidence
Drop in documents as they happen. Each one is read, named to a consistent convention, filed into the taxonomy, and matched to the obligation it belongs to. Your professional asks for what is missing as a checklist, not as a paragraph in a chat.
- 4
Close the loop
When the acknowledgement lands, the obligation closes and the seal appears against it. Until then it stays open and keeps saying so — and where the rules charge by the day for delay, what the waiting is costing.
What “done” means here
Submitted is not filed. Filed is not proved.
Most tools stop at a reminder or a folder. PortalHQ tracks a document all the way to its receipt, because the receipt is the only thing that helps you a year later when someone asks.
- Draft
- Executed
- Filed
- Acknowledged
Bring your last two years of filings.
The gaps show up quickly, and they are usually not the ones people expect.
Get startedPlain answers
Questions people ask before they start
- How does setup start?
- You profile the entity: what it is (Limited Liability Company, C Corporation and S Corporation), when it was incorporated, who owns it and what it is registered for. You can answer in your own words or hand over the incorporation pack and confirm the facts PortalHQ reads out of it.
- Where does the compliance calendar come from?
- Obligations are derived from a versioned rule pack for the United States against the facts recorded on the entity. The derivation fails closed: a fact that is not answered makes the rule not apply, so the calendar names the unanswered questions rather than inventing work.
- How is an obligation closed?
- By attaching the acknowledgement that proves it was filed. A document used as evidence must exist, belong to that engagement and be available; attaching it seals it so it cannot be deleted afterwards.
- What happens after setup?
- The work is answering requests and dropping in documents as they arrive. Re-deriving obligations adds what is newly applicable and duplicates nothing.