What Alembic will not decide, and why that holds

Most document software is sold on the list of things it can do. This is about the other list. Alembic will not tell you which amendment controls, whether an invoice is payable, whether a subcontractor's waiver is sufficient, or whether a vendor's security evidence is good enough. None of those are gaps in the roadmap. They are the design, and if you are the person whose name goes on the decision, that list matters more than the first one.

The reading was never the part that needed authority

Two things happen in a document review, and only one of them requires standing. The first is preparation: finding the term, pulling the number, lining the amendment up against the rent roll, checking that the line items add to the subtotal, noticing that the certificate expired in March. The second is the decision — what the term means, whether the difference is material, whether money moves.

Preparation is repetitive, slow, and largely mechanical, which is exactly why it is worth handing to software. The decision is none of those things. It is the moment your role stops being decorative. Software that quietly absorbs it has not saved you an afternoon; it has moved a liability from a person who can explain themselves to a system that cannot.

The failure mode is rarely dramatic. Nobody ships a product that announces it is approving invoices on your behalf. What ships is a green tick, a percentage, a status reading verified, and a queue that gets shorter because records left it rather than because anyone looked at them. Six weeks later somebody asks who decided, and the honest answer is that nothing did.

Four industries, four lists that stay yours

The boundary is not a slogan. It is enumerated, workflow by workflow, and it is published on the page for each one.

Commercial real estate. Alembic reads the whole packet — master lease, amendments, estoppels, notices, rent roll — and files each term against its property and tenant. It does not decide which amendment controls, whether a discrepancy is material, how a charge should be treated for accounting, or whether counsel and the counterparty need to be involved. When the rent roll says the expansion started July 1 and the signed amendment says August 1, you get both, with both pages, and the conflict stays a conflict until a lease, legal, or accounting role settles it.

Accounting and accounts payable. Header fields and every line item come back structured, the arithmetic gets checked, and the purchase order and receiving report arrive as context. Alembic does not match or pay invoices, and it does not approve payment. Accounting and tax treatment, coding, discrepancy handling, evidence sufficiency, and bank-detail verification stay with finance. The controller starts the day on the records that need judgment. The controller still makes every one of those calls.

Construction and contracting. The binder assembles as the pieces land: schedule of values, approved change orders, the conditional waiver, the insurance certificate, the field tickets. Alembic does not decide contractual entitlement or pricing, percent complete, waiver and evidence sufficiency, statutory compliance, or payment release. A complete packet is not an approved packet, and the product is careful never to let those two words blur.

SaaS contracts and vendor operations. One packet, four review lanes. Parties, term, renewal notice, liability cap, privacy roles, insurance dates, and tax identity are prepared once, instead of four teams reading the same PDF in four systems. Alembic does not interpret contracts, accept residual risk, approve vendors, or authenticate banking instructions. When the MSA requires sixty days of renewal notice and the order form says thirty, it shows you both and names the conflict rather than quietly preferring one.

What arrives instead of a verdict

Refusing to decide is only useful when the refusal comes with the work already done. A tool that merely shrugs is not principled; it is unfinished. So this is what shows up in place of a verdict:

• The extracted value and its source page, one click apart, wherever a reliable source match exists.
• Configured checks — arithmetic, required documents, dates, whatever your review actually runs — with the exceptions named rather than counted.
• Conflicts kept as conflicts, both sources attached, until a person settles them.
• Missing documents shown as missing. An expired certificate never quietly becomes a current one.
• An owner and a next action on every open item, so nothing ages out in silence.

And no score. There is no percentage to interpret, no threshold to tune, no number that means one thing on invoices and something else on leases. Every value is prepared, open, or decided by someone with a name. If you have ever had to explain to an auditor what a particular decimal meant on a particular Tuesday, you already understand why we do not print one.

Refusing is the harder build

It would be considerably easier to ship a product that decides. Every shortcut that gets you there also demos beautifully. An uncertain value can be filled with the most plausible reading. An untraceable number can be paired with a nearby page that looks close enough. Two conflicting documents can be reconciled by preferring the newer one. A missing certificate can be inferred from the fact that one existed last year. Each of those makes the screen calmer and the record less true, and the gap only surfaces when somebody relies on it.

Alembic goes the other way on purpose. Where a value traces back to a page, that page opens beside it. Where it does not, the record says so. Uncertain, missing, and conflicting values keep that state all the way through review — they are never smoothed into an answer that only looks finished. A value that cannot be traced stays uncited, because Alembic will not manufacture a source relationship to make a record look clean.

Approving a record never buries what is still open. That is a deliberate separation, and it is the one people find surprising. A document can be approved and still carry open questions, because those are two different facts about it. Folding them together is how a queue gets to zero without anyone having resolved anything.

You draw the line, not us

The vocabulary is yours. Teams configure the outcome language their review actually uses — the words on the record are your words, not a fixed opinion we shipped about what approved means at your company. What does not change is where authority sits: Alembic prepares the record and keeps unresolved work visible, and the people your organization authorized make the consequential decisions.

None of this makes the work slower. It makes the list shorter and the remaining items honest. The afternoon you get back is the reconciling — the page references, the notice addresses, the margin notes from someone who has since left, the third pass through a receiving report to work out whether five units or six turned up. What stays is the part you were hired for.

If you want to see where the line falls in your own workflow, each industry page publishes its retained decisions and its limitations in plain sight — commercial real estate, accounting and AP, construction, and SaaS contracts and vendor operations. The argument behind all four is on Why Alembic.