FAQ
Questions about Brikt, answered.
The ones that come up before anybody books anything — about what the AI can and cannot do, what your data is used for, and what this costs the people you invite.
Answers
What people ask before they book a demo.
Can Claude change my schedule without me knowing?
No — and not because of a setting somebody could turn off. Claude drafts; a person applies. Every AI-authored change arrives as a proposal you review on the real grid, and applying it is a deliberate act that is logged and attributed to you.
The claude.ai connector works the same way. It exposes reading and drafting, and there is no apply on the other side of it at all: absent rather than disabled.
Is my project data used to train AI models?
Anthropic's commercial terms do not permit content submitted through their API to be used to train their models, and we do not use your project content to train models of our own.
Can I import my existing schedule?
You can bring a Microsoft Project XML file. Claude reads it and drafts it back to you as a proposal — the same review surface as any other change — so nothing writes straight into your project and there is no bulk load that leaves you guessing at what it did.
A file Brikt cannot read is refused with a clear message rather than half-imported. That is the whole of what exists today, and we would rather say so than promise a format we cannot read yet.
What do external collaborators pay?
Nothing. That is the pricing model rather than an introductory offer.
Pay only for your company's team. Every subcontractor, owner, and architect you invite is unlimited and free.
Which company holds the subscription and which people are external collaborators is decided per project, not by company type — an owner can hold the subscription with the general contractor invited as an external. The free claim attaches to the relationship, never to a kind of company.
What can someone I invite actually do?
Invited collaborators work from the real schedule — dates, float, the critical path — while your costs, internal notes, and baseline comparisons stay yours.
Everyone you invite can comment on an activity and post an update on a blocker, from the day they accept. What they can change in the schedule itself is decided by the project role you give them: a collaborator you make a project admin updates progress and edits the plan directly, the same as somebody on your own team. Everyone else adds to the record — comments and blocker updates — without moving a date.
They sign in as themselves, so nothing arrives anonymously — every change carries a name, a time, and the door it came through.
Does Brikt replace my scheduler?
No. It makes the schedule legible to everyone who has to work from it, and it drafts for review.
Somebody still has to own the logic, decide what the plan actually is, and judge whether a draft is any good. Brikt gives that person a faster way to work, and gives everyone else a way to read what they produced without being trained on scheduling software first.
Who is Brikt for, and who is it not for?
Owners, developers, designers, consultants and builders running capital projects. Brikt is built for two audiences at once — the person who owns the schedule, and the many more who have to work from one without being trained on scheduling software first.
It is not a fit if you plan in hours or shifts, if you want software to spread crews across a schedule and rebalance them for you, or if you need the schedule to carry the money as well as the dates: Brikt plans in whole working days, attaching a resource never moves a date, and it does not price the work.
Can I schedule in hours, or half-days?
No. Brikt plans in whole working days: a day is a day, and how long a day is comes from the calendar you assigned rather than from a fixed number of hours. Type 0.5d and it refuses with a reason instead of rounding quietly, and there is no hours unit to type at all.
The exception is genuine calendar-time waiting — a cure, a delivery lead, a permit sitting on somebody's desk. Elapsed durations take fractions, because that is time passing rather than work being done.
Can I put crews and equipment on activities?
Yes. Brikt keeps a resource library — crews, people and equipment, held for one project or shared across your company — and you attach them to activities so the plan says who is doing the work.
What it does not do matters as much: attaching a resource never moves a date, and Brikt will not spread crews across the schedule or rebalance them to smooth out manpower. The sequence stays yours, and no rates or costs ride along with the assignment.
What does percent complete mean in Brikt?
You tell Brikt how much time is left, not a percentage, and the percent you see is derived from it — duration percent complete, a percent of the planned time rather than of the work in place.
The column is called % Complete, and what it measures is duration percent complete — a percent of the planned time, not of the work in place. A slab with four of its ten planned days left reads 60%: a statement about the days left, not about how much of the slab is poured. It is a scheduling number, not one for a payment application.
Can I get my data out?
Yes, and without asking us. Copy cells straight into Excel, and paste back the other way. The Export button downloads the grid as you are looking at it — the filters, the grouping and the sort you have on — as a CSV rather than as a picture of a screen.
Reports come out as PDFs: the lookahead, the owner report and the milestone report. A saved report can be sent as a link that opens without a Brikt login, and that you can revoke.
A collaborator's export carries only what they can see, because a field they are not entitled to never reached their browser in the first place.
What can you give my IT reviewer?
Mechanisms rather than badges: tenant isolation enforced by the database on every query, per-field conflict control, an AI that can draft but cannot apply, deny-by-default reads, authentication through WorkOS with encrypted revocable sessions, and an audit trail that records who changed what and through which door.
Brikt is a small operation and has no third-party audit report to hand you. What it has is a list of mechanisms your reviewer can put questions to in a demo and watch the answer, and a privacy policy that says the same thing without hedging.
How do I get started?
Book a demo and bring a job you are running now. A real schedule with a real problem on it is worth more than a walkthrough of a sample project, and it is the fastest way to find out whether this fits how you work.
Self-serve plans open soon. There is no permanent free tier: Brikt is paid for by the company that runs the schedule, and the people that company invites are free.
Still deciding? Bring us a real one.
The questions that matter tend to be about your job rather than about the software.